Jump to content

Community Wishlist Survey 2019/Maps/Maps Improvements: Vector Structure, Disputed Borders, Cleaner Style

Add links
From Meta, a Wikimedia project coordination wiki

Maps Improvements: Vector Structure, Disputed Borders, Cleaner Style

  • Problem: The development of the Wikimedia Maps should be continued. Main wishes are migration to vector tile structure and fix the international borders.
  • Who would benefit: All wikis including Wikipedia, Commons, Wikidata, Wikivoyage, etc.
  • Proposed solution:
  • More comments: Two issues very important for wikipedia maps

Discussion

more tickets, not part of this proposal and older discussion

Removing this session from initial proposal

Minor wishes are the move of all controls to the left map side like nearby, full-screen, layers controls, adding an additional zoom-level control, several pushpin symbol improvements like usage of short strings, 3-digit numbers etc. A nearby map mode showing links to nearby articles should be added. Kartographer documentation should be improved. T155601, T145475, T147184, T141715, T141335, T140212, T140209, T140092, T140087, T140083, T180909. T208350

Here are some bugs that I consider a high priority:

  • Enable auto-positioned snapshot on Kartographer side (T158919)
  • Maps fast preview is broken on 2nd attempt (T151524)
  • Geoline/geoshape does not work with relations other than multipolygon/route/boundary (T156433)
  • Automatic zoom and positioning doesn't work for geomasks (T178370)
  • Remove map offset when quitting full screen mode (when screen > 1024px) (T161065)
  • Maps that contain Wikidata ids and are stored on Commons fail to display when called via <maplink> or <mapframe>(T155927)
  • Kartographer geoline service has low accuracy at high zoom levels (for long features) (T155919)
  • Ability to define a map legend (T154585)
  • Introduce global or per-wiki styles (T146343)
  • maps with "type": "ExternalData" have pointing hand mouse pointer over unclickable objects (T192613)
  • Should we use the marker cluster plugin with `<mapframe>` and `<maplink>` ? (T136455)
  • Customize map markers in Kartographer (T131618)
  • Kartographer full page view cuts off longer captions (T197735)
  • Support appropriate documentation of CC BY SA data on Commons (T200968)
  • Add a data-page-only wiki markup header to datasets (T155290)
  • Track Commons Dataset usage across wikis (what links here) (T153966)
  • Support Data namespace redirects (T153598)

The lack of support for redirects and what links here means that moving (or splitting) pages in the data namespace is liable to break stuff, with no way to know whether this has occurred – a really unacceptable situation for a repository that is supposed to be available across projects and languages. Gareth (talk) 23:45, 29 October 2018 (UTC)[reply]

In addition to T156433 and T155919 mentioned above by Gareth I'd like to highlight automatic zoom/centre issue (T187741). I think from end-users perspective these are significant deficiencies in the way OSM external data is currently handled. What else bugs me the most about external data support is that there is no way to check if reference to external data actually returns any external data, e.g. so that template/module could decide not to show map if nothing is returned for QID related to given page. (Maybe T155925 would be sufficient for the latter, or maybe it should be something more generic that also covers .map page external data.) --Pikne 09:54, 30 October 2018 (UTC)

Goog point by Pikne. It is hard to include maps in templates, or modules, whitout knowing if there is any external data. --Vriullop (talk) 10:45, 30 October 2018 (UTC)[reply]
I think T187741 is a duplicate of T158919. Gareth (talk) 23:04, 1 November 2018 (UTC)[reply]

I think this wish needs to be structured better. Perhaps the two "major" wishes (vector tiles and international borders) need to be their own wish, and "minor improvements" could be a second wish that people can vote for separately. Otherwise it is going to cause problems for the Community Tech team, who are not possibly going to be able to work through all the linked tasks, particularly if they don't have anyone experienced in mapping on their team. This, that and the other (talk) 10:54, 30 October 2018 (UTC)[reply]

I think that the wishlist should be kept monolithic until WMF acknowledges that the Maps works needs a proper allocation of work / team. Then in case we can split it --Sabas88 (talk) 11:32, 30 October 2018 (UTC)[reply]

Please consider also these, which were closed due to a lack of resources from WMF but are of interest

  • Use Wikidata international labels when OSM data is not available (T193198) (this is necessary also for OSM community)
  • Deploying new vector tiles to production (T156682) (this was practically ready to deploy)

--Sabas88 (talk) 11:38, 30 October 2018 (UTC)[reply]

@Naveenpf: Note that Community Wishlist proposals should be discrete tasks, while this proposal seems to be a catch-all for many many actually separate proposals. --AKlapper (WMF) (talk) 12:57, 30 October 2018 (UTC)[reply]

Hi naveenpf and all: I'm happy to see another Maps proposal this year, and I hope it's as successful as the Maps wish last year. As it's written, though, it's too big for a Wishlist proposal. This process determines what the Community Tech team works on next year, and they're going to investigate and address the top 10 wishes over the course of the year. A request for a year or two of Maps support is beyond what Community Tech can provide, and we don't have another team to do that work. This proposal will need to be trimmed down to a few main wishes, in order to move forward to the voting phase. Do you want to talk here about which requests are most important? -- DannyH (WMF) (talk) 21:56, 30 October 2018 (UTC)[reply]

