Versionen im Vergleich

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.

...

Panel
borderColorgrey
borderStylesolid
titleExample given (Species Distribution):

Required Layers:

    • Layer Name: SD.<CodeListValue> (1)
    • Layer Title: Species Distribution (of <human readable name>)
    • Spatial object type: SpeciesDistributionUnit (speciesName / referenceSpeciesId: ReferenceSpeciesCodeValue)

(1)   One layer shall be made available for each code list value, in accordance with Art. 14(3).

The relevant code list contains ???? code list values contains three code lists [see INSPIRE Registry: https://inspire.ec.europa.eu/codelist/ReferenceSpeciesCodeValue]. The first code liste "EU_norm" has more than 53.000 entries (http://www.eu-nomen.eu/portal/stats.php)



With x different code list values in the dataset, x layers must be provided. When using predefined map-tiles for performance considerations this could increase the costs by a multiple of x compared to a single layer where all features have been compiled together. The implementation of viewing servises for "Species Distribution" is technically not feasable due to the very large number of codelistvalues and therefore layers. 

...

Remove the obligation to provide a layer for each code list value for features of the same feature type. If not already mandated, replace this obligation by providing a single layer including all feature types regardless of specific code list values or multiply multiple layers e.g. to display classes of species instead of ieach each species indidivually. 

Impact on INSPIRE TG

The Technical Guidance would need to be updated according to the changesin the INSPIRE Implementing Rule.Hinweis auf: Helpdesk Issue 39 (https://github.com/INSPIRE-MIF/helpdesk-validator/issues/39) View Service WMS validator too strict: harmonized layer names should not be mandatory #39 ?