Earlier quoted context omitted.
I'm left wondering how much data would be saved if they were videos rather than GIFs. They'd probably end up being better quality, too!
Most of the GIF only has 2 frames, a video won't be better and smaller.
Apple's New Map
141–150 of 377 posts
Re: Apple's New Map
#142Earlier quoted context omitted.
And heck, it would be very easy to make this a setting: yes or no, this user wants as many street names as possible.
Member when software had lots of options how to configure it to show you the information you wanted? Peppridge Farms remembers. Also VLC and a few other weird fringe holdouts...
Re: Apple's New Map
#143Earlier quoted context omitted.
>Whenever you zoom in enough that there's enough room on a visible street to put a label, then put the label! I mean if I zoom in so far that only the one street is visible and there's no other text on it, but Maps still leaves it blank... it just feels inexcusable. Agreed. Happens on google maps too, and that's just so irritating
someone else said that according to a Google engineer we don't "really" want it and I wanted to see if this is true. I put in a random street (mission street in San Fransciso), this how it looked for me on desktop: https://imgur.com/a/aOERdLR Then I started filling out streets with the continuous name of the street (first copy and pasting the name in small squares, then by hand adding red dots to separate them). This…
Re: Apple's New Map
#144Earlier quoted context omitted.
He's written multiple articles about maps, even before that one: https://www.justinobeirne.com . He's very good at spotting details in maps–IIRC he worked on Apple's maps team before, so this isn't particularly surprising.
> he worked on Apple's maps team before For some reason I thought he is some random guy just passionate about maps, I was actually looking for donate me buttons on the site because I love reading his articles whenever they are posted to HN.
Nobody else would know what to look for.
Re: Apple's New Map
#145Re: Apple's New Map
#146>In other words, TomTom’s database somehow has roads from Parkfield’s boomtown days—roads that have been gone for more than 75 years. No wonder why Apple removed them. Another possible explanation is the TomTom was using these unlikely to be visited streets as trap streets. https://en.wikipedia.org/wiki/Trap_street >In cartography, a trap street is a fictitious entry in the form of a misrepresented street on a map, o…
Re: Apple's New Map
#147Earlier quoted context omitted.
someone else said that according to a Google engineer we don't "really" want it and I wanted to see if this is true. I put in a random street (mission street in San Fransciso), this how it looked for me on desktop: https://imgur.com/a/aOERdLR Then I started filling out streets with the continuous name of the street (first copy and pasting the name in small squares, then by hand adding red dots to separate them). This…
I can't tell whether you're getting serious, but I'm pretty sure most users would not prefer your change. It's so dense it's hard to read, and in a repetitive way.
For me, it's not hard to read. I'd prefer it, anyway.
Still, if you wouldn't prefer it then we can see what the Google engineer meant, as this is exactly what you get if you show as much information as possible!
Re: Apple's New Map
#148Earlier quoted context omitted.
That's your use case. I've used maps a lot to try to find hidden or secluded parks -- often with great success. I'm talking postcard-perfect views around the Sydney harbor, small beaches around various bays, isolated parks near beautiful rivers and a whole lot of other places that are really beautiful and probably only known to the locals. Lots of these places were a brisk walk away from high-traffic areas too. This…
That's great... but wouldn't satellite view be better for that anyways? Would you even trust an "interpreted" map with levels of green for what you're doing?
Re: Apple's New Map
#149Re: Apple's New Map
#150Earlier quoted context omitted.
I can't tell whether you're getting serious, but I'm pretty sure most users would not prefer your change. It's so dense it's hard to read, and in a repetitive way.
(Yes, totally serious.) For me, it's not hard to read. I'd prefer it, anyway. Still, if you wouldn't prefer it then we can see what the Google engineer meant, as this is exactly what you get if you show as much information as possible!