This is really neat but I don't really care about greenery when I'm using Apple Maps. Can they take a break from figuring out how to convert satellite images into green blobs and devise an algorithm to put street names on the screen ? Apple and Google maps are both worthless as maps without typing in an actual address and using navigation because they can't just show the main cross street names on the screen. It abso…
Agreed; and, the greenery information is useless without also a way to determine ownership or transit privileges. Is it private, public (district, state, federal), military, or some other kind of ownership class? I find it hard to believe that so much work could go into maps when actually using it doesn't seem to be the main goal. How am I going to use this greenery information?
Apple's New Map
121–130 of 377 posts
Re: Apple's New Map
#122Earlier quoted context omitted.
It's obviously an intentional choice to avoid too much screen clutter... but I agree it's infuriating. I've spoken in the past with some people who work on Maps products and have heard "people say they want it but then they really don't..." and I honestly can't imagine what UX studies are telling them that. All the time I see a destination and I'm trying to figure out what closest cross street I should stop at and by…
I wonder if this varies based on location / version? I just tried Maps on iOS 12.0.1 and it appears to do exactly this, at least in San Francisco. Every time I zoom in on a street, the label fades in right at the center, like you suggest.
Re: Apple's New Map
#123Re: Apple's New Map
#124This is really neat but I don't really care about greenery when I'm using Apple Maps. Can they take a break from figuring out how to convert satellite images into green blobs and devise an algorithm to put street names on the screen ? Apple and Google maps are both worthless as maps without typing in an actual address and using navigation because they can't just show the main cross street names on the screen. It abso…
You should read all the way to the end. "AVs navigate themselves—so all we’ll really need to know is where we want to go. And Google, with a rapidly-growing autonomy project of its own, seems to have caught on to this. "If you zoom out on Google Maps’s recent features, you’ll notice that they’re increasingly about figuring out “where to go?” "And even Google’s map seems to be following this pattern. Over the last two…
Re: Apple's New Map
#125Re: Apple's New Map
#126Re: Apple's New Map
#127Earlier quoted context omitted.
Agreed; and, the greenery information is useless without also a way to determine ownership or transit privileges. Is it private, public (district, state, federal), military, or some other kind of ownership class? I find it hard to believe that so much work could go into maps when actually using it doesn't seem to be the main goal. How am I going to use this greenery information?
This would be killer. There are some kml overlays for BLM and NFS land, but imagine an "access" layer that was something like "public free access", public access with admission fee, private but open to the public (like retail), and private.
Re: Apple's New Map
#128Earlier quoted context omitted.
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 compa…
I 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 hone…
Re: Apple's New Map
#129Earlier quoted context omitted.
It's obviously an intentional choice to avoid too much screen clutter... but I agree it's infuriating. I've spoken in the past with some people who work on Maps products and have heard "people say they want it but then they really don't..." and I honestly can't imagine what UX studies are telling them that. All the time I see a destination and I'm trying to figure out what closest cross street I should stop at and by…
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 compa…