Talk:Wikimedia Maps

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. (T105090 -- seems to be ok)
 * Open-Wikidata-map.
 * A page to jot down use cases for historical maps and geodata (Susannaanas)
 * It would be awesome if it's possible to make an interactive map with all the changes in Wikipedia. --CortexA9 (talk) 17:14, 18 September 2015 (UTC)
 * Hey CortexA9! Have you seen http://rcmap.hatnote.com/#en ? Trizek (WMF) (talk) 14:43, 21 September 2015 (UTC)


 * Using Wikimedia credentials on an external site would be best done by Wikimedia being an openid provider, or as a distant second option, supporting it in omniauth Pnorman (talk) 03:36, 25 September 2015 (UTC)

WM IT

 * I brought this to the attention of WM IT, which at some point will also become the Italian chapter for OSM, thanks to the efforts of User:Cortesi and others. HTH, --Elitre (WMF) (talk) 16:38, 26 August 2015 (UTC)

Controversial borders
Hi,

I noticed some controversial borders at https://maps.wikimedia.org :
 * The border between Crimea and Kherson is shown as international, which is the Russian Federation POV.
 * South Ossetia and Abkhazia are shown as countries, which is the Russian Federation POV.
 * The border of Kosovo looks like a border of an independent country (Kosovan POV), but it doesn't have a country name (weird POV ;) ).
 * As a technically opposite example, there's no border in the middle of Cyprus (Greek POV), but there is a label for the Turkish Republic of Northern Cyprus (Turkish POV).
 * The border between Israel and Syria is shown according to the Israeli POV.

There are possibly more issues of this kind.

Wikipedias usually show maps of disputed territories quite well. For example, maps of Russia and Ukraine usually show Crimea in a special color - even in the Russian Wikipedia.

I understand that at the moment Wikimedia's maps service probably just takes whatever OSM provides, but ideally it should do something similar to what the Wikipedias do and be as neutral as possible.

(I tried to be as neutral as I could in this post ;) ) --Amir E. Aharoni (talk) 19:39, 17 September 2015 (UTC)
 * There is no neutral way to display map borders. Not making a choice is inherently taking a side --Guerillero (talk) 01:10, 18 September 2015 (UTC)
 * Exactly - indicating a border is disputed is taking a point of view, just like representing a border as not disputed is. Countries often do not agree on if an area is disputed or not. Pnorman (talk) 08:17, 25 September 2015 (UTC)
 * No, indicating a border is disputed is showing there are multiple POVs that contradict each other. The alternate color explains this conflict, which is information that an independent medium like this should bring across. It isuseful that Amire80 put this under the attention and the solution of alternate colors is already a proven one so an ideal candidate as a solution. Lafeber (talk) 15:06, 3 May 2016 (UTC)
 * Thanks ! Filed as T113008. Indeed this does not look very NPOV. The data comes directly from OSM, so we should ultimately work with the OSM community to solve this (unless it is already present in the data with some extra flags that we should look at and draw accordingly). Also, if OSM community chooses to follow a different route, we might have to introduce a separate database of such cases and allow community to edit it. Obviously I would much rather have it fixed in OSM (if it is indeed broken there).  --Yurik (talk) 01:14, 18 September 2015 (UTC)
 * Thank you Yurik. Sounds sensible. --Amir E. Aharoni (talk) 08:19, 18 September 2015 (UTC)
 * OSM usually follows an "on the ground" POV about borders. Areas are not shown in the countries they "should" be or they rightfully belong -according to any given criteria- but they show which state de facto governs the territory. It's a simple approach that fits initial OSM goal -to provide road maps to travel using a GPS- but it couldn't be the better approach for an encyclopedia.--Pere prlpz (talk) 18:48, 21 September 2015 (UTC)
 * The OSMF policy on disputed territories is best explained at http://wiki.osmfoundation.org/w/images/d/d8/DisputedTerritoriesInformation.pdf. Crimea is a bit of a unique case as it is mapped as being in both Ukraine and Russia, as per http://wiki.osmfoundation.org/wiki/Working_Group_Minutes/DWG_2014-06-05_Special_Crimea. Pnorman (talk) 08:17, 25 September 2015 (UTC)

How to submit patches?
It's a bit unclear from the page, but it looks like https://maps.wikimedia.org/ is run by kartotherian? I've whipped up a provisional patch for hi-dpi/retina display support T112952 but can't submit it via 'git review' as there's no .gitreview in the repo T112958. --Brion Vibber (WMF) (talk) 20:31, 17 September 2015 (UTC)
 * It's all in GitHub. Also, the index.html you're probably trying to edit is just an example, we're not intending it to ever be a full-featured map:) Max Semenik (talk) 20:35, 17 September 2015 (UTC)

Missing fonts
It seems the map server is missing some fonts to render characters of place names in what I think is Georgia: https://maps.wikimedia.org/#9/41.8297/44.2474 —Galaktos (talk) 21:39, 17 September 2015 (UTC)
 * Its a Unicode bug in Mapnik, tracked by T108846. --Yurik (talk) 21:52, 17 September 2015 (UTC)
 * Alright, thanks. —Galaktos (talk) 22:09, 17 September 2015 (UTC)
 * Other case here If you zoom out, the entire name of the city is shown. Sturm (talk) 11:00, 23 September 2015 (UTC)

Geopedia
(HTML 5 / mobile and desktop)

I developed a tool called Geopedia (http://www.geopedia.de), where I could add your map too. Currently I use leaflet and the DE open street map, as I use it primarly for travelling and wanted to have latin city names... I could also add your maps through a layer selection in the settings. Let me know what you think - also very open for further ideas and improvments..

KML
Will we be able to overlay KML layers onto the map? i.e. will we be able to include links in w:en:Template:Attached KML and w:en:Template:GeoGroup (and similar templates on other language wikipedias or other projects)? Current uses are, for example: - Evad37 (talk) 04:01, 22 September 2015 (UTC)
 * Interstate 96: Route map links at top-right of page, and in box at bottom of page, from
 * Circle line (London Underground): Map all coordinates links in box at bottom of page, from )


 * Overlaying a KML layer would generally be done by the map library, (e.g. leaflet), and there would be no problems doing so with these tiles. Pnorman (talk) 23:38, 24 September 2015 (UTC)

/style/z/x/y.png format doesn't work!
says
 * https://maps.wikimedia.org/{style}/{z}/{x}/{y}.{format}

but this doesn't work and returns 404 "Cannot GET /osm-intl/7/43.66/4.719.png ", e.g.
 * https://maps.wikimedia.org/osm-intl/7/43.66/4.719.png

If I go to maps.wikimedia.org and pan around, it only updates the URL fragment without any  or path at all, e.g.
 * https://maps.wikimedia.org/#7/43.66/4.719

?? -- SPage (WMF) (talk) 02:04, 23 September 2015 (UTC)


 * {z}, {x}, and {y} are the standard slippy map tilenames, not latitude and longitude. http://wiki.openstreetmap.org/wiki/Slippy_map_tilenames has more information, including example code for converting.
 * The page at https://maps.wikimedia.org/ is a preview page to display the map, not the map tiles themselves Pnorman (talk) 23:36, 24 September 2015 (UTC)
 * The page at https://maps.wikimedia.org/ is a preview page to display the map, not the map tiles themselves Pnorman (talk) 23:36, 24 September 2015 (UTC)

Isometric projection
When I went to last Wikimania I could talk to some WMF developers, specially to Yuri, about this question (during the OSM workshops), and sorry if this not the proper place to discuss / ask for it. But, here we go! ;) Despite the main OSM visualization, there is also a isometric projection (take a look here also) implemented by the OSM Buildings website. How difficult is to offer such visualization on Maps Wikimedia? Sturm (talk) 11:09, 23 September 2015 (UTC)
 * Another very interesting "3D OSM data converter" is the OSM2World, a converter that creates three-dimensional models of the world from OpenStreetMap data. It is published as open source (LGPL). Sturm (talk) 18:27, 29 September 2015 (UTC)

Marble KDE
I find that Marble, a virtual globe application (totally open source, years of development under KDE Educational programs) which allows the user to display many planets and satellites as a 3-D model, could be a great joint venture to the Maps Wikimedia project. They have a large list of public domain and CC maps applied to it, as you may see here and they also have an app running beta, take a look here. Sturm (talk) 11:20, 23 September 2015 (UTC)
 * During last Summer of Code (GSoC), they made significant improvements in OpenStreetMap vector rendering, for example. Sturm (talk) 11:23, 23 September 2015 (UTC)

Documentation
I know that Maps Wikimedia is still a very starting project, but it would be very useful to see some version informations, release dates, changelogs, roadmaps etc. It helps a lot to understand about the project and help it. Regards, Sturm (talk) 13:08, 23 September 2015 (UTC)

Style improvements
The map style is already nice for an basemap :-) I noticed some small issues that might be worth to get fixed: Maybe somebody can see if this makes sense --MyRobotron (talk) 16:18, 24 September 2015 (UTC)
 * Area highways missing https://maps.wikimedia.org/#18/54.08876/12.13958
 * Streetnames placement repitive https://maps.wikimedia.org/#17/54.07921/12.10772
 * Streetref placement repitive https://maps.wikimedia.org/#17/53.63696/11.41197
 * more landuse features for non-urban areas https://maps.wikimedia.org/#16/54.1178/12.0449
 * All styling issues are now in phabricator. --Yurik (talk) 17:46, 10 March 2016 (UTC)

Requested feedback
User Feedback for UK looking for details in. Using Firefox on Linux

1. Map opens on the wrong continent- not on the location of the last article I saved.

2. Zoom level 7- the town names given are weird. Liverpool- but not Manchester, Sunderland but not Newcastle-upon-Tyne which is a factor of 10 bigger

