Main topic

The new maps service generates tiles, but at the moment we do not have a coherent client/wiki-side support for it, forcing various labs-based implementations. Kartographer extension attempts to solve that, but it needs some serious discussion on what features it should provide. Features should include extra data to show on the map specific to the article, static server-side map generation with layers, etc.
See also T115290 and the extension page

Bonus points

Time permitting, we may also look into other topics. Feel free to add more ideas to this list.

Decide cartographic goals for our map style - As T113912 describes, we need to establish what map style(s) we want for Wikipedia articles. What kinds of maps would illustrate different types of articles better? What information should we sabdue/hide so as not to interfere with the article's content? Style guide is what map designers will use when designing our new styles.
Extension replacing GeoHack - what should happen when users click on geo coordinates? What functionality is needed?
GeoData needs support for returning results over a wide area T112033
Migrate VE maps plugin to use the new service (should be enabled in Wikivoyage only)
Allow 3D model (e.g. buildings) storage in Commons T107410
Allow GeoJSON storage in Commons
Make Mapnik handle hstore (dictionary) values
...?

Related Objects

Mentioned In: T119593: Define the list of "must have" sessions for WikiDev '16
T119029: WikiDev 16 working area: Content access and APIs
Mentioned Here: T113912: Outline cartographic goal for style
T115290: Architect Wikipedia <map> tag
T107410: Wiki 3d warehouse
T112033: Make GeoData search over a larger area

Event Timeline

selection process. Please pay attention to the next one: > By 6 Nov 2015, all Summit proposals must have active discussions and a Summit plan documented in the description. Proposals not reaching this critical mass can continue at their own path out of the Summit.

next deadline on November 6.

@Qgil & • RobLa-WMF added a comment.Nov 6 2015, 11:47 PM

@Yurik: if you had to pick one (and only one) which style of meeting do you hope this will be? Problem-solving, Strawman, Field narrowing, Consensus, or Education? See

In T113526#1790159, @Yurik wrote:

We outlined all the topics we plan to discuss, and judging by the past conferences, there is always plenty of people interested in Map-related discussions.

Just for clarification, en wikivoyage.

I cannot find the discussion in en.wikivoyage. In any case, I guess these are not developer discussions? What are the discussions you expect at the Developer Summit, and who else will be interested in participating?

Sorry if I keep asking questions, this is nothing personal. :) The description is unclear, although at least now there are two topics featured. The two tasks related to these topics have no discussion, and this task here only contains discussion about this task as a Summit proposal.

https://en.wikivoyage.org/wiki/Wikivoyage_talk:Dynamic_maps_Expedition#New_map_layer_added_for_Wikimedia.2FKartotherian

The discussion is very much a developer one - to figure out how users can control the new map system. How maps can provide the needed functionality, and how it can seamlessly integrate with other existing or new services.

• RobLa-WMF added a comment.Nov 18 2015, 3:35 PM

In T113526#1790332, @Yurik wrote:

for the first topic, the <map tag, the Problem-solving is the closest - I need to figure out how best to solve it to satisfy everyone's interests in this feature. For other ideas, I am hoping for more of a field-narrowing - there are many ideas people have proposed, and we need to figure out which features are more valuable than others.

Given that you seem to have this mentally divided into two topics, I think it would be helpful to digitally divide them (i.e. actually put them in separate Phab tasks). We can always lump them together on the end itinerary, but splitting them off would be helpful to set expectations and define goals for the meeting.

• RobLa-WMF mentioned this in T119029: WikiDev 16 working area: Content access and APIs.Nov 19 2015, 12:47 AM

In SF for all hands and would be very interested in attending this session.

Maps/Geo has huge potential for wikimedia and could put the movement in a very important place in the FOSS4G landscape.

Would really like to see this happen.

As it stands, this sounds like this session would be about brainstorming / feature idea gathering.

@Yurik, if your intention is to narrow down the scope / prioritize, could you formulate a set of key trade-offs / prioritization questions that should be answered?