Community Wishlist Survey 2020/Archive/Kartographer improvements

Random proposal ►◄ Archive The survey has concluded. Here are the results!

Kartographer improvements

N We won't be working on the existing maps stack this year

Problem: The development of the Kartographer tool should be continued. Beside the phabricator tasks noted below the there are some additional wishes. (1) The computing time for <maplink> calls should be reduced especially for the use with Lua. (2) Showing user's position at the map; adding a button to move the map to the user's position. (3) Adding a zoom-level control to maps. (4) The Wikivoyage mode should be available at all wikis. (5) Make mapframe available for all flagged-revs Wikipedias.
Who would benefit: All wikis including Wikipedia, Commons, Wikidata, Wikivoyage, etc.
Proposed solution: Additions to the Karthographer extension.
More comments: It is very difficult to estimate the developing time. But the Kartographer should be permanently improved.
Phabricator tickets: T141715, T141335, T140083, T180909, T192334, T190069, T190067, T190064, T190062, T183770, T183766, T191585, T208713
Proposer: RolandUnger (talk) 18:46, 10 November 2019 (UTC)[reply]

RolandUnger, thank you for submitting this proposal! We have reviewed this as a team, and we will unfortunately be unable to take on this wish. Here's why: Our infrastructure team is currently discussing options to switch out the maps frontend and backend to a different technology stack, which would be more robust and easier to maintain. If we can make that work, then it could take care of many of the concerns expressed in this proposal. It will be at least several months until we'll know for sure what the decision will be, so for this year's wishlist, we're not going to take on any possible commitments to working on the existing maps stack. Thank you again! --IFried (WMF) (talk) 17:47, 19 November 2019 (UTC)[reply]