The TOPNL Data Model

Transcription

1 NICO J. BAKKER Topografische Dienst Kadaster Bendienplein SM Emmen, The Netherlands nbakker@tdkadaster.nl The TOPNL Data Model DEVELOPING A NEW GEOGRAPHICAL OBJECT DATABASE

2 Framework for Description and Comparison of Data Models Background Information General Description Use of Standards (ISO, OGC, other) Data Model Description Data Classification Object Identity Complex Objects and Relationships between Objects Portrayal Data Modelling Tools Wider Context Spatial Data Infrastructure Costs and Benefits

3 Current Production vectorfiles and maps Reconaissance Aerial photogr. Photogrammetrie Vectordata Dgn, dxf, Arc/Info, NEN1878 TOP10vector generalisation TOP50vector generalisation TOP100vector TOP250vector Generalisation Visualisations Maps kaarte Rasterdata generalisation TOP500vector

4 Datatypes Vector Database Updates VPFdatabase VMAP TOPXXvector TOPXXvector dxf dxf TOPXXvector TOPXXvector e00),shape e00),shape TOPXXvector TOPXXvector NEN1878 NEN1878 TOPXXvector TOPXXvector DGN DGN Conversion TOPXXvector DGN DGN Visualisatio n (MapPublisher) VPF-conversion GeoMedia/Dynamo Generalisation kaarten TOPXXvector TOPXXvector DGN DGN RasterXX (Geo)TIFF Military maps smaller scales RasterDatabase Civile maps Special mil maps Special civ maps

5 ctortopvector files e v 0 1 TOP or TOP50vect TOP100vector TOP250vector TOP50 0vecto r 4 pt 4 pt 2 pt 2 pt 5 pt 5 pt 5 pt 5 pt

6 1: : Topographic maps 1: : :

7 Background Information Name of the Data Model: TOP10NL Designed in 2002, definite model 2004 Introduced in second half 2006 Responsible: Topografische Dienst Kadaster

8 Development TP10NL in co-operation with Research Institutes Centre for Geo-Information (CGI/Wageningen University): A.K. Bregt and colleagues: Userdemands ITC: M.J. Kraak/ R.Knippers: Datamodeling TU Delft (TUD): P. van Oosterom en colleagues: implementation in prototype L. Heres AVV/RWS Adviser

9 General Description Topographic mapping General reference for NSDI Follows ISO standards No topology used Objects are stored as point, lines and areas Objects are stored as 2D, Model can support 3D Data are stored in a continuous data base for the Dutch territory Non-spatial data: attributes can be added tot the objects. Processes are not possible

10 Use of Standards (ISO, OGC, other) Metadata ISO Dutch Standard NEN based on ISO and OGC standards OGC : GML 3.1

11 Standards used for design data model Dutch Data model NEN 3610:1995 nl Terreinmodel Vastgoed Actualisering NEN 3610 Basic scheme for Geo-information 2005

12 Data Model Description The data model is described in a UML model GML application schema is used UGAS tool is used for deriving GML schema from UML model Multiple Resolution Model is planned for second half 2006

13 New NEN Basic Scheme for Geo Information Prerequisites: Based on International Standards (ISO, OGC) Backwards compatible with old NEN3610 Should be a base for the exchange of all geo-data in the Netherlands (Top-Down approach) Extensible

14 Advantages of a nationwide base model + Shared definitions + One shared temporal model for all data in the Netherlands - To keep everybody happy almost all attributes are optional and definitions very vague + A published base model is a good starting point for sector models

15 NEN3610 specifications Nationwide unique identifiers Temporal model useful for change only updates Fully described in UML GML Application Schema is automatically derived from the UML model. The model is not complete by itself; it is a starting point for sectors that should make a Sector Model One base class GeoObject and about a dozen subclasses.

16 IMKICH Base model and sector models OGC International standard ISO 191XX NEN3610 National standard Exchange IMRO IMWA RWS TOP10NL IM.. Sector specific Organisation specific

