Cross-Annex issues in the INSPIRE Data Specification process: Administrative Units [AU] and Statistical units [SU] case study

Transcription

1 Cross-Annex issues in the INSPIRE Data Specification process: Administrative Units [AU] and Statistical units [SU] case study Alina Kmiecik [PL] Member of INSPIRE AU TWG Facilitator of INSPIRE SU-PD TWG 1

2 Presentation content and objective An overview of the process used in developing the AU data specification, Issues, decisions and lessons learnt, cross-theme and cross-annex correspondances, SU perspective to the outcome from Annex I. 2

3 TWG AU People Jesper M. Paasch, Sweden, facilitator Geir Myrind, Norway, editor Katalin Toth, JRC contact person Ingrid Naumann, Germany, expert Frederic Mortier, Belgium, expert Ulrich Düren, Germany, expert Alina Kmiecik, Poland, expert 3

4 Development Process Use case development As-is analysis Identification of user requirements and spatial object types Gap analysis Data specification development Implementation, testing and validation Cost-benefit analysis 4

5 Administrative Units - Definition Units of administration, dividing areas where Member States have and/or exercise jurisdictional rights, for local, regional and national governance, separated by administrative boundaries. reference data that constitute the spatial frame for linking to and/or pointing at other information that belong to specific thematic fields such as the environment and socio-economic statistics, alongside many others. administrative units correspond to other teritory division systems e.g. cadastral parcels, census districts, postal regions, sea regions, statistical units, or sector-specific regions. 5

6 General Conditions / Requirements Territory division systems like cadastral parcels, census districts, postal regions, sea regions, statistical units, or sector-specific regions are not considered to constitute a part of the definition of administrative units; they are within the scope of other INSPIRE themes. Reference to the Nomenclature of Territorial Units for Statistics (NUTS), established by the European Office for Statistics (Eurostat) is mandatory in order to provide a single uniform breakdown of territorial units for the production of regional Statistics for the European Union. DS shall comply with GISCO database of EUROSTAT, which is for the AU-part based on the EuroBoundaryMap specifications (EuroGeographics)... distinction between land and (coastal) water parts of administrative units... 6

7 Thematic overlaps Geographical names Addresses Cadastral parcels Hydrography Protected sites Elevation Statistical units Land use Human health and safety Population distribution - demography Area management/restriction/regulation zones & reporting units Energy resources Postal codes can refer to administrative units The boundary of administrative unit is established based on the boundaries of cadastre parcels Administrative boundaries might overlap with the coastlines Statistical units can correspond to the administrative units 7 7

8 Reference material 40 positions submitted into the process Dutch(1), English(24), Italian(8), Norvegian(2), French(6) 8 duplicates 32 reference material identified as relevant list of required administrative units, hierarchy levels, properties, managing life cycles EBM, ERM, INTESA GIS, NUTS classification 8 8

9 As-is analysis 87 positions collected for analysis Dutch(1), English(24), Italian(8), Norvegian(2), French(6) 12 items redirected to HY, CP, BU, AD, SU, LU 8 items partialy considered 10 items identified as not relevant 8 duplicated items individual assignment of material for review among 7 TWG Members based on language preferences and knowledge over 3 months of work Taugh work but worth to be done at very begining to facilitate future TWG activities 9 9

10 Purpose / Use Cases Administrative units form an indirect spatial reference system. The reference to an administrative unit provides a spatial dimension to data without using coordinates [INSPIRE IMS 2003] Examples on high-level use-cases: Discovery of units related data searching/filtering other spatial data based on a name or code, linking/publishing thematic information finding competent authorities e.g. in case of disasters, for environmental protection, etc. boundary-based analysis of consistency of spatial objects 10

11 Operational validation 11

12 Operational validation 12

13 Operational validation UNIT A 13

14 Version1/2 abstracting EBM class overview «enumeration» CoastlineType «enumeration» BoundaryStatusType Definite = 1 Indefinite = 2 In dispute = 3 Coastline coastal waters Coastline/shoreline inland waters +admarea 1..2 Administrativ eunitarea + geometry: GM_Surface + id: Identifier + administrativeareatype: AdministrativeAreaType + landcovertype: LandCoverType «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] + validfrom: DateTime + validto: DateTime [0..1] «enumeration» BoundaryLev eltype 1st order = 1 2nd order = 2 3rd order = 3 4th order = 4 5th order = 5 6th order = 6 +boundary Coastline + type: CoastlineType 1..* 1..* «enumeration» MeaningOfLineType Boundary line between land and water = 1 Boundary line on land = 7 Boundary line on water = 9 Boundary + geometry: GM_Curve + id: Identifier + country: CountryCode «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] + validfrom: DateTime + validto: DateTime [0..1] +administrativearea Administrativ eboundary + boundarylevel: BoundaryLevelType + meaningofline: MeaningOfLineType + boundarystatus: BoundaryStatusType = Definite Administrativ eunitlow estlev el +administrativeunit +/ geometry: GM_MultiSurface [0..1] 1..* + LAUcode: CharacterString [0..1] more than one only for condominiums +boundary 1..* +admunit adminunithierarchy /* A higher level unit (e.g. administrative level of 1) must have a lower value for administrativelevel than lower level units (e.g. having a administrative level of 2). */ inv: self.administrativelevel < self.lowerlevelunit.administrativelevel AdministrativeUnit + SHNcode: CharacterString + id: Identifier + nationallevel: AdministrativeHierarchyLevel + country: CountryCode +admunit + name: GeographicalName [0..*] + validfrom: DateTime 1..* + nationallevelname: CharacterString [0..*] + validto: DateTime [0..1] + residenceofauthority: ResidenceOfAuthority [0..1] «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] 1..* constraints {adminunithierarchy} 1..* Administrativ eunitupperlev el +/ geometry: GM_MultiSurface [0..1] +lowerlevelunit upperlevelunit «datatype» ResidenceOfAuthority + name: GeographicalName + representationalpoint: GM_Point «enumeration» AdministrativeHierarchyLevel 1st order (country level) = 1 2nd order = 2 3rd order = 3 4th order = 4 5th order = 5 6th order = 6 «enumeration» Administrativ eareatype «enumeration» LandCov ertype +NUTS 1..3 Main area = 1 Branch area = 3 Special area = 4 Land area Coastal water Inland water NUTSRegion + id: Identifier + NUTScode: CharacterString + NUTSlabel: CharacterString + NUTSLevel: NUTSLevelType + validfrom: DateTime +/ geometry: GM_MultiSurface [0..1] + validto: DateTime [0..1] «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] «enumeration» NUTSLevelType NUTS 1 Level NUTS 2 Level NUTS 3 Level 14

15 Version 1: Comments resolution 130 comments for version 1( internal) 13 redirected to CT 3 redirected to DT-DS. 37 applied with modifications 13 not accepted unknown / unpopulated relationships between units and boundaries, consolidation to the work done by other themes: geographical names, hydrography (coastline) feature/attributes definitions 15 15

16 Version 2: Comments resolution 395 comments from TWGs, SDICs and LMOs 24 redirected to CT, DT-DS., 56 applied with modifications 37 not accepted 45 duplicated comments 16 16

17 Long coastlines story Boundary +boundary 1..* + geometry: GM_Curve + id: Identifier + country: CountryCode «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] +boundary 1..* +adm «voi + validfrom: DateTime + validto: DateTime [0..1] Coastline + type: CoastlineType Administrativ eboundary + boundarylevel: BoundaryLevelType + meaningofline: MeaningOfLineType + boundarystatus: BoundaryStatusType = Definite 17

