Core Content

The heart of a geologic map, required in an NCGMP09 database

Polygon features that represent areas where a contiguous mapped unit is found. These are the colors on your map.

More discussion as needed
Field Name Type Description
MapUnitPolys_ID String Primary key. Values must be unique for each polygon and ideally are universally unique.
MapUnit String Short key for the map unit. Example values: Qal, Tg, water, etc. Any value used here must be defined in the DescriptionOfMapUnits table.
IdentityConfidence String Qualitative indication of the uncertainty in this polygon's classification. Value is usually certain, questionable, or unspecified. Suggested default value of certain. Each term used here must be defined in the Glossary table.
Label String The label that should appear on a map for this polygon. Allows for subscripts and special characters.
Symbol String A reference to an area fill symbol. This may be an identifier in an ESRI style file, or it may identify a symbol in some other fashion. See the Symbolization page for more information.
Notes String Free text for additional information specific to this polygon.
DataSourceID String The identifier for a record in the DataSources table that indicates the source for this polygon.

Line features that represent the type of boundary between two mapped units belong here.

IsConcealed should be Boolean. LocationConfidenceMeters should allow null instead of faking it with -9.
Field Name Type Description
ContactsAndFaults_ID String Primary key. Values must be unique for each line and ideally are universally unique.
Type String Specifies the kind of feature represented by the line. Values could be, for example, contact, fault, waterline, glacier boundary, map boundary. Values must be defined in the Glossary table.
IsConcealed String Indicates whether or not the line is covered by an overlying map unit. Values = N, Y.
LocationConfidenceMeters Float Quantitative certainty of the line's position. Specify the uncertainty in the precision of this line's location in meters. Recommend value of -9 if value is not available.
ExistenceConfidence String Qualitative indication of the uncertainty of this line's existence. Suggested values include certain, questionable, unspecified. Suggested default value of certain. Values must be defined in the Glossary table.
IdentityConfidence String Qualitative indication of the uncertainty of this line's classification. Suggested values include certain, questionable, or unspecified. Suggested default value of certain. Values must be defined in the Glossary table.
Symbol String A reference to a line symbol. This may be an identifier in an ESRI style file, or it may identify a symbol in some other fashion. See the Symbolization page for more information.
Label String A human-readable name for this line. Can be used to store fault name, or whatever else is appropriate.
Notes String Free text for additional information specific to this line.
DataSourceID String The identifier for a record in the DataSources table that indicates the source for this line.

Polygon features that indicate the source of data for all parts of the map.

Redundant, but helpful. Should it be required?
Field Name Type Description
DataSourcePolys_ID String Primary key. Values must be unique for each polygon and ideally are universally unique.
DataSourceID String The identifier for a record in the DataSources table that indicates the source for the data in this area.
Notes String Free text for additional information specific to this polygon.

This table captures the content from the map unit legend on a traditional geologic map. This is where you describe your mapped units.

