How to take a reading 01 Start on a secure page. Geolocation requires HTTPS; on an insecure origin the panel explains the block instead of failing silently. 02 Allow location. The panel asks for high accuracy with a 20-second timeout and no cached positions, then watches continuously. 03 Read the fix card. Latitude and longitude with the horizontal accuracy, for example the demo walk's ±4 m. 04 Move to see speed and heading. Device speed and heading appear when the receiver reports them; stationary, both read as unavailable rather than zero. 05 Reset or copy. Reset clears the trip, copy puts lat, lon on the clipboard.
Worked example A four-fix demo walk — a start at 39.9042° N, 116.4074° E plus three moves of 0.000055° north and east each, accuracy ±4 m:
Step
Distance (haversine)
Counted at ±4 m
Counted at ±60 m
Speed if 0.5 s apart
Speed if 1 s apart
1
7.7079 m
7.7079 m
0 m
15.4159 m/s
7.7079 m/s
2
7.7079 m
7.7079 m
0 m
15.4159 m/s
7.7079 m/s
3
7.7079 m
7.7079 m
0 m
15.4158 m/s
7.7079 m/s
Trip total: 23.1237 m . The same arithmetic converts cleanly to the speedometer's units: 7.7079 m/s is 27.7484 km/h or 17.2421 mph , and 2 m/s is 7.2 km/h or 4.47388 mph . Headings round to the 16-point rose: 0° reads N , 236.25° reads WSW , and the boundary case 348.74° reads NNW while 348.75° already reads N . The engine's spherical distance gives 111.1951 km for one degree of longitude at the equator and 1067.312 km for Beijing to Shanghai.
Why the panel gates, smooths and ages Every fix is a probability circle, not a point: the accuracy value is a radius within which the true position is expected with roughly 95% confidence, so consecutive stationary fixes can differ by several metres. The panel refuses to integrate that jitter: a step counts only when the fix is better than 50 m and the displacement is at least max(1.5 m , 0.3 × accuracy ). On the demo walk all three legs pass; a 1 m wobble at ±4 m is discarded, and a 5 m wobble at ±20 m is discarded too because the threshold rises to 6 m. When the device supplies no speed, the panel derives it as distance over time between accepted fixes, and only when the two fixes are more than 0.2 s apart; the fix-age card turns amber past 10 s so a stale position is never read as live. Heading is likewise only meaningful in motion; the Web API reports it as unavailable when stationary.
Limits and what it does not do
A confidence circle, not a satellite list. The browser API exposes no satellite count, HDOP or fix source, so the panel cannot say whether the fix came from GNSS, Wi-Fi or a cell tower; indoors, accuracy degrades to tens of metres and speed and heading usually go missing.
Spherical distance. Trip legs use the haversine formula on a mean-radius sphere, which is accurate to about 0.5% — excellent for a walk, not a survey; positions are WGS-84. What it does not do. It does not map, route or record to a file, and it does not convert datums — for AMap/Baidu coordinates use Coordinates , for instrument tilt the Level panel , and for magnetic north the Compass .
The trap: standing still does not mean zero distance Without a gate, a stationary receiver accumulates a random walk: two fixes 1.5 m apart look like a step, and a hundred of them add a phantom kilometre to the trip. The panel's 0.3 × accuracy rule exists exactly for that. The inverse trap is over-confidence: an accuracy of ±4 m does not mean each fix is wrong by at most 4 m, and it says nothing about the altitude, whose vertical accuracy is typically two to three times worse and is printed separately. Finally, a device-reported speed is not derived from the same two fixes — it comes from the receiver, so a sudden mismatch between the chart and the position line is information, not a glitch.
Where it is used Running, cycling and driving Leave the panel open and read trip distance, maximum and average speed against elapsed time; the speed chart shows surges and stops that an average hides. The count of fixes tells you how steady the sampling was.
Field notes with coordinates Copy a fix as lat, lon with its accuracy for a photo, a sample or an incident log — a coordinate without its radius is only half the measurement.
Privacy Your position is processed in the browser and never uploaded; the copy button and the trip counters work entirely on this device, and the page stores no track.
References
W3C, Geolocation API Specification — coordinates, accuracy, speed, heading. w3.org (访问日期:2026-10-07)
Wikipedia, Global Positioning System — trilateration and error sources. en.wikipedia.org (访问日期:2026-10-07)
GPS.gov, The Global Positioning System — system segments and how GPS works. gps.gov (访问日期:2026-10-07)
Wikipedia, Circular error probable — the confidence radius. en.wikipedia.org (访问日期:2026-10-07)
Wikipedia, Haversine formula — great-circle distance. en.wikipedia.org (访问日期:2026-10-07)
Calculators in this hub
Hand-picked tools, one click away. The mini versions compute live and carry your values into the full calculator.
Sources & review
Reviewed by CalcX Editorial Team
Updated 2026-10-07