3. Zoom level 8- the town names seem to relate to cathedrals not centres of administration or population. Canterbury (55,000)but not Maidstone (113,137). Greenwich Bromley Ipswich all missing. But we have St Asaphs with a population of 3,355. (no that isn't a typo!)

4. Level 9. Names are truncated- Barnoldwick has become Barnoldswi moving south we have Whitworth|Whitwor, then Bollington|Bolling and Macclesfield|sfield. b 5 Level 12 appears OK but level 13 its back again. In level 13 we have a new set of names- that seem

6. The one thing we need from a map is the ability to place a cursor over a spot and see its lat/long geotag- like [.[Co-ord|53.7028|-2.3806|display= title, inline]] Then to copy this to the clip board with a right click- sadly this shows https://maps.wikimedia.org/osm-intl/10/504/329.png not 53.7028/-2.3806. Extracting this from the url doesn't help as there is no indication whether this centre, top left or what

7. How do I turn off selected layers?

8. How do I access the layer showing location of Wikipedia articles? ...commons images? ...wikidata?

I look forward to watching this project develop--ClemRutter (talk) 23:36, 25 September 2015 (UTC)

Project goals?
Longtime Wikipedian and OpenStreetMap contributor (and data reuser) here. It would be great to have a summary on this page about the actual project goals. Is it really just to produce another source of OSM-derived map tiles? Presumably there is some reason that OSM's own tiles, or another provider like MapBox or CartoDB could not be used - could this be explained? Is there something special that WMF wants to bring to the cartography? Novel sources of data? Different hosting requirements?

I'm probably not the only wondering why exactly WMF needs its own tile server, and how this helps "our knowledge engine ... to be powered by multiple entry points". Stevage (talk) 13:54, 27 September 2015 (UTC)


 * Stevage, I am not a member of the Discovery team, so I cannot speak on behalf of it, but I think the immediate needs were to integrate OSM easily with Wikimedia sites without creating a huge tax on OpenStreetMap servers. I do not know if that is the case anymore, but I remember at some point OSM administrators asking to ease the load from some Wikipedia functionality. Having our own tile and static image servers will allow, with enough resources, support both the huge traffic that Wikimedia sites have, and -at the same time-, not sending traffic from our users to 3rd party sites, some of them commercially driven and with privacy rules potentially not so strict than ours (anonymous, not sharing, short data rentention).
 * I know that there is a desire to also bring additional features not present on simple image tile servers (I heard about vector tiles). But you should ask about those directly to Yurik. But if it would only help to have an OSM map on every wikipedia page (not possible before), it will be positive for both Wikimedia content and OSM visibility. --JCrespo (WMF) (talk) 14:58, 27 September 2015 (UTC)
 * Regarding OSM's own tiles, see http://wiki.openstreetmap.org/wiki/Tile.openstreetmap.org/Usage_policy and https://switch2osm.org/using-tiles/ - they make it quite clear that they don't want people to use their tiles directly. - Nikki (talk) 15:45, 15 October 2015 (UTC)
 * The privacy policy is perhaps the most important reason, but also scaling and being able to do some of our own things like eventually support custom map styles and other stuff that users want to do. (e.g. we had/have the hike & bike map style on labs and toolserver)  Also better multilingual maps support is probably something we want and doesn't work so nicely with the default OSM style. Aude (talk) 21:25, 17 February 2016 (UTC)

Proposed IEG project
I've proposed an Individual Engagement Grant project to do some work on the maps style: https://meta.wikimedia.org/wiki/Grants:IEG/Wikimedia_Maps_Rendering_Improvements

I'm proposing working on road labels and borders. I'm not proposing to work on place labels as part of the IEG, because I had trouble defining good acceptance criteria. I didn't want an open-ended project where I'd have a hard time calling it done. Pnorman (talk) 19:34, 29 September 2015 (UTC)

Coordinate tagging
I think one of the simplest easiest things that we could do with the new server is tagging coordinates of photos in Commons, and tagging coordinates of articles in wikipedia. We could have a coordinate TemplateData field and hook up a dedicated editor to that. Would be awesome, relatively simple to do, and not put too much load at once on the servers. —Th e DJ (Not WMF) (talk • contribs) 09:28, 10 November 2015 (UTC)
 * I think this is a good example on where the Map service could work. No promises, but I created a task in Phabricator and will discuss the idea with the team to determine it's viability. Sorry for the late reply, I just joined the foundation and am getting familiar with the corners of our work. :) CKoerner (WMF) (talk) 20:34, 16 February 2016 (UTC)

Uniform coordinates across projects
This has very little with tiles to do, but I think this is essential. There should be a recommended, documented and tooled way of creating geodata that will be reflected in all Wikimedia projects. In my humble opinion the point or line or area for the topic of a Wikipedia article should be expressed in OSM, the data should be reflected in Wikidata (through tagging in OSM), from where the data should be displayed in all Wikipedias. A related topic is where to store the geodata that is not current street map data: historical street map (for which OpenHistoricalMap project is targeted) or thematic data (for which there is no solution). --Susannaanas (talk) 18:32, 10 November 2015 (UTC)

Map preferences
I'm trying to do more for myself with location maps, having found the page "location map many" and think that having a way to change existing location maps would help. For eg I revamped Operation Sonnenblume and managed to add red dots and place names but really needed a way to isolate Cyrenaica so that it was on a bigger scale than the existing Libya location map. I think it would help a lot to publicise the pages which describe adding red dots and place names and also to revise the advice pages so they cater for neophytes like me as well as adepts like you. Keith-264 (talk) 07:57, 13 November 2015 (UTC)
 * we are working on making it very easy to change the map using Visual Editor. Take a look at the demo at http://vem3.wmflabs.org --Yurik (talk) 21:02, 16 February 2016 (UTC)

Much need enhancement
When it is planned to be rolled out in english wikipedia ? --Naveenpf (talk) 06:14, 18 February 2016 (UTC)


 * T125126 is the blocker. You are welcome to comment there. Basically we are waiting for the next year's budget to allocate hardware money to the maps project. --Yurik (talk) 06:17, 18 February 2016 (UTC)


 * This is ridiculous. WMF has not changed. They had millions to spend to for some stupid projects. Anyway now they are not experimenting with people for godsake.   -Naveenpf (talk) 09:00, 18 February 2016 (UTC)


 * Hi Yurik, few queries in en:Wikipedia_talk:WikiProject_Highways --Naveenpf (talk) 15:09, 18 February 2016 (UTC)
 * Do you have a specific query that you could mention here, or is spending time to read a complete talk page required? --Malyacko (talk) 17:21, 18 February 2016 (UTC)

Hi, thanks for supporting maps. My plan at this point (could change of course) is to first deploy maps on wikivoyage, and once we have enough servers, start moving towards wikipedia. The maps will support geojson from the start, something like this example. For now, GeoJson will be stored directly inside the &lt;map*> tags. Eventually, I we will support KML and other data stored outside of the page, but I don't know what site it should be on - see site to store our data discussion. I will also need to build a "snapshot service" - a way to draw the map on the server and convert it to an image, with all the extra layers from geojson/kml/etc. Without this, we might not survive the wikipedia traffic. Comments, as well as any organizational and development help is always welcome of course :) --Yurik (talk) 17:37, 18 February 2016 (UTC)

Discussion from WikiVoyage NL
''Moved from WikiVoyage NL. --Yurik (talk)''

 First impressions by FredTC 

To the right a screenprint of Missing features I experienced after a first inspection. Red arrows, counter clock wise, starting at the top:
 * 1) An available switch to Mapnik is very important because Mapnik gives very important reference points. Also the switches like "Points of interest", "Cycling", "Hiking", etc. are very usefull.
 * 2) Showing the current zoom level is a great help when defining the "zoom=" with mapframe.
 * 3) The POIs button shows destination pages of other destinations in/near the area of the map. Gives the answer to "is there a described destination not far from here?"
 * 4) This button shows all markers defined on the page. Very helpfull if some makers are relatively far away.
 * 5) The missing of the right-click feature is needed very much in order to make new markers.

Clicking the button in the upper right corner brings you to a full screen, but does not allow you to open it on a separate tab. If you use the right-click on this button, it is not the map, but the whole page containing that map appearing in the new tab. This is not practical, because the and  are not close together, you have to scroll the text and you cannot switch to another tab to see the map.

With the mobile version of this page on a Full HD phone screen in portrait orientation, the map takes more than the 1080 pixels the screen is wide, but is defined with "  width="400"  ". Because of this width, it is not easy to scroll down past the map. --FredTC (talk) 9 mrt 2016 14:16 (CET)

Map layers button
''An available switch to Mapnik is very important because Mapnik gives very important reference points. Also the switches like "Points of interest", "Cycling", "Hiking", etc. are very usefull.''
 * I don't think we will be able to provide all the great capabilities offered by other mapping services at first, so this is a good feature to have. I think it should be controlled by each WV community, e.g. via the wikivoyage:MediaWiki:Common.js - where the community will decide which additional map layers to include. As long as there is a clear warning that this data is not covered by the privacy policy, I don't think there is any problem. --Yurik (talk) 15:05, 9 March 2016 (UTC)
 * i agree, this should be community managed, and can be, if the hooks are available. —Th e DJ (Not WMF) (talk • contribs) 12:34, 10 March 2016 (UTC)
 * , i'm not an expert in JS, could you propose how to code this in the phab ticket? (or a patch :)) Thanks! --Yurik (talk) 17:49, 10 March 2016 (UTC)
 * we could have a mw.hook, fired when we configure our leaflet views, that a MediaWiki:common.js page could use to add their own layers during the configuration phase. It could then do (code was moved to T129355 by Yurik (talk)) —Th e DJ (Not WMF) (talk • contribs) 21:30, 10 March 2016 (UTC)
 * , thanks! I moved your code to phab so that this page is a bit more readable. --Yurik (talk) 23:16, 10 March 2016 (UTC)
 * I'd like to note that allowing access to third-party map tiles should also have the consent of the third party. Usually requests like this is meant to add the OpenStreetMap Standard map style, but OSM explicitly forbids heavy usage of this map layer due to limited resources. I guess this might be OK for Wikivoyage, but I expect this will not be allowed for Wikipedia due to the heavy traffic involved. Remember that one of the reasons why WMF is rolling out its Maps service is to remove the burden of the heavy use of OSM's map tiles. —Seav (talk) 15:29, 15 March 2016 (UTC)

