Docstoc

JOINT RESEARCH CENTRE

Document Sample
JOINT RESEARCH CENTRE Powered By Docstoc
					                From Model to Data Transformation –
                      One approach Mapping
                   TeleAtlas Data to EuroRoadS
                                    Anders Friis-Christensen, JRC




                                                                    1
CSL Workshop, October 13-14, 2005
                 From Model to Data Transformation
       Outline:
       • Model
             – EuroRoadS subset
       • XMI/GML
             – Visio -> XMI -> Rational / EA ->
             – XMI -> GML schema
             – TeleAtlas Road data (shape) -> GML (+schema)
       • Model transformation
             – EuroRoads GML <-> TeleAtlas GML
                   • XSL
       • Data Transformation
             – XSLT
             – Population of data
       • Verification of data

                                                              2
CSL Workshop, October 13-14, 2005
                           Creating EuroRoadS subset

       • A subset of the network exchange model
       • The network model is a common base for
         roads
       • Including:
             – Attributes (modeled as abstract classes)
             – Geometry (GML data types)
       • No topology
       • No routing info
                                                          3
CSL Workshop, October 13-14, 2005
                                    4
CSL Workshop, October 13-14, 2005
                  Model interchange
                                                                                  Data interchange
                                       Import XMI in
                    EuroRoadsS
                                       Rational Rose/                                Road data
                  model (Visio2003)
                                         Enterprise                                  (TeleAtlas)
                                          Architect

                                                                  FME GML
                     XMI (ver.1.0)                                TeleAtlas         FME GML
                                        Correct and
                       UML1.1                                      schema           conversion
                                          modify
                    transformation
                                          model



                      Clean up        Export to XMI 1.0                                XSL:
                        XMI              (from RR)                                  TeleAtlas -
                                                                                    EuroRoads


                                           Apply
                     Load XMI in      ShaoeChange to                              Apply XSLT on
                      ArgoUML          produce GML                                     data
                                        2.1.2 or 3.1

                   Export XMI from
                                                                GML EuroRoads        Road data
                      ArgoUML
                                                        2.1.2    schema without     (TeleAtlas ->
                                         GML ver.                                    EuroRoads
                                                                ISO 19108 types
                                                                                      schema)
                                               3.1

                                      GML EuroRoads
                                         schema



                                          ? tools
                                         support ?

                                                                                                     5
CSL Workshop, October 13-14, 2005
                              XMI Generation from Visio
Newline in empty tag <Foundation.Core.Classifier.feature></Foundation.Core.Classifier.feature> not allowed. Changed 198
places.


        • Use of Microsoft XMIExport.dll
Newline in empty tag <Foundation.Core.AssociationEnd.qualifier></Foundation.Core.AssociationEnd.qualifier> not allowed.
Changed 192 places.


              – Invoked by ESRI add-on or by Lars Vikstroms application
Newline in empty tag <Foundation.Core.Namespace.ownedElement></Foundation.Core.Namespace.ownedElement> not allowed.
Changed 4 places.


        • Produces non-valid XMI supposedly based on UML
Undefined references:

line 5901:
          1.1
<Foundation.Core.Classifier.associationEnd>
<Foundation.Core.AssociationEnd xmi.idref="UID92E0A85B-FFCA-4D3E-AFA3-8A94E5121744"/> <-
<Foundation.Core.AssociationEnd xmi.idref="UIDFA3023F9-5631-4AF5-85C0-761190195B8C"/> <-
              – Several errors:
</Foundation.Core.Classifier.associationEnd>
deleted

line 6054:          • Newline in empty tags, more than 400 errors (only in XML spy
<Foundation.Core.Classifier.associationEnd>
                      2004, error in parser)
<Foundation.Core.AssociationEnd xmi.idref="UID958794C3-5D75-4A43-89E3-F0B6E1546E5B"/>
<Foundation.Core.AssociationEnd xmi.idref="UID59BE8B25-EFB3-4BEF-8811-B438964F63A3"/> <-
                    • Undefined references (associations ends and generalization)
<Foundation.Core.AssociationEnd xmi.idref="UID657C99EC-7244-47BD-B84B-BBEEF3A69330"/> <-
</Foundation.Core.Classifier.associationEnd>
deleted
                           – Must be an error in the model, old references not deleted properly by
