Basic support for coordinate epoch of dynamic (non-plate fixed) crs #43143
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
Returns TRUE if the given proj coordinate system is a dynamic CRS. A dynamic CRS relies on a dynamic datum, that is a datum that is no plate-fixed.
…n widget - geographic/non geographic and map units - whether crs is dynamic or not - ensemble details
|
att @rouault |
rouault
reviewed
May 9, 2021
|
@rouault good to merge now? |
rouault
approved these changes
May 10, 2021
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.
Adds basic support for coordinate epoch to QgsCoordinateReferenceSystem, keeping us in step with OSGeo/gdal#3810
Missing parts so far (will be addressed in followup PRs):