,,: The first attempt at implementing map layers feature for Wikivoyage for the community has been posted at EN-Wikivoyage. There are a number of improvements that need to be made, but hopefully it will be a good way to migrate wikivoyage off of the unstable wmflabs-based solution and solve the privacy issue. --Yurik (talk) 04:10, 18 May 2016 (UTC)

Show current zoom level
Showing the current zoom level is a great help when defining the "zoom=" with mapframe.
 * I don't think the vast majority of readers will ever care about this information, so adding it crowds the interface without much benefit. This is a very editor-oriented feature, and as such, I think we should only add it during the editing, but not during reading. I could add it for Visual Editor interface, and also possibly for the edit preview. --Yurik (talk) 15:40, 9 March 2016 (UTC)
 * I also heavily rely on the zoom indication, but only when previewing an edit. Syced (talk) 06:26, 10 March 2016 (UTC)
 * Can we think off alternative ways to make this detectable ? an info page or something perhaps, where we can present some gritty details ? —Th e DJ (Not WMF) (talk • contribs) 12:35, 10 March 2016 (UTC)
 * An alternative could be showing the info at the "mouse over" event for the +/- buttons. However, right now the function of the buttons is shown on "mouse over". --FredTC (talk) 14:08, 10 March 2016 (UTC)
 * As mentioned at "Example showing the way I can do things now" below: The main page of en:Wikivoyage opens with "the FREE worldwide travel guide that anyone can edit" (and a similar text on the Dutch site "Wikivoyage is de vrije, wereldwijde reisgids die iedereen kan bewerken."). To me that means there must be no distinguishing between editors and readers, every reader can edit and must be able to do this easily. --FredTC (talk) 09:29, 13 March 2016 (UTC)
 * I do not see how any particular type of the map curtails anyone's ability to edit the free travel guide. That's just a weird argument that should be disregarded. For example, half of the objects that I add are not shown in OSM at all, so I take their positions from satellite images and Wikimapia. However, it does not mean that satellite images and Wikimapia boundaries must be displayed in every Wikivoyage article. Having different interfaces and different amount of details for readers and editors is perfectly fine. One map will never suit all. --Atsirlin (talk) 03:26, 14 March 2016 (UTC)
 * Is it possible to make the number more useful so you can use it like a slider to move between different zoom levels (like when you hover over the + - on Google Maps, it gives the slider option)? I agree it's more of an editor feature than a user feature, but it's essential that editors know the zoom level so they can properly set up the dynamic map. Including it in the VE or the preview is probably fine, but please include it somewhere. -Shaundd (talk) 05:21, 14 March 2016 (UTC)
 * , slider works well for google in webgl mode (client-side rendering, smooth zoom), which we plan to, but haven't implemented yet. For server-side maps, it will be a bit more chappy. Also, google maps are usually shown in the full screen, whereas our maps start with a frame. Lastly, Google offers it as a user-configurable option, with the +/- buttons by default. They used to have it as a slider, but switched to button. I suspect this is because most users wheel-zoomed instead of using the slider, so they decided not to pollute the interface. Still, certainly a doable feature, just need to minimize the impact to those who don't click anything.  I agree that we should show the zoom level in all of the editor modes (preview and VE).  Also, I agree with  regarding multiple interfaces. We shouldn't try to have one solution for all use cases - they are too different. P.S. Added T129875. --Yurik (talk) 15:17, 14 March 2016 (UTC)
 * No worries and thanks for the detailed response. The slider is a "nice to have" kind of thing to me, showing the zoom level is more critical (glad to see it raised on Phabricator). Thanks -Shaundd (talk) 04:32, 18 March 2016 (UTC)

Right-click to show map coordinates
The missing of the right-click feature is needed very much in order to make new markers.
 * Just like zoom level, this is an editor, not reader-oriented feature. If you edit the map in the visual editor, you usually won't need to know the coordinates - you simply place the marker or draw the polygon where you need it. I agree that you may need it for other cases, e.g. filling out a location template.  How about I enable it only for page-preview and possibly in VE? Also, should this be right click or alt-click/shift-click/control-click? --Yurik (talk) 15:40, 9 March 2016 (UTC)
 * I use to add a description of something to see at a destination. With it I specify the map location. The "lat= | long=" can be direct copied/pasted from the right-click info. Using Visual Editor to change a  entry is very complicated. --FredTC (talk) 15:06, 10 March 2016 (UTC)
 * I don't agree this is just an editor feature. Google, Mapquest and Bing Maps all show the lat and long when you right click / ctrl-click -- so I'm assuming they think there's some value to it as a user feature. It's definitely handy as an editor feature. -Shaundd (talk) 05:33, 14 March 2016 (UTC)
 * , Google et al show coordinates because they all various coordinate searches, which we do not have. I think we could show coordinates in the full screen mode (popup), but having it in a frame would be too crowded. And of course there is a question of formats: 55,755831, 55,755831°, N55.755831°, 55°45.35′N, 55°45′20.9916″N, plus all the localized versions like 55°45′21″ с. ш. (RU). Google bypasses that complexity by simply using the first form.
 * , I don't think VE should be used for marks in WikiVoyage, because WV has very elaborate system for POIs - special templates, special extensions to allow customized editing, etc. VE will not be able to easily handle all that.  I think VE will be good for drawing various shapes/masks that are stored inside the mapframe element. See my other related comment at the bottom.  --Yurik (talk) 15:46, 14 March 2016 (UTC)
 * Yurik I don't think it should be available is full screen mode only. Too crowded is not applicable in the frame situation, because it is just temporary to obtain the "lat= | long=" info. If you just want to add one listing, you don't want to do the extra action of changing to full screen, right-click, copy, close full screen, browse to the ==See== section and add the  and then paste the "lat= | long=".
 * I never use the bêta function VE, but I activated it a few days ago to get an impression. I experienced it as very slow. And the editing of template data was a quite user-unfriendly way of doing this. It was however an easy task to add a map with VE, but then once I have the map, I miss the right-click. --FredTC (talk) 13:40, 16 March 2016 (UTC)

Full-screen as a separate page
''Clicking the button in the upper right corner brings you to a full screen, but does not allow you to open it on a separate tab. If you use the right-click on this button, it is not the map, but the whole page containing that map appearing in the new tab. This is not practical, because the and  are not close together, you have to scroll the text and you cannot switch to another tab to see the map.''
 * FredTC, not exactly sure of the goal here - are you proposing that editors should be able to easily open the map in a separate window? E.g. control+click on the "maximize" button should open a map as a separate tab instead? Would that be any different from opening the same page in two tabs, and clicking map-maximize in one of them? --Yurik (talk) 15:40, 9 March 2016 (UTC)

