Switch from ellipsoidal to 2d cartesian distances #89
Conversation
This file contains 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
…hat QGIS elevation profile tool supports. By doing so, we ensure users won't get displaced profile graphs (too much difference between ellipsoidal and cartesian distances) not displaced exported features (using 3d cartesian distances, exported features won't match in the graph and will be displaced with respect to 2d distances calculated by the elevation profile tool)
gacarrillor
changed the title
3nids
approved these changes
May 27, 2024
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.
Because that's what QGIS elevation profile tool supports.
By doing so, we ensure users won't get displaced profile graphs (too much difference between ellipsoidal and cartesian distances) nor displaced exported features (using 3d cartesian distances, exported features won't match in the graph and will be displaced with respect to 2d distances calculated by the elevation profile tool).
Fix #86
Fix #87
For the record, this is the deviation when using 3d cartesian distances:
Points are exported features (distance/elevation table) from the profile, which have their Z coordinate. The elevation profile tool doesn't take these Z coordinates into account when calculating distances, so features appear displaced with respect to its correspondent 3d cartesian distance given by the Swiss locator calculation. As a result, we use 2d cartesian distances avoiding these displacements.