European Commission logo
INSPIRE Community Forum

Group activity

  • Jake McGregor
    Jake McGregor added a new discussion topic Best practices for multiple lithologies in one polygon?
    Hello, I am hoping that someone could point me in the right direction to find best practices for representing multiple lithologies in one polygon. At present the list of terms is slash delimited and compliant with the lithology...
    • Lola Boquera

      Hello,

      I think that in the UML Geological Model you have the dataType "CompositionPart" and his multiplicity is 1 or more for each GeologicUnit. I mean you can have as many CompositionParts (material, role and proportion) as lithologies have one geological unit. I hope I have clarified something.

      Regards,

      Lola Boquera

       

  • Einar EBERHARDT
    Einar EBERHARDT replied on the discussion topic SoilPlot
    Hi Florian, as far as I know the BZE-L sampling scheme, I agree that SoilSite is the right feature type. SoilSite should hold your overall location and SoilPlot as the location of your soil profile within the SoilSite. When TWG Soil... view reply
  • Florian Hoedt
    Florian Hoedt replied on the discussion topic SoilPlot
    Any news on the missing soilProfileObervation and profileElementObservation: https://youtu.be/5KKGZfGL_Ic?t=1256 Using HALE (and the mentioned soil.xsd as target schema) I am currently unable to map the sampled parameters to a... view reply
  • Marc VAN LIEDEKERKE
    Marc VAN LIEDEKERKE replied on the discussion topic SoilPlot
    To SoilPlot - soilPlotLocation of course, as this contains the value of your location: possible values are indicated on p42. You want to avoid (X,Y), then it should be text of an identifier. I am not sure if you have identifiers that can denote a... view reply
  • Florian Hoedt
    Florian Hoedt replied on the discussion topic SoilPlot
    Thank you Marc, I will dive into the specification to get a better understanding of the profileElementObservation types. But: SoilPlot - location:   indicates the association of the Observed Soil Profile to a specific Soil... view reply
  • Marc VAN LIEDEKERKE
    Marc VAN LIEDEKERKE replied on the discussion topic SoilPlot
    Hi Florian. Feasable approach. SoilPlot - location:   indicates the association of the Observed Soil Profile to a specific Soil Plot SoilPlot - soilPlotLocation: is the attribute that contains the location -value Concerning... view reply
  • Florian Hoedt
    Florian Hoedt added a new discussion topic SoilPlot
    Hello everybody, I am working at the Thünen-Institute in germany to publish the various monitoring datasets in an inspire conformant way. Currently I try to map data from our 'Bodenzustandserhebung'...
    • Florian Hoedt

      Any news on the missing soilProfileObervation and profileElementObservation:
      https://youtu.be/5KKGZfGL_Ic?t=1256

      Using HALE (and the mentioned soil.xsd as target schema) I am currently unable to map the sampled parameters to a ProfileElement.

      After more reading I came to the conclusion that my data is more like a SoilSite Polygon with IsObservedOnLocation -> SoilPlot with a disclosed exact soilPlotLocation.

      In this constellation I still do not know how to populate the SoilSite.location (from gml:abstractFeature), since I use the vector grid as SoilSite.geometry (Soil v4.0, p. 62: The geometry defining an area in which the survey was conducted). So what to use as SoilSite.location?

      Are there any datasets which actually use the Soil schema which I could use as reference?

    • Einar EBERHARDT

      By Einar EBERHARDT

      Hi Florian,

      as far as I know the BZE-L sampling scheme, I agree that SoilSite is the right feature type. SoilSite should hold your overall location and SoilPlot as the location of your soil profile within the SoilSite.

      When TWG Soil produced the UML model (or possibly during the steps for finalising the whole data specification), it might be that the gml abstract feature already geometry (Location) was overlooked. Therefore the explicit "geometry" was foreseen for the site polygon. So it might be that we would need a revision of the model. When I find out more I will come back to you.

      There seem to be few (if not none) datasets around. Also we at BGR are still working on our first (map data) dataset with profiles.  

    • Johanna Ott

      Hi Einar,

      Are there already any news on how to store the geometry of a SoilPlot if the exact location should not be published due to data protection reasons?

      Should the grid cell, in which a SoilPlot is located really be described by referencing its name ("the name of a location" as described in the Data Specification, chapter 5.3.1.1.5) or will there be an option to describe the location of a SoilPlot with a ploygon instead of an X/Y point?

      One more alternative would be to take the X/Y point of one of the corners of the grid cell and describe the location with this - then maybe adding to the description of the Point, that it is not describing the exact location where the SoilPlot is located, but a point belonging to a grid with the size x squarmeters in which the SoilPlot is located?

       

      All the best

      Johanna

  • László SŐRÉS
    László SŐRÉS replied on the discussion topic application schema Geology - Boreholes without information on depth
    Dear Johanna, I think, option 2 is a good idea. Using the point geometry for MappedInterval and link GeologicUnit and GeologicEvent to the borehole allows the user to extract the maximum amount of available information. Best... view reply
  • Heinz ELFERS
    Heinz ELFERS replied on the discussion topic application schema Geology - Boreholes without information on depth
    Hello Johanna, Although we are not yet translating our borehole data to the INSPIRE scheme, we will have the same problems. This is, because a lot of boreholes are under protection of private owners and the geological Survey is not allowd to... view reply
  • Johanna Ott
    Johanna Ott added a new discussion topic application schema Geology - Boreholes without information on depth
    Hello everybody, We are dealing with data containing Boreholes. There is no information on their depth in the source, so we cannot meaningfully create MappedInterval instances as their "shape" attribute is mandatory and not voidable....
    • László SŐRÉS

      By László SŐRÉS

      Dear Johanna,

      I think, option 2 is a good idea. Using the point geometry for MappedInterval and link GeologicUnit and GeologicEvent to the borehole allows the user to extract the maximum amount of available information.

      Best regards,
      Laszlo 

       

    • Tilman BROCK-HESSE

      By Tilman BROCK-HESSE

      Dear Johanna,

      could you please describe what solution you used and also what mappingFrame you have set on the MappedInterval instances?

      That would be very interesting to know.

      Thanks,
      Tilman

    • Johanna Ott

      Dear Tilman,

      The data provider we are working for decided to use solution 1). It is technically not correct but avoids that misleading/confusing/wrong data is delivered to users.

      The mappingFrame value for our data is http://inspire.ec.europa.eu/codelist/MappingFrameValue/surfaceGeology

       

      All the best

      Johanna

  • Enrico Iredi
    Hello Sören, yes, GroundwaterBody and HydrogeologicalObject are still affected. I have re-uploaded the HydrogeologyCore_Delta.xsd ... view reply
  • Sören Dupke
    Hello Enrico, thank you for the quick reply. It looks okay on the Aquiclude now. However, I discovered that there is the same problem with the GroundwaterBody. Will this schema replace the version currently published at some... view reply
  • Enrico Iredi
    Hello Sören, change the xsd. See HydrogeologyCore_Delta.xsd https://themes.jrc.ec.europa.eu/file/view/220298/hydrogeologycore-deltaxsd. I did not create gml with the xsd yet. Try it. Best regards Enrico  view reply
  • Enrico Iredi
    Enrico Iredi uploaded the file HydrogeologyCore_Delta.xsd
    answer to https://themes.jrc.ec.europa.eu/discussion/view/220071/missing-nillable-property-on-beginlifespanversion-and-endlifespanversion-on-hydrogeologicalunittype
  • Sören Dupke
    The attributes beginLifespanVersion and endLifeSpanVersion of the FeatureType HydrogeologicalUnit are voidable in the UML model, but are missing the nillable property and the nilReason attribute on the schema. This makes it impossible...
  • Amelia BAPTIE published a news post Earth Science Cluster at the INSPIRE Conference 2018
    Dear all, The INSPIRE conference 2018 (https://inspire.ec.europa.eu/conference2018) is taking place from the 18th to the 21st of September in Antwerp.   The facilitators of the Earth Science cluster would like to invite you to...
  • Enrico Iredi
    Enrico Iredi uploaded the file GML Example RenewableAndWastePotentialCoverage (er-c)
    gml file now ETF valid
  • Tomas LINDBERG
    Tomas LINDBERG replied on the discussion topic Mapping Layers to be provided by INSPIRE view services to ERML-Lite
    Could not attend Vancouver, but we (SGU) have now started work on creating an Inspire view service based on the data used in M4EU/EGDI (the common GEUS database-model and the Deegree WFS). Work done so far: We have used FME to transform data... view reply
  • Tomas LINDBERG
    Tomas LINDBERG uploaded the file SLD for GeoServer: MineralOccurrences-primaryCommodity
    Based on work by James Passmore (BGS), edited by Tomas Lindberg (SGU) An attempt at creating an INSPIRE compliant style for MR.MineralOccurrence, work undertaken as part of the OneGeology project (onegeology.org) by James Passmore (British...
  • Amelia BAPTIE
    Amelia BAPTIE added a new discussion topic Post on 3D Geologic Models - INSPIRE and Linked Data
      Dear all,   László SŐRÉS has shared some interesting information and questions about 3D Geological models, INSPIRE and Linked data. This post, including a web page link to an article about 3D Geologic Model...
Earth Science

Earth Science

Join this group to share your knowledge, learn and collaborate with INSPIRE Earth Science Cluster for Geology, Soils, Natural Risk Zones, Mineral resources, and Energy resources