INSPIRE KEN: Workshop about transformation of themes: Hydrography. Alicia González Jiménez IGN-Spain

Size: px

Start display at page:

Download "INSPIRE KEN: Workshop about transformation of themes: Hydrography. Alicia González Jiménez IGN-Spain"

Sabrina Lucas
6 years ago
Views:

INSPIRE KEN: Workshop about transformation of themes: Hydrography Celia Sevilla Sánchez (cssanchez@fomento.

1 INSPIRE KEN: Workshop about transformation of themes: Hydrography Celia Sevilla Sánchez Julián Delgado Hernández 21-22/10/2014 Alicia González Jiménez IGN-Spain 1

2 Main Hydrography Datasets in Spain Competence and responsibility on HY data is spread and it depends on the type of the data (geometry or semantic data) IGN (Ministry Public Works) DG Agua & Hydro- Confederations (Ministry Environment & Agriculture) or Water Agencies (Regional Governments)

Main Hydrography Datasets in Spain Main national datasets: IGN:

Models DG Agua: Water Integrated System, National System of

Calidad y Evaluacion Ambiental: National Wetland Inventory

3 Main Hydrography Datasets in Spain Main national datasets: IGN: National Topographic Databases (BTN) and Digital Elevation Models DG Agua: Water Integrated System, National System of Floods Zones (SCNZI), Dams & Reservoirs Inventory (IPE) DG Calidad y Evaluacion Ambiental: National Wetland Inventory (INZH) Hydro-Confederations: Hydrologic Automatic Information System (SAIH) Etc.

IGN works regarding HY: GRIHY Objetive (GRIHY): To have geographic reference information (GRI) about hydrography compliant to INSPIRE, from data IGN which

4 IGN works regarding HY: GRIHY Objetive (GRIHY): To have geographic reference information (GRI) about hydrography compliant to INSPIRE, from data IGN which should be enriched with other HY sources attributes in order to satisfy Spanish users requirements Principals GRI: Objective information As High resolution as possible (e.xy=3m, e.z=0.5m) Good quality: geometrical, semantic and topological Sustainable along time As automatic as possible DEM consistent Oriented with flow water direction Hydrologic codification Harmonized with rest of parallel themes (i.e. marine regions, area & regulation zones, land cover, transports, buildings, etc.)

IGN-HY data model definition according to INSPIRE Matching process: The main HY datasetshave been analysedin relation with INSPIRE in order to identify missing-overlap objects and the correspondence

5 IGN-HY data model definition according to INSPIRE Matching process: The main HY datasetshave been analysedin relation with INSPIRE in order to identify missing-overlap objects and the correspondence between features, attributes, and code lists values. -> RESULT: Data Identification that should be considered in GRI HY Data model to be compliance with INSPIRE and represent correctly this theme in Spain as well. INSPIRE specifications Native National datasets UML Model: from INSPIRE xmi filesand using Enterprise Architecsoftware INSPIRE HY UML has been extended to represent HY information considered in GRI-HY but nonexisting in INSPIRE.

6 Application Schema: main differences Main differences regarding INSPIRE HY New attributes added Modification of some data value (free text -> codelist) Don t use voidable nor optional attributes, and values without relevance in the Spanish scope Hydrography packages Fully INSPIRE Outside of work, because this package was moved to regulation areas theme Extended according Spanish scope

7 INSPIRE object IGN object Extensionof INSPIRE model(following GCM v3.4, annex F). To add new attribute it is required to create a new object, as sub-class, to add there the new attribute. class Hydrography - Physical Waters, surface waters Example of Physical Waters (PhW) +neighbour 0..* HydroObject Hydro - Physical Waters::SurfaceWater + geometry :GM_Primitive + inspireid :Identifier + levelofdetail :MD_Resolution [0..1] «voidable, lifecycleinfo» + beginlifespanversion :DateTime + endlifespanversion :DateTime [0..1] + localtype :LocalisedCharacterString [0..1] + origin :OriginValue + persistence :HydrologicalPersistenceValue + tidal :Boolean localtype is shaped as SurfaceWaterValue instead as LocalisedCharacterString SurfaceWaterValue + naturalwatercourse + canal + ditch + lake + reservoir + pool tags owner = DGAgua & IGN -waterlevelvalue. From a cartographic overview, it is eassier to manage this attribute in the water elements themself, instead of using the separate object LandWaterBoundary -canalization. To describe if there is a canalization infrastructures in watercourses, even if originvalue is natural or artificial. -nationalwatercoursehier archy. Aninteger code used to categorize rivers. (1st category, 2dn, etc.) Hydro - Physical Waters::Watercourse + condition :ConditionOfFacilityValue [0..1] + delineationknown :Boolean + length :Length + level :VerticalPositionValue + streamorder :HydroOrderCode [0..1] + width :WidthRange {geometryiscurveorsurface} {onlymanmadehasconditionattr} Watercourse + canalization :boolean + nationalwatercoursehierarchy :int SurfaceWater + waterlevel :WaterLevelValue {persistenceisnotephimeral} StandingWater Hydro - Physical Waters:: StandingWater + elevation :Length + meandepth :Length + surfacearea :Area {geometryissurfaceorpoint} Accommodation of a data value. Attribute localtype uses only a string to define type of element, that can provoke misunderstanding depending on datasets, version, etc. Decision to generate a consolidate codelistfor values reached by consensus between IGN, DGAgua. For HydrologycalPersistenceV alue, no all values will be used: - Dry - Ephemeral - Intermittent - Perennial

INSPIRE object IGN object Example of PhW and other themes class Hydrography - Physical Waters, wetlands and glaciers Examples::Wetland + geometry :GM_Surface + inspireid :Identifier HydroObject

8 INSPIRE object IGN object Example of PhW and other themes class Hydrography - Physical Waters, wetlands and glaciers Examples::Wetland + geometry :GM_Surface + inspireid :Identifier HydroObject «voidable, lifecycleinfo» + beginlifespanversion :DateTime + endlifespanversion :DateTime [0..1] + localtype :LocalisedCharacterString [0..1] + tidal :Boolean Wetland + marsh + coastallagoon + peat + wetland + saline localtype is shaped as WetlandValue instead as LocalisedCharacterString WetlandValue tags owner = DG Calidad y Evaluación Ambiental HydroObject «placeholder,featuretype» Examples::GlacierSnow field + geometry :GM_Surface + inspireid :Identifier «voidable, lifecycleinfo» + beginlifespanversion :DateTime + endlifespanversion :DateTime [0..1] Wetlandis maintained in HY, due to Land Cover theme doesn't consider feature objects as HY demands. It is necessary to define a consolidated codelistto describe types of wetlands, compliant with RAMSARconvention and National Wetland Inventory. Utilization of Sea Regions theme objects, SeaAreaand Coastline. Extension of SeaAreaTypeto allocate a new value ria (special marine environment not considered in INSPIRE). class Hydrography - Physical Waters, marine waters +relatedhydroobject 0..* Hydro - base::hydroobject + geographicalname :GeographicalName [0..*] + hydroid :HydroIdentifier [0..*] Sea Regions::Shoreline + segment :ShoreSegment [1..*] + waterlevel :WaterLevelValue + geometry :GM_Curve Sea Regions::ShoreSegment + shoreclassification :ShoreTypeClassificationValue [0..1] + shorestability :ShoreStabilityValue [0..1] +subarea 0..* Sea Regions::SeaArea + inspireid :Identifier + extent :MarineExtent [1..*] + seaareatype :SeaAreaTypeClassificationValue [0..1] + parametervalue :ParameterValuePair [0..*] «voidable, lifecycleinfo» + beginlifespanversion :DateTime + endlifespanversion :DateTime [0..1] Sea Regions::Coastline {coastline is special case of shoreline at Mean High Water Level} Sea Regions:: SeaAreaTypeClassificationValue Sea Regions::NationalSeaAreaTypeClassificationValue + ria tags owner = DG Sostenibilidad de la Costa y el Mar & IGN + extent :MarineExtent Sea Regions::Sea {extent.waterlevel must be meanhighwater} «datatype» Sea Regions::MarineExtent + geometry :GM_MultiSurface + waterlevel :WaterLevelValue [0..1]

9 INSPIRE object IGN object Example of PhW and other themes class Hydrography - Physical Waters, basins +containsbasin 0..* +neighbour 0..* Hydro - Physical Waters:: Riv erbasin HydroObject Hydro - Physical Waters::DrainageBasin + geometry :GM_Surface + inspireid :Identifier + area :Area + basinorder :HydroOrderCode [0..1] + origin :OriginValue «voidable, lifecycleinfo» + beginlifespanversion :DateTime + endlifespanversion :DateTime [0..1] {largestbasinisriverbasin} 1..* +drainsbasin +outlet 1..* HydroObject Hydro - Physical Waters::SurfaceWater + geometry :GM_Primitive + inspireid :Identifier + levelofdetail :MD_Resolution [0..1] «voidable, lifecycleinfo» + beginlifespanversion :DateTime + endlifespanversion :DateTime [0..1] + localtype :LocalisedCharacterString [0..1] + origin :OriginValue + persistence :HydrologicalPersistenceValue + tidal :Boolean Riv erbasin 1..* 1..* Area Management Restriction Regulation Zones and Reporting units:: Riv erbasindistrict {ZoneTypeCodeIsRiverBasinDistrict} {EnvironmentalDomainIsWater} También aplicable para: - Zonas sensibles a nitratos (Directiva 91/676) - Zonas de protección de aguas potables (Directiva 80/778) - Zonas de aguas de baño - Masas de agua bajo protección (Directiva 2006/44 & 2006/113) - Zonas de inundación (Directiva 2007/60) - Regiones marinas (Directiva 2008/56 & OSPAR & Barcelona Convention UNEP Region Seas Programme) - Zonas de tránsito (Decisión 884/2004) - Zonas de aguas sensibles (Directiva 91/271) class Hydrography - Physical Waters, construcions and buildings Area Management/Restriction/Regulation Zone +relatedzone 0..* Area Management Restriction and Regulation Zones:: ManagementRestrictionOrRegulationZone + inspireid :Identifier + geometry :GM_Object + zonetype :ZoneTypeCode [1..*] + environmentaldomain :EnvironmentalDomain [1..*] + thematicid :ThematicIdentifier [0..*] + name :GeographicalName [0..*] + specialisedzonetype :SpecialisedZoneTypeCode [0..1] + designationperiod :TM_Period + competentauthority :RelatedParty [1..*] «voidable, lifecycleinfo» + beginlifespanversion :DateTime + endlifespanversion :DateTime [0..1] HydroObject Area Management Restriction and Regulation Zones::ZoneTypeCode Hydro - Physical Waters::ManMadeObject + inspireid :Identifier tags + levelofdetail asdictionary :MD_Resolution = true [0..1] «voidable, lifecycleinfo» extensibility = any + beginlifespanversion :DateTime vocabulary = + endlifespanversion :DateTime [0..1] xsdencodingrule = iso19136_2007_inspire_extensions + condition :ConditionOfFacilityValue + geometry :GM_Primitive {Specify at least the most specific legal instrument.} {competentauthority.role shall be "authority"} Hydro - Physical Waters:: DamOrWeir DamOrWeir + type :DamOrWeirTypeValue {BuildingNatureValueIsDam} DamOrWeirTypeValue Area Management Restriction and Regulation Zones:: SpecialisedZoneTypeCode tags asdictionary = true extensibility = any Buildings::Deposit vocabulary = xsdencodingrule = iso19136_2007_inspire_extensions {BuildingNatureValueIsStorageTank} Utilization of Area & Regulation zones to materialize as feature type the RiverBasinDistrict. And relation with Buildings to make links between artificial structures (i.e. bridges, dams, pools, etc.) Buildings Building BuildingInfo BuildingsExtended2D::Building BuildingsBase:: BuildingNatureValue Buildings::ArtificialWaterBody {OtherConstructionNatureValueCanBeOpenAirPoolOrPoolOrPond} AbstractOtherConstruction BuildingsExtended2D::OtherConstruction + geometry2d :GM_Primitive Hydro - Physical Waters:: Crossing + type :CrossingTypeValue Crossing {OtherConstructionNatureValueBridge} BuildingsExtendedBase:: OtherConstructionNatureValue Hydro - Physical Waters:: CrossingTypeValue + aqueduct + bridge + culvert + siphon Buildings:: NationalOtherConstructionNatureValue + pool + pond + swimmingpool tags owner = DG Catastro & IGN

10 Documentation All GRI dataset (including HY and TN themes) are documented by means of specifications created according to ISO Particularly, extended objects and modified attributes are documented in the GRI-HY feature catalogue

Database creation Mapping table is the base to implement the

manually, in PostGIS with pgadmin III and TOAD In order to

values, links with other themes, identifiers sequences, and to

11 Database creation Mapping table is the base to implement the data model on the database schema Database schema was done manually, in PostGIS with pgadmin III and TOAD In order to ensure relationships, constrictions, restrictions for codelist values, links with other themes, identifiers sequences, and to define functions and trigger events impossible to reproduce automatically from UML

Database upload Transformation from the current real data to the GRI- HY database schema FME software for transformation Geomedia, ArcGIS, QGIS for management and control Continuous

12 Database upload Transformation from the current real data to the GRI- HY database schema FME software for transformation Geomedia, ArcGIS, QGIS for management and control Continuous feedbackfor UML and mapping table in case of misunderstanding with real data INSPIRE output, as view-tables from GRI-HY database schema GRI Database Native National datasets Translation mechanism

13 GRI-HY Database schema Database schema is defined from a production and maintenance overview, but it enables to reproduce INSPIRE schema easily Final INSPIRE schema is obtained after transformation processes Example: Watercourses are split in parts but they can be aggregated in order to reproduce both INSPIRE views. Benefits: only one geometry per object is maintained Id_link:55 Id:1 Att1 Att2 Id_link:55 Id:2 Att1 Att2 Id_link:44 Id:4 Att1 Att2 Id_link:55 Id:3 Att1 Att2 Aggregation by id_link reproduce network model Id_link:55 Id_link:44 Id_link:55

14 GRI-HY Data Hydro-network geometry is automatically obtained from geo-processes from digital elevation model (grid size 5m & hydrologic runoff calculus)

identifiers) River Basin District code to determinate responsible organization Pfafstetter code for

