3 ms·

Working great in Bay Area? Who told you that? I was under impression that this all similar to "antena gate" (kinda not big deal), but iOS maps are really reall

by tlogan 14y ago

Working great in Bay Area? Who told you that? I was under impression that this all similar to "antena gate" (kinda not big deal), but iOS maps are really really bad even in Bay Area. EDIT: Here is an example: Search for "428 University Ave, Palo Alto": you will end up in Los Gatos.

awolf 14y ago
Not in my experience. It's fine here, at least in the city and in Berkeley. No problems aside from a few addresses needing me to add "sf" to them to avoid having them go to different cities (which sometimes also occurred with Google's map data). I'm working on a routing/location based app right now. Out of curiosity could you give examples of what you mean by "really bad"?
awolf 14y ago
Ah, I see that too. Clearly problematic since there doesn't seem to be a way at all to load up the intended 428 University Ave address. No good. Still though, "really really bad" makes me think you have experienced many other issues. I'm genuinely curious about how Maps performs in the places it is "supposed" to be at least passable. Got any other examples? Meta: please don't edit your comments to respond to sub-comments. It makes the flow of the conversation very difficult to follow and makes my previous comment seem irrelevant and out of place.
- spinchange 14y ago
  Both David Pogue and Anil Dash have written about getting driving directions that takes them to the wrong location in places like New York city. I'm just one user, but if a navigation app takes you the right address in the wrong location in a place like the Bay area or NYC, that's a "really bad" problem.
cwe 14y ago
Ironic that as I tested out that address example, I noticed an Apple story across the street from the actual address.
st0p 14y ago
I didn't say it was working great in Bay Area, the person I responded to did... But apparently even that is not true.
myko 14y ago
"Antennagate" wasn't a big deal? When my wife used her iPhone 4 it would drop calls constantly (pretty decent AT&T coverage, Columbus, Ohio). She even had it replaced due to the issue (which wasn't fixed until she put a case on it).

by tlogan 14y ago

awolf 14y ago

Not in my experience. It's fine here, at least in the city and in Berkeley. No problems aside from a few addresses needing me to add "sf" to them to avoid having them go to different cities (which sometimes also occurred with Google's map data). I'm working on a routing/location based app right now. Out of curiosity could you give examples of what you mean by "really bad"?

awolf 14y ago

Ah, I see that too. Clearly problematic since there doesn't seem to be a way at all to load up the intended 428 University Ave address. No good. Still though, "really really bad" makes me think you have experienced many other issues. I'm genuinely curious about how Maps performs in the places it is "supposed" to be at least passable. Got any other examples? Meta: please don't edit your comments to respond to sub-comments. It makes the flow of the conversation very difficult to follow and makes my previous comment seem irrelevant and out of place.

spinchange 14y ago
Both David Pogue and Anil Dash have written about getting driving directions that takes them to the wrong location in places like New York city. I'm just one user, but if a navigation app takes you the right address in the wrong location in a place like the Bay area or NYC, that's a "really bad" problem.

cwe 14y ago

Ironic that as I tested out that address example, I noticed an Apple story across the street from the actual address.

st0p 14y ago

I didn't say it was working great in Bay Area, the person I responded to did... But apparently even that is not true.

myko 14y ago

"Antennagate" wasn't a big deal? When my wife used her iPhone 4 it would drop calls constantly (pretty decent AT&T coverage, Columbus, Ohio). She even had it replaced due to the issue (which wasn't fixed until she put a case on it).