17 'General Feature Model' <<metaclass>> GF_Operation 1 +supertype 1 0..* <<metaclass>> GF_FeatureType 0..* 1..* <<Abstract>> GF_PropertyType Generalization -subtype +carrierofcharacteristics +memberof +observesvaluesof 0..* 0..* +triggeredbyvaluesof 0..* Specialization <<metaclass>> GF_AttributeType 0..* 0..* <<Abstract>> GF_Constraint 0..* +characterize constrainedby GF_InheritanceRelation 0..* <<metaclass>> GF_AssociationType +linkbetween 0..* +constrainedby +characterizedby 0..* 1..* <<metaclass>> GF_AssociationRole +DependsOn 0..* GF_AggregationType GF_SpatialAssociationType GF_TemporalAssociationType To facilitate international interchange, the Basic Scheme for Geoinformation was drawn up in accordance with the rules set down in ISO The 'General Feature Model' defined in this standard is the metamodel for the Basic Scheme for Geoinformation +affectsvaluesof AttributeOfAttribute

18 Basic Scheme for Geo-information <<FeatureType>> GeoObject +geoobject 0..* 0..* +rechtenopobject <<FeatureType>> Rechten +rechtstype : Rechtstype [0..1] +rechtenvansubject 0..* 0..* +subject <<FeatureType>> Subject <<FeatureType>> NatuurlijkPersoon <<FeatureType>> NietNatuurlijkPersoon <<FeatureType>> RegistratiefGebied <<FeatureType>> FunctioneelGebied <<FeatureType>> GeografischGebied <<FeatureType>> PlanologischGebied <<FeatureType>> Terrein <<FeatureType>> Water <<FeatureType>> Weg <<FeatureType>> Spoorbaan <<FeatureType>> Leiding <<FeatureType>> Meting <<FeatureType>> Inrichtingselement <<FeatureType>> Gebouw <<FeatureType>> Waterkering <<FeatureType>> Kunstwerk High-level view of the Basic Scheme for Geo-information with the GeoFeature superclass and the fourteen geographic feature basic classes and their relationships

19 NEN3610 base class: GeoObject Unique nationwide Identifier Temporal attributes can be used for incremental updates Almost all attributes are optional

20 TOP10NL the complete model

21 The TOP10NL Model Top level model (NEN3610) is a generic model shared by all data providers in the Netherlands Every feature type is modeled as a subclass of a national model Roads is one of the many classes. All TOP10NL objects are extensions of existing classes in NEN3610

22 Automatic Translation of UML model UML Application UML Schema model (XMI) Guidelines ShapeChange (Java, program) Servlet) Encoding Rules Configuration (XML) GML Application Schema (XML Schema)

23 Part of xsd schema TOP10NL

24 Part of NEN3610 xsd schema <?xml version="1.0" encoding="utf-8"?> - <schema xmlns=" xmlns:gml=" xmlns:nen3610=" xmlns:scxml=" xmlns:smxml=" xmlns:xlink=" elementformdefault="qualified" targetnamespace=" version="1.0"> <import namespace=" schemalocation="base/feature.xsd" /> <element name="adres" type="nen3610:adrespropertytype" /> <element name="begintijd" type="datetime" /> <element name="bestemmingsfunctie" type="gml:codetype" /> <element name="bouwvergunning" type="gml:codetype" /> <element name="eindtijd" type="datetime" /> <element name="functiegebouw" type="gml:codetype" /> <element name="gebouwvoorpand" type="nen3610:gebouwpropertytype" /> <element name="gemeentecode" type="string" /> <element name="gemeentenaam" type="string" /> <element name="gemeente" type="nen3610:gemeentepropertytype" /> <element name="geoobject" type="nen3610:geoobjectpropertytype" /> <element name="huisletter" type="string" /> <element name="huisnummer" type="string" /> <element name="huisnummertoevoeging" type="string" /> <element name="identificatie" type="string" /> <element name="land" type="string" /> <element name="ligtboven" type="nen3610:geoobjectpropertytype" /> <element name="ligtonder" type="nen3610:geoobjectpropertytype" /> <element name="locatienaam" type="string" /> <element name="locatie" type="nen3610:locatiepropertytype" /> <element name="locatieomschrijving" type="string" /> <element name="materiaalgebouw" type="gml:codetype" /> <element name="materiaalinrichtingselement" type="gml:codetype" /> <element name="materiaalkunstwerk" type="gml:codetype" /> <element name="materiaalleiding" type="gml:codetype" />

