关于Geolocation API海拔数据偏差及GeolocationCoordinates.altitudeAccuracy返回undefined的技术咨询

Hey Tom, let’s break down your two questions about the Geolocation API—they’re both common quirks with straightforward explanations!

一、为什么获取的海拔总是远高于Google Maps的数值？ #

First off, this isn’t a bug—it’s a difference in reference frames that trips up a lot of developers. Here’s the breakdown:

• The GeolocationCoordinates.altitude value you’re getting is an ellipsoidal height, measured against the WGS84 reference ellipsoid (a mathematical model of the Earth’s shape). This is what GPS chips natively output.
• Google Maps displays orthometric height, which is measured against the geoid (a surface that matches average sea level across the globe). This is the "real-world" elevation we’re used to seeing.

The gap between these two values is called the geoid height. In your case, the geoid in your location is roughly 71 meters below the WGS84 ellipsoid—so 44m (orthometric) + 71m (geoid height) = 115m (ellipsoidal). The "twice as high" observation is just a coincidence for your specific location, not a universal rule.

If you need to match Google Maps’ elevation, you’ll need to convert the ellipsoidal height using a geoid model like EGM96 or EGM2008. There are open-source GIS libraries or offline lookup tables that can handle this conversion.

二、为什么altitudeAccuracy总是返回undefined？ #

This usually boils down to hardware limitations, positioning sources, or browser implementation choices:

• Hardware constraints: Many consumer devices (including some smartphones) have GPS chips that calculate altitude but don’t report accuracy metrics. The hardware simply isn’t built to output that data.
• Non-GPS positioning: If your device is using WiFi or IP-based location (instead of its built-in GPS), these methods can’t provide reliable altitude data at all, so altitudeAccuracy will be undefined.
• Browser behavior: Some browsers will return undefined for altitudeAccuracy if the GPS signal is weak (e.g., indoors, surrounded by tall buildings) and the system can’t calculate a reliable accuracy value.
• API implementation gaps: Not all browsers handle the Geolocation API identically—some skip returning altitudeAccuracy even when the hardware supports it, due to implementation choices.

To troubleshoot, check your device’s location settings to confirm it’s using GPS (not network positioning). If it is and you still get undefined, it’s likely a hardware limitation that can’t be fixed with code.

内容的提问来源于stack exchange，提问作者Claus Ginsel