Show destination pages of other destinations in the area
''The POIs button shows destination pages of other destinations in/near the area of the map. Gives the answer to "is there a described destination not far from here?"''

A button to show all page markers
''This button shows all markers defined on the page. Very helpfull if some makers are relatively far away.''
 * I use this button often, both as a reader and as an editor. Most maps are zoomed to the town center, with theme parks/suburbs attractions/camping grounds/daytrips not visible. Syced (talk) 06:26, 10 March 2016 (UTC)

Example showing the way I can do things now
Assume I want to add a mapframe to the Lewes page at en:Wikivoyage. I know London has a mapframe, so I go to the London page and open the map full screen, then zoom in, move the map, until Lewes is in the center at zoom level 16. Now I need to switch to the Mapnik layer, because there is no helpful info in the Wikimedia layer. Now I see Lewes Castle as potential center of the map, so I do the right-click, and select and copy "lat=50.87289 | long=0.00753" that appears. Now I go to the Lewes page and type " ", ending up with " ". Now I click "Show preview" zoom in until I see a map that shows what I want, I look at the zoom level and add a "zoom=16" to the mapframe, giving " ". After clicking "Save page" the mapframe is in the page.

So to do this, I needed the right-click [5], the zoom level [2] and the switch from Wikimedia to Mapnik [1] to perform this task. --FredTC (talk) 09:07, 10 March 2016 (UTC)
 * And you can do this easily at that was designed specifically for this purpose.  I very much agree with Yurik's concept of distinguishing between map interface for readers and map interface for editors. --Atsirlin (talk) 17:52, 10 March 2016 (UTC)
 * Atsirlin, the link you give, brings a usefull screen, but how do you get it with a simple action from a Wikivoyage page? In the present situation I can right-click on the map that is on a page and copy the map position. Then in the edit screen of a "See" section of the page I add the info below with a single mouse click and I can paste the map position into it. During these actions I don't need to go to another website to obtain the map location. --FredTC (talk) 08:15, 11 March 2016 (UTC)


 * The main page of en:Wikivoyage opens with "the FREE worldwide travel guide that anyone can edit" (and a similar text on the Dutch site "Wikivoyage is de vrije, wereldwijde reisgids die iedereen kan bewerken."). To me that means there must be no distinguishing between editors and readers, every reader can edit and must be able to do this easily. --FredTC (talk) 08:15, 11 March 2016 (UTC)


 * You don't get this link from the Wikivoyage page, and you don't have to get it, because this page has its own search field. Every active editor keeps this page open in a separate tab, and that's how things were supposed to work when maps were developed back in 2013. The way you describe (right-clicking, copy-pasting, reading the zoom level and adding it by hand) is something that I never heard about. Having a pre-filled template is by all means better, because it requires only one click, and typing errors are avoided. You can consider adding a link to geomap.php into editor window in Dutch Wikivoyage. That will solve the problem. --Atsirlin (talk) 03:36, 14 March 2016 (UTC)
 * Well... if your goal is just to make it easy to insert a map, then I think that this map extension is winning hands-down over the old method. I've just added a very simple map here, and I didn't need to copy anything at all, or have any idea what the coordinates are.  I clicked Insert > Map and dragged and zoomed the map until it looked about right.  There are things I'd like to figure out how to do (e.g., add markers for each of the cities in that region), but so far, the initial and most basic step of "adding a map to the page" is about as simple as anyone could wish.  WhatamIdoing (talk) 02:09, 16 March 2016 (UTC)


 * WhatamIdoing: Yes, you are right, if that is the only goal, it is easy to do. But once having the map, I also want to add 's and 's and more at the ==See==, ==Do==, ... sections of the page, and put values in their "lat= | long=" parameters. And then I miss the right-click I have now available. --FredTC (talk) 12:24, 16 March 2016 (UTC)

My workflow is pretty similar. I usually copy-paste a map from another page, preview without changing anything, push the "Show all markers" button to center on the right city, adjust the area/zoom, and right-click in the center to get the final coordinates. Syced (talk) 02:14, 28 March 2016 (UTC)

What is your expectation of "FullScreen" button?
When the user clicks "Full Screen" button, would you like the map to stay at the same zoom level but show surrounding areas, or would you like the map to show the same area as original but in greater details (zoom in). --Yurik (talk) 19:45, 11 March 2016 (UTC)
 * The first option is the way it works now, if I'm correct. I like it that way. But that is a personal opinion. So maybe the behavior could be controlled by some options on the Preferences screens. In that case there also could be one more option that says "open it in the extra screen layer that can be closed with the close button" (the present behaviour) or "open it on a new tab". --FredTC (talk) 08:23, 12 March 2016 (UTC)


 * There is one more way to go to full screen. You locate something on the small map in the page. Then you go to full screen. In the present situation the full screen version has the same center as the small version, so you must find the thing you were watching again on the full screen. A possible alternative is shown in the images. After clicking the full screen button the map expands to the left and towards the top of the screen, but what you were looking at is still at the same position, and you do not need to find it again. --FredTC (talk) 09:29, 12 March 2016 (UTC)


 * I also prefer to stay at the same zoom level. --Atsirlin (talk) 22:38, 1 April 2016 (UTC)

How is placing a marker in the VE supposed to work with Wikivoyage listings?
First off, I want to say thanks for all the work you're doing on Maps right now. I like the clean look of the map tiles and the Visual Editor map is easy to edit without any GIS/map/JS/GeoJSON knowledge. Very cool, but it's also concerning me in a couple of areas: I understand this is a demo and still in development, so my question is, what is the end point that you're trying to get to with the VE interface? Is there going to be further work so setting feature properties is more user-friendly and markers created through the VE can be linked to POIs later in the article?
 * 1) It's very easy to create markers, polygons and lines, but in order to make them useful, the user needs to edit the GeoJSON -- which I'm guessing not many users have a lot of knowledge of, and
 * 2) Creating a marker through the VE puts it in the GeoJSON and not the listings tags that Wikivoyage uses. This creates the potential for duplicate markers or markers that don't line up with listings.

If you want a more specific example, I tried to create a mapmask using the VE. What I did was to create one big square around the edges and then a second polygon for what was supposed to be the unmasked area. The VE codes this as two separate features so they just sat on top of each other. I know enough GeoJSON to know both polygons need to be part of the same feature so I'd have to go in and manually edit the GeoJSON to create the mapmask effect. But if this is the way the VE interface is launched, I don't think most users are going to know this and will cause frustration. Is it possible to create a mapmask button that when clicked creates the initial bounding box and then the user just cuts out the area that is unmasked (and the VE then codes it properly as one feature)? -Shaundd (talk) 06:09, 14 March 2016 (UTC)
 * Shaundd, I was about to ask you to comment about your map experiment, and then I saw you already did! Thanks :) Here's my perspective, but I would also like  to comment, since he is our VE guru, and his opinion may differ.  First, the VE support is indeed lacking - see #kartographer tasks, especially VE column. More specifically, the T125539 describes the property editing like color and marker selection. The masking capability can be added as part of those property pages.
 * The ability to edit all of map's POIs in one spot is more complicated. VE operates on each page element separately, so the map element is not connected to any other page element (e.g. maplink inside a template) from VE's perspective. VE does not understand templates - e.g. the or  templates do not have any special meaning to VE, and thus cannot be easily edited beyond the simple form editor. Also, there is a significant resistance from the VE team to even allow &lt;mapframe> and &lt;maplink> to share the same data - so that mapframe shows data from maplinks. We have enabled it for Wikivoyage, but it might be different for Wikipedia. This is still an open discussion. --Yurik (talk) 14:59, 14 March 2016 (UTC)
 * Interesting. I'm fine if POIs can't be edited through the map (they've always been separate on WV), my concern is more that people will click on the "add marker" button in the VE and either get frustrated and/or create clutter on the maps that will need to be cleaned up. Is it possible to turn off the "add marker" button in the WV installation of Maps if that is the situation? -Shaundd (talk) 04:47, 18 March 2016 (UTC)
 * BTW -- when I tested it on my user page sandbox, the map didn't pick up the standard WV listings tags. Is this a bug or just a case of WV needing to tweak their listings templates? -Shaundd (talk) 04:50, 18 March 2016 (UTC)

Licensing of data during map data editing
I'm not completely familiar with how the map data editing works but please take note of some thorny issues with respect to derivation of map data based on tracing or referencing from an OSM-based base map or layer. OSM data is currently licensed under the Open Database License (ODbL) and on a case-to-case basis, tracing objects or plotting points from an OSM-based base map or layer could possibly mean that the derived data should also be ODbL-licensed. It mostly all depends on whether the derived data is considered "substantial" (a legal term in Europe) or not. Wikimedia project communities are known sticklers for IP issues, and I think the same due diligence should be exercised when the map editing feature is used. —seav (talk) 15:41, 15 March 2016 (UTC)

Is this being used live in any reader-facing page Wikimedia project?
If it is, could someone show an example where? I see the examples here in documentation but I wonder if there is any example use for typical readers.  Blue Rasberry   (talk)   17:32, 16 March 2016 (UTC)
 * Hi Blue Raspberry, the Wikimedia OpenStreetMap tiles for maps are available for use on Wikivoyage wikis at the moment. Some communities have adopted them as default, some as an option. I believe they have been available since Fall 2015 (at least as an option next to Mapnik, Mapquest open, and other tile providers). Just last week the Kartographer extension was enabled on Wikivoyage wikis. This allows for integration with the visual editor to adding maps and points of interest.


 * You can see an example of the Wikimedia tiles in use (with the existing maps tools) on pages in the Has map frame category. As the Kartographer extension is still really new there are not a lot of uses in the wild just yet. You can find some on the English Wikivoyage in the Pages with maps category.


 * I hope that long-winded answer helps give a few examples. :) CKoerner (WMF) (talk) 21:51, 24 March 2016 (UTC)

Saving the location and zoom level in the VE
One thing I noticed when playing with the VE was it automatically saves the center location and zoom level of the map, overwriting whatever was there before. Is it possible to make saving the location and zoom an option, with the default being to not save the location and zoom level? On en:voy (and I'm sure the other WV instances, as well), a fair bit of care has been taken to get the coordinates and zoom level right when placing a dynamic map. We don't want it changed after that. I saw the "reset" button and belatedly realized the user is supposed to hit this button first and then save to work around this problem, but IMO, this isn't intuitive and not an ideal way to deal with it. -Shaundd (talk) 05:03, 18 March 2016 (UTC)

Implementation in Russian Wikivoyage
First of all, many thanks to the developers! The new map feature is great, and it more or less works out of the box, as you can see here, where I tried to combine the new maps with the existing templates in Wikivoyage. I have only a couple of questions concerning the implementation: @Yurik and others, I would be grateful for your advice! --Atsirlin (talk) 22:57, 1 April 2016 (UTC)
 * Sometimes we want to have a map that spans the whole width of the page. Our earlier implementation allowed to set a div environment with width:100%, and it changed the width of the map accordingly. Now, the width parameter accepts only numbers in pixel, so we can't adjust map size to the screen size any longer. How can one set width=100% within the new mapframe environment?
 * Another question along the same lines: When I try to unfold the map here (by clicking on "Открыть карту"), I always get a map that is wrapped by some text on the left. I would like to avoid this, but I can't. It looks like the mapframe overrides all div's it is in.
 * Let's now look at the map markers created inside the article. For the sake of comparison, I kept the old markers too, and you can see that the size of the colored boxes is different, even though css styles should be the same. The new colored boxes have larger height, but I don't understand where it comes from and how to change it. Apparently, the style= parameter of maplink has only limited effect on the appearance of this marker.

--- Just in case, here is the complete implementation: --Atsirlin (talk) 11:31, 2 April 2016 (UTC)
 * City article
 * Country article (including map of regions)

Map markers in black and white
When dynamic maps appeared in Wikivoyage back in 2013, we had a discussion about map markers. Of course, it is very natural to use different colors, as implemented at the moment, but this will not work if you want to print the map in black and white. Printing in general and using black-and-white printers in particular becomes a more rare case nowadays, but it remains a crucial option for the travel guide. Readers who do not properly recognize colors are another concern, and I think that WMF may even have some special policy on this.

Do we have any ideas on how to fix this problem? Back in 2013 we chose to use pictures (icons) instead of colored markers in order to make maps readable in black and white, but I have to admit that our old markers are not good. They look outdated and unprofessional, so I personally would go for the new colored markers even if they are not easily distinguishable in black and white. However, it may not be easy to reach community consensus on this point. --Atsirlin (talk) 23:09, 1 April 2016 (UTC)

Size of the popup window and its customization
When I click on the marker, a window pops up. Wikivoyage used to put object name and a photo there. This is easy to achieve with the new maps, but I noticed that the popup windows do not have fixed size any longer. Instead, their width changes without any obvious reason. Try, for example, the map on this page and compare the popup windows for gray markers 2 and 6. Why are they so different? It will be better to have fixed width of popup windows (then we could adjust it to the imagewidth).

Another question: I tried to make the city name show in bold in the popup window, but it does not work. Why? --Atsirlin (talk) 08:59, 2 April 2016 (UTC)

Wikidata tempo-spatial display integration in Wikimedia projects?
Re-posted here after @Yurik's suggestion.

Does anyone know if Wikidata tempo-spatial display (direct link) could be easily integrated in Wikimedia projects? Because I noticed it may be more practical than what currently used in Wikipedias to show date series and locations of successive events. For example, battle dates in wars or movie releases per country (the last one being what I'm currently working on, the old way). Also, even a partial integration displaying only the timeline could work and still be readable in a Wikipedia article (and I'm not sure everyone would like to see such large maps in articles anyway). Maybe even some tweaking for responsive and customizable sizes could do? --Feldo (talk) 01:49, 3 April 2016 (UTC)


 * , I think this is an awesome visualization for the Wikidata data, and I am one of the biggest proponents of anything interactive of that sort. That said, there is a number of things that need to happen for anything to be added to Wikipedia. For one, we have to make the technology fast, scalable, and support legacy devices and printing. In other words, anything on wikipages need to be shown as a text/image rather than complex client-side rendering if needed. Which means we have to create a complex server-side image rendering. For graphs, I built graphoid service, for maps I am building kartotherian static service, etc.  Second: we are still waiting for more maps hardware, otherwise we won't be able to have maps for Wikipedia, only smaller projects. Third: anything we build should be organically expanded by the community. For example, the graph extension provides graphing language called Vega (which is sadly somewhat complex) that allows anyone to build graphs without sacrificing site security and user privacy. The tempo-spacial display would require its own language for the community to specify needed visualisations, which might take time to develop and secure. So if possible, we should try to maximize the use of existing technologies, and only add new ones when there is clearly no way to adapt the existing technologies. What do you think? --Yurik (talk) 22:17, 10 April 2016 (UTC)
 * , I think I understand your point. Do you think you could get at least similar results about displaying data a bit like tempo-spacial display with the tools you developed, while it could still be readable with legacy devices and printing? Especially regarding how to display chronological events on a timeline you can still interact a bit on recent devices? (zooming, additional annotations, clickable links, etc.) Side-question: what's a legacy device for you and what's required to stop to support them? --Feldo (talk) 01:00, 11 April 2016 (UTC)
 * , it is possible, but not as straightforward or as easy as with your timeline. Plus graphs are not integrated with maps yet, so it won't be possible to highlight an object on a map when clicking on a timeline yet. See some demos here - you will see the interactive graphs shown as images at first. Btw, ideally, we should have a stable secure platform for anyone to build any javascript-based content, but this technology is nowhere near ready yet. For legacy devices - we don't really stop supporting them - basically we should always provide some way to view basic HTML content and png/jpeg images, even if javascript is off. Maybe this will change in the future. --Yurik (talk) 12:52, 11 April 2016 (UTC)

Marker support
Tar Lócesilion (queta) 21:43, 14 April 2016 (UTC)
 * 1) There's a "museum" symbol used on the Kartographer help page. Could anyone make a list of other icons, or at least link do one, please?
 * 2) Imho, if VE supported some settings besides coordinates ("type", other "properties"), usability would improve massively.
 * , I think this is similar to T125539. Mapbox used to have a good page with all icons, but now one has to look through the file list. And yes, we need to make it easier to use. --Yurik (talk) 23:00, 14 April 2016 (UTC)

