-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify the replacement for MD_ReferenceSystem #57
Comments
Proposal applied on Description of the spatial and temporal reference systems used in the dataset. The reference system may be:
|
…roposal of Metadata.reference_system_info specification. The question about what should be MD_ReferenceSystem type is discussed in #57
ISO 19115-1:2014/Amd 2:2020 adds the following properties in
If we keep the current GeoAPI approach, which is to use |
ISO 19115-1 figure 12 defines
MD_ReferenceSystem
with two properties: anIdentifier
and aMD_ReferenceSystemTypeCode
(a code list - see #50). A note said: "Refer to SC_CRS in ISO 19111 when coordinate reference system information is not given through reference system identifier." However there is no details about how to reference ISO 19111. In particularMD_ReferenceSystem
has no field forSC_CRS
.In order to allow reference to ISO 19111 and also in order to reduce overlapping between standards, GeoAPI 3.0 uses ISO 19111
RS_ReferenceSystem
instead of ISO 19115MD_ReferenceSystem
. It allows us to reference ISO 19111 sinceSC_CRS
is a subtype ofRS_ReferenceSystem
. If user wants to specify only the identifier, this is possible by usingReferenceSystem.getIdentifiers()
. There is currently no way to get the CRS type however, except the way described in #50.We should clarify the following:
SC_CRS
).ReferenceSystem
type appears in:base.py
:Metadata.reference_system_info
(as a sequence)representation.py
:GCPCollection.coordinate_reference_system
lineage.py
:Source.source_reference_system
The text was updated successfully, but these errors were encountered: