Skip to content
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

Closed
wants to merge 2 commits into from
Closed

INSPIRE / Add TG2 support #3399

wants to merge 2 commits into from

Conversation

fxprunayre
Copy link
Member

@fxprunayre fxprunayre commented Jan 7, 2019

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

Codelist attribute

Thesaurus

CRS

Format

Resource identifier

  • Encode resource identifier using Anchor - not mandatory

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

  • Add all required thesaurus in the INSPIRE pack (ie. spatial scope, priority dataset)

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.

  • Adapt editor if needed
  • Review mapping to ISO19139
  • Codelist URL update

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
@josegar74
Copy link
Member

@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.

@pvgenuchten
Copy link

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}}"/>

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>

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

@fxprunayre
Copy link
Member Author

Related to #3638

@fxprunayre
Copy link
Member Author

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

@fxprunayre fxprunayre added this to the 3.8.1 milestone Aug 22, 2019
@fxprunayre fxprunayre modified the milestones: 3.8.1, 3.8.2 Sep 23, 2019
@fxprunayre fxprunayre modified the milestones: 3.8.2, 3.8.3 Oct 29, 2019
@fxprunayre
Copy link
Member Author

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

@fxprunayre fxprunayre closed this Oct 29, 2019
@fxprunayre fxprunayre changed the title [WIP] INSPIRE / Add TG2 support INSPIRE / Add TG2 support Oct 29, 2019
@fxprunayre fxprunayre deleted the inspire/tg2support branch February 21, 2020 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants