Figure 2-11 - uploaded by Boyan Brodaric
Content may be subject to copyright.
Contexts in source publication
Context 1
... Stratigraphic Time Scale Table ( figure 2-10) is a hierarchical structured look-up table. Parent-child relationships in the stratigraphic time scale are captured in the Stratigraphic Tree Table and the level within the hierarchy is defined in the Stratigraphic Rank Table. This structure solves many of the problems with storing stratigraphic time information and facilitates the production of derivative maps based on rock unit age as well as the creation of derivative rock units based on stratigraphic age. The structure also facilitates the analysis of geologic maps where comparisons of stratigraphic age are required. All three of these tables, Stratigraphic Time Scale, Stratigraphic Rank, and Stratigraphic Tree are standardized look-up tables that are provided with the data model. Any organization using the data model may replace these with their own standardized tables, but the user or creator of each digital geologic map does not need to create these tables. For maximum use of the archive, the same standard tables should be used for all ...
Context 2
... stratigraphic age of the rock unit is stored in the same manner as the radiometric age, in the Stratigraphic Age Table. A one-to-many relation also links the Stratigraphic Age Table to the Rock Unit Table so that more than one stratigraphic age interval can be associated with each rock unit. In most cases, there will only be one record for stratigraphic age for each rock unit specifying the minimum and maximum age of the unit. There are, however, occasional units on geologic maps that have discontinuous age ranges. These units will require multiple records in the Stratigraphic Age Table. The key attribute, coa_id, identifies the rock unit with which each age record is associated. Because there can be any number of stratigraphic age ranges for a single rock unit, the key attribute and sequence number, strat_seq, is used to assure that each record has a unique key. The Stratigraphic Age Table contains attributes for minimum and maximum stratigraphic age as well as attributes for source references for the age determinations. A difference between the two tables is that the Radiometric Age Table includes numeric values for the ages, while the Stratigraphic Age Table uses figure ...
Context 3
... additional attributes included in the description of each rock type, lith_class and rock_name, are used to define the lithology and name of the rock composition, respectively. The lith_class attribute is used to select a lithology classification for the rock type from a pre-defined, hierarchical classification of rock types stored in the Lithology Table ( figure 2-10). The Lithology ...
Context 4
... to the Rock Unit Table on figure 2-9, there is a one-to-many relation between the Rock Unit Table and the Rock Composition Table. The Rock Composition Table is used to store descriptive information about the rock unit. A one-to-many relation is used so that there may be multiple composition records for each rock unit. This is particularly useful for rock units which are composed of a mixture of rock types; each rock type will be described in a separate Rock Composition record with no limit on the number of rock types, or compositions, that may be stored for a single rock unit. The Rock Composition Table uses the coa_id attribute plus a sequence number, comp_seq, as the key attributes. In addition to providing a unique key, in combination with the coa_id, the sequence number is used to specify the sequence of display of the composition records when a rock unit description is created for a map legend. Rock Composition is another table that is not complete at this stage of design of the data model. It is expected that additional attributes will be added to the table before it is adopted. All information that is unique to a single rock type within a rock unit should be stored in this table or linked to this table. The attributes, mineralogy, color, texture, and alteration, represent simple text descriptions of the rock type; additional descriptive attributes could be added. The attributes, percent and quality, are used to specify an estimate of the volume percent of the rock unit composed of the rock type in question and the quality of that estimate, respectively. These values are important for creating derivative maps based on rock type or lithology. For example, it would be extremely difficult to produce a major lithology derivative map without an estimate of the volume percent of each rock type for each rock ...
Context 5
... addition to the lith_class attribute, which forms the key, the Lithology Table ( figure 2-10) also contains attributes for storing an identification number for each record, a level number for each record, and a description of the particular rock type, if needed. The identification number, lith_id, forms the link with the Lithology Tree Table, which is used to store parent-child relations between records in the Lithology ...
Context 6
... with all other objects in the Compound Object Archive, structural features are represented in the COA Table ( figure 2-8) with an object identification number, a name, a description, source information, and a type code which identifies the object as a structural feature. There are two different types of structural features that can be represented in the Compound Object Archive, individual structures, such as named faults, and generic structures, such as all normal faults. Normally, there would be a single record in the COA Table for each generic type of structure, one for all approximately located normal faults, one for all anticlines, one for all queried contacts, etc. For each type of structure, which has an individual symbol or description on the map legend, there would be a generic record in the COA Table. In addition, there would be a record in the COA Table for each individual structure that is uniquely identified on the map, usually by a name. Thus, although the San Andreas Fault might be a dextral, strike- slip fault on a particular map, it would have its own individual record in the COA Table so that the name San Andreas Fault could be associated with the entire structure. For records that are identified in the COA Table as structures, there is a one-to-many relation between the COA Table and the Structural Correlation Table. The Structural Correlation Table is used in much the same manner as other correlation tables in the data model. It serves to convert a many-to-many relation between the COA Table and the Structural Type Table ...
Context 7
... Spatial Object Composition Table is used to store information about the composition of individual spatial objects. Although the table could be used to store information about other types of spatial objects, its primary use is to store information about the composition of individual rock unit polygons, and thus this table links individual spatial objects to the Compound Object Archive. The normal procedure for defining a rock unit is to store the definition of the rock unit and its composition in the Compound Object Archive ( figure 2-8). The rock unit definition is then linked to multiple spatial objects through the legend and the Spatial Classification Table. In some cases, a compound unit will be defined in the legend which refers to several rock units in the Compound Object Archive or a rock unit defined in the Compound Object Archive will contain several different compositions. The unit is then linked to multiple polygons through the Spatial Classification Table. For most polygons in the map area, there may be no information as to which of the rock units in the legend definition (or compositions of a single rock unit) occur within the polygon, or the extent to which they occur within the polygon. However, if there is information about the composition of an individual polygon, the Spatial Object Composition Table permits the user to store information about the composition of an individual polygon in terms of rock units defined in the Compound Object Archive. In addition to the usual attributes shared with all Singular Object Archive Tables, the Composition Table includes attributes for coa_id, comp_seq, percent, quality, source_org, and source_id. The attributes, coa_id, and comp_seq are used to identify a specific unit in the Compound Object Archive and the particular portion of the unit (composition), respectively. The unit must be defined in the Compound Object Archive. The attributes, percent and quality, are used to specify an estimate of the volume percent of the polygon composed by the unit in question and the quality of the estimate. Typically, there would be several records in the Singular Object Composition Table for a given polygon, each referring to a different rock unit or portion of a rock unit in the Compound Object Archive and each specifying the volume percent within the polygon. The source_org, and source_id attributes refer to the source record for information specific to the composition breakdown specified in the composition ...
Context 8
... the features of the previous figures yields a generalized diagram of the relational data model ( figure 2-4). It differs from the previous diagrams in the addition of metadata and a spatial object archive (Geographic Information System, or GIS). Metadata includes an original source for each archive object (whether descriptive or spatial) as well as descriptive information about individual maps. At the general level of this diagram, the box labeled metadata represents all of the metadata for each map in the archive, whether an original publication or a new derivative map. However, in the model presented here, only the information needed for the model is included in the tables. Additional metadata could be added to the model, or the archive could be linked to an external metadata ...
Context 9
... fig. 2 Central to this diagram is the classification object. It permits spatial objects to be connected with their descriptive data in the Compound Object Archive, and it permits symbolization to be assigned to each object. Heavy lines represent a relationship between an individual table in the Singular Object Archive and all tables within the GIS. These relationships are portrayed in this manner because geologic entities of any type can be represented as any of the GIS geometric types (i.e. areas, lines, or points on 2-D maps) and individual map entities (single point, line segment, or polygon) can be given a specific name or age and can represent more than one sub-unit. For example, although site details are normally associated with map points, the model allows site details (in the Singular Object Archive) to be associated with any type of map entity. The Singular Object Archive, presented here as individual tables in the relational database, could just as well represent connections to external databases (e.g. a database of field notes). Note that all entities are tied to an original source. Each rock unit as a whole can have associated one or more stratigraphic age ranges (each with a minimum and a maximum) as well as one or more radiometric ages. These data can come from sources that are different than the source of the unit definition. Each rock unit has a rank (group, formation, member, etc.) and the relative level of unit ranks is maintained in a Unit Rank table. This table allows easy creation of derivative maps at various rank levels. Each rock unit is made up of one or more compositions. Rock compositions correspond to individual rock types, or lithologies, which are included in the defined unit. For example, a clastic rock unit composed of conglomerate, sandstone, and shale would have three rock composition records. Each would describe a single lithology within the ...
Context 10
... COA Table ( fig, 2-8) connects the Compound Object Archive to the legend, and thus, to the rest of the data model through the Data Classification Correlation Table (described above). The key to the COA Table is the attribute, coa_id, which contains an identification number assigned to the compound object. Because the key attribute to the COA Table must be unique within the Compound Object Archive, the name of the object cannot be used as the key attribute. It is always possible for the same object name to be used on different maps for differing objects. The coa_id is used to link between the COA Table and the rest of the Compound Object Archive. The COA Table also includes source_org and source_id attributes to link each entry in the Compound Object Archive to its original source. The attribute, coa_name, contains a short name for the object. The attribute, coa_desc, is a text attribute which can be used to describe the object in more detail than what is provided in the coa_name attribute. Finally, the attribute, coa_type, defines the type of object being described. The coa_type attribute is used to determine which of the additional tables in the Compound Object Archive contain the remaining attributes for the object and, therefore, distinguishes rock units from structural or metamorphic overlay units, ...
Context 11
... Compound Object Archive is composed of a number of data tables and look-up tables that are used to define Compound Geologic Objects. The heart of the archive is the COA Table, which links the legend, and thus the rest of the data model, to the various types of compound geologic objects that can be described and defined within the archive. The Compound Object Archive stores the definitions of all objects that are related to multiple spatial entities (points, lines, or polygons). The archive can be used to define many different types of geologic objects, of which only three will be described here. These three have been selected because each represents a common and different class of geologic object. The first to be defined, Rock Units, represents the most common use of the archive, which is to define various types of map units based on rock features (lithology, age, stratigraphic position, mineralogy, etc.) Any type of unit, which forms a polygonal base for a geologic map, would be treated in a fashion similar to Rock Units. Structural Features will also be described because they form the second most common type of geologic object and because they represent a class of generally linear geologic objects. Any other linear geologic object would be treated in a manner similar to Structural Features. Finally, Metamorphic Overlay Units will be described, not because they are particularly common in geologic maps, but because they represent a unique class of geologic objects-polygonal objects that overlay a polygonal geologic map base. These units are an example of any unit type that overlies the base Rock Units and are thus, in a sense, transparent to this base. Note that these polygons do not represent metamorphic rock units; they represent metamorphism that crosscuts the underlying rock units. Other examples of this class of units would be alteration overlays or glacial extent overlays. The diagrams of the Compound Object Archive show a table for Additional COA Types ( figure 2-8), which is included to indicate additional types of objects, such as geomorphologic or soil objects. These additional types of objects are distinct from additional attributes, such as engineering properties of rock units, which would attach to the Rock Unit ...
Context 12
... final correlation table that is connected to the Classification Object Table is the Spatial Classification Table ( figure 2-7) which connects the legend to the Spatial Archive. The Spatial Classification Table has no additional attributes and simply functions as a correlation table to convert the many-to-many relation between the Classification Object Table and the various Spatial Object Archive tables to several many-to-one relations. This many-to-many relation between the spatial object and its classification implies that a spatial object may be classified in more than way: i.e. if its appearance varies on different maps, or if it is classified as more than one type of object such as a fault that is also a ...
Context 13
... digital archive of geologic features is connected to a geologic map legend facility ( figure 2-1). This legend facility can be viewed as a filter, which selects specific geologic features from the archive and symbolizes them for presentation on a map. Thus, the process of creating a new, or derivative, map from existing data within the archive, becomes a natural process of defining the new map's legend and then applying it to the ...
Context 14
... lines connecting entities in the diagrams represent relations between the entities. Figure 2-5 shows the method used to identify the type of relation between the two entities connected by the line. Relations are characterized by whether an entity's existence is dependent on its related entities, and in what amounts an entity may participate in the relation. Each entity may occur zero, once or many times in the relation. Binary entity relationships may thus have one-to-one, one-to-many, or many-to-many cardinalities. For instance, if entity A is related to entity B in a one-to-many way, then for each occurrence of an instance of A, there may exist many occurrences of B, whereas each occurrence of B can only be related to one instance of A. If B is independent of A, then the relationship could be described as being one-to-zero or many. In general, all of the relations shown in the diagrams are one-to-one or one-to-many. Where a many-to-many relation would be indicated by the nature of the connected entities and their contained data, a correlation table has been inserted between them to convert the many-to-many relation to two one- to-many relations. This type of conversion is required by the nature of relational databases and is one of the differences between the relational model and the object-oriented model. In object oriented database implementations, these correlation tables are not ...
Context 15
... data model is consistent with the fact that any geologic feature may be represented as one or more geometric shapes (e.g. figure 2-2 -volumes, surfaces, areas, lines, etc.) depending on the type and scale of the map. For example, rock units are not confined to a volume (or area, in two-dimensions) geometry. At a small enough map scale, thin rock units may appear as surfaces (represented as lines or line segments in two dimensions) and small, but important, units may be represented as points. Similarly, veins, dikes, fault zones, etc. may change representational geometry with changes in scale. For purposes of data modeling, geologic objects can be divided into two categories, singular objects and compound objects. Singular geologic objects are those which have been directly observed at a single point location, such as bedding orientations, sample descriptions, chemical analyses, measured sections, etc. as well as those which relate to a single map entity (single polygon or line segment). Compound geologic objects typically include information from observations at multiple locations, such as locations of contacts or structures as well as descriptions of stratigraphic units, structural units, metamorphic units, etc. Singular and compound objects are generally treated differently and are therefore stored in different portions of the data ...
Similar publications
In the past decade, the deployment of deep learning (Artificial Intelligence (AI)) methods has become pervasive across a spectrum of real-world applications, often in safety-critical contexts. This comprehensive research article rigorously investigates the ethical dimensions intricately linked to the rapid evolution of AI technologies, with a parti...
![Figure 1. Barnes-Hut-SNE [32] visualization of the deep feature...](profile/Pablo-Muse/publication/321571084/figure/fig1/AS:635164589817857@1528446447800/Barnes-Hut-SNE-32-visualization-of-the-deep-feature-embedding-learned-for-the_Q320.jpg)
Deep neural networks trained using a softmax layer at the top and the cross-entropy loss are ubiquitous tools for image classification. Yet, this does not naturally enforce intra-class similarity nor inter-class margin of the learned deep representations. To simultaneously achieve these two goals, different solutions have been proposed in the liter...
Citations
... Paralelamente a la publicación por el British Geological Survey de los vocabularios de rocas, sedimentos y depósitos superficiales (Gillespie y Styles, 1999;Robertson, 1999;Hallsworth y Knox, 1999;McMillan y Powell, 1999), se difunden los primeros modelos de datos complejos para el almacenamiento y explotación de la información geológica representada en los mapas geológicos (Johnson et al, 1999). La creación de tales modelos se plantea ante la evidente capacidad de los sistemas digitales para almacenar una representación numérica de determinadas facetas de la Tierra y facilitar la ejecución de análisis complejos (Richard, 1999). ...
The communication of geoscientific information via telematic networks is of limited value if there is no prior agreement as to the semantics involved. An understanding of the basic concepts expressed on geological maps is essential to their reuse and interoperability. Vocabularies of controlled terms play a key role in guaranteeing this matter, apart from constituting the main pillar of ontology. During recent years several international initiatives have been undertaken to establish lists of controlled terms to be used in the communication of digital geological information. The OneGeology-Europe Project (ECP-2007-GEO-317001) undoubtedly represents the greatest attempt made to harmonize the semantics of geological data. To facilitate web-accessible, interoperable, geological spatial datasets at national scale within the framework of the European Union, one of its achievements is to have developed a geoscientific language composed of 15 hierarchically structured vocabularies. Terminology referring to lithology and geological age, each containing more than 150 words and phrases, has been used to make multilingual queries in the OneGeology-Europe geoportal.
... Based on previous experience with geologic map database design and implementation, especially the evolution of implementations based on the Johnson et al. (1998) model version 4.3 (see http://nadm-geo.org for examples listed under " Data Model Design Team " ), it became apparent that a widely applicable geoscience database implementation must be adaptable to evolving data requirements. In order to provide the flexibility and expressiveness required for a widely applicable geoscience information system, we are implementing a relatively abstract logical model that allows different users to configure the data structure to include entities and properties appropriate for their requirements. ...
A geologic map is typically a 2D representation of 3D subsurface structures in a given area. It is based on the currently accepted geologists' model explaining the observed phenomena and the processes that shaped them in the geologic past. For historical reasons, this model is recorded in a geologic map with an explanatory booklet that describes the authors' conclusions as well as relevant field observations and other data such as tectonic measurements, drill hole logs or fossil records. Today, however, this variety of information can be better handled by converting it into digital and even hypermedial format. This necessitates the prior conception, development and implementation of a suitable geologic “hypermap model”. The main objective of this study is to design models and tools well-suited for the interaction between users and geologic hypermaps. The unique aspect of this family of applications is that users, in general, are both end-users (e.g., engineers) and designers (e.g., mapmakers). Objectives, concepts and methods for developing a human interface to geologic hypermaps have been tested using a prototype (i.e., GeoHyp) within the GIS environment of ArcView from ESRI. Tools to access the underlying background database via hyperlinks have been implemented, as well as functions especially developed to meet specific geologic requirements. Tests with various types of users have shown that the prototype matches their expectations and serves as a good basis for further development. In this article, we report on our design choices for GeoHyp and the current status of our project.