Matroc (talk) 06:14, 24 April 2016 (UTC) - I created a list from a Mapbox directory - Should be fairly accurate (hope this helps):
 * (added note: Icon names below are for use with <mapframe -- Mapbox icon names follow pattern filename-12/18/24.svg)


 * - style="vertical-align:top;"
 * aerialway.svg
 * airfield.svg
 * airport.svg
 * alcohol-shop.svg
 * america-football.svg
 * art-gallery.svg
 * bakery.svg
 * bank.svg
 * bar.svg
 * baseball.svg
 * basketball.svg
 * beer.svg
 * bicycle.svg
 * building.svg
 * bus.svg
 * cafe.svg
 * camera.svg
 * campsite.svg
 * car.svg
 * cemetery.svg
 * chemist.svg
 * cinema.svg
 * circle.svg
 * circle-stroked.svg
 * city.svg
 * clothing-store.svg
 * college.svg
 * commercial.svg
 * cricket.svg
 * cross.svg
 * dam.svg
 * danger.svg
 * dentist.svg
 * disability.svg
 * dog-park.svg
 * embassy.svg
 * emergency-telephone.svg
 * entrance.svg
 * farm.svg
 * fast-food.svg
 * ferry.svg
 * fire-station.svg
 * fuel.svg
 * garden.svg
 * gift.svg
 * golf.svg
 * grocery.svg
 * hairdresser.svg
 * harbor.svg
 * heart.svg
 * heliport.svg
 * hospital.svg
 * ice-cream.svg
 * industrial.svg
 * land-use.svg
 * laundry.svg
 * library.svg
 * lighthouse.svg
 * lodging.svg
 * logging.svg
 * london-underground.svg
 * marker.svg
 * marker-stroked.svg
 * minefield.svg
 * mobilephone.svg
 * monument.svg
 * museum.svg
 * music.svg
 * oil-well.svg
 * park.svg
 * park2.svg
 * parking.svg
 * parking-garage.svg
 * pharmacy.svg
 * pitch.svg
 * place-of-worship.svg
 * playground.svg
 * police.svg
 * polling-place.svg
 * post.svg
 * prison.svg
 * rail.svg
 * rail-above.svg
 * rail-light.svg
 * rail-metro.svg
 * rail-underground.svg
 * religious-christian.svg
 * religious-jewish.svg
 * religious-muslim.svg
 * restaurant.svg
 * roadblock.svg
 * rocket.svg
 * school.svg
 * scooter.svg
 * shop.svg
 * skiing.svg
 * slaughterhouse.svg
 * soccer.svg
 * square.svg
 * square-stroked.svg
 * star.svg
 * star-stroked.svg
 * suitcase.svg
 * swimming.svg
 * telephone.svg
 * tennis.svg
 * theatre.svg
 * toilets.svg
 * town.svg
 * town-hall.svg
 * triangle.svg
 * triangle-stroked.svg
 * village.svg
 * warehouse.svg
 * waste-basket.svg
 * water.svg
 * wetland.svg
 * zoo.svg
 * }
 * Just looking at this particular list raises the issue that more icons need to be created - (ie. religious-hindu.svg or religious-buddist.svg as well as others for specific Wikivoyage use).... Matroc (talk) 06:18, 24 April 2016 (UTC)
 * zoo.svg
 * }
 * Just looking at this particular list raises the issue that more icons need to be created - (ie. religious-hindu.svg or religious-buddist.svg as well as others for specific Wikivoyage use).... Matroc (talk) 06:18, 24 April 2016 (UTC)


 * Matroc, thanks for making the list. We are using Maki icon set (see the list at the bottom). Some of these icons were recently added and have not been updated yet, but hopefully they will become available soon. Btw, all these icons are CC0, so they can be uploaded to Commons. --Yurik (talk) 19:31, 23 May 2016 (UTC)
 * Yurik -- I redid table above on my home page showing the differences between both name sets. - Matroc (talk) 06:15, 24 May 2016 (UTC)

Translation
Uhm, how do you/we/I set up a translation page for the page Help:Extension:Kartographer/sv. Riggwelter (talk) 16:27, 24 April 2016 (UTC)
 * Riggwelter, I think this translation info will help. --Yurik (talk) 19:24, 23 May 2016 (UTC)

Some testing notes

 * 1) If a description has an image file set to a specific size - it does not hold true if the title length is very long or very short when you click on the map icon.
 * 2) * Should Properties have a File or Image property instead of putting an image in the description?
 * 3) I have used Wikidata as a source for creating a mapframe of the 47 notable cities in the Plains Region of India using a Lua Module. (a Module has processing limits so not to be used for hundreds of lookups as it would quit with an error)
 * 4) * For cities, the locations are based on the entity.ids and should already exist in Wikidata in order to get the latitude, longitude, name, image, description etc. To produce a mapframe of restaurants and other places is yet another ball of wax to be investigated as Wikidata would not be a good source. Wikidata is not completely accurate or missing data.
 * 5) * The module is run with safesubst so once saved in the editor - all the code for the mapframe becomes visible when one re-enters the wiki editor and can be modified accordingly. (As you can guess - I am old school and don't use the Visual Editor yet!)
 * 6) * This test will remain on my Wikivoyage home page for a short period of time.
 * 7) For marker icons (marker symbol) list above I left out -number and -alpha
 * 8) * To add a counter simply add -yourfavoritecountername to the names above: ie. -number-see or -alpha-cities etc.
 * 9) mapframe - lat and long are evidently required for all features in a FeatureCollection - if missing, apparantly an empty map will be displayed. Matroc (talk) 18:06, 26 April 2016 (UTC)
 * 10) It appears that when using numbered icons with maplink and incorporating then in a map with show, the color for the number on the article page is one color and on the main mapframe a different color. Probably an error on my part.
 * 11) With maplink - I think a little more background color to the left and right should be added to the icon when it appears on an article page. - Matroc (talk) 03:58, 30 April 2016 (UTC)
 * 12) Browser Opera has an issue with displaying a map - actual it has a hard time displaying a mapframe in general.
 * 13) mapframe - if marker-color is not specified then gray or grey color is applied as default
 * 14) mapframe - if maker-symbol is not specified than the marker point (balloon) will just be in the marker-color with no symbol Matroc (talk) 20:59, 14 May 2016 (UTC)


 * 1) The layers button on top right is covering the close button in latest version when map is expanded to full screen.
 * 2) One can use the File tag in description and is useful for adding more content text and eliminating link to image to Commons. The additional text if wanted can make the map more informative.
 * 3) * ie.  - Matroc (talk) 23:16, 17 May 2016 (UTC)


 * In maps created using mapframe - if you want the group select name to appear in the map layers - It appears important to use the group="aaa" parameter in the mapframe as well as a maplink. Also consider using the show="aaa" parameter as well and verify by checking your map by toggling the differen group layers.
 * It is also possible to place different maps in collapsible div statements. - Matroc (talk) 01:59, 23 May 2016 (UTC)

Location maps
Location maps are used very inconsistently on Wikipedia (for some examples, see here). I believe that the use of interactive maps as location maps could be a huge improvement. I have put some specimens here, with my comments. Maproom (talk) 15:50, 27 April 2016 (UTC)
 * Maproom, that's a very very impressive collection of maps, thank you!!! Take a look at static map discussion by Jheald. The big distinction between interactive and static maps is that the static map is generated by an artist (user) to represent all the information they want for that specific location, using certain map drawing tools like QGIS. A different location or zoom would require that user to start from scratch. So if a user wants to draw zoomed-out map of the given location in the upper-right corner, they can. But next time, they may choose to draw it somewhere else, or not at all. On the other hand, the interactive maps are drawn once for the whole globe. So if the zoomed-out map is needed (which is obviously very useful), we would have to implement some standard way to add it by drawing a globe in the corner and drawing a big red dot on it to explain what you are looking at. But it won't be as nice as for the static image. More thoughts to be added later. --Yurik (talk) 20:17, 23 May 2016 (UTC)

Use of existing tags for points and location maps
I would really love to see Wikimedia Maps using osm ids and tags for displaying points or creating location maps, in some way similar to the one OSM site itself uses to display things.

WIWOSM is something that I would like to see being used.

A could have an attribute for a relation, way, or node, and use this instead of providing coordinates to create a polygon on top of the same feature.

For example: http://www.openstreetmap.org/relation/2348445 are the boundaries of a greek municipality.

Do something like

That should be displaying a map like in the example for Lyon or WIWOSM saving us from putting a block of coordinates into the article's code.

It should be easy for wikipedia editors to embed maps without having to drawing polygons from scratch, or exporting coordinates that can be accessed automatically, and also we should not put all this code into the articles.

-Geraki (talk) 18:33, 3 May 2016 (UTC)
 * Geraki, thanks, I had almost the same goal in mind, but with one important change - we should use Wikidata IDs, not OSM IDs, because, as even the WIWOSM page mentions, OSM IDs are fragile, whereas Wikidata IDs were created to be much more stable and easily referenceable. See T134086. --Yurik (talk) 01:23, 24 May 2016 (UTC)


 * Yurik, I am aware of that and I agree that Wikidata IDs are more stable than OSM IDs. But since OSM IDs are fragile, then the related reference in the Wikidata item can be equally invalid. If someone delete and recreate a relation/node/way in OSM it is unlikely that he, or someone else will update, the property in Wikidata. On the other hand if someone modify/recreate an OSM feature (f.e. replace a single node with a polygon) it is more probable that he will copy the previous tags in the new feature. So, maybe an intermediate service like WIWOSM would be a better solution. -Geraki (talk) 15:45, 25 May 2016 (UTC)


 * Geraki, i never said OSM ID should be stored in Wikidata :) Au contraire, the OSM polygon/relations should contain Wikidata ID, and when we import OSM db, we should make it possible to query OSM DB by that ID and present the result. Of course we will have to deal with the cases when multiple items have the same ID. --Yurik (talk) 15:54, 25 May 2016 (UTC)


 * I misunderstood. I thought you were focusing on d:Property:P402. Querying for the wikidata tag on OSM is the right solution. -Geraki (talk) 16:49, 25 May 2016 (UTC)

Help: I need to create an image
Help: I need to create an image like the one used here. How can I do the same on other wp? --Llorenzi (talk) 13:18, 18 May 2016 (UTC)