Comment by drob518
17 hours ago
It’s gotten a lot better, but I still find the address database better in Google Maps, which helps when you have only a fragment of an address. I also find that the Apple Maps database has a lot of roads that read the same. For instance, in Texas where I live, we have a lot of “Ranch Roads” that are numbered. Think of them like state highways in other state (which we also have; don’t ask). For whatever reason, most of the Ranch Roads are spoken by Maps as “Ranch Road,” not with the number. So, if you have a spot where multiple Ranch Roads intersect, Maps will just say “turn left on Ranch Road” instead of “turn left on Ranch Road 123.” It’s tremendous annoying. In another state, imagine it saying “turn left on Interstate,” without a number. Anyway, Google Maps does better.
Google is not without its errors.
I used to work to resolve addressing disputes and google just doesn't expose (maybe even store) the relevant information for a lot of parcels of land.
It’s all available freely from the government in simple formats but for Joe Public they don’t know that much less how to access it and it’s the case that technicians on the ground don’t always have it in their SOP either. Google has a level of market dominance that means their errors can be, for a small individual or over an aggregation of small individuals, costly.
Addresses are hard. OSM Nominatim struggles with them all the time. Probably the biggest hurdle to OSM adoption, imo
Yep, they all have flaws. I just fine that when I want to drive somewhere, Google does better for me than Apple, though certainly Apple has improved a lot recently.
actually a sign of our times that we can gripe about this. i remember how annoying it was to rent a car on a business trip without anything other than a road atlas. you had to dedicate a fair bit of cognitive load you really didnt want to use.
3 replies →
Google Maps often picks the non-idiomatic thing. It'll say the road name when no sign uses that, and it's a US highway that you have been following for a while. Or it will tell you the state highway number when it is a major named artery, and nobody knows that it is a state highway at that point or uses the highway number. This makes it hard to know if it is carrying you along on the same route or if it has come up with one of its weird shortcuts to save 1 minute.
It has absolutely no clue about roundabouts. On a journey in England or France on a road that has a roundabout every mile it will constantly spam you with "take the second exit onto wailing street" every minute, when a human would say "go straight at the next 20 roundabouts staying on the A38".
You're not wrong that it does that, but that's kinda what I'd expect. Maybe because I'm used to it, but if there's a potential turn it'll say "keep right" or "keep left". So it makes sense to me that it says "second exit".
"Straight" can be ambiguous, second exit isn't. Maybe it's because I'm terrible with directions and hate driving, but I like the constant feedback that I'm going the right way.
I once printed out a directions from an online map that contained "pass straight over the next fourteen roundabouts" (I think it was on the way into Reading). Lose count, and you are stuffed. I much prefer a turn-by-turn approach.
Here in Australia Apple Maps names everywhere by local council, which isn’t used at all, we use localities. I have reported this as a bug repeatedly but they just keep at it.
It just means nothing here except who you pay to collect the bins.
Salt Lake City roads are amusing
"Turn right on East one hundred and twenty three thousand South"
Salt Lake City is a perfect grid, better than Manhattan. An address in SLC tells you EXACTLY where it is. It was GPS before GPS.
Yep, that’s sometimes true as well.
I hate how Google scrapes business addresses so you get like "There's a grocery store X here" but actually that's just their corporate office building. I see that all the time. Machines just don't know.