51–60 of 165 posts
Hmm. I saw the behavior you describe, but I also got the expected directions: https://maps.app.goo.gl/YpVHhPf1U9Ytu6U86
This smells like some weird caching, although I do most of my tests in an incognito window to minimize this.
"Is the parcel in the geographical bounds of the city name entered?" The "city name" on an address isn't really a "city". SFO's address is "San Francisco, CA", but is not within SF city limits. Queens NY addresses have "cities" that are just neighborhoods. Applying any kind of logic to addresses will just be a minefield.
In the logistics industry the commonly held wisdom is that there really isn't any accepted system for "how street addresses work". Different countries have completely different systems, and even within a country there are often many different conventions. The thing that really matters in delivery is whether the address on the consignment has enough information for an operator to complete the next leg. By the time an…
If my fixes had been published in the promised 24 hours then this blog post would not have been written but after two weeks this is the best idea I could come up with.
I think it is practical for Google Maps to understand the systems used in most major cities and then use this knowledge to reduce the number of errors.
I also think it is possible for the feedback system to work better. It does work sometimes, but it is slow and opaque and unreliable. It's even worse for bike directions.
Driving directions on the expressways here are also spotty. If I wait for Maps to tell me to exit the expressway, I'm already at or past the exit. I basically have to already kind of know where I'm going to make use of driving directions (you know, like we used to do with paper maps). Never mind that there are actual bugs in the directions: at one spot on the Ayer Rajah Expressway (AYE), if I need to exit onto the MCE, it tells me to exit onto the AYE, which is incorrect).
Still, I guess it's better than nothing.
"Is the parcel in the geographical bounds of the city name entered?" The "city name" on an address isn't really a "city". SFO's address is "San Francisco, CA", but is not within SF city limits. Queens NY addresses have "cities" that are just neighborhoods. Applying any kind of logic to addresses will just be a minefield.
The Pentagon's address even has the wrong state. The address is Washington, DC, but it's in Arlington, VA.
Google Maps has declined remarkably two or three years. It’s now an ML-brained mess. Like the rest of Google. Apple Maps is actually better now! That’s incredible.
I don't recall last time Google Maps made a mistake for me. I'm sure it has messy data. I don't envy developers that have to work with geography or timezones. And Google Map devs have to work with both. Ouch.
Google Maps is really bad when streets are even slightly unusual. That's even with North American address conventions, which are extremely regular by comparison to many nations.
For example, if you have both a North and a South version of a road, and the address numbering for North and South versions overlaps -- say, North and South begin at a county midline road and North increases going north and South increases going south -- it will irregularly put a pin on the wrong road or wrong segment of road.
Similarly, it will be confused if you have River Rd and West River Rd. And it can be confused when Oak Ln becomes Oak Ct or insist that Oak Ct is really Oak Ln even when the road name actually changes.
It also gets very confused by roads that have two names. For example if there's a county line road, the east county might call it "Franklin Rd" while the west county calls it "E County Line Rd." And in that case the east side of the road have one set of addresses, and the west have another set. Worse, the address numbers often don't align. Except that's not what Google screws up that often. Instead, Google will sometimes insist that one or the other road doesn't exist at all. It will say that 123 E County Line Rd is actually 123 Franklin Rd, and then it will put a pin where 123 would be on Franklin Rd if that road didn't begin its address numbering at 3000.
Sometimes it insists the city is incorrect, too. If your address is "123 Miller Rd, New London" and New London is a tiny unincorporated town near Portland, Google might translate the name to "123 Miller Rd, Portland." Sometimes even when there's a street the next county over with an address "123 Miller Rd, Portland". In this case if you enter the Portland address, it will point you to the address actually in Portland, and if you put in the New London address, it will show you the New London address... but it will still correct your New London address to Portland.
If you have a road with breaks in it, such as for a river without a bridge, it will occasionally just... put a pin at the end of one segment of the road and not find the address on the correct segment on the far side of the break.
About the only things that's really consistent is: If you zoom in and the pin is in the middle of the road, then Google Maps probably can't find the address. On the other hand, if the pin is off the road, then it's probably exactly on the structure based on the local or municipal authority and their GIS data. In that case, Google found the address on the GIS data they got from that municipality.
And you might say, "Oh, but those are really easily confusing things! It's entirely understandable." And, maybe that's true. But USPS's ZIP code finder still knows the addresses well enough to both find and correct them for you, and ArcGIS interfaces also seem to be able to find things much more easily. Google Maps was groundbreaking 20 years ago. But it really hasn't kept pace. The only thing that seems to confuse the other sites is new construction. At the very least, I wish Google Maps would be more clear when it's guessing rather than when it's found an exact match.
All that is to say, yes, we did use Google Maps to help find addresses. But when things looked even a little weird, we assumed that Google Maps was wrong. And it usually was wrong in those cases. And what it got wrong was sometimes really, really wrong.
So we now regularly get people driving down here or trying to park, when it's actually just a one-lane driveway.
In the logistics industry the commonly held wisdom is that there really isn't any accepted system for "how street addresses work". Different countries have completely different systems, and even within a country there are often many different conventions. The thing that really matters in delivery is whether the address on the consignment has enough information for an operator to complete the next leg. By the time an…