line 12659:                   Visio
<Foundation.Core.GeneralizableElement.specialization>
<Foundation.Core.Generalization xmi.idref="UID496EBF06-CABE-46F1-87C0-F66CDEAD17D8"/> <-
<Foundation.Core.Generalization xmi.idref="UID7EA823B3-EB2F-4160-B6C8-F8518860E7F0"/>
</Foundation.Core.GeneralizableElement.specialization>
deleted

                                                                                                                      6
 CSL Workshop, October 13-14, 2005
                  XMI Import (Based on Visio export)

       • Rational Rose
             – Does not read UML 1.1 XMI
             – Possible workarounds??
       • Enterprise Architect
             – Based on OMG UML 1.1 XMI 1.0 dtd, success on import
             – However, several errors. E.g.:
                   • Generalizations not imported
                   • Enumerations not imported
                   • Association multiplicity not imported



                                                                 7
CSL Workshop, October 13-14, 2005
                  XMI Import (Based on Visio export)

       • ArgoUML 0.18:                             As a curiosity: ArgoUML
             – Possible to import XMI              cannot read its own import if
             – Errors:                             it is saved as a project. The
                   • Multiplicities not imported   XMI parsing fails.
             – Export UML 1.3 XMI 1.0 (without multiplicities)
       • Rational Rose:
             – Import new XMI possible
             – No import of enumerations
       • Enterprise Architect:
             – Same as RR

                                                                              8
