Inspire revision 4711
Gyldig
A set of documents that indicates a strategic direction for the development of a given geographic area, states the policies, priorities, programmes and land allocations that will implement the strategic direction and influences the distribution of people and activities in spaces of various scales. Spatial plans may be developed for urban planning, regional planning, environmental planning, landscape planning, national spatial plans, or spatial planning at the Union level.
| Egenskap |
Stereotype |
Beskrivelse |
Type |
Multiplisitet |
| inspireId |
|
|
Identifier
(datatype)
|
1..1 |
| - localId |
|
|
CharacterString |
1..1 |
| - namespace |
|
|
CharacterString |
1..1 |
| - versionId |
|
|
CharacterString |
0..1 |
| extent |
|
|
GM_MultiSurface |
1..1 |
| beginLifespanVersion |
|
|
DateTime |
1..1 |
| officialTitle |
|
|
CharacterString |
1..1 |
| levelOfSpatialPlan |
|
-- Name --
level of spatial plan
|
LevelOfSpatialPlanValue
(kodeliste)
|
1..1 |
| endLifespanVersion |
|
|
DateTime |
0..1 |
| validFrom |
|
|
Date |
0..1 |
| validTo |
|
|
Date |
0..1 |
| alternativeTitle |
|
|
CharacterString |
1..1 |
| planTypeName |
|
|
PlanTypeNameValue
(kodeliste)
|
1..1 |
| processStepGeneral |
|
|
ProcessStepGeneralValue
(kodeliste)
|
1..1 |
| backgroundMap |
|
-- Name --
background map
|
BackgroundMapValue
(datatype)
|
1..1 |
| - backgroundMapDate |
|
-- Name --
background map date
|
DateTime |
1..1 |
| - backgroundMapReference |
|
|
CharacterString |
1..1 |
| - backgroudMapURI |
|
-- Name --
background map URI
|
URI |
1..1 |
| ordinance |
|
|
OrdinanceValue
(datatype)
|
1..* |
| - ordinanceDate |
|
|
DateTime |
1..1 |
| - ordinanceReference |
|
|
CharacterString |
1..1 |
| Name |
Type |
English |
Description |
| inspireId |
Identifier
|
|
External object identifier of the spatial plan.
-- Description --
NOTE An external object identifier is a unique object identifier published by the responsible body, which may be used by external applications to reference the spatial object. The identifier is an identifier of the spatial object, not an identifier of the real-world phenomenon. |
| extent |
GM_MultiSurface |
|
Geometrical union of all the instances of the spatial objects ZoningElement and SupplementaryRegulation. When a SpatialPlan is only composed of a document, the attribute extent is the border of the cartographic image that contains the land use information (i.e. the land use map extent). |
| beginLifespanVersion |
DateTime |
|
Date and time at which this version of the spatial object was inserted or changed in the spatial data set. |
| officialTitle |
CharacterString |
|
Official title of the spatial plan. |
| levelOfSpatialPlan |
LevelOfSpatialPlanValue
|
|
Level of the administrative units covered by the plan.
-- Description --
Member states should make a mapping to this enumeration. |
| endLifespanVersion |
DateTime |
|
Date and time at which this version of the spatial object was superseded or retired in the spatial data set. |
| validFrom |
Date |
|
First date at which this spatial plan is valid in reality. |
| validTo |
Date |
|
The time from which the spatial plan no longer exists in the real world. |
| alternativeTitle |
CharacterString |
|
Alternative (unofficial) title of the spatial plan. |
| planTypeName |
PlanTypeNameValue
|
|
Name of the type of plan that the Member State has given to the plan.
-- Description --
NOTE The admissible values for this attribute are managed at the member state level via a code list
EXAMPLE:
FR: DTA, SCOT, PLU, etc.
DE: Bebauungsplan, Flächennutzungsplan, Regionalplan, Landesentwicklungsplan
NL: bestemmingsplan, structuurvisie. |
| processStepGeneral |
ProcessStepGeneralValue
|
|
General indication of the step of the planning process that the plan is undergoing.
-- Description --
NOTE This enumeration contains values that are common to most planning systems.
|
| backgroundMap |
BackgroundMapValue
|
|
Identification of the background map that has been used for constructing this Plan. |
| ordinance |
OrdinanceValue
|
|
Reference to relevant administrative ordinance.
-- Description --
NOTE This attribute is multiple because, independently from the current legal status of the plan, there can be references to more than one ordinance, in relation to the different steps that the planning process has already undergone (e.g. ordinance for the preparation of a new plan, ordinance of adoption, ordinance of approval, etc.). |