6 ms·
I’ve worked on mapping software, and in fact on street name placement (Not Google or Apple). The code we had for deciding where and when to draw street names ha
by ryandrake 8y ago
I’ve worked on mapping software, and in fact on street name placement
(Not Google or Apple). The code we had for deciding where and when to draw street names has to be among the most complicated, full-of-edge-cases code I have ever encountered. Engineering is pulling one direction, data providers are pulling another direction. UX is pulling this direction, cartography is pulling that direction. Everybody in the company wants to bike-shed about it and insert their opinions because the problem to them “seems so easy.”
I’m not going to go into too many specifics but for most map products I’ve worked on, the usual reason that a label doesn’t appear somewhere is because the map data provider hard-codes the potential places where a label could be displayed, and it’s not “everywhere along the road”. You might be zooming into a place where a cartographer chose not to add a label point. Good map software will try to sensibly fill in these gaps but are not perfect. Too aggressive about adding labels and you have the artists and cartographers telling you some areas on the map are too cluttered. Not aggressive enough, and some areas on the map are bare.
It’s maddening getting those bugs saying “I think there are too many labels”, backing it off, then a few days later getting the bugs, “I can’t find the street label next to my house!” Lots of simple-to-whiteboard solutions would work well for your particular neighborhood but look terrible in Manhattan or rural Idaho, not to mention Japan. It’s really not simple.
- ianmcgowan 8y agoThanks for explaining that - I tend to assume there are smart people are working on these things, and when thinking "Can't they just... it would be so easy to..", I assume it's because the problem is a lot harder than I think it is, not because they're missing the obvious solution right in front of them. For my own personal more mundane stuff, it's usually "can't you just parse the names and addresses and put them in separate fields?" and the answer is usually, "80% of the time, yes. If you're ok with that, we're good". They never are ok with that :-)
- ethbro 8y agoI think the thing that confuses me and parent is that Maps ALREADY knows about road continuity. And road names. I'm sure I'm missing something, but (1) flow labels along their roads to the center of the screen, (2) separate them with predefined padding, (3) drop labels if visible label count > maximum, smallest-to-largest road, until under the threshold. If UXers want to bitch, hide it behind a layer filter. But honestly, #&@+ them. (Sorry, but we are talking about maps that don't show road names here)
- deleted 8y ago[deleted]
- cooper12 8y ago> but we are talking about maps that don't show road names here That presumes that road names are an intrinsic part of a map. While they certainly were in the past, I think there's a paradigm shift happening that's become so common we don't notice it anymore. We don't tell people to meet us at "The intersection of Street X and Y" as much anymore, we tell them to meet us near a prominent landmark like a park, train station, or restaurant. We barely even need street names for navigation anymore; instead, our software tells us how many blocks to walk and when to turn (even automobile GPS tells us to expect turns in the next X miles). I feel this will be part of a larger revolution where we might start using alternative easy-to-shate GPS coordinates [0], and even completely new map styles like isochrone maps. [1] [0]: See https://what3words.com/ https://what3words.com/ and Google's https://plus.codes/ https://plus.codes/ [1]: https://www.atlasobscura.com/articles/isochrone-maps-commutes-travel-times https://www.atlasobscura.com/articles/isochrone-maps-commute...
- dingaling 8y ago> we tell them to meet us near a prominent landmark So that's the navigational use case for 'meet person' Another common use case is 'proceed to building at 123 Long Street'. I've met several confused tourists and couriers whose satnav has dumped them at, say, 973 Long Street with an arrival fanfare.
- ethbro 8y agoI hear what you're saying, but at least in the US we only have 2 pieces of well labelled and persistent navigational data in the real world: street names and numeric addresses. In my experience, navigation with Google Maps can be terrible about interchange / exit lanes. It's much easier just to pick the road name and follow the well-labelled and up-to-date highway signs.
- crazygringo 8y ago> We don't tell people to meet us at "The intersection of Street X and Y" as much anymore, we tell them to meet us near a prominent landmark like a park, train station, or restaurant. Citation needed. As a New Yorker, intersections of streets are how we do it all the time, when you want to meet on the street to walk somewhere together. "Meet me on 23rd and 8th." > We barely even need street names for navigation anymore; instead, our software tells us how many blocks to walk and when to turn (even automobile GPS tells us to expect turns in the next X miles). When streets are closely spaced, the name is absolutely necessary to know which one to turn onto -- you can pass a whole street in the time it takes the GPS to start and stop speaking and have no idea which street the "next street" refers to. And plenty of people still walk or bike, where they check their phone only occasionally and memorize the name of the next street they need to stop at or turn on. Sure there are new use cases, but the old ones aren't going away at all.
- deleted 8y ago[deleted]
- mulmen 8y agoI don't doubt your experiences or the reasons for constant regression in smartphone map usability over the last decade. Thanks for providing first hand experience. I hope I did not suggest that I think this is an easy problem to solve. I do think this missing feature betrays a deep organizational dysfunction as you have described. This dysfunction leads to losing sight of what is valuable to users.
- fouc 8y agoSeems like this is the type of thing that should be ultimately built out as an algorithm rather than hardcoded exceptions etc.
- CamperBob2 8y agoOr -- gasp -- give the user the ability to control the name density.
- egypturnash 8y agoThis really really sounds like an argument for adding a “name density” slider somewhere in the corners of the main UI. Just admit that no one setting works for all people in all places and stop even trying to find it.
- dexterdog 8y agoThat violates the "it just works" directive that designers and developers are working under. If it has to be configurable they view it as a design problem so instead they force you to use it the way they want it to look.
- sib 8y agoI'd say that, unfortunately, this is a case of designers trying to capital-D "Design" rather than truly understanding & solving user / customer problems. Given the wide variety of use cases and user needs (which are also context-dependent for the same user), "it just works" may lead to it not working in a plurality of instances. (/currently leading a design and Pmgmt team)
- egypturnash 8y agoThere is configuration though. Pretty much any map app has a place you can switch between map/satellite/other views. And toggle overlays for traffic and other things. Stick a slider in there if you must hide your shame at not being able to make your tool all things to all people, this is where you’ve already admitted that people have different needs.
- dahauns 8y agoA professional meteorological mapping and modelling tool we use at work has exactly this: A simple "declutter" slider. And it is easily one of its most impressive features - so incredibly simple (esp. compared to all the other bells and whistles it offers) and yet constantly proving its usefulness in everyday use. Gmaps & Co. have become even more tiresome to use since I actually have experienced how much more comfortable it could be.