Vector maps, internationalized maps, improval of docs sound great ideas. Gryllida 22:36, 30 October 2018 (UTC)[reply]

Judging by the No. 1 place of Kartographer improvements last year I think there probably would be enough support that splitting it into 2-3 proposals as suggested above that could all get enough support for the Top 10 would be possible Galobtter (talk) 08:17, 31 October 2018 (UTC)[reply]

Yes, I definitely would advise splitting into 3 of 4 chunks rather than "fix all da things" —TheDJ (talk • contribs) 10:36, 31 October 2018 (UTC)[reply]
Same here, splitting the proposal would be more practical approach. Capankajsmilyo (talk) 10:40, 31 October 2018 (UTC)[reply]

The style of this proposal is very much the same as last year's proposal (which wasn't split up). Even "It is very difficult to estimate the developing time. I think minimumly a year, better two years are needed." comes directly from that proposal (and, yes, it's clearly an unrealistic suggestion). Gareth (talk) 23:04, 1 November 2018 (UTC)[reply]

Unfortunately, that was a problem with last year's proposal that we don't want to repeat. :) Last year's proposal was very broad, and expectations were very high. The team delivered on several important changes this year, but there was still a sense that some people in the community were disappointed, because they assumed it was possible that a Wishlist proposal would result in a long-term, full-time Maps team. We want to be clear this year about what the team can deliver for one Wishlist proposal. You'll need to take the "minimum a year/two years" out of the proposal, and scale down (or split up) the requests in this proposal before it moves to the voting phase. -- DannyH (WMF) (talk) 15:23, 2 November 2018 (UTC)[reply]
Or maybe we/ WMF need to recognise the need for a full-time maps team, and start to look for grant- (or other) funding for such? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:25, 3 November 2018 (UTC)[reply]
+1 --Sabas88 (talk) 10:59, 4 November 2018 (UTC)[reply]

Hi Naveenpf and all, it's been about a week since I posted that someone needs to cut this proposal down, or split it up into separate proposals. Ideally, the proposal would have the top two or three problems that are most important to solve. There is a ticking clock here -- the proposal phase ends on November 11th, and if this proposal stays the way it is, we'll have to archive the proposal, and it won't move on to the voting phase. The note about the "minimum a year/two years" needs to be taken out, and the proposal needs to be clear about what you're asking for. With the bullet list of 17 tickets in the Discussion section, we'll have to make it clear that that's part of the discussion and not the actual proposal. I'm happy to talk more about how to edit the proposal; please ping me here if you have questions that I can help with. -- DannyH (WMF) (talk) 00:59, 8 November 2018 (UTC)[reply]

Can we have just two ? vector tile structure and fix the international borders. first one as far as I know development is over. Only testing and deployment is required. Can we have both of them ? --naveenpf (talk) 13:07, 8 November 2018 (UTC)[reply]
Naveenpf: Yes! Vector tile structure and fix the international borders would make a great proposal. -- DannyH (WMF) (talk) 20:47, 8 November 2018 (UTC)[reply]
@DannyH (WMF): And will this proposal be renamed to better reflect its hobbled status? Gareth (talk) 08:01, 14 November 2018 (UTC)[reply]
I created one with the OSM issues [1] --Sabas88 (talk) 15:33, 9 November 2018 (UTC)[reply]
I created another one about OSM external data issues (above one being about styles/i18n). Pikne 17:07, 9 November 2018 (UTC)[reply]
  • I wanted to mention something for people who may not know the history behind the two main Phabricator wishes mentioned above, T153282 and  T113008. You wouldn't guess it from the titles, but one of the very cool results of doing those two tickets is that the styling of our maps will become much more sophisticated. The art of digital maps lies in knowing what to hide or show, abstract or provide in detail, at what level of magnification. If we put those tickets in place, dynamic wiki maps will look a lot cleaner and generally nicer. Plus the issue of clarifying disputed borders is quite important. —JMatazzoni (WMF) (talk) 21:38, 9 November 2018 (UTC)[reply]

I've created some proposals; please adopt these if you're interested, otherwise they'll be moved to the archive:

p.s. I think the revised "main wishes" proposal should be resubmitted with a more descriptive name and this proposal should be moved to the archive. Gareth (talk) 08:38, 10 November 2018 (UTC)[reply]

Is it in the cards to use background images that are actually useful as opposed to simply blank space? Google and Bing have contour levels and satellite images. Jo-Jo Eumerus (talk, contributions) 08:31, 14 November 2018 (UTC)[reply]
Proposal does not state a problem. --Traveler100 (talk) 14:41, 17 November 2018 (UTC)[reply]

Voting

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Community_Wishlist_Survey_2019/Maps/Maps_Improvements:_Vector_Structure,_Disputed_Borders,_Cleaner_Style&oldid=18675051"