Add support for specific vertical CRS definition #841
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Moving to draft as there is missing mobile client implementation. |
This was referenced Nov 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the mobile app we currently use ellipsoid elevation. With the work coming in MerginMaps/mobile#4234 we will start using orthometric (geoid) heights. However, we will use only EGM96 geoid model by default, which will be bundled by app, to recalculate incoming values. This PR adds the option for QGIS admins to set a different vertical CRS and also bundle that model with the project (it's necessary).
Default value:
Custom vertical CRS:
Testing:
us_nga_egm08_25.tif(EGM2008 model) can be used for testing, it should be in localprojfolder or can be downloaded here