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

 * Full support for both directional and non-directional coordinate notations in DMS, DD, DM and float notation.


 * Rewritten #geocode parser function that has named parameters, has build in smart geocoding, can take in coordinates in all supported notations, and can also output them in any of these.

Refactoring

 * Update the OpenLayers version from 2.8 to 2.9, assuming it's out by then.


 * Mayor clean up of the coordinate handling, mainly to facilitate better integration by the GeoCoords data type in Semantic Maps.


 * Use native MW hook system for mapping services and features if possible.

Bug fixes

 * Add mapping to the language codes that are send to the Google Maps API to null the naming differences between MW and the API.

New features

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


 * Overlay definition for OpenLayers. example

New features

 * Display_route parser function, to auto generate routes


 * Functionality similar to Tetherless Map (list of points next to maps). Example.


 * Bing Maps (formerly called Virtual Earth) support


 * Mapstraction support


 * KML support for Google Earth


 * KML support for Open Layers


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


 * Street view support for Google Maps (code from the street view widget by Sergey can probably be reused)


 * Allow for complex wiki-text in the title and label parameters, such as being able to specify parameters for an image. This is now not possible cause Maps can not determine if a parameter separator (|) is coming from one of it's parser function, or a nested one.


 * Client side marker grouping. Example. Article.


 * Option to force show a marker pop-up once the map loaded.

Bug fixes

 * Fix issues with UK postcode support.


 * Strange behavior with the Bing Maps base layer in OpenLayers - when it's the default layer, it shows points in the wrong place, and when it's not, it doesn't show anything when selected - see the last two maps here. -Yaron


 * Fix issue causing the pan and drag around functionality on Yahoo! Maps maps not to work for some wiki installations.


 * Marker popups in Yahoo! Maps show up with a white background under them (probably a CSS issue) -Yaron


 * Fix issue with language codes for Google Maps. The language codes used by MW aare different from those expected by GMaps in some cases.

Turned down proposals

 * 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)

The Yahoo! API does not allow turning that off/on separately from the scroll wheel zoom. So that issue can't be fixed.

- Jeroen De Dauw 23:14, 20 August 2009 (UTC)

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

Can you provided a link to an example?

-Jeroen De Dauw 20:36, 9 August 2009 (UTC)

Did you mean something similar to this?

-Jeroen De Dauw 21:55, 9 August 2009 (UTC)

How about having custom marker icons? Also having a flexible width?

--Jhoogy 04:44, 26 October 2009 (UTC)

Maps already allows custom marker icons. A flexible size for the map might be neat to have, but won't be done by me any time soon.

--Jeroen De Dauw 08:43, 27 October 2009 (UTC)

in principle it should be possible (http://code.google.com/apis/maps/documentation/staticmaps/)
 * static map for google maps like already implemented for OSM. Do you plan to add this feature?

--Tkrueger73 20:52, 20 February 2010 (UTC)

Hey,

I've already given that some thought, and agree it would be cool to have. There are several things, like image-as-layer functionality that do take priority though. So don't expect this to show up any time soon.

Do you need it somewhere?

Cheers

-- Jeroen De Dauw 03:13, 21 February 2010 (UTC)

The problem with the dynamic maps is, that the export as pdf or book is not working correctly. I hope that this would work with the static maps. It would be great if it would be possible to export the pages of my harbour wiki (http://www.bluewater-info.net/wiki_/Main_Page) as pdf /book.

best regards,

--Tkrueger73 18:49, 21 February 2010 (UTC)

Hey,

I see your point, and will hold it into account for prioritizing all the Maps to-do's. Of course, if you can, or can find someone, who can fund the dev for this, it could be done a lot sooner.

Cheers

-- Jeroen De Dauw 16:02, 22 February 2010 (UTC)

Bugs
The base maximum zoom was set to 14 by default, which is not high enough for me for the maps that are there. I had to change the code so that I can have higher zoom. Is there's a reason that the max zoom was set at 14? If not, then the code should be changed to allow the maximum zoom actually allowed by the maps.

67.170.217.247 20:46, 23 January 2010 (UTC)


 * This has been fixed in 0.5.2 :)


 * Cheers --Jeroen De Dauw 08:41, 6 February 2010 (UTC)