European Commission logo
INSPIRE Community Forum

Which are the issues on INSPIRE compliance of EMODnet Bathymetry CDIs?

Dear community members,

As highlighted by Marc Roesbeke as a comment to the page dedicated to the EMODnet Bathymetry project, "The ideal would be for European EMODnet member states to be able to deliver the created CDIs with the associated BAG files for both the INSPIRE Data Portal and the EMODnet Data Portal. Less work for the hydrographic organizations.".

I am opening this discussion topic with the aim to identify, collect and discuss about the current issues that prevent EMODnet CDIs and related Bathymetry Data to achieve full INSPIRE compliance.

Please, feel free to participate and/or point any of your colleagues / contacts to intervene in this discussion thread.

Happy to count with your active contribution!

  • Fanny LECUY

    Hello,

    I work for the french hydrographic office and I am currently working on our bathymetric data conversion.

    We mainly have DTMs and point cloud data (I guess the CDIs mentioned by Mark) from surveys that are used for the EMODnet european DTM.

    As I can not find anything about point cloud data in the Elevation specfication I am even wondering if they are out of  scope. We could say that they are Vector Elements - Spot Elevation (hence the GML format mentioned by Mark) but it does not really fit.

    What do you think about it?

    Fanny

     

  • George Spoelstra

    By George Spoelstra

    Hi Fanny,

    The CDI's Mark is referring to are not the data holders as such but contain the metadata. This is INSPIRE compliant metadata and included in the CDI Data Discovery and Access service as adopted and adapted for EMODnet Bathymetry from SeaDataNet (see https://www.emodnet-bathymetry.eu/metadata-data).

    The Elevation specification supports three technical implementation models (raster, vector and TIN). Point clouds as such are not explicitly mentioned. There is an ongoing forum discussion about this (see https://inspire.ec.europa.eu/forum/discussion/view/22150/web). So I believe the question here is a bit out of scope. 

    Cheers

    George Spoelstra

    EMODnet Bathymetry DTM coordinator

     

  • Fanny LECUY

    Hi George,

    Sorry, I forgot that if you deliver BAG it is with a GML for the domain set and that is why I got it confused with the vector elements of the spec. I am not yet a master of the coverage subjet in INSPIRE.

    Fanny

  • George Spoelstra

    By George Spoelstra

    When I re-read Marc's comment I do believe that he is using GML in relation to the CDI's (GML is of course a flavour of XML). In the CDI there is a coverage polygon or trackline defined so the CDI contains a mbit of GML as well. Hence the confusion. 

  • Katharina SCHLEIDT

    By Katharina SCHLEIDT

    Dear all,

    a bit of technical clarification (based on my experience mapping data from the SeaDataCloud project to INSPIRE data specifications a few years ago)

    • CDI files are based on the ISO 19115 standard for spatial metadata, same standard as is used for metadata under INSPIRE
    • Some additional fields have been defined for the CDI extension, hosted by seadatanet.org. Unfortunately, at least in the version my examples use, this schmema file has issues (it imports ISO schema components from an invalid URL)
    • While the CDI files do contain a bit of GML, this is purely metadata, providing information on spatiotemporal extent of the data being provided (same as INSPIRE metadata)
    • One should probably to a check to assure that all metadata elements specified for INSPIRE are contained in the CDI files (many elements required by INSPIRE are optional in the ISO 19115 standard, may not be contained within the CDI)

    To my understanding, as long as the potential issues in the last point are covered, it should be possible to provide CDI files as INSPIRE metadata. The data the CDI files are describing should then be provided in accordance with the relevant INSPIRE Data Specifications (Elevation Model (EL) for Bathymetry, Oceanographic Features (OF) and Environmental Monitoring Facilities (EF) for marine measurement data

    Hope this helps

    :)

    Kathi

  • George Spoelstra

    By George Spoelstra

    Hi Kathi,

    Thanks for your feedback.I can confirm that today the SeaDataNet CDI's pass the Inspire validator test and are therefore fully Inspire compliant. The following is from the SeaDataNet site:

    " More recently (December 2019), activities have been concluded in discussion and cooperation with the INSPIRE team at EU-JRC to update the CDI XML coding in full compliance with the latest INSPIRE ISO19139 metadata schema. This can be validated using the latest version of the new ETF validator of INSPIREWhereby one has to select metadata for interoperability as the target conformance class."

    The questin from Fanny as far as I understand was more about the somewhat cryptic description in an original comment from Marc Roesbeke from the Flamish Hydrography about the coding of CDI data. 

    Cheers 

     

    George

  • Jordi ESCRIU

    Thank you all for your good discussion.

    Answering the former qustion from Fanny, "As I can not find anything about point cloud data in the Elevation specfication I am even wondering if they are out of  scope", regardless point clouds are not covered as a common data format in the INSPIRE Data specification on Elevation, bathymetry vector data is totally in the scope of INSPIRE (see the mentioned "Vector Elements" schema - "Spot Elevation" spatial object).

    Therefore, if you are working with bathymetry data sets in point cloud format, such data sets are in the scope of INSPIRE and they are candidates to be transformed and provided for INSPIRE according the rules defined in the Directive.

    In my view, the original post from Mark Roesbeke here (let me remember his closing sentence: "The ideal would be for European EMODnet member states to be able to deliver the created CDIs with the associated BAG files for both the INSPIRE Data Portal and the EMODnet Data Portal. Less work for the hydrographic organizations") does not only refer to CDI metadata file but also the bathymetry data (BAG files) described by them.

    Concluding, it would be really helpful if you (ALL) could share with the community any issues you may have encountered while transforming your bathymetry data sets for the purpose of the INSPIRE Directive.

     

Elevation, Ortho & Grids

Elevation, Ortho & Grids

INSPIRE Thematic Cluster Elevation, Orthoimagery, Reference systems, Geographical grids - Join this group to share your knowkledge, learn and collaborate in solving issues related to the Elevation, Orthoimagery, Reference systems and Geographical grids themes