Deprecated: Return type of YDataTable::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bdavid/prod/georef/yamldoc/ydclasses/ydata.inc.php on line 428

Deprecated: Return type of YamlDataTable::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/bdavid/prod/georef/yamldoc/ydclasses/yamldata.inc.php on line 295
inspire-mdcvoc (pub)
Menu : html yaml json edit check reindex dump unset
* 

{
    "prefLabel": {
        "fr": "Zones de gestion, de restriction ou de réglementation et unités de déclaration",
        "en": "Area management/restriction/regulation zones and reporting units"
    },
    "inScheme": [
        "inspireThemesAnnexIII"
    ],
    "topConceptOf": [
        "inspireThemesAnnexIII"
    ],
    "definition": {
        "fr": "Zones gérées, réglementées ou utilisées pour les rapports aux niveaux international, européen, national, régional et local. Sont inclus les décharges, les zones restreintes aux alentours des sources d'eau potable, les zones vulnérables aux nitrates, les chenaux réglementés en mer ou les eaux intérieures importantes, les zones destinées à la décharge de déchets, les zones soumises à limitation du bruit, les zones faisant l'objet de permis d'exploration et d'extraction minière, les districts hydrographiques, les unités correspondantes utilisées pour les rapports et les zones de gestion du littoral."
    },
    "broader": [
        "planningCadastre"
    ],
    "scopeNote": {
        "en": "The theme \"Area management/restriction/regulation zones and reporting units” is thematically broad and encompasses any zones that are established in accordance with a legislative requirement related to an environmental policy or a policy or activity that may have an impact on the environment at any level of administration (international, European, national and sub-national).  \nThe zones are typically established to deliver specific objectives related to any environmental media, for example, air, water, soil and biota (plants and animals). This includes, but is not limited to, objectives established to protect and improve environmental quality (includes reducing pollution levels), protect and conserve environmental and natural resources, protect and control risk from natural and man-made hazards, protect plant, animal and human health or control development.  \nThe theme also addresses reporting units, which are defined as \"spatial objects that provide the spatial reference for any non-spatial data exchanged under environmental reporting obligations.” The reported non-spatial data must include a property that contains a reference to the spatial object. This is typically an identifier, code or name and is a join key between the spatial and non-spatial objects enabling the data to be combined. This allows the non-spatial data to be visualised as a map or enable spatial analysis.  \nDifferent INSPIRE spatial object types can perform the role of \"Reporting Unit”. For example, surface waters (rivers, lakes and canals from the Annex I theme Hydrography) are \"Reporting Units” for indicators of chemical and ecological status. Thus, Reporting units cannot be modelled as a distinct spatial object type and no specific reporting units data model is defined. Instead, the theme defines obligations on how to make reporting units spatial data available under INSPIRE.\n"
    }
}