1 / 13

EuroRegionalMap

EuroRegionalMap. A step-wise approach for harmonisation. NDB similar scale. EuroRegionalMap. Nat. Harm. Core. NDB1. NDB larger scale. NDB2. Nat. Harm. Core. Nat. Harm. Core. Harmonisation approach. acceptable. core. best compromise.

kalyca
Download Presentation

EuroRegionalMap

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EuroRegionalMap A step-wise approach for harmonisation

  2. NDB similar scale EuroRegionalMap Nat. Harm. Core NDB1 NDBlarger scale NDB2 Nat. Harm. Core Nat. Harm. Core Harmonisation approach acceptable core best compromise • Determining a reference dataset to producers, which is the in term of harmonisation • Data that we have in • Harmonise them at the most useful and cost efficient to do so • maintenance and derivation common Easy

  3. Harmonisation approach 1:200 000 -1:300 000 • Map resolution allowed • Data content restricted to usually maintained by mapping agencies • Basic spatial analysis requirements • of transport and water network • of administrative boundaries topographic data Full connectivity Geometrical consistency

  4. General Technical CharacteristicsCompliant to INSPIRE

  5. Conceptual Model • Level 3 topology • Node-to-edge, Face-to-edge • Simple primitive • Feature Class • Set of features sharing a homogeneous set of attributes • Point, area, line, text • FACC DIGEST except italics*

  6. Content Requirement Topology Requirement User Purpose Arc/Info Model Administrativeboundaries • Lowest level (commune) • Integration of SABE attributes with relate tables SABE.NAM and SABE.ISN Mandatory 3, full topology Consistent geometry with water network ( at least for international boundary *) Geo-spatial analysis Visualisation Location BNDNET (arc, poly)

  7. Content Requirement Topology requirement User Purpose Arc/Info Model • Water Network (BH502) • Navigability,Name, Classification (WD7,WD8) • Water area, ice • Ponctual features Water Network Most Mandatory 3, full topology Full connectivity by portraying fictitious axis in open water andunderground network Geo-spatial analysis Visualisation Location HYDRONET ( arc, poly,node) HYDROPOINT ( point )

  8. Content Requirement Topology requirement User Purpose Arc/Info Model Vegetation and Soil • Trees, Orchard, Sand area Woods mandatory 3, full topology Nothing specific Visualisation, cartographic applications VEGPOLY (poly)

  9. Content Requirement Topology requirement User Purpose Arc/Info Model Miscellaneous • Power lines • Building, Landmarks, Industrial el., Towers, Physical el. • Natural parks Most optional Natural parks mandatory 3, full topology Nothing specific Visualisation, cartographic applications, location (name) MISCPOLY (poly) MISCLINK (arc,point)

  10. Content Requirement Topology Requirement User Purpose Arc/Info Model • Road network • Railway network • Airfields, Harbours • Ferry lines, • Stations, parkings, level crossings, interchanges Transport Most Mandatory 3, full topology Full connectivity of road and railway network Intelligent transport systems, Location based services, Map display , visualisation TRANSNET (arc, poly) TRANSLINK (arc, node,point)

  11. Content Requirement Topology Requirement User Purpose Arc/Info Model Built up area: • Name • population • population range (PP1 PP2 ) • Named location Settlement Mandatory 3, full topology Selection consistent with the road network Visualisation, LBS, Planning POPPOLY (poly) POPPOINT (point)

  12. Technical Docs Validation Tools NDB1 Harmonisation of National Components ERM harmonisednationalcomponent Validation Phase A/IIGNB local local NDB2 Final Approval N ERM finalProduct Installing onODS ERMStored Data OracleBKG Assembly Phase A/IBKG Y Delivery Formats On-lineDeliverySystem 3. The result is the ERM national data component 2. Using specifications and technical guide , the validation tools are available for national validation 7. Designing the product in varied delivery formats and installing it on the ODS 1. Harmonisation of NDBs 6. Assembly phase with edge-matching to create the ERM final product 4. Final validation by the technical management team 5. Corrections performed until final approval Production Work Flow

  13. National responsibilities • Finding agreement for a common international boundary with neighbours • Proceeding the harmonisation of national territory • Controlling the consistency for cross-border data with neighbour territories ( data selection ) • Proceeding own validation phase

More Related