1 / 13

Progress Report: North American Geologic Map Data Model (NADM) Design Team Activities

Overview. Progress Report: North American Geologic Map Data Model (NADM) Design Team Activities. Introduction to DMDT Report on activities requirements analysis data model variants data model revision Summary. Introduction. Data Model Design Team (DMDT) fact sheet:

napua
Download Presentation

Progress Report: North American Geologic Map Data Model (NADM) Design Team Activities

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. Overview Progress Report: North American Geologic Map Data Model (NADM) Design Team Activities • Introduction to DMDT • Report on activities • requirements analysis • data model variants • data model revision • Summary Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  2. Introduction Data Model Design Team (DMDT) fact sheet: Established: 1999 Purpose: geological map data model development for NADM Members: ~ 8 from state and U.S. and Can. Federal surveys; experts in GIS, data modeling, databases, mapping Reports to: NADM Steering Committee Meets: twice yearly, at GSA and DMT; working groups meet as required Activities: requirements analysis, variant documentation, data model revision Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  3. Introduction • What is a data model ? • Database design: a schema for storing data in a database • Interchange format: a syntax for transferring data, e.g. XML • Formal thesaurus: a conceptualization of geologic data types Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  4. 1. Requirements Analysis • Purpose:develop a document to • inform how geologic map databases might be queried • inform what the contents of map databases should be • Data:~ 800 questions gathered by NADM SLTT • e.g. select all map units with lithologic description X, geologic age Y, in geographic area Z • Method: • manual categorization and simplification by SLTT and DMDT Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  5. 1. Requirements Analysis • Results: • simplification: ~ 30 representative queries • categorization: metadata, descriptions, classifications, • relations, cartography, spatial • contents: representative components Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  6. 2. Variants • Purpose: • document database activity related to/derived from NADM • inform revision of NADM 4.3 • Data:several variant developments • Method: follow template as per Nov. 01, Boston GSA meeting notes: • Abstract, Diagram, Comparison with NADM 4.3, Example. • Results: • CORDLink v5.2 (GSC Pacific) • Idaho GS (IGS) • Arizona GS (AGS) • NGMDB/Kentucky (USGS, KGS) Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  7. 3. Data Model Revision • Purpose: • revise NADM 4.3 • Data: • NADM: requirements analysis, 4.3, variants • other: e.g. ESRI, XMML, Geoinformatics Network,… • Proposed Method: develop • Conceptual Model: technology neutral (e.g. ontologic) • Logical Model: technology specific (e.g. E-R, O-O) • Physical Models: platform specific (e.g. ESRI, SW) • Interchange Format: technology specific (e.g. XML) Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  8. Geologic Unit Chronostratigraphic MagneticProperty VolumetricProperty Biostratigraphic LithologicUnit Lithostratigraphic Lithodemic Surface-bounded UncomfomityBound Genetic Tectonic Geologic Structure Primary Structure Contact SedimentaryStructure Bedding Tectonic Structure Fault Fold Fracture Foliation Lineation Geologic Process RockFormingProcess Sedimentation Volcanism Diagenesis Intrusion RockChangingProcess Metamorphism Deformation Weathering HydrotherAlteration Metasomatism Geologic Property Genesis Fabric Texture Composition Spatial Description Morphology Orientation Geologic Age Instant Radiometric Interval UnNamedInterval NamedInterval Stratigraphic Biostratigraphic Magnetostrat. Measurement Sample Rank Earth Materials Rock Unconsolidated Soil Sediment Mineral Geologic Relation WholePart TypeOf Intrusion Superposition Geologic Classification Scheme TimeScale RockNameScheme Strat.Lexicon 3a. Conceptual Model (technology neutral) Geologic Thing Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  9. Relational:NADM 4.3 Object-oriented:NGMDB/KY (Johnson et al., 1999) (Brodaric & Hastings, 2002) … theme … rock unit ‘X formation’ rock type ‘granodiorite’ ‘monzogranite’ ... granodiorite porphyritic foliated monzogranite recrystallized gneissic etc. 3b. Logical Model (technology specific) Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  10. ESRI geodatabase GE SmallWorld Object Feature NADM Object Spatial Object point line polygon (ESRI Geology Working Group) (Wahl, 2001) 3c. Physical Models (platform specific) Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  11. Standard     3. Data Model Revision—Summary Purpose Content Example Conceptual Model technology neutral concept arrangement science language Richard, S. (1999), DMT’99. Interchange Format web-based data exchange, interoperability science language in a specific syntax XMML (CSIRO) Logical Model technology specific database design general abstractions: COA, concepts, … NADM 4.3, variants Database Design Physical Model platform specific database design specific abstractions: feature, object ESRI geodatabase, GESW Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  12. Summary • Past—DMDT development: • requirements analysis • variant documentation • Future—proposed DMDT development of a standard: • conceptualmodel for geologic map data • web-based interchangeformat for interoperability • (via Data Interchange Technical Team) • database design logicalmodel for geologic map data • facilitate physical model implementations • http://geology.usgs.gov/dm/steering/teams/design/ Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

  13. Questions? Progress Report: NADM Data Model Design TeamDMT’02, Salt Lake City

More Related