EuroBoundaries Project WP3

1
EuroBoundaries ProjectWP3 EBDB Technical
Robert Balanche Federal Directorate for Cadastral
Surveying Modeling exchange of cadastral
surveying data
2
W3 - Members

• Dr. Ingrid Naumann, Federal Agency of Cartography
  and Geodesy, Germany,
• Stefan Gustafson, Lantmäteriet - National Land
  Survey of Sweden,
• François Chirié, Institut Geographique National
  de France (IGNF),
• Robert Balanche, swisstopo Swiss Federal Office
  of Topography, Leader of the WP3.

3
WP3 EBDM Technical Definition tasks

• The main task of the WP3 EBDM is to create a
  core data model for the future European
  Boundaries database or distributed architecture.

4
EB Data model requirements (1)

• Coordinate ETRS89
• Unique identifier
• Bilateral international treaty
• Definition of topographic boundaries when there
  is no geographic information, for example middle
  of river, top of mountain, comb, crest, etc
• Indicator of reliability, accuracy
• Management of a status agreement or not with
  neighbour country, in discussion, in conflict,
  treaty, etc
• Movable boundaries
• Boundaries are formed of straights and/or
  circular arcs
• Type of marks.

5
EB Data model requirements (2)

• Each object has to be attributed (metadata)
• Management of photos or sketchs
• Mandatory plane coordinates and height as option
• Management of for and back reference mark in
  boundary
• Maintenance but no history
• Model description language and transfer format
  have to be system neutral and independent (for
  example GML)
• The EBDM will represent the minimal requirements
  that each country has to satisfy countries will
  be free to extend this EBDM according to their
  own requirements
• The WP3 must define the data model description
  language and the data transfer format.

6
WP3 Responsabilities

• The WP3 must work in very close collaboration
  with the EuroSpec Experts Group "Information and
  Standards" and Distributed Services Architecture
  Expert Group
• The WP3 develops guidelines and best practices
  for NMCAs

7
Plan and delivery

• The first version of the core data model has to
  be finished at the end of 2005,
• In 2006, we have to test the implementation of
  this model (in 2-3 countries),
• In 2006 we have to establish the best practices
  and guidelines for the NMCAs,

8
First draft of the conceptual core data model
9
Standards and specifications

• First specifications of   Expert Group on
  information and Data Specifications  
• Schema (UML GML),
• Feature Catalogues,
• Distributed product specifications.

10
Schema

• The standard GML (Geography Markup Language) will
  be the future ISO Norm 19136
• The WP3 group will describe the data model with
  the description data modelling language
   INTERLIS  and generate automatically GML
  Schema.

11
INTERLIS

• The INTERLIS language has been developed in such
  a way that it can easily be read by human beings.
  
• The interpretation of INTERLIS models is
  nevertheless precise and unambiguous.
• The language is textual and well-suited to
  complement the graphical description language
  Unified Modelling Language (UML), but goes well
  beyond that.
• The INTERLIS concept also includes a transfer
  service, which can automatically generate the
  transfer file from the conceptual model.
• INTERLIS has been designed for the interaction
  between information systems, in particular land
  information systems.
• It therefore is a conceptual description language
  with which the data model of the real world can
  be described. Such a description is called a
  "conceptual model".
• Properties and relations of real world objects
  are being described with clearly defined
  expressions and terms.
• Furthermore, INTERLIS makes a clear distinction
  of the description of the real world objects and
  their graphical representations.
• INTERLIS is not geared towards a particular
  application. It is based on object-oriented
  principles and while coordinates, lines and areas
  are basic constructs, there are many others to
  describe other properties of the objects,
  enabling INTERLIS to also deal with
  non-geographic data and applications

12
INTERLIS (2)
13
INTERLIS principle
n interfaces
GIS A
GIS B
INTERLIS
Model description
Exchange transfert format
GIS D
GIS C
interfaces
14
INTERLIS - GML
Interlis File
Transfer format
UML
GML Schema
Data catalogue
15
File automatically genereted
Euroboundaries.ili / Boundary
definition/ CLASS Boundary
Boundary_Status MANDATORY Euroboundaries.Status
Remark TEXT200 Identifier
MANDATORY TEXT20 UNIQUE Identifier END
Boundary / Useful point for oteh
application, for example roads, river, power,
etc. / CLASS Connectingpoint Number
TEXT20 Name TEXT20
Description TEXT100 Position
MANDATORY Euroboundaries.ETRF93
Application ( Transport
,Hydrograph ,Power ,Pipelines
,Other ) Remark TEXT200
Identifier MANDATORY TEXT20 UNIQUE
Identifier END Connectingpoint
Euroboundaries.xml ltiom04.metamodel.Tab
le TID"x15"gtltnamegtResponsability_partylt/namegtltcon
tainer REF"x9"/gtltisFinalgtfalselt/isFinalgtltisAbstra
ctgtfalselt/isAbstractgtltisExtendedgtfalselt/isExtended
gtltisStructuregtfalselt/isStructuregtlt/iom04.metamodel
.Tablegt ltiom04.metamodel.LocalAttribute
TID"x1101"gtltnamegtRemarklt/namegtltcontainer
REF"x15"/gtltisFinalgtfalselt/isFinalgtltisAbstractgtfal
selt/isAbstractgtlttype REF"x1107"/gtlt/iom04.metamode
l.LocalAttributegt ltiom04.metamodel.LocalAttribute
TID"x1100"gtltnamegtContactlt/namegtltcontainer
REF"x15"/gtltisFinalgtfalselt/isFinalgtltisAbstractgtfal
selt/isAbstractgtlttype REF"x1108"/gtlt/iom04.metamode
l.LocalAttributegt ltiom04.metamodel.ViewableAttribu
tesAndRoles TID"x1104"gtltviewable
REF"x15"/gtltattributesAndRoles REF"x1101"
ORDER_POS"3"/gtlt/iom04.metamodel.ViewableAttribute
sAndRolesgt ltiom04.metamodel.ViewableAttributesAndR
oles TID"x1102"gtltviewable REF"x15"/gtltattributesA
ndRoles REF"x1099" ORDER_POS"1"/gtlt/iom04.metamod
el.ViewableAttributesAndRolesgt
Euroboundaries.gml ltxsdcomplexType
name"Euroboundaries.Boundaries.Country"gt
ltxsdcomplexContentgt ltxsdextension
base"gmlAbstractFeatureType"gt
ltxsdsequencegt lt/xsdsequencegt
lt/xsdextensiongt lt/xsdcomplexContentgt lt/xsdcom
plexTypegt ltxsdelement name"Euroboundaries.Bounda
ries.Point" type"Euroboundaries.Boundaries.Point"
substitutionGroup"gml_Feature"/gt ltxsdcomplexTy
pe name"Euroboundaries.Boundaries.Point"gt
ltxsdcomplexContentgt ltxsdextension
base"gmlAbstractFeatureType"gt
ltxsdsequencegt lt/xsdsequencegt
lt/xsdextensiongt lt/xsdcomplexContentgt lt/xsdcom
plexTypegt
16
EuroBoundaries questionnaire 2005

• Results from 15 countries
• Agreed vector representation 6500 kms
• Accuracy lt 100 cm
• ETRS89 Coordinate
• 7 countries have already boundary data model
• 10 countries have already ETRS process
• Very good feeling to start

17
WP3 Next steps

• Exchange information with Eurospec ExGs
• Core data model to be consolidated
• Implementation test in collaboration with
  Euroboundaries WP4 EBDB Prototype
• Best practiced for NMCAs

18
Thank you for your attention
Questions, remarks