1 / 22

From Model Interoperability to Data Transformation

From Model Interoperability to Data Transformation. Steve Grise ESRI. Overview. Detailed approach for Schema mapping for Euroroads example Interoperability and semantics tools Some attempts at answers to questions. EuroRoads for Geodatabase.

brooke-griffin
Télécharger la présentation

From Model Interoperability to Data Transformation

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. From Model Interoperability to Data Transformation Steve Grise ESRI

  2. Overview • Detailed approach for Schema mapping for Euroroads example • Interoperability and semantics tools • Some attempts at answers to questions

  3. EuroRoads for Geodatabase • Created EuroRoads Geodatabase UML, exported to XMI, used ArcCatalog Schema wizard to create Geodatabase • Started with Canadian National Road Network (NRN) data in GML • Mapped schema from NRN to EuroRoad target (data interoperability extension) • Downloaded GML sample for the Yukon Territory • Created geoprocessing model to load the Yukon data into the model • Used XML Schema tools in ArcGIS to create export dataset

  4. EuroRoads for Geodatabase • Usually start with an Analysis Diagram • Simplified UML • Stepping stone between ideas and implementation • Example from Ontario roads prototype below • Would do Analysis Diagram to handle the more complex event/attributes for implementation model for EuroRoadS

  5. EuroRoads for Geodatabase CASE Tool UML

  6. EuroRoads for Geodatabase CASE Tool UML

  7. EuroRoads for Geodatabase • Mapping File (Road Node)

  8. EuroRoads for Geodatabase

  9. EuroRoads for Geodatabase

  10. EuroRoads for Geodatabase • XML Schema excerpt

  11. Semantic Interoperability

  12. Catalogs and Searching • Search support • Thesauri • English/other Languages • Geo • Euro SDI • Key is management of terms and relationships between concepts in real datasets • W3C and other standards exist • Some key geo pieces missing • Standards needed in this area • Basically the same problem as conceptual schema mapping, but done at the dataset/catalog level (and the feature level)

  13. W3C Options • XML Schema • Structure/hierarchies, i.e. “Family” • Resource Description Framework (RDF), (RDFS) • “Parents and children” • Ontology Web Language (OWL) • “Cousins” and other more complex relationships

  14. Results • Better search results • “parcel” search returns “Cadastre” • “Cadastral” search returns “Parcel”, “Corner”, other datasets • Some basic structure / semantics missing for Geo • Alexandria Digital Library • ISO Categories • … are both too general for Semantic Web needs (maybe even basic searches)

  15. A Few Tools • Protégé • Stanford, Open Source • Developed for medical ontology work (initially) • protégé.stanford.edu • LegendBurster • GeoReference Online, Commercial tools • Developed for mineral exploration market (initially) • www.georeferenceonline.com

  16. Protégé Example

  17. LegendBurster Example • TreeList Editor • Standalone tool • Query Tools • Complex searches • Results stored as attribute • Complex mapping results

  18. LegendBurster Example

  19. Summary • Euroroads schema mapping • Implementation tools available • Alternative approach • Uml-xmi-gdb-xml (+ other) • Need to work on semantics and relationships between datasets • Important for searching • Tools available • Small group should try to manage relationships

  20. Q&A • Do conceptual modeling languages satisfy Geo needs? • UML missing spatial patterns • UML probably too complex for most people • No other current alternative for graphical representation • Need to add simple, graphical examples to aid communication and comprehension • Consider information products and demonstration systems now, in parallel with CSL work • Harmonize? • Content, not necessarily CSL • Keep it simple at first • Meta model for cataloging and searching between terms • Watch for mixing of concepts and formats

  21. Q&A • Is a common conceptual schema needed? • Challenge is to be convinced that it adds value, makes things easier for partners/designers • Should target more broad audience than Euro community • UML extensions feasible? • Conceptual models – yes • Transition to logical models should be considered

  22. Q&A • Representing constraints? • Difficult to get agreement on behavior other than basic data integrity constraints • Suggest keep this as simple as possible • Different technologies and architectures means major differences in logical models • Relationship to Ontologies? • Catalog/search tool problem for a small group of people • Start work on this now in parallel with other activities

More Related