Should labels encourage implementation-specific markup? Fullname should not tell you what a map-app will do. All label, name and fullname are all null-able? How do I "notify GEOLEX" if my unit isn't in there? Really need to pay some attention to what's required here.
Field Name Type Description
DescriptionOfMapUnits_ID String Primary key. Values must be unique for each record and ideally are universally unique.
MapUnit String Short string that identifies a mapped unit. Examples include Qal, Tec, or Qvt. Each unit abbreviation must be unique in the database. Values in this field provide the link between this table and the MapUnitPolys table. Using special characters is not recommended in this field. Null values are acceptable, and are commonly associated with headings.
Label String A text string used label polygons when the map is displayed. May include markup to indicate special fonts, formatting, subscripts, etc. For example, Triassic Newark Formation might be labeled as <font=FGDCGeoAge>#</font>. Null values are okay for units that do not appear on map or are not labeled, like headings, water, glacier, and perhaps overlay units.
Name String The name of the mapped unit. Two examples are Chinle Formation or Shnabkaib Member. These names should be verified in the U.S. Geologic Names Lexicon (GEOLEX). If your usage does not agree with GEOLEX's, notification should be submitted to the Lexicon website.
FullName String Full name of unit, including identification of containing higher rank units. For example, Shnabkaib Member of the Moenkopi Formation. See lexicon-related note in 'Name', above. Null values are okay for headings or other geologic units that are not shown on map.
Age String Stratigraphic range, or for intrusive and extrusive rocks, age. This is free-form text, and is often shown within parentheses in traditional legend. To be more specific, or to record multiple stratigraphic ranges or ages for a unit, utilize the optional tables: ExtendedAttributes and GeologicEvent. Null values may be used for map units that inherit Age from a parent unit, or for headings or overlay units.
Description String Free-form text description of a map unit. These descriptions are commonly structured according to long-standaing tradition and are terse. Markup for formattingis permitted. Null values are okay for headings or obvious mapped units (e.g. water).
HierarchyKey String Description of the parent-child relationships between mapped units. This field encodes units as children of a particular heading, or members within a formation. Should take the form nn-nn-nn, nnn-nnn, or similar. These are numbers, left-padded with zeros, dash-delimited. Each fragment must be the same length to allow text-based sorting of the DMU entries.
ParagraphStyle String A term to describe the formatting of this record on a printed map. Example values include Heading1st, Heading2nd, standard or similar. The formatting associated with these terms should be explained in the Glossary table.
AreaFillRGB String Red, Green, Blue tuples that specify the suggested color for symbolizing this mapped unit. Consistent syntax is important in order to read this field and display the intended color. Each color value is an integer between 0 and 255 and are separated by commas: 0,234,245 or 12,46,189. Null values are okay for headings, etc.
AreaFillPatternDescription String Text description of any pattern suggested for symbolizing this mapped unit. For example, randomly oriented small red dashes. Provided as a convenience for users who must recreate the suggested symbolization. Null values are okay for headings and unpatterned map units.
Symbol String A reference to a polygon symbol. This may be an identifier in an ESRI style file, or it may identify a symbol in some other fashion. See the Symbolization page for more information.
DescriptionSourceID String The identifier for a record in DataSources table that indicates the source for the mapped unit description.
GeneralLithology String Term to categorize the map unit based on lithologic and genetic character, from the NGMDB standard term list. Null values OK for headings and unmapped units.
GeneralLithologyConfidence String Describes appropriateness of the specified GeneralLithology term for describing this map unit. Null values OK for headings and unmapped units.

This table lists sources of content that were used to generate the geologic map. Think of this as the list of citations, only less formal.

More discussion as needed
Field Name Type Description
DataSources_ID String Primary key. Values must be unique for each record and ideally are universally unique.
Source String A short, human-readable description that identifies the data source. For example, RJC new mapping, 2013.
Notes String Notes on this source, providing a more complete description of processing or data acquisition procedure. May include a full citation and/or URL.

This table defines terminology used throughout the data set. Help other people understand what you mean.

There are a number of fields that contain words or phrases that must be defined in the Glossary table:
In this table... define terms from these fields
MapUnitPolys IdentityConfidence
ContactsAndFaults Type ExistenceConfidence IdentityConfidence
DescriptionOfMapUnits ParagraphStyle
Any additional tables any fields that convey a type or a confidence in words.
Furthermore, its okay to put in more than you need. It just fine to include terms in the Glossary that are not found in one of these fields, or even not found in the entire database. This means you could feasibly build a Glossary table once, and then keep expanding and reusing it in all of your future NCGMP09 databases.
There has been some discussion about how to utilize terminology from other, perhaps already existing, vocabularies in order to define terms. Read more on this topic...
Field Name Type Description
Glossary_ID String Primary key. Values must be unique for each record and ideally are universally unique.
Term String Plain-language word for a concept. Values must be unique within database as a whole. These are terms used elsewhere in the dataset which require more explicit definition. For example, granite, foliation, certain, Heading1st.
Definition String Free-form description of the term in as plain language as possible.
DefinitionSourceID String The identifier for a record in DataSources table that indicates the source for the definition.