Extension:Kartographer/Future

There is a VERY long backlog of potential maps work. Kartographer Kartotherian etc.

Maps is mostly in a 'maintenance' mode however and that comes with severe restrictions of what is actually feasible to do at this moment in time. Anything that requires a lot of testing and verification, like changes to the style of the map, changing the tileserver itself, or the features it provides are largely impossible to achieve. However there are also a LOT of things that are possible to do especially for volunteers. Below I detail some steps that we can and likely should be working on.


 * Convert Kartographer to make use of Leaflet instead of (deprecated) Mapbox.js T187582
 * Make sure that we use reuseable modules (that are maintained) for things like layers, nearby, simplestyle etc.
 * Upgrade the maki icons from 0.5 to 6.2 on both server and client
 * Introduce a GeoData api action that exports coordinates for a page as KML/GPX/GeoJSON etc.. (use api raw mode that TimedText uses as well).
 * Convert en.wp en:Template:coord function to Kartographer
 * Make external maps sidebar configurable per server or region dependant.
 * WikiVoyage depends on wmflabs for nearby locations... can we use GeoData database instead T244691
 * Show a location on the map in Commons MediaInfo object.
 * Expand Extension:NearBy with a map view using our leaflet
 * Fix preview on 2nd live preview T151524
 * Add a 'show my location on map' option T208713
 * Add Wikidata support to geosearch api T35704
 * Create a leaflet module to use mediawiki geosearch api
 * This will also help fix many of the nearby layer issues of wikivoyage T190069
 * Define a long term idea about marker symbol api
 * Consider making graphs shareable and embeddable using iframes on 3rd party sites.
 * Fix chaining of external data (wikidata query on Commons map)