Skip to content

GNSS bundle - Elevations, transformations, providers - #727

Open
alex-cit wants to merge 18 commits into
mainfrom
iss_701-describing-providers
Open

GNSS bundle - Elevations, transformations, providers#727
alex-cit wants to merge 18 commits into
mainfrom
iss_701-describing-providers

Conversation

@alex-cit

@alex-citalex-cit commented Feb 19, 2026

Copy link
Copy Markdown
Contributor

fix#701

  • new page for elevations describing the providers and options
  • added note to height variables that they may not be available for all providers
  • List of known supported GPS devices updated: all "yes" for iOS devices set to "yes (mock)", fixed references in the table
  • plugin - option to define custom geoid / vertical crs

@alex-cit
alex-citforce-pushed the iss_701-describing-providers branch from e69ff61 to 562d0aaCompareFebruary 26, 2026 13:31
Comment threadsrc/gis/elevations/index.md Outdated
Comment threadsrc/gis/elevations/index.md Outdated
Comment threadsrc/gis/elevations/index.md Outdated
Comment threadsrc/gis/elevations/index.md Outdated
Comment threadsrc/gis/elevations/index.md Outdated
Comment threadsrc/gis/elevations/index.md Outdated
Comment threadsrc/layer/variables/index.md Outdated
Comment threadsrc/layer/variables/index.md Outdated
Comment threadsrc/layer/variables/index.md Outdated
Comment threadsrc/layer/variables/index.md Outdated
@alex-cit

Copy link
Copy Markdown
ContributorAuthor

Thanks @Withalion for the review! I tried to fix most of them. Could you please go over the variables descriptions if it's correct now? Thank you!

@WithalionWithalion left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The variables description looks alright now!

Comment threadsrc/gis/elevations/index.md
@alex-cit
alex-citforce-pushed the iss_701-describing-providers branch from b63c5c4 to 4a4e739CompareJune 10, 2026 10:28
@alex-cit

alex-cit commented Jun 10, 2026

Copy link
Copy Markdown
ContributorAuthor

rebased and:

  • added info about EPSG:4979
  • "custom geoid" renamed to "custom vertical reference system" as I think this is more consistent with the plugin (the setup in plugin is named "Vertical CRS"
  • we will need to update the screenshot used in https://merginmaps.com/docs/manage/plugin/#mergin-maps-project-properties , so that it includes both filtering and vertical CRS setup (for now I left the current screenshots with filtering that do not contain vertical CRS)

Comment threadsrc/gis/elevations/index.md Outdated
## Internal provider (no external device)

### Android
On Android, the [internal (fused)](../../field/mobile-app-ui/#gps-settings) GPS provider is used by default. It reports ellipsoidal heights that <MainPlatformName /> transforms to **orthometric heights using the EGM96 geoid model** by default and displays them in the [GPS info panel](../../field/mobile-app-ui/#current-position-and-gps-info).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While technical correct wouldn't the wording here be better to switch it up?

It reports ellipsoidal heights that transforms to orthometric heights using the EGM96 geoid model by default and displays them in the GPS info panel.

"It reports orthometric heights transformed from ellipsoid heights..."

Comment threadsrc/gis/elevations/index.md Outdated

![Mergin Maps QGIS plugin datum transformation warning](./plugin-transformation-warning.webp "Mergin Maps QGIS plugin datum transformation warning")

To make sure that <MainPlatformName /> uses the correct operation, make sure that the datum transformation you want to used is defined in the **Transformations** tab in **Project Properties**.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make sure that the datum transformation you want to used is defined in the

missing word?

Comment threadsrc/layer/variables/index.md Outdated
- for internal GPS, returns "internal"
- for external GPS, returns "external"
- for internal GPS, returns `internal`
- for [external GPS](../../field/external_gps/), returns `external`

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this doc is also including the changes from network provider feature, then this either returns external_ip or external_bt.

Comment threadsrc/layer/variables/index.md Outdated
- for internal GPS, returns "<NoSpellcheck id="devicegps" />"
- for external GPS, returns the MAC address
- for internal GPS, returns `devicegps`, `android_fused` or `android_gps`
- for [external GPS](../../field/external_gps/), returns the MAC address

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

continuing from the comment above. This should return MAC address for Bluetooth devices and IP address with port for network devices

@alex-citalex-cit mentioned this pull request Jun 22, 2026
Comment threadsrc/field/external_gps/index.md Outdated
| Emlid | Reach RX models<sup><a href="#link-2">2</a></sup> | yes | yes (mock location) |
| Emlid | Reach RS models<sup><a href="#link-3">3</a></sup> | yes | yes |
| EOS | Skadi models<sup><a href="#link-11">11</a></sup> | yes | yes |
| EOS | <NoSpellcheck id="Skadi" /> models<sup><a href="#link-11">11</a></sup> | yes | yes |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not adding this to the wordlist instead? I think it is already there (on main branch)


There are some differences in the functionality and available details depending on the GPS provider, the OS of the mobile device and the connection setup, namely the type of elevation provided, available [position variables](../../layer/variables/#position-variables) and whether it is possible to use [custom vertical reference system](#custom-vertical-reference-system).

## Internal provider (no external device)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we using the "provider" term anywhere else in the docs? I am thinking "source" or "receiver" is more clear

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GNSS enhancements bundle

3 participants

@alex-cit@tomasMizera@Withalion