CSL Workshop, October 13-14, 2005
                                          XMI – Issues
       • Conclusion:
             – Microsoft Visio is not interoperable (choose another software for UML, if it is
               foreseen that exchange of models is required)
             – Various vendors of XML editors/importers have errors in their parsers which
               complicates the process of validating XMI
             – Tools do not support same versions of XMI
             – Tools interpret XMI in different ways
             – It is very difficult to validate the content of the XMI, i.e. if the model imported is
               correct even though the XMI is validated.

       • Report John Herring (communicated by Morten)
             – EA problem with RR XMI:
                   • It does not import data types <<DataType>> (see also the example EA diagram that
                     was send to you
                   • It does not see realization ("inheritance" from interfaces and types) in the same way
                     as Rose. It transforms those into a type of dependency



                                                                                                    9
CSL Workshop, October 13-14, 2005
                   Model interchange
                                                                                   Data interchange
                                        Import XMI in
                     EuroRoadsS
                                        Rational Rose/                                Road data
                   model (Visio2003)
                                          Enterprise                                  (TeleAtlas)
                                           Architect

                                                                   FME GML
                     XMI (ver.1.0)                                 TeleAtlas         FME GML
                                         Correct and
                       UML1.1                                       schema           conversion
                                           modify
                    transformation
                                           model



                       Clean up        Export to XMI 1.0                                XSL:
                         XMI              (from RR)                                  TeleAtlas -
                                                                                     EuroRoads


                                            Apply
                     Load XMI in       ShaoeChange to                              Apply XSLT on
                      ArgoUML           produce GML                                     data
                                         2.1.2 or 3.1

                    Export XMI from
                                                                 GML EuroRoads        Road data
                       ArgoUML
                                                         2.1.2    schema without     (TeleAtlas ->
                                          GML ver.                                    EuroRoads
                                                                 ISO 19108 types
                                                                                       schema)
                                                3.1

                                       GML EuroRoads
                                          schema



                                           ? tools
                                          support ?
                                                                                                      10
CSL Workshop, October 13-14, 2005
          Prepare Sub-set Model in RR to support GML

       • Creation of GML schemas is done by
         ShapeChange tool (Interactive Instruments):
             – Converts XMI 1.0 to GML 2.1.2 and 3.1 (3.1.1?)
             – Other XMI than export from RR??
                   • Experiments from EA (Clemens)
       • ShapeChange put different requirements on
         the UML model (and hence the resulting XMI)


                                                            11
CSL Workshop, October 13-14, 2005
          Prepare Sub-set Model in RR to support GML

                                      Multiple inheritance:
                                      ER_RoadnetElement inherited
                                      directly from both ER_RoadFeature
                                      and ER_IdentifiableObject




                                                              12
CSL Workshop, October 13-14, 2005
          Prepare Sub-set Model in RR to support GML




                                    Two associations between
                                    ER_RoadAttribute and ER_RoadnetElement




                                                                     13
CSL Workshop, October 13-14, 2005
          Prepare Sub-set Model in RR to support GML



                                      Added multiplicities to
                                      associations and made them
                                      bidirectional




                                                               14
CSL Workshop, October 13-14, 2005
          Prepare Sub-set Model in RR to support GML




                  Added a concrete class with a value of string
                  datatype in order to store data




                                                                  15
CSL Workshop, October 13-14, 2005
          Prepare Sub-set Model in RR to support GML



                                    Added a validityFrom and validityTo
                                    Instead of TM_Period in order of simplicity
                                    and to support GML 2.1.2




                                                                        16
CSL Workshop, October 13-14, 2005
                             Other UGAS requirements

       • Additionally following rules needed to be
         applied the model
             – Model must be represented in a package
               stereotyped with <<Application Schema>>
             – The XML namespace (a URI) and an abbreviation
               must be present as tagged values




                                                         17
CSL Workshop, October 13-14, 2005
<?xml version="1.0" encoding="UTF-8"?>
                                                     Resulting GML
<!--Output of ShapeChange has been modified JRC-AFC-->
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:cslWorkshop="http://www.jrc.it/inspire/cslWorkshop"
xmlns:gml="http://www.opengis.net/gml" xmlns:sc="http://www.interactive-instruments.de/ShapeChange"
   <!--Added FeatureCollection in order to validate GML containing multiple feature members. JRC-AFC-->
xmlns:scXML="http://www.isotc211.org/scXML" xmlns:smXML="http://www.isotc211.org/smXML" xmlns:xlink="http://www.w3.org/1999/xlink"
targetNamespace="http://www.jrc.it/inspire/cslWorkshop" elementFormDefault="qualified" version="0.1">
   <element name="FeatureCollection" type="cslWorkshop:FeatureCollectionType"
   <import namespace="http://www.opengis.net/gml" schemaLocation="feature.xsd"/>
                 substitutionGroup="gml:_FeatureCollection"/>
   <!--Added FeatureCollection in order to validate GML containing multiple feature members. JRC-AFC-->
   <complexType name="FeatureCollectionType">
   <element name="FeatureCollection" type="cslWorkshop:FeatureCollectionType" substitutionGroup="gml:_FeatureCollection"/>
   <complexType name="FeatureCollectionType">
      <complexContent>
      <complexContent>
         <extension base="gml:AbstractFeatureCollectionType"/>
         <extension base="gml:AbstractFeatureCollectionType"/>
      </complexContent>
      </complexContent>
   </complexType>
   </complexType>
   <!--Type and element definitions of this package-->
   <complexType name="ER_RoadnetLinkType" abstract="true">
      <annotation>
         <documentation>Note: The attribute TM_Period in the original EuroRoadS model has been replaced by validityFrom and validityTo for
simplicity reasons</documentation>
      </annotation>
      <complexContent>
         <extension base="cslWorkshop:ER_RoadnetElementType">
            <sequence>
               <element name="validityFrom" type="date" minOccurs="0"/>
               <element name="validityTo" type="date" minOccurs="0"/>
               <element name="curve" type="gml:LineStringPropertyType" minOccurs="0"/>
            </sequence>
         </extension>
      </complexContent>
   </complexType>
   <complexType name="ER_RoadnetLinkPropertyType">
      <sequence>
         <element ref="cslWorkshop:ER_RoadnetLink" minOccurs="0"/>
      </sequence>
      <attributeGroup ref="gml:AssociationAttributeGroup"/>
   </complexType>
   <complexType name="ER_RoadnetLinkPropertyByValueType">
      <sequence>
         <element ref="cslWorkshop:ER_RoadnetLink"/>
      </sequence>                                                                                                                  18
    CSL Workshop, October 13-14, 2005
   </complexType>
   <element name="ER_RoadnetLink" type="cslWorkshop:ER_RoadnetLinkType" abstract="true" substitutionGroup="cslWorkshop:ER_RoadnetElement"/>
                                    19
CSL Workshop, October 13-14, 2005
                                    20
CSL Workshop, October 13-14, 2005
                                    Resulting GML

       • Because of the many classes in the model,
         the GML is complex
       • I did not work further with GML 3.1 schemas
             – Complex model
             – 3.1 schemas not valid (according several parsers),
               experience in producing 3.1.1?
             – Tools support (3.1 and 3.1.1)?
             – Any experiences??

                                                             21
CSL Workshop, October 13-14, 2005
                   Model interchange
                                                                                   Data interchange
                                        Import XMI in
                     EuroRoadsS
                                        Rational Rose/                                Road data
                   model (Visio2003)
                                          Enterprise                                  (TeleAtlas)
                                           Architect

                                                                   FME GML
                     XMI (ver.1.0)                                 TeleAtlas         FME GML
                                         Correct and
                       UML1.1                                       schema           conversion
                                           modify
                    transformation
                                           model



                       Clean up        Export to XMI 1.0                                XSL:
                         XMI              (from RR)                                  TeleAtlas -
                                                                                     EuroRoads


                                            Apply
                     Load XMI in       ShaoeChange to                              Apply XSLT on
                      ArgoUML           produce GML                                     data
                                         2.1.2 or 3.1

                    Export XMI from
                                                                 GML EuroRoads        Road data
                       ArgoUML
                                                         2.1.2    schema without     (TeleAtlas ->
                                          GML ver.                                    EuroRoads
                                                                 ISO 19108 types
                                                                                       schema)
                                                3.1

                                       GML EuroRoads
                                          schema



                                           ? tools
                                          support ?
                                                                                                      22
CSL Workshop, October 13-14, 2005
                                    Data transformation

       • Produce GML from TeleAtlas data
             – FME GML
             – Create schema option
             – No support for 3.1 or 3.1.1??
       • TeleAtlas based on GDF
             – Should be no problems when mapping attributes
             – Except that the attributes are named: ID, FEATTYP, FT, F_JNCTID,
                 F_JNCTTYP, T_JNCTID, T_JNCTTYP, PJ, METERS, FRC, NETCLASS, NETBCLASS, NET2CLASS, NAME,
                 NAMELC, SOL, NAMETYP, CHARGE, ROUTENUM, RTETYP, RTEDIR, RTEDIRVD, PROCSTAT, FOW, SLIPRD,
                 FREEWAY, BACKRD, TOLLRD, RDCOND, STUBBLE, PRIVATERD, CONSTATUS, ONEWAY, F_BP, T_BP,
                 F_ELEV, T_ELEV, KPH, MINUTES, POSACCUR, CARRIAGE, LANES


                                                                                                    23
CSL Workshop, October 13-14, 2005
                                    24
CSL Workshop, October 13-14, 2005
                                         XSL


                                                                 FID (TA) mapped to
                                                               ID:permanentID (should
                                                                actually have been ID
                                                                  (TA)FeatureCollection
                                                                       as FID is FME
                                                                        only map
                                                                    Weproperties data to
                                                                      generated) (e.g.
                                                                        ER_RoadLink
                                                                      bbox) are mapped




                  KPH (TA)
                 mapped to
                 Name (TA)
                 speedLimit
                 mapped to          lineStringProperty
               StringAttribute        (TA) mapped to
                                        GM_Curve mapped
                                           FOW (TA)
                                               Always
                                            to FormOfWay
                                        FRC (TA) mapped to
                                         ER_RoadElement
                                          using lookup table
                                         NationalRoadClass
                                         using lookup table                          25
CSL Workshop, October 13-14, 2005
                                    27
CSL Workshop, October 13-14, 2005
                                    28
CSL Workshop, October 13-14, 2005
                                    Result in Gaia




                                                     29
CSL Workshop, October 13-14, 2005
                                    30
CSL Workshop, October 13-14, 2005
                                    Resulting GML

       • Validates to EuroRoadS submodel GML
         schema
       • Complex attribute types not possible to import
         via FME or ArcGIS
             – Requires flat structure
       • After short! trial, no success in publishing via
         GeoServer WFS


                                                       31
CSL Workshop, October 13-14, 2005
                                        Approach(1)                                                  - Automatically (preferably no
                                                                                                     manual intervention)
                                                                                                     - Easy set-up
       • Pragmatic solution                                                                          - Minimum cost
                                                                                                     - Support from
       • Feasibility of approach                                                                     vendors/technologies
                                                                                                     - Support a SOA
             – Does it satisfy requirements:
                   • It is automatic.
                   • Creating XSL files can be complicated, especially if the semantics of
                     attributes to be transformed vary too much
                   • Time-consuming (costly)
                   • XSLT is a standardized methodology, GML is supported by the important
                     software producers
                   • We shall later see similar approach in a service architecture (Snowflake,
                     Finnish Geodetic Ins. etc..)
       • Would best support:                                Common conceptual
                                                                 model



                                                                  Derivation/
                                                                 specialization

       • s                                   Local conceptual
                                                  model
                                                                                  Local conceptual
                                                                                       model


                                                                 Implementation


                                              Logical/physical                    Logical/physical
                                                   model                               model
                                                                                                                                32
CSL Workshop, October 13-14, 2005
                                           Approach
       • Requires that the two models that need to be mapped do not
         differentiate too much:
             – Attribute types, feature types, etc.
             – No (immediate) generalization mechanisms
                   • i.e., the approach is scale dependent
             – Aggregation (attributes, features) is complicated
       • Requires in-depth knowledge of both models
             – From domain to low level spatio-temporal aspects of models
       • How to test that a mapping occurs error free
             – Validation of data?
             – Constraints?
       • Other possibilities:
             – Materialized views and stored procedures for mapping
                   • Create DB schema based on ‘complex’ UML or GML schemas?

                                                                               33
CSL Workshop, October 13-14, 2005
                                    34
CSL Workshop, October 13-14, 2005

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:4
posted:8/13/2012
language:
pages:33