INSPIRE Planned Land Use as a basis for revising SOSI Planned … · 2016. 9. 23. · SOSI Feature Catalogue shall gradually align with the specifications referenced from our Geodata

INSPIRE Planned Land Use as a basis for revising SOSI Planned Land Use

Presentation at INSPIRE Conference 2016,

Barcelona, September 27th

Morten Borrebaek

Norwegian Mapping Authority

Outline • Background

• Project goals and achievements

• Norwegian Standard SOSI

• SOSI standardization strategy

• Extension pattern (subtyping, realization, redefine)

• Summary and conclusions

Background

Update of SOSI Planned Land Use according to:

• The Planning and Building Act of 27th of June 2008 • 3D

• Synchronization with the Digital Planning Registers. • Modelling of planning decisions • Synchronization with building processes • Update of UML models according to revised versions of ISO 19103

(2015) Conceptual Schema Language and ISO 19109 (2015)Rules for application schemas.

• Alignment with INSPIRE Planned Land Use

For detailed presentation of Planned Land Use in 3D, see presentation «Improved Land Use Planning in 3D» by Tor Gunnar Øverli and Hilde Johannesen Bakken Thursday at 14:00.

SOSI standards and UML model repository

Standardization since 1990’s • Set of standards for modelling of

geographic information, and mapping to realization platforms (GML + SOSI)

• Fully ISO 191xx compliant • EA SVN model repository

• ISO standards and European specifications

• General concepts • General feature catalogue (57

themes) • Several versions • Product specifications according to

ISO 19131. • Model validation script according to

ISO 19103 (2015) and ISO 19109 (2015).

• Web view (geonorge.no)

National strategy for further development of SOSI.

Extension mechanisms are standardized as part of SOSI, and consists of :

SOSI Feature Catalogue shall gradually align with the specifications referenced from our Geodata act (INSPIRE) where appropriate, and at the same time fulfill requirements in national laws, regulations and use cases identified at the national level.

• Subtyping • Realization • (Redefine)

If there is no relationship to INSPIRE, a note should be added to the introduction of the specification.

Rules for extensions in INSPIRE

Annex F

(informative)

Example for an extension to an

INSPIRE application schema

Extending an INSPIRE data specification would imply at a minimum that: - the extension does not change anything in the INSPIRE data

specification but normatively references it with all its requirements - the extension does not add a requirement that breaks any requirement

of the INSPIRE data specification

F.2 General rules

Approach 1 – Subtyping according to the experience of the modelling rules applied in the ELF (European Location Framework) models

class Hov eddiagram INSPIRE tilpasning uten plan-assosiasjoner

Kommune(del)plan Regulerings- og bebyggelsesplaner

«featureType»

Arealplan

«featureType»

KpOmråde

«featureType»

RpOmråde

constraints

{Kan bare ha assoisasjon tl rp_ objekter}

«featureType»

Arealformål

«featureType»

HensynOgBestemmelser

«featureType»

Plandokumentasjon

+ inspireId: Identifier

«voidable»

+ pbl2008: LegislationCitation [0..1]

+ planbestemmelse: CharacterString [0..1]

+ planbeskrivelse: DocumentCitation [0..1]

«featureType»

KpArealformålOmråde

«featureType»

KpArealbrukOmråde

«featureType»

RpArealformålOmråde

«featureType»

RbFormålOmråde

«featureType»

KpAngittHensynSone

«featureType»

KpBestemmelseOmråde

«featureType»

KpBåndleggingSone

«featureType»

KpDetaljeringSone

«featureType»

KpFareSone

«featureType»

KpRestriksjonOmråde

«featureType»

KpRetningslinjeOmråde

«featureType»

RpAngittHensynSone

«featureType»

RpBestemmelseOmråde

«featureType»

RpBåndleggingSone

«featureType»

RpDetaljeringSone

«featureType»

RpFareSone

«featureType»

RpGjennomføringSone

«feature...

RpSikringSone

«featureTy...

RpStøySone

«featureType»

RbBev aringOmråde

«featureType»

RbFareOmråde

«featureType»

RbFornyelseOmråde

«featureType»

RbRekkefølgeOmråde

«featureType»

RbRestriksjonOmråde

INSPIRE

SOSI plan - eksisterende lov

SOSI plan - Gammel lov

SOSI plan - felles

Forklaring til fargebruk

+officialDocument

«voidable»1..*

+plan

1

+member

0..*

+plan

1

+restriction

0..*

+officialDocument

«voidable»

1..*

1

+officialDocument

«voidable»

1..*

OfficialDocumentation

SupplementaryRegulation SpatialPlan ZoningElement

Preliminary scheme of harmonization - Land-use element of the municipality master plans class Hov eddiagram Arealplan

Datatyper og kodelister definert i INSPIRE

«codeList»

Kp felles::KpPlantype

+ Kommuneplanens arealdel = 20

+ Kommunedelplan = 21

+ Mindre endring av kommune(del)plan = 22

«featureType»

Kp felles::KpOmråde

+ arealplanId: NasjonalArealplanId

+ plantype: KpPlantype

+ planstatus: Planstatus

+ planbestemmelse: KpPlanbestemmelser

+ lovreferanse: LovreferanseType

+ lovreferanseBeskrivelse: CharacterString [0..1]

+ vedtakEndeligPlanDato: Date [0..1]

+ kunngjøringsdato: Date [0..1]

+ opprinneligplanid: CharacterString [0..1]

+ opprinneligadministrativenhet: CharacterString [0..1]

::SpatialPlan

+ identifikasjon: Identifier

+ område: GM_MultiSurface

+ plannavn: CharacterString

+ plantypeINSPIRE: LevelOfSpatialPlanValue


«slettes»

+ område: Flate [0..1]

+ posisjon: Punkt [0..1]

+ ikrafttredelsesdato: Date [0..1]

+ plannavn: CharacterString [0..1]

«lifeCycleInfo, voidable»

::SpatialPlan

+ vedtakEndeligPlandato: DateTime

+ sluttdato: DateTime [0..1]

«voidable»

::SpatialPlan

+ gyldigFra: Date [0..1]

+ gyldigTil: Date [0..1]

+ alternativtPlannavn: CharacterString

+ planstatusINSPIRE: ProcessStepGeneralValue

+ basiskart: BackgroundMapValue

+ vedtaksorgan: OrdinanceValue [1..*]

«featureType»

Planned Land Use::Arealplan

+ identifikasjon: Identifier

+ område: GM_MultiSurface

+ plannavn: CharacterString




+ vedtakEndeligPlandato: DateTime

+ sluttdato: DateTime [0..1]

«voidable»

+ gyldigFra: Date [0..1]

+ gyldigTil: Date [0..1]




+ vedtaksorgan: OrdinanceValue [1..*] «codeList»

Planned Land Use::

Lev elOfSpatialPlanValue

«codeList»

Planned Land Use::

ProcessStepGeneralValue

Eksternt forvaltet kodeliste:

http://inspire.ec.europa.eu/codelist/ProcessStepGeneralValue

-in the process of adoption

-legally binding or active

-obsolete

-under elaboration

Eksternt forvaltet kodeliste:

http://inspire.ec.europa.eu/codelist/LevelOfSpatialPlanValue

-infra-local

-infra-regional

-local

-national

-other

-regional

-supra-local

-supra-regional

«codeList»

Planned Land Use::

KpPlantype

Types of plans as defined in the Member States. The

allowed values for this code list comprise any values

defined by data providers

NOTE For each plan type name a level of spatial plan

must be provided using the enumeration

LevelOfSpatialPlanValue

«dataType»

Planned Land Use::BackgroundMapValue

+ bakgrunnskartDato: DateTime

+ bakgrunnskartType: CharacterString

«voidable»

+ backgroudMapURI: URI

«dataType»

Planned Land Use::OrdinanceValue

+ vedtaksdato: DateTime

+ vedtaksorgan: CharacterString

«featureType»

Planned Land Use::

Arealformål

«featureType»

Planned Land Use::


+plan

1

+member

0..*

+plan

1

+restriction

0..*

Approach 2 – Use the realization extension pattern to identify the relationship to INSPIRE. class Hov eddiagram INSPIRE

«featureType»

Planned Land Use::OfficialDocumentation


«voidable»

+ legislationCitation: LegislationCitation [0..1]

+ regulationText: CharacterString [0..1]

+ planDocument: DocumentCitation [0..1]

«featureType»

Planned Land Use::SpatialPlan


+ extent: GM_MultiSurface

+ officialTitle: CharacterString

+ levelOfSpatialPlan: LevelOfSpatialPlanValue

+ planTypeName: PlanTypeNameValue


+ beginLifespanVersion: DateTime

+ endLifespanVersion: DateTime [0..1]

«voidable»

+ validFrom: Date [0..1]

+ validTo: Date [0..1]

+ alternativeTitle: CharacterString

+ processStepGeneral: ProcessStepGeneralValue

+ backgroundMap: BackgroundMapValue

+ ordinance: OrdinanceValue [1..*]

«featureType»

Planned Land Use::SupplementaryRegulation


+ geometry: GM_Object

+ regulationNature: RegulationNatureValue

+ supplementaryRegulation: SupplementaryRegulationValue [1..*]

«voidable»



+ specificSupplementaryRegulation: SpecificSupplementaryRegulationValue [1..*]



+ dimensioningIndication: DimensioningIndicationValue [0..*]

+ inheritedFromOtherPlans: Boolean

+ specificRegulationNature: CharacterString

+ name: CharacterString [0..*]




«featureType»

Planned Land Use::ZoningElement


+ geometry: GM_MultiSurface

+ hilucsLandUse: HILUCSValue [1..*]

+ regulationNature: RegulationNatureValue

«voidable»



+ hilucsPresence: HILUCSPresence

+ specificLandUse: LandUseClassificationValue [1..*]

+ specificPresence: SpecificPresence



+ dimensioningIndication: DimensioningIndicationValue [0..*]




INSPIRE Planned Land Use

SOSI

Planning Rregister

Forklaring til fargebruk

«featureType»


+ identifikasjon: Identifikasjon

+ geometri: GM_Object

+ legalitet: RegulationNatureValue

+ hensynsoneBestemmelser: SupplementaryRegulationValue

+ gyldigFra: DateTime [0..1]

+ gyldigTil: DateTime

+ hensynssonetype: SpecificSupplementaryRegulationValue [1..*]



+ utnyttelsesgrad: DimensioningIndicationValue [0..*]

+ arvetFraReguleringsplan: boolean

+ plantypeGenerelt: CharacterString

+ plannavn: CharacterString [0..*]



«featureType»

Arealplan


+ geometri: GM_Surface






+ plantype: PlanTypeNameValue

+ vedtaksorgan: OrdinanceValue

+ plannavn: CharacterString [0..*]




«featureType»

Arealformål


+ geometri: GM_Surface

+ legalitet: RegulationNatureValue

+ hensynsoneBestemmelser: SupplementaryRegulationValue




+ utnyttelsesgrad: DimensioningIndicationValue [0..*]



+ arealformålskode: HILUCSValue [1..*]

- D: int

Ikke ferdig

«featureType»

Planregister 2016Utkast::Plandokumentasjon


+ PBL2008: integer

«Geointegrasjon»

+ finnPlandokumenter(characterString, Saksnummer, boolean, PlanKontekst): Plandokument

+relasjonTilAnnenPlan 0..*

0..*

+officialDocument

«voidable»

1..*

+officialDocument

«voidable»

1..*

1

+offisiellDokumentasjon

1..*


1..*

+plan

1

+member

0..*

+arealformål

1..*

+plan

1

+officialDocument

«voidable»1..*

+relasjonTilAnnenPlan 0..*


1..*

+plan

1

+restriction

0..*

+restriksjon

0..*

+plan

1

Summary and conclusions • Our SOSI model for Planned Land Use including the model for the

planning register fits quite well with the INSPIRE Planned Land Use, but a generalized level for INSPIRE is required and is an extra burden.

• Our existing model (and the Planning and Building Act) has stronger semantics than INSPIRE (for example: Compositions rather than aggregations). No interest to weaken the semantics in the model to fulfil INSPIRE extensions informative rules.

• At the current stage, we are using the realization relationship, including a matching table (from ESDIN/ELF project) to document the mapping between INSPIRE and the SOSI/Planning Register.

• UML 2.4 has a different extension pattern <redefine> that would fit well, but there is a lack of tool support.

• We will continue to examine the result from the JRS/Geonovum Extension pattern project.

• INSPIRE extension rules are too strict.

Example of <redefine>

Documents

INSPIRE Planned Land Use as a basis for revising SOSI Planned … · 2016. 9. 23. · SOSI Feature Catalogue shall gradually align with the specifications referenced from our Geodata