Record a route
Enable journey GPS logging and grant location access if you want route information. Without location, battery readings can still be useful, but maps and some distance or elevation information may be unavailable. A phone with poor reception can produce gaps even when permission was granted.
View a route map
Journey maps load OpenStreetMap tiles. Those requests go to a map service and need internet access. The service can receive your IP address and the tile area requested. A Wi-Fi adapter network with no internet can therefore show vehicle readings while map tiles fail to load.
Where the height comes from
The app prefers the recorded barometer-derived elevation where available, with GPS/GNSS information as another source. On Android, fresh GNSS height can replace a poor fused-location altitude. These sensors do not measure exactly the same thing: pressure-based change is relative to the journey start, while GPS height has its own reference and noise.
Terrain lookup is a fallback
When a finished journey has usable coordinates but no barometer height and missing or apparently frozen GPS altitude, opening its detail can trigger an Open-Meteo terrain lookup. Coordinates are sent to that service in batches, and returned heights are written into the local journey so it need not repeat a successful lookup.
Terrain is a model of the ground. It may not describe a bridge deck, tunnel or multilevel road accurately. If the request fails offline, the original data is kept and a later opening can retry.
Location and privacy
Disabling GPS for future journeys does not remove coordinates already recorded. Delete existing records separately if desired, and review CSVs before sharing. The app privacy policy explains map and elevation recipients; export and deletion covers local copies.