the end of a perfect record
Google Maps almost failed me this morning. That's never happened before. Those "M" guys used to get things wrong so much that I couldn't rely on them at all; they even managed to leave out a major state road once, telling me that I could exit the interstate and get onto such-and-such road that was miles and miles away. And those "Y" guys led me on some merry romps a couple times. But Google Maps had always given me what I needed with a smile and useful photos besides.
This morning I had to run an errand in Wilkinsburg before work. I don't particularly know the wilds of Wilkinsburg, but it's not the land of unnamed dirt roads or anything like that. I was a little surprised that Google's directions didn't actually have me turn onto the street named in the address, but a street number of "xxx02" is likely to be at a corner, so that seemed ok. So, armed with directions and Street View of the key intersections I didn't already know (Street View has made my life so much easier in this land of sometimes-inadequate road signs), I headed off... and at the end of the directions found myself at the end of a road facing an iron gate. Oops.
So I called my destination, told them where I was, and asked how to recover. How far was I from such-and-such road? Sorry, not from around here -- never heard of such-and-such road. Ok, I should go back to other-such-and-such road and... wait, never encountered that one on my way here. We went back and forth a couple times and I said I guessed I was going to have to reschedule and get better directions. I repeated what I had said at the beginning of the conversation: I was at the end of such-and-such road facing an iron gate with an "authorized personnel only" sign and no other markings.
Wait, the guy said, is it a blue sign? Yup. Could I see a white building beyond the gate? Yup. He told me to wait. A couple minutes later somebody came to open the back gate so I could drive in. Weird!
So it worked out in the end (costing me 10 minutes or so), but it was very puzzling.
This morning I had to run an errand in Wilkinsburg before work. I don't particularly know the wilds of Wilkinsburg, but it's not the land of unnamed dirt roads or anything like that. I was a little surprised that Google's directions didn't actually have me turn onto the street named in the address, but a street number of "xxx02" is likely to be at a corner, so that seemed ok. So, armed with directions and Street View of the key intersections I didn't already know (Street View has made my life so much easier in this land of sometimes-inadequate road signs), I headed off... and at the end of the directions found myself at the end of a road facing an iron gate. Oops.
So I called my destination, told them where I was, and asked how to recover. How far was I from such-and-such road? Sorry, not from around here -- never heard of such-and-such road. Ok, I should go back to other-such-and-such road and... wait, never encountered that one on my way here. We went back and forth a couple times and I said I guessed I was going to have to reschedule and get better directions. I repeated what I had said at the beginning of the conversation: I was at the end of such-and-such road facing an iron gate with an "authorized personnel only" sign and no other markings.
Wait, the guy said, is it a blue sign? Yup. Could I see a white building beyond the gate? Yup. He told me to wait. A couple minutes later somebody came to open the back gate so I could drive in. Weird!
So it worked out in the end (costing me 10 minutes or so), but it was very puzzling.

no subject
If you can say, I'm curious about the nature of the bug -- bad data for that specific address? A more general data-representation problem? Something else? And if that's not for public consumption that's cool; I'm just curious.
no subject
There's a bunch of machinery around that "area" issue to try to deal with it correctly, so users get the front entrance when they ask for directions. Some of that machinery got out of whack -- I don't even know more detail than that.