Extension:Maps/Future

Future work on Maps

Feel free to add new feature requests to the new proposals section. Please review the turned down proposals first. Adding your vote or objection to proposals will help determining which ones will get the priority. If you have any comments on the already accepted or turned down proposals, please add them to the talk page, but refer from adding them to the lists themselves.

Accepted to-do's
Items that have strikethrough have been completed/fixed.

New features

 * display_points and display_addresses parser functions. This will enable you to display multiple markers on one map, and will be particularly useful together with custom base layers in OpenLayers.


 * Aliasing system for map property parameters (like currently the hard-coded center which changes into centre)


 * Separate title and label values for each marker


 * Open Street Maps support for OpenLayers


 * Making the map type controls configurable for Google Maps and Yahoo! Maps

Refactoring

 * Create hook system for the mapping services.


 * Base class that bundles common functionality from MapsBaseMap and SMFormInput.


 * Geocoder base class


 * Separate default parameter handling for each mapping service


 * CURL requests in the geocoder classes (to avoid security issues)

Bug fixes

 * Extension description is not showing up in 0.2.1 & 0.2.2.


 * Bing maps (for open layers) is not working

New features

 * Ability to define custom base layers (with images) for OpenLayers. example, example


 * Bing Maps (formerly called Virtual Earth) support


 * Mapstraction support


 * Display_route parser function, to auto generate routes


 * KML support for Google Earth


 * KML support for Open Layers


 * Google Maps moon/mars/skye support (2D)


 * Google Earth moon/mars/skye support (3D)


 * Street view support for Google Maps


 * Multi geocoder support: creation of a hook-like system that allows to easily add new geocoders to the extension


 * Geocoding support for the centre parameter. Automatically detect if the provided value are coordinates, and if not, attempt to geocode.

New proposals

 * Add some kind of custom route tool, like done by the Google Maps extension? vid - Jeroen De Dauw 01:30, 22 July 2009 (UTC)


 * Add based syntaxis for the parser functions - Jeroen De Dauw 22:48, 23 July 2009 (UTC)


 * General zoom level system: one zoom level scale for all services. This would make it easier for users to get the hang of the zoom levels, and would not affect the zoom when changing the service parameter. However, this would not allow backward compatibility, by affecting the zoom of all maps using one of the current zoom scales. Even if this is a good idea, there needs to be voted for the scale system to use. - Jeroen De Dauw 01:43, 24 July 2009 (UTC)


 * Add support for optional Directions controls (From here - To here) or any parameter to facilitate generating directions to or from a location on the map. Directions could be generated in a new view, not necessarily on the embedded map, although that would be a nice addition. - Laurent Alquier 11:50, 03 August 2009

Bugs

 * Scrolling up and down the page with the arrow keys also scrolls the map, for Yahoo! Maps (it doesn't do this for Google Maps or OpenLayers).

- Yaron

This is not really a bug I guess, just part of the Yahoo! API. I you set autoszoom=off, the hotkey stuff will also be disabled. I'm going to have a look if scroll wheel zoom and key controls can be set individually for 0.3 though.

- Jeroen De Dauw 18:02, 31 July 2009 (UTC)