Errors in the Inspire interoperability regulation

This page reports some errors found in the Inspire interoperability regulations.

Errors common to several versions of the regulation

  1. the regulation doesn't define values for the AdministrativeHierarchyLevel codelist defined by the section 4.2.4.1 of annex II.
    Proposal: Use the values defined in the regulation n° 102/2011.
  2. the attribute endLifepanVersion of the MaritimeZone spatial object type defined in section 4.3.1.3. of annex II is misspelled in most versions but the spelling has been corrected in some versions.
    Proposal: Correct the spelling of attribute endLifepanVersion to endLifespanVersion in all versions.
  3. the type of the building association role of the Address spatial object type is defined in section 5.2.1. of annex II as "Type to be specified in the spatial data theme Buildings" which is not a correct type.
    Proposal: Replace this definition by "Building of the Buildings Base package".
  4. the type of the association role controlTowers of the spatial object type AerodromeNode is defined in section 7.4.1.3. of annex II as "Type to be specified in the spatial data theme Buildings" which is not a corect type.
    Proposal: Replace this definition by "Building of the Buildings Base package".
  5. the spatial object type TrafficSeparationScheme defined in section 7.8.1.13. of annex II is an abstract type but has no subtype defined ; therefore it can be used.
    Proposal: Suppress this spatial object type or don't define ir as abstract type.
  6. the type Percentage is never defined but is used for the attribute percentageUnderDesignation of data type DesignationType in section 9.2.1. of annex II.
    Proposal: Replace the type Percentage by Integer.
  7. the codelist DesignationValue defined in section 9.4.2. of annex II is defined as "an abstract type". Definitions of article 2 state that (i) only types can be abstract and (ii) a codelist is not a type; therefore the codelist DesignationValue can't be an abstrat type. Moreover, (i) this codelist is the only one defined as abstract type in the regulation, and (ii) the goal of the writers was to define this codelist as the union of a set of sub-codelists. This case appears for other codelists in the regulation, for example AppurtenanceTypeValue which is a union of the codelists for the different utility networks.
    Proposal: Don't define DesignationValue as an abstract type but define it as a codelist with sub-codelists like it is done for AppurtenanceTypeValue.
  8. the association role tesselation of the AreaStatisticalUnit spatial object type defined in section 1.3.1.2. of annex IV is misspelled in most versions but the spelling has been corrected in some versions.
    Proposal: Correct the spelling of attribute tesselation to tessellation in all versions.
  9. three spatial object types named Building are defined in the buildings theme in section 2. of annex IV. Therefore when this name is used in section 6.9.2.2. of annex IV for the attribute serviceLocationByBuilding, the text should specify which type should be used; the current specification is ambiguous.
    Proposal: Replace Building by "Building of the Buildings Base package".
  10. three spatial object types named BuildingPart are defined in the buildings theme in section 2. of annex IV. Therefore when this name is used in section 2.3.1.3. of annex IV for the association role parts, the text should specify which type should be used; the current specification is ambiguous.
    Proposal: Replace BuildingPart by "BuildingPart of the Buildings Base package".
  11. the value bottomOfConstruction of the codelist HorizontalGeometryReferenceValue defined in section 2.3.3.6. of annex IV is defined in French but not in some other languages such as English.
    Proposal: Define the value bottomOfConstruction in all the versions of the regulation in which it is not defined.
  12. in the codelist SoilDerivedObjectParameterNameValue defined in section 3.3.9. of annex IV, the value named chemicalParameter is referred as chemicalParameters as the parent the value carbonStock.
    Proposal: Replace chemicalParameters by chemicalParameter.
  13. in the codelist SoilProfileParameterNameValue defined in section 3.3.12. of annex IV, the value named chemicalParameter is referred as chemicalParameters as the parent the value carbonStock.
    Proposal: Replace chemicalParameters by chemicalParameter.
  14. the type InstallationType is never defined but is used for the attribute type of the spatial object type ProductionInstallation in section 8.2.2. of annex IV.
    Proposal: Replace the type InstallationType by InstallationTypeValue.
  15. the type InstallationPartType is never defined but is used for the attribute type of the spatial object type ProductionInstallationPart in section 8.2.3. of annex IV.
    Proposal: Replace the type InstallationPartType by InstallationPartTypeValue.
  16. the type HazardCategoryValue is never defined but is used for the attribute hazardCategory of the data type NaturalHazardClassification in section 12.3.4. of annex IV.
    Proposal: Replace the type HazardCategoryValue by NaturalHazardCategoryValue.
  17. the type AbstractObservableProperty is never defined but is used for the attribute phenomenon of the spatial object type MarineContour in section 15.1.8. of annex IV and for the attribute parameter of the data type ParameterValuePair in section 15.2.3. of annex IV.
  18. in annex IV, two data types named RangeType are defined: one in the Soil theme in section 3.2.6. and one in the Species Distribution theme in section 18.3.3.. Therefore, when RangeType is used in sections 3.1.3., 3.2.1, 3.2.5. and 18.3.2., the regulation should precise which type should be used; the current specification is ambiguous.
    Proposal: In the Soil theme, replace RangeType by "RangeType of the Soil theme"; in the Species Distribution theme, replace RangeType by "RangeType of the Species Distribution theme".
  19. the type VerticalReferenceRangeType is never defined but is used for the attribute range of the union type VerticalExtentValue in section 19.3.1.3. of annex IV.
  20. the type HydrocarbonMeasure is never defined but is used for the attribute quantity of the data type FossilFuelResourceType in section 19.4.2.5. of annex IV.
  21. in sections 12.2.1., 12.2.2. and 12.2.4. of annex IV, instead of type "identifier", "Identifier" should be used.
    Proposal: replace the type identifier by Identifier.
  22. the type GM_Position is never defined but is used for the attribute location of data type TimeLocationValueTriple in section 7.4.2.1. of annex I.
    Proposal: Add GM_Position in section 1 of annexe I, paragraph (2).
  23. in section 1. of annex I, two definitions are given for the types Sign (from ISO/TS 19103:2005 and EN ISO 19136:2009) and Quantity (from EN ISO 19136:2009 and from "Robin, Alexandre (ed.), OGC®SWE Common Data Model Encoding Standard, version 2.0.0, Open Geospatial Consortium, 2011.").
    Proposal: suppress one of the two references.

