Extension:Semantic Maps/Future

Future work on Semantic 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. Note that development that affects both Maps and Semantic Maps is placed on the Maps future work page.

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

New features

 * Added a result format for the OL optimized for OSM service.


 * Add a form input for the OL optimized for OSM service.


 * Add support for the new Special:Ask page's parameter handling to the query printers.

Refactoring

 * Moved the geographical coordinate data type handling from SMW to SM.

Bug fixes

 * Fix issue with the form input registration. The main service names are getting changed into the default mapping service. Aliases work as they are supposed to.

New features

 * Ability to define custom overlays for OpenLayers

New features

 * General geocoding support for forms, with a geocervice parameter
 * Add GeoNames geocoding support for all mapping services

New proposals
An example of such usage would be to have a link to maps.google.com, where the user can immediately enter a second location, and then get a route, after clikcing the relevant link.
 * Some kind of build in way of linking to (external) pages with the coordinates (or other queried properties?) in marker po-ups. This can be done by querying something already containing the correct link, but this build in way is supposed to make it more easy. I see 2 ways to do this:
 * Hardcode some stuff, and have a parameter like link= that accepts a value indicating which of the hardcoded presets should be used.
 * Link the url's to some kind of 'magic words', that can be used in a label= parameter, like label=http://whatev.com/api?coords=__coordinates__, where __coordinates__ is the magic word.

-- Jeroen De Dauw 01:43, 9 November 2009 (UTC)