European Commission logo
INSPIRE Community Forum

Group activity

  • Stefania MORRONE
    Stefania MORRONE replied on the discussion topic HabitatsAndBiotopesDistribution XSD
    Hi Kate, the maintenance of draft schemas is not foreseen (al least for the moment being). Moreover, those draft schemas do not reflect the changes introduced in the amendment of the Implementing Rules (Commission Regulation (EU) No 1253/2013)... view reply
  • Katharina SCHLEIDT
    Katharina SCHLEIDT replied on the discussion topic HabitatsAndBiotopesDistribution XSD
    Hi Kate, good point, seems that while the basic Habitat Types made it to the final version, the Habitat Distribution never got past draft stage. Habitat Distribution is not marked as deprecated within the data models, but it also isn't... view reply
  • Kate Lyndegaard
    Kate Lyndegaard added a new discussion topic HabitatsAndBiotopesDistribution XSD
    Hi, Is anyone aware of the status of the HabitatsAndBiotopesDistribution schema currently located here: https://inspire.ec.europa.eu/draft-schemas/hbd/? Does anyone know when there will be an official release? I would like to complete my...
  • Enrico Iredi
    Enrico Iredi uploaded the file GML Example ProtectedSite (ps)
    gml file now ETF valid
  • Enrico Iredi
    Enrico Iredi commented on the file GML Example Species Distribution (sd)
    Here's the manipulated SpeciesDistribution.xsd. It works well. https://inspire.ec.europa.eu/forum/file/view/261552/changed-in-speciesdistributionxsd
  • Enrico Iredi
    Enrico Iredi uploaded the file change in SpeciesDistribution.xsd
    changed SpeciesDistributionDelta.xsd for discussion https://inspire.ec.europa.eu/forum/file/view/261368/gml-example-species-distribution-sd
  • Enrico Iredi
    Enrico Iredi commented on the file GML Example Species Distribution (sd)
    Hi Stefania, deegree is fine. Bad is the SpeciesDistribution.xsd I think. At this place I need a type="gml:ReferenceType" and not a type="sd:SpeciesDistributionUnitPropertyType". Then deegree can resolve the references to the...
  • Stefania MORRONE
    Stefania MORRONE commented on the file GML Example Species Distribution (sd)
    Dear Enrico, what deegree version are you using?  In my experience, deegree (at least from v 3.3.18 onwards) is able to transform the internal '#' references in 'GetFeatureById' queries ... Kind regards, Stefania
  • Enrico Iredi
    Enrico Iredi commented on the file GML Example Species Distribution (sd)
    Hello Stefania, yes, with the notation <sd: member xlink: href = "# SpeciesDistributionUnit _... ></sd: member> the gml file is etf valid, but then deegree can't resolve the references to the SpeciesDistributionUnit...
  • Johanna Ott
    Johanna Ott replied on the discussion topic HB: encoding of ReferenceSpeciesSchemeValue using EUNIS reference list
    Dear Stefania, Thank you for your reply and explanation. The issue is, that I have a tenthousands of datasets here and cannot start to search for the URLs to all of them manually. That is why I asked if 1. it is either allowed to build a... view reply
  • Stefania MORRONE
    Stefania MORRONE replied on the discussion topic HB: encoding of ReferenceSpeciesSchemeValue using EUNIS reference list
    Dear Johanna, all from the page https://eunis.eea.europa.eu/ it is possible to perform a search by habitat codes. Searching e.g. for C1.4 code, you get the list of all Eunis codes starting with C1.4. Clicking in turn on the desired... view reply
  • Stefania MORRONE
    Stefania MORRONE commented on the file GML Example Species Distribution (sd)
    Dear Enrico, thank you for providing this useful example. Regarding the references to the SpeciesDistributionUnits in the SpeciesDistributionDataSet, you don't need to use the embedded description. Be aware that in the <sd:member>...
  • Enrico Iredi
    Enrico Iredi uploaded the file GML Example Species Distribution (sd)
    GML file for deegree valid, but not etf valid. Because I only want to have references to the sd:SpeciesDistributionUnit in the sd:SpeciesDistributionDataSet. I dont want built-in sd:SpeciesDistributionUnit-objects.
    • Stefania MORRONE
      Stefania MORRONE
      Dear Enrico, what deegree version are you using?  In my experience, deegree (at least from v 3.3.18 onwards) is able to transform the internal '#' references in 'GetFeatureById' queries ... Kind regards, Stefania
    • Enrico Iredi
      Enrico Iredi
      Hi Stefania, deegree is fine. Bad is the SpeciesDistribution.xsd I think. At this place I need a type="gml:ReferenceType" and not a type="sd:SpeciesDistributionUnitPropertyType". Then deegree can resolve the references to the...
    • Enrico Iredi
      Enrico Iredi
      Here's the manipulated SpeciesDistribution.xsd. It works well. https://inspire.ec.europa.eu/forum/file/view/261552/changed-in-speciesdistributionxsd
  • Johanna Ott
    Johanna Ott replied on the discussion topic HB: encoding of ReferenceSpeciesSchemeValue using EUNIS reference list
    Hello everybody, Almost three years ago, Iurie wrote Simmilar, for EUNIS Habitat Types the schema is http://inspire.ec.europa.eu/codelist/ReferenceHabitatTypeSchemeValue/eunis and the value for "Ash-alder-spruce galleries of... view reply
  • The UN-GGIM Europe Working Group on Core Data has published the first draft of the deliverable “Core Data Spatial theme ‘Regulated or Managed Areas’ Recommendations for content” that is based on user requirements and on the corresponding INSPIRE...
  • Stefania MORRONE
    Stefania MORRONE replied on the discussion topic Implementation of multiple attributes
    Dear Miroslav, I understand your point of view, anyway I don't think your implementation proposal could be considered as INSPIRE compliant not even in the future. Moreover, consider that currently most software tools are not able to... view reply
  • Miroslav FANTA
    Miroslav FANTA replied on the discussion topic Implementation of multiple attributes
    Dear Stefania, Thank you for your reply. It means, if using of multiple attributes is intended, then gml data format has to be used only. Unfortunately, I am affraid, such situation is not comfortable for many data providers and data users... view reply
  • Stefania MORRONE
    Stefania MORRONE replied on the discussion topic Implementation of multiple attributes
    Dear Miroslav, generally speaking, a property with multiplicity (1..*) can appear 1 or multiple times in the same spatial object (specific <gml:featureMember> or <wfs:member>). Let's say, as an example, that one wants to... view reply
  • Miroslav FANTA
    Miroslav FANTA added a new discussion topic Implementation of multiple attributes
    Dear colleagues,  I am looking for an example how multiple attributes should be implemented. In the spatial object type "ManagementRestrictionOrRegulationZone", many attributes have the multiplicity 1..* or 0..* (e.g. thematicId,...
    • Stefania MORRONE

      By Stefania MORRONE

      Dear Miroslav,

      generally speaking, a property with multiplicity (1..*) can appear 1 or multiple times in the same spatial object (specific <gml:featureMember> or <wfs:member>).

      Let's say, as an example, that one wants to provide two names and two zone type values for the same ManagementRestrictionOrRegulationZone spatial object e.g. "AM_1". The GML would look like the following :

       <gml:featureMember>

      <am:ManagementRestrictionOrRegulationZone gml:id="AM_1">
            <am:inspireId> ... </am:inspireId>
            <am:thematicId>.... </am:thematicId>
            <am:name>
              <gn:GeographicalName>
                <gn:language>eng</gn:language>
                <gn:nativeness xsi:nil="true"/>
                <gn:nameStatus xsi:nil="true"/>
                <gn:sourceOfName xsi:nil="true"/>
                <gn:pronunciation xsi:nil="true"/>
                <gn:spelling>
                  <gn:SpellingOfName>
                    <gn:text>Name1</gn:text>
                    <gn:script xsi:nil="true"/>
                  </gn:SpellingOfName>
                </gn:spelling>
              </gn:GeographicalName> 
            </am:name>
            <am:name>
              <gn:GeographicalName>
                <gn:language>ger</gn:language>
                <gn:nativeness xsi:nil="true"/>
                <gn:nameStatus xsi:nil="true"/>
                <gn:sourceOfName xsi:nil="true"/>
                <gn:pronunciation xsi:nil="true"/>
                <gn:spelling>
                  <gn:SpellingOfName>
                    <gn:text>Name2</gn:text>
                    <gn:script xsi:nil="true"/>
                  </gn:SpellingOfName>
                </gn:spelling>
              </gn:GeographicalName>   
            </am:name>    
            <am:geometry> ...    
            </am:geometry>
            <am:zoneType xlink:href="http://inspire.ec.europa.eu/codelist/ZoneTypeCode/value1"></am:zoneType>
            <am:zoneType xlink:href="http://inspire.ec.europa.eu/codelist/ZoneTypeCode/value2"></am:zoneType>

            ....

        </gml:featureMember>

      Hope this helps

      Stefania

       

    • Miroslav FANTA

      By Miroslav FANTA

      Dear Stefania,

      Thank you for your reply. It means, if using of multiple attributes is intended, then gml data format has to be used only. Unfortunately, I am affraid, such situation is not comfortable for many data providers and data users at all, because in most cases, shapefile or geodatabase are widely used as basic spatial data formats. In both shapefile and geodatabase formats, two or more attributes with identical names are not allowed. If the gml file containing multiple attributes with identical names is converted to shapefile or to geodatabase feature class, these attributes are renamed during the conversion process by adding suffix "_1", "_2", etc.

      It is a pity that multiple attributes cannot be solved by relation from attribute table to external table containing multiple values for given multiple attribute. E.g., if spatial data should contain multiple values of zoneType attribute, then the spatial dataset will have one zoneType attribute only and this atribute will contain link (relation) to external table, in which multiple values of zoneType are stored. By that way, multiple attributes could be implemented also for shapefiles and geodatabases. Do you think, this solution could be considered as INSPIRE compatible in the future?

      Best wishes

      Miroslav

       

    • Stefania MORRONE

      By Stefania MORRONE

      Dear Miroslav,

      I understand your point of view, anyway I don't think your implementation proposal could be considered as INSPIRE compliant not even in the future.

      Moreover, consider that currently most software tools are not able to resolve the xlinks (both internal and external) in the gml dataset , and this would constitute a 'side effect' of your proposal to be duly taken into account.

      Best regards,

      Stefania

       

       

       

  • Peter MCKEAGUE
    Peter MCKEAGUE added a new discussion topic Call for papers:Towards a Spatial Data infrastructure for Archaeology
    Where:  -   European Archaeological Association Bern, Switzerland When:   4-7 September 2019 Through the INSPIRE Directive public organisations across Europe are required to share environmentally-related spatial...
Biodiversity & Area Management

Biodiversity & Area Management

If themes like Protected Sites, Area Management/Restriction/Regulation Zones and Reporting Units, Habitats and Biotopes, Species Distribution, Bio-geographical Regions matters to you, join these groups!