Wikimedia Maps/2015-2017

OpenStreetMap and Wikimedia are collaborating at multiple levels, many times thanks to individual efforts of volunteers, sometimes through formal projects involving the Wikimedia Foundation or chapters.

Let's map this collaboration. Every entry should have a wiki page, a bug report or a URL somewhere.

Use cases

 * An editor wants to easily add a map to a Wikipedia article without leaving the Wikipedia site.
 * A reader wants to zoom and pan a map in a Wikipedia article.
 * A reader wants to see a zoomable, pannable map immediately when they click geo-coordinates on an article.
 * An editor wants to add geographic information about the location where they currently are.
 * A reader wants to navigate articles with an atlas (instead of typing a page name or URL, zoom and pan a map, and click pins)
 * A reader wants to browse Wikimedia Commons images on a map.
 * A reader wants to visualize geospatial data (country and city outlines, river courses, habitats for animals etc.)
 * An article shows interactive historical maps for certain areas. The map can contain annotation layers, POIs, routes, data layers etc. to illustrate the article topic. An editor wants to create these maps. (Taking part: Susannaanas (talk))
 * A historical map file can be displayed overlaid on a slippy map in the file display (file page / media viewer). Wikimaps design doc. (Taking part: Susannaanas (talk))
 * A reader/Commons user/editor wants to find scanned maps by selecting the area on a slippy map. Wikimaps design doc. (Taking part: Susannaanas (talk))
 * A reader can explore complex shapes (highways, geographic borders etc.) inside the infoboxes much better by using a slippymap than a static image. (need support for: kml, geoJSON, topoJSON)
 * An editor wants to add and edit maps using VisualEditor. We already have some proof of concept code so we just need some API endpoints. ESanders (WMF)
 * User Mey2008's WikiVoyage dynamic maps, such as POI Map, Art Map, and Monument Map (RU).

Mobile app use cases

 * User is able to see the map of the nearby points of interests from the mobile app
 * User is able to explore points of interest next to the current article
 * User is able to view articles similar to the current one on the map (based on Wikidata class)

Ongoing projects

 * Kartotherian - Vector tile server in development - Demo Server (or without varnish caching)
 * Create a high-capacity OSM cluster for Wikimedia projects use
 * Set up vector tiles rendering.
 * http://a.tiles.wmflabs.org/osm/slippymap.html
 * Bug 33980 - (tileserver-prod) Wikimedia-hosted OpenStreetMap (OSM) / mapnik tileservers wanted for mobile usage.
 * Wikimaps & OpenHistoricalMap
 * WikiMiniAtlas deployed on major Wikipedias for years now, supporting over 50 languages.

Implementation

 * Tile Server Implementation

Key Performance Indicators
We all know maps are important part of the knowledge eco-system, but to better serve the community, we should invest our efforts into addressing the maps use cases that are more used than others. In order to find such use cases, here are some key performance indicators we should track.
 * Overall map usage
 * How many people viewed any map
 * What percentage interacted with them (clicks, drags)
 * Percentage of each tile service used
 * Switch-overs if possible
 * Discovery contributions
 * How many new articles were viewed due to the map

Wishlist

 * Proposed Bot to add Wikipedia/Wikidata tags to OSM features.
 * Local and regional bridges between both projects in order to collaborate in activities and events.
 * Wikimedia CH plans.
 * Log in to OSM with Wikimedia credentials.
 * Clarify licensing situation of OSM data used in Wikimedia.
 * Open-Wikidata-map.
 * A page to jot down use cases for historical maps and geodata (Susannaanas)