Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Data analysis wikipedia , lookup
Entity–attribute–value model wikipedia , lookup
Information privacy law wikipedia , lookup
Relational model wikipedia , lookup
Clusterpoint wikipedia , lookup
Data vault modeling wikipedia , lookup
Business intelligence wikipedia , lookup
1 Progress report on the implementation of a prototype National Geologic Map Database The National Geologic Mapping Act of 1992 and its Reauthorizations contain provisions that mandate the establishment of a National Geologic Map Database (NGMDB), distributed through links to Federal and State holdings, to include geologic maps and related geoscience data developed under the auspices of the Mapping Act. NGMDB design considerations: · database as an archive of geoscience information from which geologic maps are a type of report. · depth of knowledge representation and flexibility, not simplicity or performance. · provision to record alternative interpretations, evolving terminology and science paradigm, uncertainty, incomplete knowledge, and metadata pertaining to data acquisition, processing, and automation. · integration of geologic data from published maps by different authors at different scales, as well as newly acquired field data. NGMDB implementation provides a relatively abstract framework that may be customized for particular project applications. Software tools are designed against the abstract framework, and thus portable across different customized environments that follow the design pattern. NGMDB implementation of the NADM-C1 conceptual model revolves around three logical elements: · Vocabulary-- collection of terms and text definitions that enumerate things thought to exist in a domain or possible values for properties. · Data Schema-- explicit representation of the data model implemented in a particular repository, included as part of the data. It specifies kinds of data objects and their properties, relationships between objects, and rules that determine valid database conditions. · Data instance-- collection of related database records conforming to the Data Schema, which together specify attribute values for some entity of interest. Stephen M. Richard, David R. Soller, Jon A. Craigue ESRI Geodatabase implementation: Basic feature classes for spatial description 2 Feature ESRI top-level class for located data NGMDB top-level class for standard properties--DisplayName, TextDescription, Tracking, and system-maintenance fields. MappedOccurrence always has an explicit or implicit defining map horizon, and a classifier that specifies the geologic entity that intersects the map horizon to form the Occurrence. GeologyFeature MappedOccurrence GeomorphicFeatureTrace. Lines rep- Surface traces lines in a GIS that resenting the trace of a linear feature defined by the morphology of the map horizon surface. Subtypes: o Escarpment. uphill edge of a geomorphic escarpment o FaultScarp. Line representing the uphill edge of a fault scarp. Topology rules: must be covered by FaultTrace or Concealed FaultTrace. represent intersection of 3-D surfaces with a map horizon. Thus a surface trace always has a defining map horizon, and a classifier that specifies the kind of surface that intersects the map horizon to form the trace. Surface traces have a location uncertainty property. GeologicSurfaceTrace GeomorphicFeatureTrace Point represents collar location from which a borehole was drilled. Generally is intersection of borehole with EarthSurface. Has associated borehole object (not a geodatabase feature class). Polygons representing intersection between a geologic unit and a map horizon, whether or not the geologic unit is exposed on that horizon. The term exposure is used to refer to places where the geologic unit is visible on the map horizon. Subtypes GeologicUnitOutcrop DikeVeinMarkerTrace HingeSurfaceTrace Surface traces that do not participate in topologic rules between polygons and the geologic surface traces that bound them. · DikeVeinMarkerTrace. Represents intersection of a dike, vein, or marker bed, considered as a surface, with a map horizon. Concealed traces are depicted using the same feature class. Subtypes differentiate dike trace, vein trace, and marker trace. · HingeSurfaceTrace. Represents intersection of a fold hinge surface with a map horizon. Concealed traces are depicted using the same feature class. OutcropBoundaryTrace ConcealedBoundaryTrace ConcealedBoundaryTrace. Represents OutcropBoun- daryTraces that are not in the depicted map horizon and do not participate in geologic unit polygon topology on the map horizon depicted. 1. Trace of a boundary surface on a buried map horizon (e.g. top of bedrock beneath Quaternary cover). 2. Connect traces of surfaces that have been obliterated (e.g. intruded by igneous rocks) to indicate inferred continuity. 3. boundaries on a pre-existing but related map horizon o Concealed GeneticSurfaceTrace o Concealed FaultTrace. o StructureContour. represents the trace of a geologic surface on a horizontal surface of some given elevation; contour elevation identified by the map horizon property of the trace. ObservationLocation Station 3 · Station. an observation location point. Has related structural measurements, text notes, images, samples… Logical framework for NGMDB implementation Vocabulary < Described Concept Term Description Instance Data Instance Specificaton > Value Purpose Context Attribute Property Domain Cardinality Data Schema Observation Properties o GeologicUnitOutcrop. outcrop of a geologic unit. Topology rules: boundary must be covered by OutcropBoundaryTrace on same map horizon. Must not overlap other GeologicUnitOutcrop on same map horizon. Must not have gaps. o SuperimposedUnitOutcrop. outcrop of a geologic unit superimposed on the principal mapped units, for example alteration zones, zones of crushing, metamorphic zones… No topology rules. Surface traces that participate in topologic rules between polygons and the geologic surface traces that bound them. Subtypes: o GeneticSurfaceTrace. Represents intersection of genetic boundary surface (intrusive contact, depositional contact, facies boundary, etc.) with a map horizon. Classified using terms from the science language vocabulary. Topologic constraints: no dangles; may not intersect OutcropBoundaryTrace; must be covered by the boundary of a geologic unit polygon; may be covered by DikeTrace or VeinTrace where the dike or vein is intruded along the contact. o FaultTrace. Represents intersection of a fault surface with a map horizon. Classified (thrust fault, normal fault, strike slip fault, detachment fault, etc.) using terms from the science language vocabulary. Topologic constraints: dangles allowed; FaultTrace may not intersect OutcropBoundaryTrace; may be covered by DikeTrace or VeinTrace where the dike or vein is intruded along the fault; may cover the boundaries of outcrop polygons. 4 Extents associated with observations in the sense of GML Observation and Measurement (Cox et al., 2004). They represent features located based on where observations are made, and do not (inherently) represent the location of observable phenomena. All descriptions specify properties to distinguish normative and instance descriptions, by recognizing that the distinction is always context and purpose dependent: * Description purpose--makes the intended function of a description explicit, e.g., default description, necessary property description, identifying property description, or instance description. * Context-- specifies the domain within which the description is valid for the stated purpose. This domain may be spatial-(defined by a geodatabase feature), or it may be human-e.g., a particular project or person, some organization, or some published authority (e.g. the Glossary of Geology…). In the database implementation, data instances must include a pointer to the DataSchema Description entity that the data instance instantiates Implemented using standard relational (SQL) database technology (currently MS Access and Microsoft SQL Server) integrated into a geographic information system as an ESRI Geodatabase that links 'thematic' information with geologic map visualization. Test databases include: BoreholeCollar EarthFissureTrace · EarthFissureTrace. Represents trace of a fissure in the map horizon. 5 Database prototypes Northwest part of the Phoenix, AZ, metropolitan area. Full implementation; 1:24000-scale data Eastern Pima County. Level 1 implementation, 1:100,000 scale data Az Oil and Gas wells: customized Level 1 to focus on borehole information Conodont paleontology: customized Level 1 for conodont sample tracking and interpretation 6 Tool development for data entry Vocabulary tree view • Hierarchical representation of vocabularies allows the visual construction and grouping of concepts. • The nodes may be arranged using drag and drop • Abstract nodes -- not selectable in a pick-list • Deprecated terms -- no longer used, but keep in the hierarchy for previous references. Geologic unit maintenance Catalog is the collection of defined geologic units Each unit has at least one description (default) Each unit may have many other descriptions Different locations (quad, polygon, outcrop, borehole…) Different people Different focus (sedimentary structure, mineralogy..) Geologic unit description editor Several versions of implementation with escalating complexity and content: Level 0. Basic entities required for all geologic map databases All properties in Geologic unit and Earth material descriptions are specified with single values and no observation-related metadata (No attribute relationships) Geologic units may be composed of materials identified in the standard lithology vocabulary Geologic units may have parts that are other geologic units Geologic unit descriptions may be associated with stations or outcrops Stations have associated samples, structure observations, documents (images etc.), and text notes Simple representation of geologic ages with numeric bounds and free text named chronostratigraphic unit Simple free-text feature level metadata Left side is basic properties for selected description Tracking record Level 1. Standard level implementation Add BoreholeCollar, Borehole, SectionInterval, SectionIntercept SectionInterval has associated Geologic Unit description, sample, text notes, documents, structure observation Geologic structure description. Attribute relationship. Multiple valued attributes, observation-related metadata (confidence, basis, frequency, intensity, source) General semantic relationships between data objects (lineation in foliation, pluton intrudes fault) Multiple classification of mapped occurrences Full representation of geologic time scale, and geologic ages as ranges, multiple possible values, and multiple ages Data schema tables allow customization of schema using base tables and attribute relationships Display Name Link to Activity, defines ‘Project’,Person, Organization, Start/End, and Processing Method Tracking Record Maintenance In-depth feature level metadata (person, project, organization, activity, citations) Database persistence of map views (map legends, symbolization schemes) Fault slip and separation; aggregation of fault segments into faults and faults into fault systems. Add Traverse, Flight line as observation sections AreaOfInterest, and SectionTrace feature classes as ObservationLocations 7 Prototyping workflow Many fields are populated with 36 ASCII character GUIDs (globally unique identifiers, the unique identifier used throughout). In order to present user with meaningful words in ArcMap, generate geodatabase domains to provide lookups to science language terms. Domains are imported from tables generated by query from ScienceLanguage, and are exported as XML using ESRI Geodatabase Designer 2 extension (available free from ArcScripts site) to facilitate moving domains between databases. Thematic data entry using NGMDB tool and Microsoft Access forms interface free text Comment Citations linked to this Tracking record (0..*) Full implementation Model database using Microsoft Visio UML with ESRI geodatabase template Export design to XML interchange format Build database in ArcCatalog using ESRI CASE tool Add tables required by NGMDB data entry tool Load data using ESRI ArcCatalog data loader, or digitize line work Right side is tab control for geologic properties Level 0 Geologic Unit and Earth Material Description GeologicUnitDescription -DescribedUnitTermGUID : dGeologicUnit -ExtentContextSysGUID : esriFieldTypeString -ExtentTypeEntityGUID : dDescriptionContextEntity -GeologicAgeSysGUID : dGeologicAge -OutcropColor : esriFieldTypeString -WeatheringCharacter : dGUWeatheringCharacterTerm -CompositionType : dGeologicUnitCompositionTerm -Genesis : dGUGenesisTerm -GeneticEnvironment : dGUGeneticEnvironmentTerm -GeneticProcess : dGUGeneticProcessType -OutcropCharacter : dGUOutcropCharacterTerm -InternalStructure : dGeologicUnitStructureType -UnitMorphology : dGUMorphologyTerm -MetamorphicGrade : dMetamorphicGrade -ThicknessMin : esriFieldTypeSingle -ThicknessMax : esriFieldTypeSingle -ThicknessTypical : esriFieldTypeSingle Data Examples Report from Phoenix NW GeologicUnit Description EarthMaterialDescription -DescribedLithologyTermGUID : dStandardLithology -DegreeOfCrystallinity : dDegreeOfCrystallinityTerm -ConsolidationDegree : dConsolidationDegreeTerm -GrainDiscernibility : dGrainDiscernibilityTerm -RepresentativeSize : esriFieldTypeSingle -GenesisType : dEMGenesisTerm -CompositionTerm : dEMCompositionTerm -Fabric : dFabricTerm -Protolith : dStandardLithology -MetamorphicGrade : dMetamorphicGrade -Color : esriFieldTypeString Report from oil and gas well database