Initial support for ISO19111 CoordinateMetadata class #3562
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
rouault
changed the title
rouault
force-pushed
the
coordinateMetadata
branch
6 times, most recently
from
e70473e
to
95013a1
Compare
…epoch(), support if in proj_create() and proj_get_source_crs()
…nciate a CoordinateMetadata
…tadata but not both. Note also that the core of createOperations() does not take into account the source/target coordinate epoch in its logic to infer pipelines. It just keep those values in its metadata, so that PJ* objects constructed from them can later override the PJ_COORD.xyzt.t component. So basically this is currently useful only for transformations between a dynamic CRS and a static CRS (or the reverse).
rouault
force-pushed
the
coordinateMetadata
branch
from
95013a1
to
76959be
Compare
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.
CoordinateMetadata: add C++ class, WKT and PROJJSON support
C API: add PJ_TYPE_COORDINATE_METADATA, proj_coordinate_metadata_get_epoch(), support if in proj_create() and proj_get_source_crs()
createFromUserInput(): accept 'CRS_name@decimal_year' syntax to instanciate a CoordinateMetadata
createOperations(): support one of source/target to be a CoordinateMetadata but not both.
Note also that the core of createOperations() does not take into account
the source/target coordinate epoch in its logic to infer pipelines. It
just keep those values in its metadata, so that PJ* objects constructed
from them can later override the PJ_COORD.xyzt.t component.
So basically this is currently useful only for transformations between a
dynamic CRS and a static CRS (or the reverse).