25 TOP10NL object in GML <gml:featurecollection xmlns:top10nl=" xmlns:nen3610=" xmlns:gml=" xmlns:xlink=" xmlns:xsi=" xsi:schemalocation=" top10nl.xsd base/gml.xsd"> <gml:description>testversie voor top10nl</gml:description> <gml:boundedby> - <gml:envelope srsname="urn:opengis:crs:epsg::28992"> <gml:pos> </gml:pos> <gml:pos> </gml:pos> </gml:envelope> </gml:boundedby> - <gml:featuremembers> - <top10nl:wegdeel> <gml:metadataproperty xlink:type="simple" xlink:href="metadata.xml#top " /> <top10nl:naam xml:lang="nl">rijksweg A-12</top10nl:naam> <nen3610:objectid>top10:400001</nen3610:objectid> <nen3610:objectbegintijd> t13:24:10+02:00</nen3610:objectbegintijd> <nen3610:versiebegintijd> t02:08:42+02:00</nen3610:versiebegintijd> <top10nl:status>in gebruik</top10nl:status> <top10nl:typeweg>autosnelweg</top10nl:typeweg> <top10nl:typeinfrastructuur>verbinding</top10nl:typeinfrastructuur> <top10nl:hoofdverkeersgebruik codespace=" <top10nl:verhardingsbreedteklasse codespace=" 7meter</top10nl:verhardingsbreedteklasse> <top10nl:verhardingsbreedte uom="#m">20.9</top10nl:verhardingsbreedte> <top10nl:verhardingstype codespace=" <top10nl:hoogteniveau>0</top10nl:hoogteniveau> <top10nl:a-wegnummer>a12</top10nl:a-wegnummer> <top10nl:e-wegnummer>e25</top10nl:e-wegnummer> <top10nl:e-wegnummer>e30</top10nl:e-wegnummer> - <top10nl:hartlijn> - <gml:linestring srsname="urn:opengis:crs:epsg::28992"> <gml:poslist srsdimension="2"> </gml:posList> </gml:linestring> </top10nl:hartlijn> - <top10nl:wegvlak> - <gml:polygon srsname="urn:opengis:crs:epsg::28992"> - <gml:outerboundaryis> - <gml:linearring> <gml:poslist srsdimension="2"> </gml:posList> </gml:linearring> </gml:outerboundaryis> </gml:polygon> </top10nl:wegvlak> <top10nl:brontype>gbkn</top10nl:brontype> <top10nl:bronbeschrijving>hello</top10nl:bronbeschrijving> <top10nl:bronactualiteit> </top10nl:bronactualiteit> <top10nl:bronnauwkeurigheid uom="m">0.1</top10nl:bronnauwkeurigheid> <top10nl:dimensie>2d</top10nl:dimensie> </top10nl:wegdeel> </gml:featuremembers> </gml:featurecollection>

26 Data Classification Conceptual model has been defined. TOP10NL is specialization of the Dutch standard NEN Object Catalogue is stored in Excel and Access For relation TOP10NL and INSPIRE see next slide There is no provision for multi-lingual classification We have a provisional schema translation to FACC and ATKIS (not completed Access db). Translations from FACC tot EGM and ERM are available.

27 NEN3610 Object classes Road Water Railroad Terrain Building Construction Specific terrain element Dyke Cables underground Registrational Area (province, municipality boundary) Geographic Area areas with vague boundaries (like the Lake District or the Alps ) Functional Area Planning Area Measurement

