Comments (7)
Using wording similar to TG Recommendation C.8: metadata/2.0/rec/common/use-anchors-for-cv-keywords, the requirements (TG Requirement 2.2: metadata/2.0/req/isdss/crs-id and TG Requirement 6.2: metadata/2.0/req/sds-interoperable/crs-http-uris) could be restated as something like:
If the coordinate reference system is listed in the table Default Coordinate Reference System Identifiers in Annex D.4, the gmd:referenceSystemInfo/gmd:MD_ReferenceSystem/gmd:referenceSystemIdentifier/gmd:RS_Identifier/gmd:code element shall be encoded using a gmd:keyword/gmx:Anchor element. The xlink:href attribute of the gmx:Anchor element shall be the value of the HTTP URI Identifier column.
This wording would actually make the requirement stricter that is currently is. Currently, both of the following are allowed.
<gmd:referenceSystemInfo>
<gmd:MD_ReferenceSystem>
<gmd:referenceSystemIdentifier>
<gmd:RS_Identifier>
<gmd:code>
<gmx:Anchor xlink:href="http://www.opengis.net/def/crs/EPSG/0/4258">EPSG:4258</gmx:Anchor>
</gmd:code>
</gmd:RS_Identifier>
</gmd:referenceSystemIdentifier>
</gmd:MD_ReferenceSystem>
</gmd:referenceSystemInfo>
<gmd:referenceSystemInfo>
<gmd:MD_ReferenceSystem>
<gmd:referenceSystemIdentifier>
<gmd:RS_Identifier>
<gmd:code>
<gco:CharacterString>http://www.opengis.net/def/crs/EPSG/0/4258</gco:CharacterString>
</gmd:code>
</gmd:RS_Identifier>
</gmd:referenceSystemIdentifier>
</gmd:MD_ReferenceSystem>
</gmd:referenceSystemInfo>
See also the following lines of code: https://github.com/inspire-eu-validation/ets-repository/blob/3ed17ef069b758420063fadb9c6872e4ff26dfa9/metadata/2.0/datasets-and-series/ets-md-isdss-bsxets.xml#L114-L142, especially these two lines: https://github.com/inspire-eu-validation/ets-repository/blob/3ed17ef069b758420063fadb9c6872e4ff26dfa9/metadata/2.0/datasets-and-series/ets-md-isdss-bsxets.xml#L131-L132.
A possible solution could be to add two new TG recommendations (one after TG Requirement 6.2 2.2 and one after TG Requirement 6.2):
If the coordinate reference system identifier is an HTTP URI, this identifier should be encoded using a
gmx:Anchor
element; thexlink:href
attribute of thegmx:Anchor
element should contain the identifier.
For some metadata elements, the use of gmx:Anchor
is required (e.g. TG Requirement C.17: metadata/2.0/req/common/limitations-on-public-access), but for most metadata elements, the use of gmx:Anchor
is only recommended (e.g. the aforementioned TG Recommendation C.8: metadata/2.0/rec/common/use-anchors-for-cv-keywords).
Note: should the Short name from the table in D.4 be encouraged, so as to separate between the various ETRS89s? Or (as per the example), the EPSG code in its simpler form?
Some guidance would probably be good. There is indeed the AUTHORITY:CODE option, and then there are also the name and aliases listed on https://epsg.org (the INSPIRE identifiers are usually listed as aliases, it seems). So for http://www.opengis.net/def/crs/EPSG/0/4258, all the following could be used:
- ETRS89 (perhaps not the best choice indeed...)
- ETRS89-GRS80
- EPSG:4258
Perhaps we should keep the establishment of a CRS registry in mind (see e.g. INSPIRE-MIF/helpdesk-registry#79), so we should avoid wording referring to the static table ("Short name from the table in D.4"), and use more general wording ("name or alias from a common register").
from technical-guidelines.
The INSPIRE MIG approved the change proposal, since no objections were raised during the two week scrutiny period from October 12 to October 26, 2021. The change can be now implemented.
from technical-guidelines.
Meeting 16.9:
- agreement
- emphasize that the guidance is just informative text (not a recommendation)
from technical-guidelines.
Summarized:
3.2.1.1 Coordinates reference systems
[...]
TG Requirement 2.2: metadata/2.0/req/isdss/crs-id (kept as is)
If the coordinate reference system is listed in the table Default Coordinate Reference System Identifiers in Annex D.4, the value of the HTTP URI Identifier column shall be used as the value of gmd:referenceSystemInfo/gmd:MD_ReferenceSystem/gmd:referenceSystemIdentifier/gmd:RS_Identifier/gmd:code
element.The gmd:codeSpace
element shall not be used in this case.
TG Recommendation x.y: metadata/2.0/rec/isdss/crs-id (new)
If the coordinate reference system identifier is an HTTP URI, this identifier should be encoded using a gmx:Anchor
element; the xlink:href
attribute of the gmx:Anchor
element should contain the identifier.
(new text)
As explained in section 2.1.1 Encoding of code list values, the textual content of the gmx:Anchor
element is purely informative. A possibility in the case of coordinate reference system identifiers is to use either the name (e.g. ETRS89) or one of the aliases (e.g. ETRS89-GRS80) of the CRS as available in the EPSG Geodetic Parameter Dataset. Another possibility is to use a short name in the form of AUTHORITY:CODE (e.g. EPSG:4258).
[...]
4.4.1.1 Coordinate Reference System Identifier
[...]
TG Requirement 6.2: metadata/2.0/req/sds-interoperable/crs-http-uris (kept as is)
If the coordinate reference system is listed in the table Default Coordinate Reference System Identifiers in Annex D.4, the value of the HTTP URI Identifier column shall be used as the value of gmd:referenceSystemInfo/gmd:MD_ReferenceSystem/gmd:referenceSystemIdentifier/gmd:RS_Identifier/gmd:code
element.The gmd:codeSpace
element shall not be used in this case.
TG Recommendation x.y: metadata/2.0/rec/sds-interoperable/crs-http-uris (new)
If the coordinate reference system identifier is an HTTP URI, this identifier should be encoded using a gmx:Anchor
element; the xlink:href
attribute of the gmx:Anchor
element should contain the identifier.
from technical-guidelines.
The INSPIRE MIG-T approved the change proposal during the 67th MIG-T meeting. In the next step, the proposal will be moved to the MIG for the final endorsement.
from technical-guidelines.
Postponed to milestone 2022.2 in order to solve issue INSPIRE-MIF/helpdesk#32 and provide a consistent pull request
from technical-guidelines.
TG Recommendation x.y: metadata/2.0/rec/isdss/crs-id (new)
If the coordinate reference system identifier is an HTTP URI, this identifier should be encoded using a gmx:Anchor element; the xlink:href attribute of the gmx:Anchor element should contain the identifier.
The new TG Recommendation in section 3.2.1.1 Coordinates reference systems has been numbered as "TG Recommendation 2.1.1" (introducing the third level) so as not to alter the numbering of subsequent recommendations.
from technical-guidelines.
Related Issues (20)
- SU - Vector - Changes from 1089 amendment
- SU - Grid - Changes from 1089 amendment
- SO - Changes from 1089 amendment
- LU - Planned Land Use - Changes from 1089 amendment
- HH - Changes from 1089 amendment
- All data specifications - Add paragraph in Article 7 HOT 1
- AD - Changes from 1089 amendment
- TN - Air - Changes from 1089 amendment
- TN - Railway - Changes from 1089 amendment
- TN - Water - Changes from 1089 amendment
- US - Administrative And Social Governmental Services - Changes from 1089 amendment
- EF - Changes from 1089 amendment
- PF - Changes from 1089 amendment
- AF - Changes from 1089 amendment
- SR - Changes from 1089 amendment [1]
- SR - Changes from 1089 amendment [2]
- View Services TG - Deprecate WMS 1.1.1 HOT 2
- LU - Correct broken link HOT 2
- GE - Major update of TG to version 3.3 HOT 2
- TG Recommendation 1.11: metadata/2.0/rec/datasets-and-series/uri-for-regulation-1089-2010 : URI no more suitable HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from technical-guidelines.