18 Version 3: keep things simple class overview «enumeration» TechnicalStatusValue edgematched notedgematched «codelist» AdministrativeHierarchyLevel + 1stOrder + 2ndOrder + 3rdOrder + 4thOrder + 5thOrder + 6thOrder «enumeration» LegalStatusValue agreed notagreed +coadminister 0..* +administeredby 0..* Administrativ eunit Administrativ eboundary + geometry: GM_Curve + inspireid: Identifier + country: CountryCode + nationallevel: AdministrativeHierarchyLevel [1..6] 1..* + legalstatus: LegalStatusValue = "agreed" + technicalstatus: TechnicalStatusValue = "edge-matched" «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] +boundary +admunit 1..* + geometry: GM_MultiSurface + nationalcode: CharacterString + inspireid: Identifier + nationallevel: AdministrativeHierarchyLevel + country: CountryCode + name: GeographicalName [1..*] + nationallevelname: LocalisedCharacterString [1..*] + residenceofauthority: ResidenceOfAuthority [1..*] «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] constraints {CondominiumsAtCountryLevel} {AdmininstrativeUnitHighestLevel} {AdministrativeUnitLowestLevel} +upperlevelunit lowerlevelunit 0..* «datatype» ResidenceOfAuthority + name: GeographicalName + geometry: GM_Point +admunit 1..* +condominium 0..* Condominium + inspireid: Identifier + geometry: GM_MultiSurface + name: GeographicalName [0..*] «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] +NUTS 1..3 NUTSRegion + geometry: GM_MultiSurface + inspireid: Identifier + NUTSCode: CharacterString «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] 18

19 Is UML precise enough for unique common view of AU? B0 Administrative Boundary: B1 B2 B3 B4 B3.level = 1stOrder, 2ndOrder B5 B6 B7 B8 19

20 Is UML precise enough for unique common view of AU? Administrative Boundary: B1 B2 B3 B4 B5 B3.level = 2ndOrder B6 B7 B0 Administrative Boundary: B0.level = 1ndOrder B8 20

21 Coastline goes to Annex II:EL 21

22 Predefined feature in Annex III: Statistical Units units for dissemination and use of statistical information; support establishment, aggregation, assessment and display of statistical information i.e. any numerical representation of some observed phenomenon; geo-reference statistical data from different statistical fields like demography, economy, environment and natural resources are organized into hierarchy, can have temporal characteristics and timedependent relations to other feature types representing units of territorial dissemination, can be spatially represented by: areas e.g. NUTs regions, census and statistical districts, urban areas, management zones, postal codes, reporting units, points corresponding to the addresses, households, can spatially link to administrative units, address, or land cover. 22

23 Relationships with Annex III:SU pkg Package Structure «applicationschema» StatisticalUnits + NUTSRegion «applicationschema» Base Types + Identifier + SpatialDataSet + VoidReasonValue + ConditionOfFacilityValue + VerticalPositionValue (from Generic Conceptual Model) 23

24 [SU] what to do with an already defined feature type? +upperlevel 0..* StatisticalUnit the hierarchy of statistical Units can be build based on the same type of unit i.e. hierarchy of Grid StatisticalUnit or hierarchy of Area Statistical units, not the mixture GridStatisticalUnit StatisticalUnitWithTime - validfrom: DateTime - validto: DateTime 0..1 AdministrativeUnits::AdministrativeUnit +referencegridcell Quadrilateral Grid:: CV_GridCell {root} PointStatisticalUnit - geometry: GM_Point AreaStatisticalUnit - geometry: GM_MultiSurface LinearStatisticalUnit - geometry: GM_MultiCurve +lowerlevelregion +NUTS 1..3 NUTSRegion +upperlevelregion 0..1 «Codelist» NUTSHierarchy - 1stLevel: int - 2ndLevel: int - 3rdLevel: int - LAU1: int - LAU2: int + geometry: GM_MultiSurface + inspireid: Identifier + NUTSCode: CharacterString - NUTSLevel: NUTSHierarchy - validfrom: DateTime - validto: DateTime «voidable, lifecycleinfo» + beginlifespanversion: DateTime + endlifespanversion: DateTime [0..1] 24

25 Questions? Intergraph Corporation Alina Kmiecik IT Analyst Security, Government & Infrastructure Facilitator of INSPIRE TWG on Statistical Units & Population distribution-demography t: +48.(42) m: +48.(66) Intergraph Polska Sp. z. o.o. f: +48.(42) ul. Piotrkowska Łódź, Polska 25