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

 * Backwards compatibility by using the $wgGoogleMapsKey when this one is set and $egGoogleMapsKey isn't.


 * Hook for Admin Links


 * A true aliasing system for service names


 * Centre parameter, that will allow you to set a custom map centre (different from the place where the marker will be put)


 * Multi geocoder support: creation of a system that allows to easilly add new geocoders to the extension, and allows the user to set a default one in the settings file, and also add a parameter for this selection to the geocoding functions


 * Yahoo! geocoder


 * Open Street Maps support for OpenLayers

Refactoring

 * Refactor MapsBaseMap and all it's child classes (a lot of common code can be moved up, and the overall structure can be improved).


 * Major rewrite of the Google Maps and Yahoo! Maps code. The parser function classes should only print a call to a JS function with all needed parameters, which then does all the logic and creates the map.

Bug fixes

 * Issue causing aliases for service names getting turned into the default service since they are not in the allowed services list

New features

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


 * Bing Maps (formerly called Virtual Earth) support


 * Popups for the markers: adding of a markertext(?) parameter to allow the user to display some text in the popup


 * Display_route parser function, to auto generate routes


 * KML support for Google Earth


 * KML support for Open Layers


 * Adding 'physical' to the map type control when this map type is enabled for Google Maps


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


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


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

New proposals

 * Add an display_points (and display_addresses) parser function(s). This would enable you to display multiple markers on one map, and would be particularly useful together with custom base layers in OpenLayers. - Jeroen De Dauw 22:48, 23 July 2009 (UTC)


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


 * Change the OpenLayers control handling. Make it accept all controls (by using eval in the JS) - this will make the values case sensitive and more error prone though. Good idea or not? - Jeroen De Dauw 23:25, 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)