15 GRI-HY Data Hydro-network semantic is obtained from current national responsible databases (IGN, DG Agua) Main attributes: National identifier for watercourses and dams (as INSPIRE thematic identifiers) River Basin District code to determinate responsible organization Pfafstetter code for stream ordering (under development) geographical names from official gazetteers and links with objects in other themes

16 GRI Results Hydro-network semantic is obtained from current national responsible databases (IGN, DG Agua)

Encoding tasks To generate GML and Web Services is needed to use XSDs published by INSPIRE Open issue about how to encode new extended attributes modeled.

17 Encoding tasks To generate GML and Web Services is needed to use XSDs published by INSPIRE Open issue about how to encode new extended attributes modeled. (XSDs don t contain their definition) So output data will not be compliant to INSPIRE? Should stakeholders extend their own XSDs? What software should we usedto reproduce INSPIRE GML properly? FME, Geoserver, Degree, etc. What happes if INSPIRE XSDs are not sufficient well referenced?

18 Thank you very much! Celia Sevilla Sánchez Julián Delgado Hernández 21-22/10/ /10/2014 Alicia González Jiménez IGN-Spain 18

Keep it simple! a Nordic view on technical simplification issues. Nordic INSPIRE Network. INSPIRE Conference 2017

Keep it simple! a Nordic view on technical simplification issues 1 The network Formed in 2007 as a result of the INSPIRE directive Share experience and knowledge Develop common standpoints Exchange action