For more information, click on a feature class or table name. The values in certain fields must be defined in the Glossary table. These fields are highlighted in magenta bold type in the tables that follow.
| Field name | Description | Notes |
|---|---|---|
| MapUnit | Short, easily understood ASCII-character1 identifier for the map unit represented by this polygon. Foreign key to DescriptionOfMapUnits table (see table 14) | Examples of values are “Qal”, “Tg”, “Kit”, “Trdu”, “water” (see table 11). Use of special characters is discouraged. Null values not permitted |
| IdentityConfidence | Indicates how confidently this polygon has been identified as a particular map unit | Typical values are “certain”, “questionable”, “unspecified”. Values must be defined in Glossary table. Null values not permitted; suggest setting default value = “certain” |
| Label | Describes text label for this map-unit polygon | May or may not be same as MapUnit value. Determined from value of Label in DescriptionOfMapUnits table and IdentityConfidence (that is, if IdentityConfidence = “questionable”, then “?” is appended to Label value in DescriptionOfMapUnits table). Allows for special fonts to show geologic age symbols (see table 11) and other non-ASCII characters. Null values permitted |
| Symbol | References an area-fill symbol | Area-fill symbols (map-unit color, pattern, or color+pattern) must be included in accompanying .style file. Null values (which would indicate polygon is not filled on map) permitted; if Esri cartographic representations are used to symbolize map units, value may be null. Value is typically assigned by joining MapUnitPolys to DescriptionOfMapUnits table via MapUnit and calculating MapUnitPolys.Symbol = DescriptionOfMapUnits.Symbol |
| DataSourceID | Identifies source of each data element. Foreign key to DataSources table | Null values not permitted |
| Notes | Optional field | Free text for additional information specific to this polygon. Null values permitted |
| MapUnitPolys_ID | Primary key | Examples of values are “MUP1”, “MUP2”. Values must be unique in database. Null values not permitted |
| Field name | Description | Notes |
|---|---|---|
| Type | Specifies type of geologic feature represented by this database row | Examples of values are “contact”, “fault”, “thrust fault”, “waterline”, “glacier boundary”, “map boundary”. Values must be defined in Glossary table. Null values not permitted |
| IsConcealed | Indicates whether this contact or fault is concealed by an overlying map unit | Values = “N” or “Y”. Null values not permitted |
| LocationConfidenceMeters | Half-width (in meters) of positional-uncertainty envelope around this line feature | Data type = float. Null values not permitted; recommend setting value = −9 if value is not known (see discussion above in “Feature-Level Metadata” and example values in table 1) |
| ExistenceConfidence | Indicates how confidently existence of this line feature has been determined | Typical values are “certain”, “questionable”, “unspecified”. Values must be defined in Glossary table. Null values not permitted; suggest setting default value = “certain” |
| IdentityConfidence | Indicates how confidently this line feature has been identified as a particular type | Typical values are “certain”, “questionable”, “unspecified”. Values must be defined in Glossary table. Null values not permitted; suggest setting default value = “certain” |
| Label | Describes text label for this line feature | Can be used to store fault name or other easily understood name for line feature. Allows for special fonts to show geologic age symbols (see table 11). Null values are typical |
| Symbol | References a line symbol | Line symbols must be included in accompanying .style file. Null values (which would indicate lines are not shown on map) permitted; if Esri cartographic representations are used to symbolize lines, value may be null. Determined from values of Type, IsConcealed, LocationConfidenceMeters, ExistenceConfidence, and IdentityConfidence fields, as well as map display scale |
| DataSourceID | Identifies source of each data element. Foreign key to DataSources table | Null values not permitted |
| Notes | Optional field | Free text for additional information specific to this line feature. Null values permitted |
| ContactsAndFaults_ID | Primary key | Examples of values are “CAF1”, “CAF2”. Values must be unique in database. Null values not permitted |
| Field name | Description | Notes |
|---|---|---|
| MapUnit | Short, easily understood ASCII-character1 identifier for the map unit | Examples of values are “Qal”, “Tg”, “Kit”, “Trdu” (see table 11). Use of special characters is discouraged. Null values only permitted for headings and for units that do not appear on map or in cross sections |
| Name | Short name of formal2 or informal map unit, as shown in DMU | Examples of values are “Chinle Formation”, “Shnabkaib Member”, “basaltic andesite of Middle Sister summit”, “Ada Group”, “sandy siltstone”. Should contain no hierarchy specifications (these are given in ParagraphStyle and HierarchyKey fields). Place headings in this field; place headnotes in Description field. Null values not permitted |
| FullName | Full name of formal or informal map unit; must include complete identification of any higher rank unit(s) that contain this unit (may or may not be same as Name value) | Examples of values are “Shnabkaib Member of the Moenkopi Formation”, “sandy siltstone subunit of the Monterey Formation”. Values correspond to usages reported by Geolex (http://ngmdb.usgs.gov/Geolex/). Null values only permitted in rows that correspond to headings |
| Age | Age of map unit, as shown in DMU | Examples of values are “late Holocene”, “Pliocene and Miocene”, “Lower Cretaceous”. When age of subunit is not shown in DMU because it is same age as higher rank unit, use age of higher rank unit; do not leave empty. Null values only permitted for rows that correspond to headings |
| Description | Full description of map unit, as contained in DMU | Free text field. Allows for markup-language (for example, HTML) or special characters to show new paragraphs, superscripts, and geologic age symbols. Note that map-unit descriptions can be structured according to one or more accepted traditions (see text for discussion of content, structure, and style of unit descriptions). In rows that correspond to headings, place headnotes in this field (place headings in Name field). Null values permitted |
| HierarchyKey | Text string that indicates place of map unit or heading within DMU hierarchy | Text string has form of “n-n-n”, “nn-nn”, “nn-nn-nn”, “nnn-nnn”, or similar (see discussion in appendix 3); each dash-delimited fragment of string (1) is numeric, (2) has same length as others in string and in DescriptionOfMapUnits table, and (3) is left-padded with zeroes if values are greater than 9 (that is, if they exceed one digit). Examples of values are shown in appendix 3, which illustrates HierarchyKey values of several DMUs. Values describe order and rank of DMU elements and facilitate resolving queries such as “find all members of formation x” or “what is the parent unit of map unit y”. Null values not permitted |
| ParagraphStyle | Name of user-defined paragraph style that indicates hierarchy of map units and headings within DMU | Examples of values are “DMUHeading1”, “DMUHeading2”, “DMUUnit1”, “DMUUnit2”. Values must be defined in Glossary table; definition typically includes formatting specifications (for example, in Glossary table for Term = “DMUUnit1”, value for Definition might be Definition = “Paragraph style for formatted description of first-rank map unit. Times New Roman, Regular, 10 pt, 12 pt leading, left justified, 66 pt left indent, –20 pt 1st line indent, 3 pt space before”). Null values not permitted |
| Label | Describes text label for map-unit polygons. Field from which map-unit label is generated | May or may not be same as MapUnit value. Allows for special fonts to show geologic age symbols and other non-ASCII characters (see table 11). Null values only permitted for headings, for units that are not labeled on map or cross sections, and for units that do not appear on map or cross sections (for example, water, glaciers, overlay units, and units that are represented on map only by their subunits) |
| Symbol | References an area-fill symbol | Area-fill symbols (map-unit color+pattern, or color+pattern) must be included in accompanying .style file. Null values (which would indicate polygon is not filled on map) permitted; if Esri cartographic representations are used to symbolize map units, value may be null. Null values also permitted for headings and for units that do not appear on map or cross sections |
| AreaFillRGB | Specifies RGB3 equivalent of area-fill color of map unit as{<red value>,<green value>,<blue value>} tuples4 | Examples of values are “255,255,255”, “124,005,255”. Use of consistent syntax is important to enable computer programs to read field and display intended color: (1) each RGB color value is integer between 0 and 255; (2) values are left-padded with zeroes so that each consists of 3 digits; (3) values are separated by commas with no spaces (for example, nnn,nnn,nnn). Provided as convenience for users who want to re-create area-fill colors for onscreen viewing; especially important to non-ArcGIS users who are unable to use .style file supplied with database. Null values only permitted for uncolored map units and for headings |
| AreaFillPatternDescription | Easily understood description of pattern fill of map unit (for example, “random small red dashes”) | Provided as convenience for users who want to re-create area-fill patterns; especially important to non-ArcGIS users who are unable to use .style file supplied with database. Null values only permitted for unpatterned map units and for headings |
| DescriptionSourceID | Identifies source of Description. Foreign key to DataSources table | Example values include “DAS1” ( = this report), “DAS2” ( = Smith, J.G., 1899) (see tables 6, 7). Useful for documenting derivation of map-unit descriptions from another source. Null values not permitted |
| GeoMaterial | Categorizes map unit in terms of its lithologic and genetic character | Use terms from the NGMDB standard term list in appendix 1; see discussion in “Extensions to Traditional Geologic Map Content” section above. Null values only permitted for unmapped units and headings |
| GeoMaterialConfidence | Describes appropriateness of GeoMaterial term for describing map unit (see appendix 1) | Values must be defined in Glossary table. Null values permitted only for unmapped units and headings |
| DescriptionOfMapUnits_ID | Primary key | Examples of values are “DMU1”, “DMU2”. Values must be unique in database. Null values not permitted |
| Field name | Description | Notes |
|---|---|---|
| Source | Short, terse, easily understood ASCII-character1 identifier for a data source | Contains brief citation. For DataSources_ID = “DAS1”, Source = “this report” (by convention). If source is another publication, provide full reference citation in Notes field. Null values not permitted |
| Notes | Optional field | Free text for additional information specific to this data source. Provide full reference citation(s) here (if applicable). Processing or data acquisition procedures may be described here. Null values permitted |
| URL | Optional field | Contains link, either online URL or Digital Object Identifier (DOI), to either data source or full description of data source. Null values permitted |
| DataSources_ID | Primary key | Examples of values are “DAS1”, “DAS2”. Values must be unique in database. Null values not permitted |
The GeoMaterialDict table will be installed automatically in any database created with the script GeMS_CreateDatabase_Arc10.py. Note that users of the GeMS schema do not create this table; furthermore, this table should not be modified by authors or publishers of individual maps.
| Field name | Description | Notes |
|---|---|---|
| HierarchyKey | Text string that indicates hierarchy of entries within list of GeoMaterial terms | Text string has form of “n-n-n”, “nn-nn”, “nn-nn-nn”, “nnn-nnn”, or similar (see discussion in appendix 3); each dash-delimited fragment of string (1) is numeric, (2) has same length as others in string and in DescriptionOfMapUnits table, and (3) is left-padded with zeroes if values are greater than 9 (that is, if they exceed one digit). Examples of values are shown in appendix 3, which illustrates HierarchyKey values of several DMUs. Documents, for example, that “limestone” (HierarchyKey = “01-02-02-01”) is a kind of “carbonate rock” (HierarchyKey = “01-02-02”), which is a kind of “sedimentary rock” (HierarchyKey = “01-02”), which is a kind of “sedimentary material” (HierarchyKey = “01”) |
| GeoMaterial | Name of GeoMaterial unit | Terms used to populate GeoMaterial field in DescriptionOfMapUnits table |
| IndentedName | GeoMaterial name with indentation that corresponds to rank of entry within hierarchy | Useful for visually portraying hierarchy of GeoMaterial terms |
| Definition | Definition of GeoMaterial name | For example, GeoMaterial = “limestone” has Definition = “carbonate sedimentary rock, consisting chiefly of calcite” |
| Field name | Description | Notes |
|---|---|---|
| Term | Geologic concept, feature, phenomenon, or other terminology being defined | Examples of values are “foliation”, “syncline axis”, “contact”, “thrust fault”, “certain”, “low”, “fission track”, “K-Ar”. Values must be unique within database. Null values not permitted |
| Definition | Definition of value in Term | Null values not permitted |
| DefinitionSourceID | Identifies source of definition. Foreign key to DataSources table | Null values not permitted |
| Glossary_ID | Primary key | Example of values are “GLO1”, “GLO2”. Values must be unique in database. Null values not permitted |