Altitude displays N/A in GPS Info panel when antenna height contains an invalid (NaN) value
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start by locating the GPS Info panel and the code that combines antenna height with altitude, then reproduce the issue with an invalid antenna-height value for both internal and external GPS. Done means the panel still shows the raw GPS altitude or a clear invalid-height warning instead of N/A; verify the result on iOS and Android paths.
Written by the indexing model from the issue text.
Description
Description
When the antenna height field contains a NaN (Not a Number / invalid non-numeric) value, the Altitude field in the GPS Info panel displays N/A instead of the actual GPS altitude. This affects both internal and external GPS connections and is reproducible on both iOS and Android.
Environment
[x] Staging
Application (+ app version, build, operating system)
Mergin Maps Mobile App
- iOS version: 2025.6.0 — iOS 26.0 / iOS: 26.6.921312
- Android version: 2025.6.0 — Samsung Galaxy A53 5G, Android 15
Steps to reproduce
- Open the Mergin Maps mobile app.
- Navigate to the GPS Info panel.
- Set the antenna height field to an invalid or non-numeric value (NaN).
- Observe the Altitude field in the GPS Info panel.
- Repeat with both internal GPS and an external GPS receiver.
Actual results
The Altitude field in the GPS Info panel displays N/A when the antenna height contains an invalid (NaN) value. This occurs for both internal and external GPS connections.
Expected results
The Altitude field should display the actual GPS altitude regardless of the antenna height value. If the antenna height is invalid, the app should either:
- Fall back to displaying the raw GPS altitude without antenna height correction, or
- Display a clear warning that the antenna height value is invalid, while still showing the GPS altitude.
Screenshots or logs
(Please attach screenshots or relevant logs if available)
https://github.com/user-attachments/assets/ac255cc5-1bc8-4b1a-b24a-bbf2626e5c7a
Conclusion
Created by Claude and supervised by a human test analyst.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 23
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MerginMaps/mobile
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
MerginMaps/mobile#4669 ·
-
bug Good first issue ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MerginMaps/mobile#4665 ·
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MerginMaps/mobile#4647 · 1 comment ·
-
enhancement sync
MerginMaps/mobile#4713 · 2 assignees ·
-
enhancement performance qgis
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MerginMaps/mobile#4701 ·
All issues in MerginMaps/mobile
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google/libultrahdr#485 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
godotengine/godot#123776 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 60/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/common_interfaces#344 ·