I was redoing my auxiliary dashboard (a Galaxy tablet running "Torque") when I noticed "GPS altitude" so I made it one of my gauges. It does work ! It seems to lag a good bit because a couple of times the altitude would go up even though I was regening down a hill. I live in a tiny Kentucky town, Science Hill, and make frequent trips to a larger town, Somerset KY. I make occasional trips to the nearest city, Lexington. At home the GPS shows 980 feet, in Somerset, 10 miles away, it's 820 feet. To get to Lexington I must climb to 1220 feet then descend to 740ft in Lexington. Now I understand why I get better mileage going to Lexington than on the return trip and why I use less EV miles getting to Somerset than returning.
My Garmin tells my altitude when I touch the vehicle icon, but I've never found it to be very accurate. It's usually off by 50m or more. My Galaxy Note 2 has a barometer to help compensate for such inaccuracies, but it's not been much of an improvement so far. The app I use let's me dial in the barometric pressure, which I get from a weather app. But it also seems to be off. I think there needs to be an overhaul of the GPS system to improve altitude accuracy.
Very true. The U.S. GPS system is optimized for accuracy in the "X-Y" plane, not the "Z" plane, at least in the public mode we have access to. The government and military has access to a more-accurate augmentation system that can locate in 3-D space to millimeter accuracy: GPS.gov: Augmentation Systems .
My BS meter went off scale at this one! GPS can have accuracy of inches with the proper equipment like that used in surveying, cruise missiles, commercial aircraft and drones. The accuracy is in 3 dimensions, in other words lat, long, ALTITUDE! The inaccuracies are due to the cheap and dirty implementations in consumer electronics. Yes GPS works by measuring time differences in microwave propagation from multiple satellites (up to 12 at once). From the time difference measurements and the orbital positions of the satellites a 3 dimensional location is calculated. The speed and precision of the calculations are what usually limits accuracy.
You point is well taken, but I think you must also consider the ability to time-average the GPS altitude estimates in any geostationary use. Averaging 100s of estimates over time will give far more accurate results. Estimating alt while driving is harder and while flying harder still as the situation is changing every second, sometimes quite dramatically. I have been evaluating the altitude estimates of a Bad Elf GPS Pro unit as some pilots use it for flight purposes. So far in "automobile" mode the estimates are unstable enough for me to not want to use it in an aircraft for precision approaches without a LOT more careful testing.
I'd like to see the source for the statement "The U.S. GPS system is optimized for accuracy in the "X-Y" plane, not the "Z" plane" as I believe it is simple BS. My understanding is that all 3 dimensions of a position estimate have equal uncertainty. Most consumer, commercial implementations simply don't bother refining the estimates of altitude. Early on in the history of GPS there was a deliberate reduction in available accuracy called "selective availability" but that ended during the first gulf war.
No BS here. I've used GPS equipment which can determine a position within 4 inches, but it cost $10,000 or more. It uses a number of algorithms for error-correction, and it took about 20 minutes of processing to achieve that accuracy. The same company (Trimble) offered a lower-cost model ($5000) could achieve about 8" accuracy with proprietary PC software which downloaded correction data from a number of base stations, with post-processing. Instead of calling "BS," I suggest you research the topic a bit. Consumer-grade GPS equipment can't compare with that used in surveying.
I think that would be true if the GPS receiver were a point in space surrounded by satellites scattered evenly in the X, Y, and Z directions. But an automobile GPS must cope with a hemisphere of available satellites at best, usually narrower than that, so I believe there is more uncertainty in the Z direction (alt), especially if one operates a car in an urban canyon. It is also quite possible that the solution algorithm can be adjusted to assume things like "only small changes in altitude per second" when solving for the X and Y locations. The Bad Elf's "aviation" mode setting (software selectable) may more evenly emphasize altitude along with latitude and longitude , but I cannot say for sure until I beg, buy, or borrow an airplane and go flying with it in that mode . But very important to do so before relying on its alt info on a dark and stormy night!
Robert, The process of estimating position is certainly easier when the position is static. All GPS receivers do some "filtering" to refine the position estimate some estimate vehicle motion and use that to "predict" the position estimates. For aircraft use vehicle velocity in all 3 dimensions needs to be part of the filtering algorithm. OTH for terrestrial navigation occasional updates of altitude are relatively adequate. Using a hikers GPS for unlimited hydroplane racing is as foolish as using an automotive GPS to fly an airplane.
Greg, You make my point completely! " triangulation from satellites, which it notoriously inaccurate." IS BS. With the proper equipment it is quite accurate. It is the cheap and dirty implementations that are notoriously inaccurate!
As much as I understand GPS receivers, the position is triangulated in orthogonal space (X-Y-Z). Those coordinates are then converted to spheric space (lat-long-elev) within GPS receiver. For the purpose of presentation only. Given X-Y-Z position of Earth center and X-Y-Z position of GPS receiver, latitude and longitude angles can be calculated quite straightforward by GPS receiver. However, calculating the elevation is a whole different story. Earth is not a perfect sphere. I remember, I've read somewhere, in order to approximate sea level elevation around the globe one would need to use a 2D polynomial of at least 28th order, which is an overkill for commercial GPS receivers to perform in real time. Since memory is cheap now-a-days, one would expect to have this problem solved with 2D lookup table stored in ROM by now. The end result is, the elevation is probably precise about the same as latitude and longitude, but it is not accurate. You just need to determine the offset for your area and your GPS receiver model manually. For calculating elevation difference within 500mi radius you should be fine using your GPS "altitude" measurement.