28 Object Classes TOP10NL Road Railroad Water Terrain Building Specific terrain element Relief Registrational area Geographic area Functional area

29 TOP10NL object classes Geografic area Registrational area Functional area Water Terrain TOP10NL Specific terrain element Building Road Railway

30 Relation to INSPIRE Themes INSPIRE Themes Annex 1 Coordinate reference systems Geographical names Geographical grid systems Administrative units Transport networks Hydrography / water catchments Protected sites Annex 2 Elevation Addresses Cadastral parcels Land cover Ortho-imagery Geology covered by TOP10NL (or partly) yes yes no yes yes partly no partly no no partly no no

31 INSPIRE themes covered by TOP10NL Annex 3 Statistical units Buildings Soil Land use and land use plans Human health and safety Government service Environmental monitoring facilities Production and industrial facilities Agricultural and aquaculture facilities Population distribution Area management/restriction/regulation zones & reporting units Natural risk zones Atmospheric conditions Meteorological spatial features Oceanic spatial features Sea regions Bio-geographical regions Habitats and biotopes Species distribution Energy resources Mineral resources partly partly no no no no no no no no no no no no no no no no no no no

32 Object Identity Objects are defined by : - identification - geometry - description - temporal data - meta data TOP10NL Identification: NL.TOP10NL Objects can be found if you know the number, but there is no system in the numbering. A number once used will never be given out again

33 Unique objects (GIS)

34 What is an object? Objecttype : Terrain Landuse : meadow Objecttype : Building Function : fire tower Hight : 30 meters Status : not in use

35 Objects above each other Objecttype : Waterpart Watertype : Watercourse Hight level : -1 Objecttype : Waterpart Watertype : Watercourse Hight level : 0 Objecttype : road segment Roadtype : main road Hight level : 0

36 Objects in TOP10NL with attributes object type sfdhjk naam dkien functie ekmdi begindatum ldiye einddatum mnduy forest object type sfdhjk naam dkien functie ekmdi begindatum ldiye einddatum mnduy water tramdepot factory object type sfdhjk naam dkien functie ekmdi begindatum ldiye einddatum mnduy object type sfdhjk naam dkien functie ekmdi begindatum ldiye einddatum mnduy grass church object type sfdhjk naam dkien functie ekmdi begindatum ldiye einddatum mnduy farm object type sfdhjk naam dkien functie ekmdi begindatum ldiye einddatum mnduy brid ge object 4598 type sfdhjk naam dkien functie ekmdi begindatum ldiye einddatum mnduy mill object type sfdhjk naam dkien functie ekmdi begindatum ldiye einddatum mnduy

37 Object characteristics Basic object Identifying characteristic descriptive characteristics Geometric characteristics Temporal characteristics Meta characteristics

38 Object characteristics: road part Attribute (Attribuut) Domain (Domein) Cardinality (Multipliciteit) Optionally (Optionaliteit) Type (Type) Connection (Verbinding) Single Mandatory Crossing (Kruising) Area (Vlak) Road type (Wegtype) Highway (Autosnelweg) Single Mandatory Main road (Hoofdweg) Regional road (Regionale weg) Local road (Lokale weg) Street (Straat) Other road (Overige weg)

39 Characteristics of TOP10NL Designing the data-model and its structure the following user requirements were taken into account: Object-oriented data-model with unique ID s, Structured attributes with the possibility to add new attributes, Based on international standards (ISO, OGC), Change-only data instead of complete update delivery, Availability of object life cycle information, Meta data on object level, Distinction between Digital Landscape Model and Digital Cartographic Model, Seamless database, Integration TOP10vector (roads as polygon) and TOP10roads (roads as centre-line), Prepared for automatic generalisation and scale less database, Linkage with user data-models (e.g. environment, water) and user datasets.

40 Identify result

41 Object example Geometry Unique Object ID Meta data reference Object History Object life cycles Object Version Attributes

42 Multiple geometry in one object Integration TOP10NL, TOP10roads point area line

43 Selection from road object: road area or centre line A. Road areas B. Road centre lines

44 In detail A. road polygons B. Road centre lines

45 NEN3610 temporal model Four temporal attributes for version management and incremental updates. objectbegintime and objectendtime indicate the lifetime of an object. If an attribute changes a new version is shipped with a new versionbegintime. An object is deleted by shipping it with a non null objectendtime. Two temporal attributes for when the object changed in the real world: begintime and endtime

46 Meta-information at object level building Attribuut Value TOP10_ID SOURCE_REF DIMENSION 2D TDN_CODE 1000 SOURCE_TYPE interpreted aerial photograph SOURCE_DESCRIPTION Orthogonal aerial ph.; flight hight 3800 m; scale 1:18,000 SOURCE_ACTUALITY 2001 SOURCE_ACCURACY 5 meter

47 Meta-information at Dataset level Metadata (MD_Metadata) ISO-ID Obligation Data type root entity which defines metadata about a resource or resources file identifier 2 O Text metadata file TOP10NL language 3 Code nl characterset 4 Code 007 In accordance to ISO parentidentifier 5 O Text hierarchylevel 6 M Code 005 hierarchylevelname 7 O Text dataset TOP10NL datestamp 9 M Date metadatastandardname 10 O Text ISO19115 point of contact 29 M individual Name 375 M Text organisation Name 376 M Text Topografische Dienst position Name 377 O Text Research & Development Division contact Info 378 O phone 388 O voice 408 O Text facsimile 409 O Text address 389 O delivery point 381 O Text Bendienplein 5 city 382 O Text Emmen postal Code 384 O Text 7815 SM country 385 O Text NL electronic Mail Address 386 O on-line resource 390 O linkage 397 M URL

48 Lifecycle of objects What happens with a modified object depends on the size of modification. At 'small' modifications an object gets a new version date. At 'large' modifications the original object terminates and a new object is erected with a new TOP10_ID and a starting date. Then the original object is considered as disappeared, and gets an end date. Whenever a modification is 'small' or 'large', is subjective. For that reason rules have been defined, to judge to what extent object modifications leads up to a new version date or new TOP10_ID. Depending on the kind of modification certain rules are applied. Small changes of the geometry won t cause a change of object ID. When an attribute has changed, in the most cases only the version date is changed.

49 Aggregation and splitting of objects Aggregation of objects Splitting rule

50 Changing geometry Change of geometry of objects Change of geometry within buffer

51 Updating New production software for Updating objects

52 Workflow terrain information ESPA 3D interpretation Rastermodel Aerial Photo s PEN PC Reconnaissance Work model Check & Correction

53 Production process Produce orthophoto s Delivery Terrain Reconnais sance e.g. Water boards Process External Sources Planning Control Managing tasks Manage Model Workset Update & lifecycle rules constraints TOP10NL Core GBKN buildings delivery TOP10NL Process External Data GML SHAPE DWG

54 Extended functionalities and interface upon ArcGIS 9.1

55

56 New punch tool for updating objects For efficient updating of the objects special functionality is developed in ArcGIS 9. A function called punching helps to resolve creating new objects and the splitting and merging of existing objects when an update activity takes place. In the next 4 sheets the successive steps are shown. The first shows the existing objects and the contours of a new road (in green). The second shows the digitised polygon of the new road, above the existing terrain polygons. The third sheet shows the punch functionality is running and creates new objects and splits the underlying objects in smaller ones. The fourth sheet shows the new situation.

57 Contours of a new road (1)

58 New road, above the existing terrain polygons(2)

59 Punch tool is running and creates new objects (3)

60 The new situation (4)

61 Complex Objects and Relationships between Objects Complex objects are not directly but indirectly defined in the data model Examples: a road exist of many road segment. For composing a road with a certain road name or road number: search for the attribute street name with a certain name in certain area Different layers on the top of the basic terrain data ( roads, water, terrain (and a separate layer of buildings) are defined as functional area, registrative area, geographical area. Selections of underlying objects can only be made in an GIS application Object referencing: Attributes or attribute values can be added tot the object classes One of the principles: keep the model simple; complex objects are defined in applications and sql questions in GIS software

62 Portrayal There are no standards applied for presentation, but TDK delivers a own style sheet for presentation which is a look-a-like of the current topographical map scale 1:25,000. For some GIS software presentations files are made, ArcGIS, and GeoMedia. For web based presentation SLD will be produced On the other hand users are free to choose there own presentation, depending of the purpose and the combination with there own data See some examples

63 Visualisatie met ArcGIS 9.2 (β) (1. random read)

64 Visualisation with ArcGIS 9.2 (2. Define symbology)

65 Visualisation with ArcGIS (3.symbol linked to object)

66 No special visualization

67 Visualisation as Topographical map 1:25.000

68 Selection important watercourses

69 Selection centre lines of roads

70 Automatic text placement TOP10NL

71 Flexibel visualisation

72 Visualization detail

73 Wider Context TOP10NL Data Model is a part of the Dutch Basic Scheme for Geo- Information NEN The Basic scheme covers more sectors like Planning, Water, Historical geo information and so on. TOP10NL was the first

74 TOP10NL in GML3.1 supported by FME / SAFE Safe Software Adds Comprehensive Support for TOP10NL (TOP10GML) to FME Vancouver, B.C. March 2, 2006 Safe Software is pleased to announce that its industry leading spatial data translation product, FME, now supports reading and writing of TOP10NL, the Dutch standard format for sharing GIS data across multiple platforms. TOP10NL is based on GML 3.1 and employs a multiple-geometries-perfeature data model. Because few commercial GIS applications can support this directly, Safe Software has developed a set of data model transformations that allow six different commercial systems to import and export TOP10GML using FME; additional configurations for other vendor systems could easily be added. The configurations were developed for Autodesk AutoCAD DWG/EED, Bentley MicroStation GeoGraphics, ESRI Geodatabase, Intergraph GeoMedia, MapInfo TAB, and Oracle Spatial, and can be downloaded from the fmepedia, a Safe Software-sponsored wiki or community website for FME users, at

75 Spatial Data Infrastructure The Netherlands is developing an infrastructure for Spatial and Non- Spatial Data (Basic Registrations) TOP10NL will be the first level that will serve as geographical base for the spatial data at the scale 1:10,000 and smaller. Later on it is expected that Large scale data (1:1000 / 2000) will follow (5 years?), because large scale data are not harmonized enough to satisfy the requirements of a basic registration (Large Scale Basic Map: GBKN)

76 Basic registrations (SDI + adminstrative registers) BRI Basisregistratie Income LUD Wages Contracts BRK Basis Registratie Cadastre Spatial objects IOR BRT Topography Small scale <=1:10,000 BSN KR Car registration BSN Persoon Natuurlijk persoon RNI Registratie Niet Ingezetenen BSN FIN GBA NHR population Register Admini Commercial stration enterprises AON BSN BSN FIN BIN AON GBKN Large scale Base map DINO Subsoil mapping FIN AON BGR buildings BRA Adresses First 6 registrations (2010) Next three INA Following three

77 Costs and Benefits See 10 advantages of TOP10NL Also needed in connection with the Basic Registrations Principles of the Basic Registrations: Collect once, use many times Obligatory use for governmental organizations One government portal for civilians

78 Marketingresearch Limitations current data sets More complex analyses needed Coupling data sets needed Faster delivery of data Internet applications Geographic Core data set (Dutch standard) Technological developments Faster hardware More advanced GIS software More data available Internet developments Standardization (ISO / Open GIS)

79 Development TOP10NL Communication 2004 Use Launch TOP10NL 2006 Built object-editor TOP10NL 2005 Conversion TOP10vector > TOP10NL Built conversion software 2003 Design Oracle9i database structure 2002 Producing Pilot en Demo CD / Website 2001 Development Datamodel 2000 First development and marketingresearch Ideas

80 Thank you for your attention