Entry tags:
two dimensions out of three
It's funny to see (well, hear) my phone's navigator app react to parking garages. "Do X... oh ok you're going north so do Y... oh you're going west so do Z... oh you're going south do A... oh you're going east do X which I'll pretend I haven't said before..." -- iterate until you reach the exit. It doesn't respond to elevation, only latitude/longitude.
I can think of three possible reasons for this, and I wonder which it is (or if it's something else I haven't thought of):
1. The GPS in the phone doesn't detect altitude.
2. The map data (Google's, in this case) doesn't record elevation. It does you no good to know that the GPS is at a certain elevation if the app can't tell that that's 200 feet above the road, after all.
3. The GPS and map data are available, but the app isn't programmed to take it into account. How often does this really come up, after all?

I can think of three possible reasons for this, and I wonder which it is (or if it's something else I haven't thought of):
1. The GPS in the phone doesn't detect altitude.
2. The map data (Google's, in this case) doesn't record elevation. It does you no good to know that the GPS is at a certain elevation if the app can't tell that that's 200 feet above the road, after all.
3. The GPS and map data are available, but the app isn't programmed to take it into account. How often does this really come up, after all?


no subject
If they do support it, I hope they maintain test coverage. :)