Errors specific to the French version of the regulation

  1. in section 8.4.1.1. of Annex II, in the French version the HydroNode spatial object type has one attribute beginLifespanVersion where in the English version the same type has one attribute hydroNodeCategory.
    Proposal: suppress beginLifespanVersion attribute and add the hydroNodeCategory one.
  2. in section 20.3.3.3. of Annex IV, in the French version the parent value of the value specialityAndOtherIndustrialMinerals is named "nonMetallic Minerals" instead of nonMetallicMinerals.
    Proposal: replace the value "nonMetallic Minerals" by nonMetallicMinerals.

Errors specific to the English version of the regulation

  1. in section 5.2.3. of Annex IV, in the English version the attribute "geometric Mean" of the BiomarkerStatisticalParameterType data type should be named "geometricMean".
    Proposal: replace "geometric Mean" by "geometricMean".
  2. in section 5.2.4. of Annex IV, in the English version the attribute "mean Age" of the BiomarkerThematicMetadata data type should be named "meanAge".
    Proposal: replace "mean Age" by "meanAge".

Errors specific to the German version of the regulation

  1. in the codelist BoreholePurposeValue defined in section 4.2.3.2. of Annex III, the parent value of hydrocarbonProduction, hydrocarbonExploration, hydrocarbonAppraisal and geothermalEnergy is explorationExploitationEnergyResources in the German version as it is explorationExploitationRawMaterial in the English, French, Italian and Spanish versions;
    Proposal: use in the German version the parent value defined in the English, French, Italian and Spanish versions.
  2. the codelist OtherSoilNameTypeValue defined in section 3.3.5. of Annex IV is named in German with the neutral name OtherSoilNameType;
    Proposal: use the neutral name defined in the English version.
  3. in the codelist SewerAppurtenanceTypeValue defined in section 6.5.2.1. of Annex IV the value meter is named in German with the neutral name Zähler.
    Proposal: use the neutral name defined in the English version.
  4. in the codelist SewerWaterTypeValue defined in section 6.5.2.2. of Annex IV the value reclaimed is named in German with the neutral name Aufbereitet.
    Proposal: use the neutral name defined in the English version.

Errors specific to the Italian version of the regulation

  1. the 2 codelists and 8 sub-codelists of section 7.3.3. of annex I are not defined in Italian.
    Proposal: define the codelists.
  2. the codelist http://inspire.ec.europa.eu/codelist/EvolutionTypeValue defined in section 1.3.3.2. of annex IV is not defined in Italian.
    Proposal: define the codelist.
  3. the neutral name of the following attributes or roles have been modified in Italian :
    typeoriginal neutral namemodified namesection
    NamedPlacenamenome section 3.1.1. of annex II
    ElementLengthlengthlunghezza section 7.4.1.14. of annex II
    Watercourselengthlunghezza section 8.5.1.24. of annex II
    GeologicCollectionnamenome section 4.2.1.4. of annex III
    HydrogeologicalSurfacesurfaceReferenceableGridsurfaceReferencableGrid section 4.4.2.1. of annex III
    Evolutiondatedata section 1.3.1.4. of annex IV
    Proposal: use the neutral name defined in the English version.
  4. the neutral name of the following codelists or subcodelists have been modified in Italian :
    original neutral namemodified namesection
    EconomicActivityWasteStatisticsValueEconomicActivityNACEValue section 8.1.3.1. of annex I
    InstallationPartTypeValueInstallationTypeValue section 8.4.3. of annex IV
    EunisHabitatTypeCodeValueEunisCodeValue section 17.4.2. of annex IV
    Proposal: use the neutral name defined in the English version.
  5. the neutral name of the following codelist's values has been modified in Italian :
    codelistoriginal neutral namemodified namesection
    OilGasChemicalsAppurtenanceTypeValueoilGasChemicalsNodenode section 6.4.2.1. of Annex IV
    SewerAppurtenanceTypeValuesewerNodenode section 6.5.2.1. of Annex IV
    ServiceTypeValuehydrantidrante section 6.9.3.1. of Annex IV
    Proposal: use the neutral name defined in the English version.

Errors specific to the Spanish version of the regulation

  1. the neutral name of the sub-codelist http://inspire.ec.europa.eu/codelist/Article17CountingUnitValue defined as a sub-list of the codelist http://inspire.ec.europa.eu/codelist/CountingUnitValue by section 18.4.2. of annex IV has been replaced in Spanish by the neutral name CountingUnitValue;
    Proposal: use the neutral name defined in the English version.
--
Page updated on the 2/8/2014 9:40