Article 4.Types for the Exchange and Classification of Spatial Objects
Article 6. Code Lists and Enumerations for Spatial Data Sets
Article 14a.Requirements for invocable spatial data services
Article 14b. Interoperability arrangements and harmonisation requirements for invocable spatial data services
COMMON TYPES, DEFINITIONS AND REQUIREMENTS
REQUIREMENTS FOR SPATIAL DATA THEMES LISTED IN Annex 1 to Commission Regulation (EC) No. 1205/2008
1. When gridded data is delivered using geodetic coordinates as specified...
3. The grid shall be based on the ETRS89-GRS80 geodetic coordinate...
4. The origin of the grid shall coincide with the intersection...
5. The grid orientation shall be south-north and west-east according to...
6. For grid referencing in regions outside of continental Europe data...
7. This grid shall be subdivided in zones. The south-north resolution...
8. The grid shall be designated Grid_ETRS89-GRS80z n_res , where n...
4.1. Structure of the Spatial Data Theme Administrative Units
4.4. Theme-specific Requirements
1. Each instance of spatial object type AdministrativeUnit, except for the...
2. Each instance of spatial object type AdministrativeUnit, except for those...
3. If an administrative unit is co-administered by two or more...
4. Administrative units at the same level of administrative hierarchy shall...
5. Instances of the spatial object type AdministrativeBoundary shall correspond to...
7. Condominiums can only be administered by administrative units at country...
7.3. Common Transport Elements
7.6. Railway Transport Network
7.8.1.4. Condition Of Water Facility (ConditionOfWaterFacility)
7.8.1.12. Restriction For Water Vehicles (RestrictionForWaterVehicles)
7.8.1.13. Traffic Separation Scheme (TrafficSeparationScheme)
7.8.1.14. Traffic Separation Scheme Area (TrafficSeparationSchemeArea)
7.8.1.15. Traffic Separation Scheme Crossing (TrafficSeparationSchemeCrossing)
7.8.1.16. Traffic Separation Scheme Lane (TrafficSeparationSchemeLane)
7.8.1.17. Traffic Separation Scheme Roundabout (TrafficSeparationSchemeRoundabout)
7.8.1.18. Traffic Separation Scheme Separator (TrafficSeparationSchemeSeparator)
7.8.1.21. Water Traffic Flow Direction (WaterTrafficFlowDirection)
7.9. Theme-specific Requirements
REQUIREMENTS FOR SPATIAL DATA THEMES LISTED IN Annex 2 to Commission Regulation (EC) No. 1205/2008
1.4. Elevation – Grid Coverage.
1.5. Elevation - Vector Elements
1.7. Theme-specific Requirements
1.7.2. Requirements for Elevation Grid Coverages
(1) By way of derogation from the requirement in Section 2.2...
(2) The domainExtent attribute of every ElevationGridCoverage instance shall be at...
(3) The elevation property values included within the range set of...
(5) The contributing footprints of any two ElevationGridCoverage instances referred to...
(6) The union of the contributing footprints of the ElevationGridCoverage instances...
(7) The ElevationGridCoverage package shall be restricted to two-dimensional geometries.
(8) Information about the acquisition dates of data contained in elevation...
1.7.6. Requirements on data quality and consistency
(1) If measures other than ISO data quality measures have been...
(2) Connected contour line spatial objects shall have the same elevation...
(3) When the elevation values of break line spatial objects are...
(5) Contour line spatial objects having different elevation value shall neither...
(6) The boundary of an isolated area spatial object shall not...
3.5. Theme-specific Requirements
3.5.2. Requirements for Orthoimage Coverages
(1) By way of derogation from the requirement in Section 2.2...
(2) The footprint of an OrthoimageCoverage instance shall be spatially included...
(3) The value type of the metadata property carried by the...
(4) All the OrthoimageCoverage instances, to which an aggregated OrthoimageCoverage instance...
(5) The contributing footprint of an OrthoimageCoverage instance referred by an...
(6) The contributing footprints of any two OrthoimageCoverage instances referred to...
(7) The union of the contributing footprints of the OrthoimageCoverage instances...
4.2.3.1. Anthropogenic Geomorphologic Feature Type (AnthropogenicGeomorphologicFeatureTypeValue)
4.2.3.11. Geomorphologic Activity (GeomorphologicActivityValue)
4.2.3.14. Natural Geomorphologic Feature Type (NaturalGeomorphologicFeatureTypeValue)
4.2.3.16. Thematic Classification (ThematicClassificationValue)
REQUIREMENTS FOR SPATIAL DATA THEMES LISTED IN Annex 3 to Commission Regulation (EC) No. 1205/2008
3.3.4. Other Horizon Notation Type (OtherHorizonNotationTypeValue)
3.3.6. Layer Genesis Process State (LayerGenesisProcessStateValue)
3.3.8. Profile Element Parameter Name (ProfileElementParameterNameValue)
3.3.9. Soil Derived Object Parameter Name (SoilDerivedObjectParameterNameValue)
3.3.10. Soil Investigation Purpose (SoilInvestigationPurposeValue)
3.3.12. Soil Profile Parameter Name (SoilProfileParameterNameValue)
3.3.13. Soil Site Parameter Name (SoilSiteParameterNameValue)
3.3.16. WRB Reference Soil Group (RSG) (WRBReferenceSoilGroupValue)
3.4. Theme-specific Requirements
(1) The values of the first level hierarchical code lists ProfileElementParameterNameValue,...
(2) When an additional descriptive parameter for the soil derived object...
(3) Only one Other Horizon Notation Type classification shall be used...
(4) Only one Other Soil Name Type classification shall be used...
4.7.2.2. Character-valued Dimensioning Indication (DimensioningIndicationCharacterValue)
4.7.2.3. Integer-valued Dimensioning Indication (DimensioningIndicationIntegerValue)
4.7.2.4. Measure-valued Dimensioning Indication (DimensioningIndicationMeasureValue)
4.7.2.5. Real-valued Dimensioning Indication (DimensioningIndicationRealValue)
4.7.2.6. Dimensioning Indication (DimensioningIndicationValue)
4.8. Theme-specific Requirements
(2) The spatial object type CoverageByDomainAndRange must only be of subtypes...
(3) Where a zone has been established to regulate planned land...
(4) Based on the INSPIRE horizontal coordinate reference system, each appropriate...
(5) The use of the common metadata element ‘Spatial Resolution’ (according...
(6) Data providers shall include the following keywords in addition to...
5.4. Theme-specific Requirements
(1) Statistical information on the spatial data theme Human Health and...
(2) Where possible, the ICDValue code list shall be used to...
(3) Raw measurement data shall be based on ISO/TS 19103:2005.
(4) Health determinant statistical data shall be modelled as health statistical...
(5) Health determinant coverages shall be represented using the spatial object...
6. UTILITY AND GOVERNMENTAL SERVICES
6.1. Structure of the Spatial Data Theme Utility and Governmental Services...
6.4. Oil-Gas-Chemicals Network
6.8. Environmental Management Facilities
6.9. Administrative And Social Governmental Services
7. ENVIRONMENTAL MONITORING FACILITIES
7.1.1. Abstract Monitoring Feature (AbstractMonitoringFeature)
7.1.2. Abstract Monitoring Object (AbstractMonitoringObject)
7.1.3. Environmental Monitoring Activity (EnvironmentalMonitoringActivity)
7.1.4. Environmental Monitoring Facility (EnvironmentalMonitoringFacility)
7.1.5. Environmental Monitoring Network (EnvironmentalMonitoringNetwork)
7.1.6. Environmental Monitoring Programme (EnvironmentalMonitoringProgramme)
9. AGRICULTURAL AND AQUACULTURE FACILITIES
11. AREA MANAGEMENT/RESTRICTION/REGULATION ZONES AND REPORTING UNITS
13. ATMOSPHERIC CONDITIONS AND METEOROLOGICAL GEOGRAPHICAL FEATURES
15.4. Theme-specific Requirements
(1) The Sea spatial object type shall be used to describe...
(2) The MarineExtent of a Sea spatial object shall have a...
(3) The low water level used to define an IntertidalArea shall...
(4) The code lists defined in the spatial data theme Oceanographic...
(5) SeaAreas shall be represented as 2-dimensional geometries.
IMPLEMENTING RULES FOR THE INTEROPERABILITY OF INVOCABLE SPATIAL DATA SERVICES
IMPLEMENTING RULES FOR THE HARMONISATION OF INTEROPERABLE SPATIAL DATA SERVICES