-
-
Notifications
You must be signed in to change notification settings - Fork 487
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
INSPIRE / Add TG2 support #3399
Conversation
Configure INSPIRE view * Encode resource identifier using Anchor * Configure thesaurus to encode using Anchor for INSPIRE theme and classification of spatial data service * Encode CRS using Anchor
… INSPIRE TG2) Still need to keep it encoded as Anchor in thesaurus-transformation.xsl
@fxprunayre we are working in the Dutch profiles in similar stuff and also for Sweden have done similar stuff for their profile, let's discuss how to contribute to this. |
The quality conformance section would typically state which version of TG is supported, maybe we can use this value to show/hide a TG1 or TG2 view? Also interesting is a suggest function that updates a record from TG1 to TG2 |
tooltip="gmd:code|gmd:MD_Identifier"/> | ||
</values> | ||
<snippet> | ||
<gmd:identifier> | ||
<gmd:MD_Identifier> | ||
<gn:copy select="gmd:authority"/> | ||
<gmd:code> | ||
<gco:CharacterString>{{code}}</gco:CharacterString> | ||
<gmx:Anchor xlink:href="{{code}}"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you're not using the label of the code here?
@@ -725,7 +734,7 @@ | |||
<gmd:referenceSystemIdentifier> | |||
<gmd:RS_Identifier> | |||
<gmd:code> | |||
<gco:CharacterString>http://www.opengis.net/def/crs/EPSG/0/4936</gco:CharacterString> | |||
<gmx:Anchor xlink:href="http://www.opengis.net/def/crs/EPSG/0/4936">EPSG:4936</gmx:Anchor> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it make sense to introduce a thesaurus for these references, a user can then easily add values to the thesaurus if wants to add (national) projections
Related to #3638 |
Anyone having a TG2 schematron ? maybe done in some profiles that we can use in GeoNetwork too ? or should we now rely only on ETF to validate for INSPIRE ? @josegar74 @pvgenuchten |
Closing as 3.8.2 can support INSPIRE TG2 records as documented in https://geonetwork-opensource.org/manuals/3.8.x/en/user-guide/describing-information/inspire-editing.html |
List of changes required for better INSPIRE TG2 support
Documentation
https://geonetwork-opensource.org/manuals/3.8.x/en/user-guide/describing-information/inspire-editing.html
XSD
Encoding
Anchor support
Fields can be populated from a thesaurus and be encoded using Anchor (see Editor / Add configuration for field to use a thesaurus. #3078).
Any text element (including multilingual) can be using Anchor; currently not easy to add an URL
Codelist attribute
Thesaurus
CRS
Format
unknown
orinnaplicable
. See ISO19139 / Format / nilReason is set to unknown when missing #3925Resource identifier
Editor app
Remote validation
INSPIRE View
Configure INSPIRE view to (maybe we should have a TG1 and TG2 separated view for backward compatibility ?):
Discussions:
Migration
Installer
ISO19115-3:2018
http://metawal.wallonie.be is an example of catalogue using ISO19115-3 as a standard and keep compliance with regard to INSPIRE TG2 validation rules.