· MapUnitDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by MapUnitID for each record. Domain: 427 = the DataSetID for the MapUnits table.
· MConf: Character, width 16. For polygons of type “Rock Volume Map Unit” (ID = 2406) or “Surficial Map Unit” (ID = 2405), this field contains a text string that indicates the subjective confidence of the person making the map unit classification in the assignment of the material within the polygon to a particular rock volume or surficial geologic map unit. Otherwise the field does not contain a value. Domain: ‘low’, ‘standard’, or ‘high’.
·
Label: Character, width 50. This field contains
strings that are equivalent to the geologic map unit labels on the default map
visualization. This attribute represents the default classification of each
polygon to a particular rock unit and is included to make symbolizing and viewing
the default map visualization relatively simple. The label is queried if the
classification confidence is low. In addition, map labels with Tertiary,
Pennsylvanian, Precambrian, Cambrian, Paleozoic, or Mesozoic geologic age
prefixes are shown using their corresponding special font symbols included in
the AZGSArial font (included with this database, /support/fonts/Azgsa___.ttf).
When shown in the default ArcView font, as in ArcView tables, these special
characters are displayed as follows: _files/image002.jpg){kind=small}
= ² (Alt-0178) ; _files/image004.jpg){kind=small}
= ³ (Alt-0179); _files/image006.jpg){kind=small}
= ¹ (Alt-0185); _files/image008.jpg){kind=small}
= º (Alt-0186); _files/image010.jpg){kind=small}
= ¼ (Alt-0188); and _files/image012.jpg){kind=small}
= ¾ (Alt-0190). Domain: Free text.
· Name: Character, width 255. This field contains strings that are equivalent to the geologic map unit names in the map explanation on the default map visualization. This is a redundant field added to simplify the use of the dataset in non-relational database environments. Domain: Free text.
Arc Attributes
· ObjectID: Integer, width 16. Compound primary key. This field contains an integer value that uniquely identifies each feature in the RoskGeo arc coverage. Each feature has a different value. Domain: >0 and <1016, no duplicates.
· DataSetID: Integer, width 16. Compound primary key. This field contains an integer value that uniquely identifies the RoskGeo arc coverage. All features in the dataset have the same value. Domain: 422 = the DataSetID for this table in the DataSetAZ dataset.
· Accuracy: Integer, width 8. This field contains an integer value that represents the spatial uncertainty in the location of a feature, in meters. For example, a value of 10 for a line feature indicates that the geologic entity represented by the line on the default map visualization is within 10 meters of the mapped feature’s actual location on the ground. At present this uncertainty combines the geologic uncertainty in the accuracy of location (e.g. for a gradational or poorly exposed contact), and the numerical uncertainty in the computer representation of the line location resulting from accumulated calculation and digitizing errors. The uncertainty must be greater than the numerical precision of the X,Y coordinates that locate a point (i.e. the accuracy cannot exceed the precision). This value determines the line style that represents the line by using standard solid, dashed, and dotted lines. For most existing maps, this length will be based on standard map accuracy, i.e. the geologic entity is located within the width of the line shown on a map for a solid line. In this data set, location uncertainties are qualitatively estimated. A value of 0 indicates that accuracy is not defined, as in the case of cartographic lines. Domain: >numerical precision of data and <108.
· TrackingID: Integer, width 16. This field contains an integer value that uniquely identifies the origin tracking for each object. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID for each record. Domain: 18 = the DataSetID for the TrackingRecord table.
· ConceptID: Integer, width 16. This field contains an integer value that specifies the concept used to identify the kind of spatial feature represented by this record. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: See Table 5.
Table 5. Classification concept code values used in the RoskGeo.aat table.
|
ConceptID |
Name |
|
7 |
Contact,
not classified, timing not specified |
|
58 |
Fault,
High-angle, normal separation |
|
596 |
Fault,
Generic high-angle, separation unknown |
|
642 |
Mapping
boundary surface |
|
2423 |
Contact,
intraformational, timing not specified |
· ConceptDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by ConceptID for each record. Domain: 1 = the DataSetID for the ClassificationConcept table.
· CConf: Character, width 16. This field contains a text string that subjectively describes the identification confidence by which an object has been classified. Domain: ‘low’, ‘standard’, or ‘high’.
· CartoObjID: Integer, width 16. This field contains an integer value that identifies the cartographic symbolization for each spatial object on the default map visualization. It is a foreign key that links to the CartoObjID field of the CartographicObject table in the RoskrugeWaterman database. Domain: See Table 6.
Table 6. Cartographic object codes used in RoskGeo.aat table.
|
CartoObjID |
Name |
|
53 |
Null
line symbol |
|
54 |
0.5pt
dashed black line (24K) (Approximate contact) |
|
55 |
0.5
pt solid black line (24K) (Accurate contact) |
|
59 |
1.5pt
dashed black line (24K) (Approximate fault) |
|
60 |
1.5pt
solid black line with queries (24K) (Queried accurate fault) |
|
61 |
1.5pt
solid black line (24K) (Accurate fault) |
|
65 |
2.5pt
solid black line (24K) (Map neat line) |
|
67 |
0.75pt
dotted black line (24K) (Concealed contact) |
|
68 |
0.5pt
solid black line with queries (24K) (Queried accurate contact) |
|
71 |
0.5pt
black line with dash-dot pattern (24K) (Scratch contact) |
· CartoObjDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by CartoObjID for each record. Domain: 21 = the DataSetID for the CartographicObject table.
· Label: Character, width 50. This field, when used, contains strings that identify line features that have a label associated with them, as in the case of named faults. Domain: Free text.
· Name: Character, width 255. This field contains strings that identify the default classification of each type of line and is included for simplification purposes. Features not shown on the default map visualization are indicated here as being hidden. Domain: Free text.
Roskruge Point Coverage
The RoskPnt coverage is a point coverage that represents geologic spatial features located at a distinct point (structural measurement stations, rock samples collection stations...).
Point Attributes
· ObjectID: Integer, width 16. Compound primary key. This field contains an integer value that uniquely identifies each feature in the RoskPnt point coverage. Each feature has a different value. Domain: >0 and <1016, no duplicates.
· DataSetID: Integer, width 16. Compound primary key. This field contains an integer value that uniquely identifies the RoskPnt point coverage. All features in the dataset have the same value. Domain: 424 = the DataSetID for this table in the DataSetAZ dataset.
· Accuracy: Integer, width 8. This field contains an integer value that represents the spatial uncertainty in the location of a feature, in meters. For example, a value of 10 for a point feature indicates that location of the point recorded in the database is within 10 meters of the mapped feature’s actual location on the ground. At present this uncertainty combines the geologic uncertainty in the accuracy of location (e.g. for a gradational or poorly exposed contact), and the numerical uncertainty in the computer representation of the line location resulting from accumulated calculation and digitizing errors. The uncertainty must be greater than the numerical precision of the X,Y coordinates that locate a point (i.e. the accuracy cannot exceed the precision). A value of 0 indicates that accuracy is not defined. Domain: >numerical precision of data and <108.
· TrackingID: Integer, width 16. This field contains an integer value that uniquely identifies the origin tracking for each object. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID. Domain: 18 = the DataSetID for the TrackingRecord table.
· ConceptID: Integer, width 16. This field contains an integer value that specifies the concept used to identify the kind of spatial feature represented by this record. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: 3340 = Field Observation Station.
· ConceptDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by ConceptID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· CConf: Character, width 16. This field contains a text string that subjectively describes the accuracy (classification confidence) for the classification of this object. Domain: ‘low’, ‘standard’, or ‘high’.
· CartoObjID: Integer, width 16. This field contains an integer value that identifies the cartographic symbolization for each spatial object on the default map visualization. It is a foreign key that links to the CartoObjID field of the CartographicObject table in the RoskrugeWaterman database. Domain: See Table 7.
Table 7. Cartographic object codes used in the RoskPnt.pat table.
|
CartoObjID |
Name |
|
52 |
Null point symbol |
|
2055 |
Inclined bedding symbol - color black (24K) |
|
2056 |
Approximate inclined bedding symbol - color black (24K) |
|
2057 |
Inclined crenulated or warped bedding symbol - color black (24K) |
|
2058 |
Inclined bedding w/tops known symbol - color black (24K) |
|
2059 |
Overturned bedding symbol - color black (24K) |
|
2060 |
Overturned bedding w/tops known symbol - color black (24K) |
|
2062 |
Vertical bedding symbol - color black (24K) |
|
2064 |
Vertical bedding w/tops known symbol - color black (24K) |
|
2076 |
Generic inclined foliation symbol - color black, open triangle (24K) |
|
2093 |
Inclined eutaxitic foliation symbol - color black (24K) |
|
2096 |
Inclined flow foliation symbol - color black (24K) |
|
2110 |
Inclined close disjunct cleavage symbol - color black (24K) |
|
2111 |
Vertical close disjunct cleavage symbol - color black (24K) |
|
2115 |
Inclined bedding parallel to cleavage symbol - color black (24K) |
|
2128 |
Horizontal joint symbol - color black, open rectangle (24K) |
|
2129 |
Inclined joint symbol - color black, open rectangle (24K) |
|
2143 |
Minor anticline symbol - color red (24K) |
|
2165 |
Fault attitude symbol - color black (24K) |
|
2172 |
Circle with filled central circle (USGS 26.2.5) - color black (24K) |
· CartoObjDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by CartoObjID. Domain: 21 = the DataSetID for the CartographicObject table.
· Label: Character, width 50. This field, when used, contains strings that are equivalent to any labels associated with point features on the default map visualization. In this database, this field contains sample identification numbers or is empty. Domain: Free text.
· Rotation: Integer, width 4. This field contains an integer value that specifies the rotation of the font symbol to correctly represent the azimuth of the of geologic feature displayed on the default map visualization at this point. This value is specific to the graphical environment of ArcView 3.2 using the AZGSgeo.ttf font (/support/fonts directory in the distribution package); the rotation angle is measured anticlockwise, starting from a compass azimuth of 90º, and is also dependent on the orientation of the symbol in its font definition. Domain: 0 to ±360.
· Name: Character, width 255. This field contains strings that identify the default classification of each type of point and is included for simplification purposes. Features not shown on the default map visualization are indicated here as being hidden. Domain: Free text.
GEOLOGIC SHAPEFILES
One ESRI shape file containing geologic lines is included in the geospatial database for DI-19. This shapefile, and the user-defined features included in its feature attribute table, is summarized in Table 8.
Table 8. Summary of geologic shapefiles showing fields, field definitions, and associated database tables. The ObjectID field, along with the DataSetID field, is the compound primary key for each shapefile. If a field joins to a lookup table, the table name is shown adjacent to that field in the last column.
|
Shapefile Name |
Type |
Field Name |
Data Type |
Width |
Lookup Tables |
|
|
Line |
ObjectID DataSetID Accuracy TrackingID TrackingDS ConceptID ConceptDS CConf CartoObjID CartoObjDS Label Name |
Integer Integer Integer Integer Integer Integer Integer Character Integer Integer Character Character |
16 16 8 16 16 16 16 16 16 16 50 255 |
|
Roskruge Other Geologic Lines Shapefile
The RoskGeoLines shapefile is a line shapefile that contains
those geologic lines that do not define polygon topology (concealed faults,
fold hinges, dikes, marker beds...).
Arc Attributes
· ObjectID: Integer, width 16. Compound primary key. This field contains an integer value that uniquely identifies each feature in the RoskGeoLines line shapefile. Each feature has a different value. Domain: >0 and <1016, no duplicates.
· DataSetID: Integer, width 16. Compound primary key. This field contains an integer value that uniquely identifies the RoskGeoLines line shapefile. All features in the dataset have the same value. Domain: 423 = the DataSetID for this table in the DataSetAZ dataset.
· Accuracy: Integer, width 8. This field contains an integer value that represents the spatial uncertainty in the location of a feature, in meters. For example, a value of 10 for a line feature indicates that the geologic entity represented by the line on the default map visualization is within 10 meters of the mapped feature’s actual location on the ground. At present this uncertainty combines the geologic uncertainty in the accuracy of location (e.g. for a gradational or poorly exposed contact), and the numerical uncertainty in the computer representation of the line location resulting from accumulated calculation and digitizing errors. The uncertainty must be greater than the numerical precision of the X,Y coordinates that locate a point (i.e. the accuracy cannot exceed the precision). This value determines the line style that represents the line by using standard solid, dashed and dotted lines. For most existing maps, this length will be based on standard map accuracy, i.e. the geologic entity is located within the width of the line shown on a map for a solid line. A value of 0 indicates that accuracy is not defined, as in the case of cartographic lines or the map neatline. Domain: >numerical precision of data and <108.
· TrackingID: Integer, width 16. This field contains an integer value that uniquely identifies the origin tracking for each object. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingDS. Domain: 18 = the DataSetID for the TrackingRecord table.
· ConceptID: Integer, width 16. This field contains an integer value that specifies the classification concept used to identify the kind of spatial feature represented by this record. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: See Table 9.
Table 9. Classification concept codes used in the RoskGeoLines table.
|
ConceptID |
Name |
|
58 |
Fault, High-angle, normal separation |
|
530 |
Vein |
|
596 |
Fault, Generic high-angle, separation unknown |
|
612 |
Marker bed |
|
1988 |
Fold hinge surface, upright anticline |
|
1994 |
Fold hinge surface, upright syncline |
|
2379 |
Mafic dike |
|
2380 |
Intermediate dike |
|
2381 |
Felsic dike |
· ConceptDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by ConceptID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· CConf: Character, width 16. This field contains a text string that subjectively describes the confidence for the classification of this object. Domain: ‘low’, ‘standard’, or ‘high’.
· CartoObjID: Integer, width 16. This field contains an integer value that identifies the cartographic symbolization for each spatial object on the default map visualization. It is a foreign key that links to the CartoObjID field of the CartographicObject table in the RoskrugeWaterman database. Domain: See Table 10.
Table 10. Cartographic object codes used in the RoskGeoLines table.
|
CartoObjID |
Name |
|
53 |
Null line symbol |
|
56 |
0.35pt dashed red line (24K) (Approximate fold hinge line) |
|
58 |
0.35pt solid red line (24k) (Accurate fold hinge line) |
|
63 |
1.75pt dotted black line (24K) (Concealed fault) |
|
66 |
0.5pt solid black line with perpendicular hashes (24K) (Dike symbol) |
|
69 |
0.5pt solid black line with spaced X's (24K) (Dike symbol) |
|
70 |
0.5pt solid black line with open circles (24K) (Vein symbol) |
|
72 |
0.5pt black line with dash-dot-dot pattern (24K) (Marker bed) |
|
73 |
0.35pt dotted red line (24K) (Concealed fold hinge line) |
|
74 |
0.5pt solid black line with alternating slashes (24K) (Dike symbol) |
· CartoObjDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by CartoObjID. Domain: 21 = the DataSetID for the CartographicObject table.
· Label: Character, width 50. This field, when used, contains strings that identify line features that have a label associated with them, as in the case of dikes that are associated with a particular geologic map unit. Domain: Free text.
· Name: Character, width 255. This field contains strings that identify the default classification of each type of line and is included for simplification purposes. Features not shown on the default map visualization are indicated here as being hidden. Domain: Free text.
CARTOGRAPHIC SHAPEFILES
The ArcView shapefiles below contain the cartographic elements for the
default map visualization for DI-19. These shapefiles, and the user-defined
features included in their feature attribute tables, are summarized in Table
11.
Because the locations of points and lines in these shapefiles are chosen to
provide cartographic clarity, the Accuracy and CConf fields are
irrelevant and therefore not included.
Table 11. Summary of cartographic shapefiles showing fields, field definitions, and associated database tables. The ObjectID field, along with the DataSetID field, is the compound primary key for each shapefile. If a field joins to a lookup table, the table is shown adjacent to that field in the last column.
|
Shapefile Name |
Type |
Field Name |
Data Type |
Width |
Lookup Tables |
|
||||||
|
|
Line |
ObjectID DataSetID TrackingID TrackingDS ConceptID ConceptDS CartoObjID CartoObjDS Name |
Integer Integer Integer Integer Integer Integer Integer Integer Character |
16 16 16 16 16 16 16 16 255 |
|
||||||
|
|
Point |
ObjectID DataSetID TrackingID TrackingDS ConceptID ConceptDS CartoObjID CartoObjDS Label Rotate Name |
Integer Integer Integer Integer Integer Integer Integer Integer Character Integer Character |
16 16 16 16 16 16 16 16 50 4 255 |
|
||||||
Roskruge Cartographic Lines Shapefile
The RoskCartoLines shapefile contains the cartographic lines
(text lead-in lines...) used in the default map visualization. The location of
these lines has no geologic significance.
Arc Attributes
· ObjectID: Integer, width 16. Compound primary key. This field contains an integer value that uniquely identifies each feature in the RoskCartoLines line shapefile. Each feature has a different value. Domain: >0 and <1016, no duplicates.
· DataSetID: Integer, width 16. Compound primary key. This field contains an integer value that uniquely identifies the RoskCartoLines line shapefile. All features in the dataset have the same value. Domain: 425 = the DataSetID for this table in the DataSetAZ dataset.
· TrackingID: Integer, width 16. This field contains an integer value that uniquely identifies the origin tracking for each object. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID. Domain: 18 = the DataSetID for the TrackingRecord table.
· ConceptID: Integer, width 16. This field contains an integer value that specifies the classification concept used to identify the kind of spatial feature represented by this record. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: 2396 = Text lead-in line; 2419 = Cross Section Surface trace.
· ConceptDS: Integer, width 16. This field contains an integer value that identifies the dataset that contains the data object identified by ConceptID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· CartoObjID: Integer, width 16. This field contains an integer value that identifies the cartographic symbolization for each spatial object on the default map visualization. It is a foreign key that links to the CartoObjID field of the CartographicObject table in the RoskrugeWaterman database. Domain: 53 = Null line symbol; 57 = 0.35pt solid black line (24K).
· CartoObjDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by CartoObjID. Domain: 21 = the DataSetID for the CartographicObject table.
· Label: Character, width 50. This field, when used, contains strings that identify line features that have a label associated with them. Domain: Free text.
· Name: Character, width 255. This field contains strings that identify the default classification of each type of line and is included for simplification purposes. Domain: Free text.
Roskruge Cartographic Points Shapefile
The RoskCartoPnts shapefile contains the cartographic points (text labels, fault symbols, fold geometry symbols...) used in the default map visualization . The locations of these points have no direct geologic significance.
Point Attributes
· ObjectID: Integer, width 16. Compound primary key. This field contains an integer value that uniquely identifies each feature in the RoskCartoPnts point coverage. Each feature has a different value. Domain: >0 and <1016, no duplicates.
· DataSetID: Integer, width 16. Compound primary key. This field contains an integer value that uniquely identifies the RoskCartoPnts point coverage. All features in the dataset have the same value. Domain: 426 = the DataSetID for this table in the DataSetAZ dataset.
· TrackingID: Integer, width 16. This field contains an integer value that uniquely identifies the origin tracking for each object. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID. Domain: 18 = the DataSetID for the TrackingRecord table.
· ConceptID: Integer, width 16. This field contains an integer value that specifies the classification concept used to identify the kind of spatial feature represented by this record. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: See Table 12.
Table 12. Classification concept codes used in the RoskCartoPnts table.
|
ConceptID |
Name |
|
3057 |
Discrete feature point symbols |
|
3317 |
Annotation, unit label |
|
3318 |
Annotation, structural measurement label |
|
3321 |
Annotation, generic text |
· ConceptDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by ConceptID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· CartoObjID: Integer, width 16. This field contains an integer value that identifies the cartographic symbolization for each spatial object on the default map visualization. It is a foreign key that links to the CartoObjID field of the CartographicObject table in the RoskrugeWaterman database. Domain: See Table 13.
Table 13. Cartographic object codes used in the RoskCartoPnts table.
|
CartoObjID |
Name |
|
2134 |
anticline symbol |
|
2137 |
syncline symbol |
|
2169 |
normal fault symbol |
|
2177 |
plunge arrowhead |
|
2270 |
structural measurement label |
|
2270 |
unit label |
|
2271 |
dike label |
|
2271 |
generic text label |
|
2271 |
structural measurement label |
|
2271 |
unit label |
|
2272 |
dike label |
|
2272 |
generic text label |
|
2272 |
unit label |
|
2273 |
generic text label |
|
2275 |
unit label |
|
2276 |
unit label |
|
2277 |
unit label |
|
2279 |
generic text label |
· CartoObjDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by CartoObjID. Domain: 21 = the DataSetID for the CartographicObject table.
· Rotation: Integer, width 4. This field contains an integer value that specifies the rotation of the font symbol to correctly represent the azimuth of the of geologic feature displayed on the default map visualization at this point. This value is specific to the graphical environment of ArcView 3.2 using the AZGSgeo.ttf font (/support/fonts directory in the distribution package); the rotation angle is measured anticlockwise, starting from a compass azimuth of 90º, and is also dependent on the orientation of the symbol in its font definition. Domain: 0 to ±360.
· Label: Character, width 50. This field, when used, contains strings that identify point features that have a label associated with them. For text label points, the field contains strings that are equivalent to the text labels that appear on the default map visualization. Domain: Free text.
· Name: Character, width 255. This field contains a text string that identifies the default classification of each type of point and is included for simplification purposes. Domain: Free text.
ROSKRUGE-SPECIFIC DATABASE TABLES
The two lookup tables defined below contain supporting information
specific to DI-19. These tables, summarized in Table 14, are
included as a Microsoft Access database. By default, each dataset field below
references a table that is included in the Arizona Geological Survey namespace.
Table 14. Summary of project-specific Microsoft Access database tables showing fields, field definitions, and associated database tables. If a field joins to a lookup table, the table name is shown adjacent to that field in the last column.
|
Table Name |
Field Name |
Data Type |
Width |
Lookup Tables |
|
|
MapUnitID DataSetID TrackingID TrackingDS MapLabel Name Description |
Number Number Number Number Text Text Memo |
Long
Integer Long
Integer Long
Integer Long
Integer 50 255 |
|
|
|
StructMeasureID DataSetID SpObjID SpObjDS TrackingID TrackingDS Name StructMeasureTypeID StructMeasureTypeDS ConceptConfidence UTME UTMN LocErr Azimuth AzimuthErr Dip DipErr DipDirection |
Number Number Number Number Number Number Text Number Number Text Number Number Number Number Number Number Number Text |
Long
Integer Long
Integer Long
Integer Long
Integer Long
Integer Long
Integer 255 Long
Integer Long
Integer 16 Single Single Single Single Single Single Single 16 |
|
|
|
ObjectID DataSetID SampleID SampleDS TrackingID TrackingDS Sample AnalyticalResults (13 fields) |
Number Number Number Number Number Number Text Number |
Long
Integer Long
Integer Long
Integer Long
Integer Long
Integer Long
Integer 255 Single |
|
|
|
ObjectID DataSetID ActivityID ActivityDS FieldID DataCollected UTME UTMN UTMzone SpObjID SpObjDS Area Quadrangle RockUnitID RockUnitDS MapUnit Notes TrackingID TrackingDS |
Number Number Number Number Text Date Number Number Number Number Number Text Text Number Number Text Memo Number Number |
Long
Integer Long
Integer Long
Integer Long
Integer 30 dd/mm/yy Single Single Long
Integer Long
Integer Long
Integer 255 255 Long
Integer Long
Integer 50 Long
Integer Long
Integer |
|
|
|
ObjectID DataSetID SampleID SampleDS TrackingID TrackingDS Sample AnalyticalResults (20 fields) |
Number Number Number Number Number Number Text Number |
Long
Integer Long
Integer Long
Integer Long
Integer Long
Integer Long
Integer 255 Single |
|
Map Unit Table
The MapUnits table defines the map units used to classify polygons in the Roskruge Geology coverage.
Database Table Fields
· MapUnitID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each geologic map unit in the MapUnits dataset. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the MapUnits dataset. Domain: 427 = the DataSetID for this table in the DataSetAZ dataset.
· TrackingID: Integer, width 16. This field contains an integer value that uniquely identifies the origin tracking for each record. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID. Domain: 18 = the DataSetID for the TrackingRecord table.
· OriginDate: Date/Time, short date. This field contains a date value, in the mm/dd/yy format, that records when the record was created. This information provides more detailed information on the time that records were originally entered, supplementing the information in the associated TrackingRecord table. Domain: Valid date.
·
MapLabel: Text, width 25. This field contains
strings used to label polygons on the default geologic map visualization. These
map labels do not necessarily correspond to the map labels in the Label
field of the RoskGeo.pat table for the
polygon that contains the point. This is because some generalization of the
geology has been made for the default visualization, and because labels may be
located outside of the polygon they identify. Map labels with Tertiary,
Pennsylvanian, Precambrian, Cambrian, Paleozoic, or Mesozoic geologic age
prefixes are shown using their corresponding special font symbols included in
the AZGSArial True Type font (/support/fonts/ Azgsa___.ttf). When shown in the
default ArcView font, as in ArcView tables, these prefixes map to the following
characters: _files/image013.jpg){kind=small}
= ² (Alt-0178) ; _files/image014.jpg){kind=small}
= ³ (Alt-0179); _files/image015.jpg){kind=small}
= ¹ (Alt-0185); _files/image016.jpg){kind=small}
= º (Alt-0186); _files/image017.jpg){kind=small}
= ¼ (Alt-0188); and _files/image018.jpg){kind=small}
= ¾ (Alt-0190). Domain: Limited to the map labels on the original
source maps.
· Name: Text, width 255. This field contains a text string that identifies the map unit name or rock type. Domain: Free text.
· Description: Memo. This field contains a full description of the rock unit. Domain: Free text.
Roskruge Structural Measurement Data Table
The StructureDataRoskruge table contains values that define the
orientation of structural features. The inclusion of both the UTM coordinates
for the station location and a link to a spatial object representing the
station location is redundant, but both forms of location are included for
reliability. If the link with the spatial object data set is corrupted, the StructureDataRoskruge
table still contains sufficient information to locate the station. Likewise,
the StructureDataRoskruge table can be exported for data exchange
without including a data set with location spatial objects. A separate
correlation table to link stations with locations is unnecessary because each
station has a unique location.
Database Table Fields
· StructMeasureID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each structural measurement in the StructureDataRoskruge table. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the StructureDataRoskruge table. Domain: 429 = the DataSetID for this table in the DataSetAZ dataset.
· SpObjID: Number, long integer. This field contains an integer value that uniquely identifies a field station record in an associated point coverage. It is a foreign key that joins with the ObjectID field of the RoskPnt point coverage. Domain: >0 and <1016, but limited to the values in the ObjectID field of the associated point datasets.
· SpObjDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by SpObjID. Domain: 424 = the DataSetID for the RoskPnt point coverage.
· TrackingID: Number, long integer. This field contains an integer value that uniquely identifies the origin tracking for each record. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID. Domain: 18 = the DataSetID for the TrackingRecord table.
· Name: Text, width 255. This field contains a text string that provides a descriptive name for each type of structural measurement. Domain: Free text.
· StructMeasureTypeID: Number, long integer. This field contains an integer value that classifies the geologic concept for each structural measurement. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: See Table 15.
Table 15. Structural measurement type codes used in the StructureDataRoskruge table.
|
StructMeasureTypeID |
Name |
|
42 |
Close disjunct cleavage |
|
543 |
Flow foliation |
|
544 |
Eutaxitic foliation |
|
546 |
Foliation, generic |
|
555 |
Joints |
|
559 |
Well developed s-tectonite |
|
563 |
Cleavage parallel to bedding |
|
567 |
Minor fault surface |
|
572 |
Lineation, generic tectonic |
|
581 |
Fold hinge, anticline |
|
588 |
Orientation, fault surface |
|
762 |
Bedding, crude or indistinct |
|
768 |
Bedding, planar parallel |
|
3324 |
Bedding, planar parallel, w/tops |
|
3326 |
Bedding, contorted or variable |
|
3329 |
Fold hinge, syncline |
· StructMeasureTypeDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by StructMeasureTypeID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· ConceptConfidence: Text, width 16. This field contains a text string that subjectively describes the accuracy for the classification of this object. Domain: ‘low’, ‘standard’, or ‘high’.
· UTME: Number, single. This field contains a positive real number that reflects the UTM easting coordinate (X-value), in meters, for the location of the structural measurement. Domain: >0 and <108.
· UTMN: Number, single. This field contains a positive real number that reflects the UTM northing coordinate (Y-value), in meters, for the location of the structural measurement. Domain: >0 and <108.
· LocErr: Number, single. This field contains a real number that records the location error, in meters, for the UTM coordinates. Domain: >0 and <108.
· Azimuth: Number, single. This field contains a positive real number that records the trend or strike of a structural feature in degrees. For planar surfaces, the measurement is recorded using the right-hand rule (i.e. the measurement is made such that the down-dip direction is to the right when facing in the azimuth direction). The magnitude of the angle is measured clockwise starting from a compass azimuth of 0º. Domain: >0 to <360
· AzimuthErr: Number, single. This field contains a real number that records the uncertainty, in degrees, associated with an azimuth measurement. For example, an AzimuthErr of 5 for an Azimuth of 127 would indicate that the azimuth actually falls within the range from 122 to 132 degrees. Domain: >0 and <108.
· Dip: Number, single. This field contains a positive real number that records the angle between a planar or linear feature and horizontal (degrees). The angle is measured in the vertical plane perpendicular to strike for planar features and parallel to trend for linear features. The dip angle here measures total rotation rather than the conventional inclination measurement. For overturned beds this results in dips >90º. This allows conceptually consistent representation of the dip of upright, overturned, or doubly overturned structures. Overturned beds have 90 < dip <=180. Doubly overturned beds have dip >180. Domain: ≥0.
· DipErr: Number, single. This field contains a real number that records the uncertainty, in degrees, associated with a dip measurement. For example, a DipErr of 3 for a Dip of 29 would indicate that the dip actually falls within the range from 26 to 32 degrees. Domain: >0 and <108.
· DipDirection: Text, width 2. This field contains a dip direction modifier, based on compass directions, that may be used as a redundant check for structural measurements recorded using the right-hand rule. Domain: N, NE, E, SE, S, SW, W, NW.
MajorConstituents
The MajorConstituents table contains whole rock chemical analyses for samples listed in the Samples table.
Database Table Fields
· ObjectID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each record in the MajorConstituents table. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. Compound primary key. This field contains a value of –1 because this dataset is unique to the RoskrugeWaterman database. A system for representing of chemical analyses is still under development at the AZGS.
· SampleID: Number, long integer. Foreign key to the Samples table. This field contains an integer value that identifies the rock sample that was analyzed to produce the data in this record. Domain: >0 and <1016, no duplicates.
· SampleDS: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the Samples table. Domain: 430 = the DataSetID for this table in the DataSetAZ dataset.
· TrackingID: Number, long integer. This field contains an integer value that uniquely identifies the origin tracking for each record. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID. Domain: 18 = the DataSetID for the TrackingRecord table.
· Sample: Text, width 30. This field contains a text string that records the sample identifier assigned to the rock collected in the field by the original collector.
· Analytical results: Number, real, single precision. Weight per cent fractions for the following constituents: SiO2, TiO2, Al2O3, Fe2O3 (Total), MnO, MgO, CaO, K2O, Na2O, P2O5, LOI, and Total. Also includes ppm Ba.
Samples
The Samples table contains location and description information for rock samples submitted for chemical analyses reported in the MajorConstituents and TraceElements tables. The inclusion of both the UTM coordinates for the sample location and a link to a spatial object representing the sample location is redundant, but both forms of location are included for reliability. If the link with the spatial object data set is corrupted, the Samples table still contains sufficient information to locate the sample. Likewise, the sample table can be exported for data exchange without including a data set with location spatial objects.
Database Table Fields
· ObjectID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each record in the Samples table. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the Samples table. Domain: 430 = the DataSetID for this table in the DataSetAZ dataset.
· ActivityID: Number, long integer. Compound primary key. This field contains an integer value that identifies the Activity for collection of the sample. Activities for sample collection should indicate the person who collected the sample. Domain: >0 and <1016, no duplicates.
· ActivityDS: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the Activities dataset. Domain: 2 = the DataSetID for the Activities table.
· FieldID: Text, width 30. This field contains a text string that records the sample identifier assigned to the rock collected in the field by the original collector.
· DateCollected: Date. Date sample was collected.
· UTME: Number, real, single precision. UTM easting coordinate for sample location. Domain: 122000 < UTME < 700000.
· UTMN: Number, real, single precision. UTM northing coordinate for sample location. Domain: 3420000 < UTMN < 4110000.
· UTMzone: Number, long integer. Zone number for UTM coordinates. Domain: 11 or 12 for the State of Arizona.
· SpObjID: Number, long integer. This field contains an integer value that uniquely identifies the field station record in an associated point coverage where the sample was collected. It is a foreign key that joins with the ObjectID field of the RoskPnt point coverage. Domain: >0 and <1016, but limited to the values in the ObjectID field of the associated point datasets.
· SpObjDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by SpObjID. Domain: 424 = the DataSetID for the RoskPnt point coverage.
· Area: Text, width 64. Geographic area name from Arizona Geological Survey Place Names list. Domain: Place names included in Trapp and Reynolds [1998]
· Quadrangle: Text, width 64. Name of USGS 7½ minute quadrangle that contains the sample location. Domain: USGS 7½ Quadrangle names.
· RockUnitID: Number, long integer. This field contains an integer value that uniquely identifies the geologic map unit in the MapUnits dataset from which the sample was collected. Domain: >0 and <1016, no duplicates.
· RockUnitDS: Number, long integer. This field contains an integer value that uniquely identifies the MapUnits dataset. Domain: 427 = the DataSetID for the MapUnits dataset in the DataSetAZ dataset.
·
MapUnit: Text, width 32. Abbreviation for map
unit from which sample was collected that is used on the default map visualization
for the RoskrugeWaterman database. Domain: Map unit labels used in RoskrugeWaterman
database.
·
Notes: Memo. Free text notes on sample.
· TrackingID: Number, long integer. This field contains an integer value that uniquely identifies the origin tracking for each record. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID. Domain: 18 = the DataSetID for the TrackingRecord table.
TraceElements
The TraceElements table contains trace element analyses for samples listed in the Samples table. Twenty trace elements are reported.
Database Table Fields
· ObjectID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each record in the TraceElements table. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. Compound primary key. This field contains a value of –1 because this dataset is unique to the RoskrugeWaterman database. A system for representing of chemical analyses is still under development at the AZGS.
· SampleID: Number, long integer. Foreign key to the Samples table. This field contains an integer value that identifies the rock sample that was analyzed to produce the data in this record. Domain: >0 and <1016, no duplicates.
· SampleDS: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the Samples table. Domain: 430 = the DataSetID for this table in the DataSetAZ dataset.
· TrackingID: Number, long integer. This field contains an integer value that uniquely identifies the origin tracking for each record. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID. Domain: 18 = the DataSetID for the TrackingRecord table.
· Sample: Text, width 30. This field contains a text string that records the sample identifier assigned to the rock collected in the field by the original collector.
· Analytical results: Number, real, single precision. Parts per million (ppm) analyses (except as noted) for the following elements: Sr, Rb, Th, Pb, Ga, Zn, Cu, Ni, Fe203 (wt. %), MnO (wt %), Cr, TiO2 (wt. %), Ba, V, As, U, Y, Zr, Nb, Mo.
ARIZONA GEOLOGIC DATA SYSTEM TABLES
The lookup tables defined below contain the supporting data that
complete the geographic database portion of DI-19. These tables, summarized in Table
16, are
included as a Microsoft Access database. By default, each dataset field below
references a table that is included in the Arizona Geological Survey namespace.
Table 16. Summary of general Microsoft Access database tables showing fields, field definitions, and associated database tables. If a field joins to a lookup table, the table name is shown adjacent to that field in the last column.
|
Table Name |
Field Name |
Data Type |
Field Size |
Lookup Tables |
|
Refnum Cite |
Number Text |
Long Integer 255 |
AzGeoBib [Trapp et al.,
1996] |
|
|
|
ActivityID DataSetID Name PersonOrgID PersonOrgDS ProjectID ProjectDS Comment |
Number Number Text Number Number Number Number Memo |
Long Integer Long Integer 255 Long Integer Long Integer Long Integer Long Integer |
|
|
|
CartoObjID DataSetID Sequence TrackingID TrackingDS Name CartoObjTypeID CartoObjTypeDS GraObjID GraObjDS ColorID ColorDS OriginDate Comment |
Number Number Number Number Number Text Number Number Number Number Number Number Date/Time Memo |
Long Integer Long Integer Integer Long Integer Long Integer 255 Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Short Date |
|
|
|
ConceptID DataSetID TrackingID TrackingDS Name ParentID ParentDS OriginDate Definition |
Number Number Number Number Text Number Number Date/Time Memo |
Long Integer Long Integer Long Integer Long Integer 255 Long Integer Long Integer Short Date |
|
|
|
ColorID DataSetID Name CMYK RGB R G B |
Number Number Text Text Text Number Number Number |
Long Integer Long Integer 255 25 25 Integer Integer Integer |
|
|
|
DataSetID NameSpace NameSpaceID NameSpaceDS DataSetName DataSetTypeID DataSetTypeDS DataSetSubjectID DataSetSubjectDS TrackingID TrackingDS SourceFileTypeID SourceFileTypeDS PhysicalAddressTypeID PhysicalAddressTypeDS PhysicalAddress IdentifierFieldName DataSetFieldName Comment |
Number Text Number Number Text Number Number Number Number Number Number Number Number Number Number Text Text Text Memo |
Long Integer 50 Long Integer Long Integer 255 Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer 255 50 50 |
|
|
|
GraObjID DataSetID Name Width Scale Pattern |
Number Number Text Number Number Text |
Long Integer Long Integer 255 Single Long Integer 50 |
|
|
|
GraObjID DataSetID Name SymbolID SymbolDS Spacing Scale Pattern Offset |
Number Number Text Number Number Number Number Text Number |
Long Integer Long Integer 255 Long Integer Long Integer Single Long Integer 50 Single |
|
|
|
GraObjID DataSetID Name PatternID PatternDS Scale Rotation |
Number Number Text Number Number Number Number |
Long Integer Long Integer 255 Long Integer Long Integer Long Integer Integer |
|
|
|
GraObjID DataSetID FontName Style Spacing Alignment Size Scale ColorID ColorDS |
Number Number Text Text Number Text Number Number Number Number |
Long Integer Long Integer 25 16 Single 25 Single Long Integer Long Integer Long Integer |
|
|
|
RelationshipID DataSetID HierarchyTypeID HierarchyTypeDS ParentID ParentDS ChildID ChildDS TrackingID TrackingDS |
Number Number Number Number Number Number Number Number Number Number |
Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer |
|
|
|
MetadataRelationshipID DataSetID RelTypeID RelTypeDS FirstRoleID FirstRoleDS SecondRoleID SecondRoleDS TrackingID TrackingDS Comment |
Number Number Number Number Number Number Number Number Number Number Memo |
Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer Long Integer |
|
|
(not included in this database) |
|
|
|
|
|
(not included in this database) |
|
|
|
|
|
(not included in this database) |
|
|
|
|
|
|
TrackingID DataSetID TrackingRecordTypeID TrackingRecordTypeDS Name LogDate ActivityID ActivityDS DataProcMethodID DataProcMethodDS Description |
Number Number Number Number Text Date/Time Number Number Number Number Memo |
Long Integer Long Integer Long Integer Long Integer 255 Short Date Long Integer Long Integer Long Integer Long Integer |
|
Bibliographic Citations Table (_AzGeoBibCite)
The _AzGeoBibCite table is derived from the Arizona Geological Survey bibliographic data base (AzGeoBib, Trapp et al. [1996], DataSetID = 4 in the DataSetAZ table), and provides a mechanism for citing published literature. In this database citations are related to tracking records through the MetadataRelationship table. This derivative table is included to replace links to the full AzGeoBib database.
Database Table Fields
· RefNum: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each citation in the _AzGeoBibCite table. Domain: >0 and <1016, no duplicates. The identifiers used here are the same as identifiers for the citation in AzGeoBib.
· Cite: Text, length 255. A text citation in standard bibliographic format (author, date, title, citation).
Activities Table
The Activities table is a link to an activity responsible
for update of, or addition to, the database. An activity is a particular
person, working for a particular organization, under the auspices of a particular
project.
Database Table Fields
· ActivityID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each activity in the Activities table. Domain: >0 and <1016, no duplicates.
· DatasetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the Activities dataset. Domain: 2 = the DataSetID for the Activities table.
· Name: Text, width 255. This field contains a descriptive string that provides a unique name identifier for each activity. This is the string the is displayed in combo boxes on data entry forms. Domain: Free text.
· PersonOrgID: Number, long integer. This field contains an integer value that uniquely identifies the person and the organization that are associated with each activity. It is a foreign key that links to the PersonOrgID field of the PersonOrg table in the RoskrugeWaterman database (the PersonOrg table is not included with this database, but the PersonOrgID field is included for future compatibility). Domain: See Table 17.
Table 17. PersonOrg codes used in Tracking Records in this database
|
PersonOrgID |
DataSetID |
PersonName |
Organization |
|
1 |
15 |
Dr. Stephen M. Richard |
Arizona Geological Survey |
|
2 |
15 |
Mr. Tim R. Orr |
Arizona Geological Survey |
|
4 |
15 |
Mr. Null N Null |
None |
|
5 |
15 |
Mr. Jason . Brander |
Bureau of Land Management |
|
11 |
15 |
Dr. Philip A. Pearthree |
Arizona Geological Survey |
|
12 |
15 |
Ms. Ann . Youberg |
Arizona Geological Survey |
|
13 |
15 |
Mr. Ray C. Harris |
Arizona Geological Survey |
· PersonOrgDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by PersonOrgID. Domain: 15 = the DataSetID for the PersonOrg link table.
· ProjectID: Number, long integer. This field contains an integer value that identifies the project associated with each activity. It is a foreign key that links to the ProjectID field of the Projects table in the RoskrugeWaterman database (the Projects table is not included with this database, but the ProjectID field is included for future compatibility). Domain: See Table 18.
Table 18. ProjectID codes used in tracking records for this database
|
ProjectID |
ProjectDS |
Project_title |
Prj_comment |
|
1 |
17 |
Arizona NADM implementation development |
Develop NADM 5.2 implementation and use for new geologic map of Arizona database |
|
2 |
17 |
DI-8 Version 3 database development |
Construct NADM-compliant database with geologic data compiled for Map 35. |
|
3 |
17 |
Phoenix N, East Half Database development |
Activities related to development of databases for east half of Phoenix North 30 by 60 minute quadrangle |
|
4 |
17 |
Null |
No project assigned |
|
5 |
17 |
Digitize Geologic Map of Arizona, using MOSS |
get 1:1,000,000 scale geologic map in digital form to assist management decisions |
|
8 |
17 |
Edit Map 26 Data to release as DI8 V.1 |
Get original MOSS version converted to ARC and into a form that could be released |
|
10 |
17 |
Statemap 1999, Waterman Peak 1:24000 quad |
Generate Statemap deliverable, geologic map of Waterman Peak quad |
|
11 |
17 |
TheodoreRoosevelt100KGISV2 |
Generate final, complete 100K geology GIS for Theodore Roosevelt Lake 100K quad. |
|
13 |
17 |
Statemap 1999 Surficial |
Surficial Geologic maps of Avra Valley and Green Valley areas |
|
16 |
17 |
AZ Geologic Map Index database conversion |
conversion of DI-9 (AZ Map Index) to new AZ_NADM datastructure |
|
17 |
17 |
Statemap2000PhxDatabases |
Project to complete 1:24k GIS databases for quads in phoenix area; includes preliminary development work on Waterman-Roskruge database also funded by this project |
|
20 |
17 |
Statemap 1999, Roskruge/Waterman Digital Data |
Digital geologic information for the Roskruge and Waterman Mountains |
· ProjectDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by ProjectID. Domain: 17 = the DataSetID for the Projects table.
· Comment: Memo. This field contains descriptive text about each activity, including the name of the person who conducted the activity, their employing organization, and the project they were working on. Domain: Free text.
Cartographic Object Table
The CartographicObject table is an implementation-independent
representation of symbols used to display points, lines, polygons, and text on
map visualization. This is done by defining links to tables that provide
implementation-dependent descriptions of graphical objects used for
symbolization. Graphical object tables in this database are designed to
describe symbology for ArcView 3.2 running in a Microsoft Windows environment.
Individual cartographic objects may consist of several graphical objects
stacked according to the sequence attribute in the table, with the lowest
sequence symbol overlain by subsequent symbols in the sequence.
Database Table Fields
· CartoObjID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each cartographic object in the CartographicObject table. Domain: >0 and <1016, no duplicates.
· DatasetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the CartographicObject dataset. Domain: 21 = the DataSetID for the CartographicObject table.
· Sequence: Number, integer. Compound primary key. This field contains an integer value that corresponds to the layer order in which graphical elements are created. For example, an ornamented line, such as a line with queries, would be created using two layers. The first layer, the line itself, would have a sequence value of 1, while the second layer, the query symbol, would have a sequence value of 2. Domain: >0 and <108.
· TrackingID: Integer, width 16. This field contains an integer value that uniquely identifies the origin tracking for each record. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID. Domain: 18 = the DataSetID for the TrackingRecord table.
· Name: Text, width 255. This field contains a text string that uniquely identifies and describes each cartographic object and is included for intelligibility. Domain: Free text.
· CartoObjTypeID: Number, long integer. This field contains an integer value that classifies the graphical element type. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: See Table 19.
Table 19. Cartographic object type codes used in the CartographicObject table.
|
CartoObjTypeID |
Name |
|
1957 |
Cartographic Object -- point |
|
1958 |
Cartographic Object -- line |
|
2392 |
Point symbol from font |
|
2393 |
Annotation at point |
|
2408 |
Fill, solid |
|
2409 |
Fill, pattern |
|
3019 |
Line, solid |
|
3020 |
Line symbol, dash-dot pattern |
|
3021 |
Line symbol, ornamented |
· CartoObjTypeDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by CartoObjTypeID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· GraObjID: Number, long integer. This field contains an integer value that corresponds to a specific graphical element. It is a foreign key that links to the GraObjID field of either the GraphicLine table, the GraphicLineOrnamented table, the GraphicPattern table, or the GraphicTextFormat table in the RoskrugeWaterman database. Domain: See Table 20.
Table 20. Graphic object codes used in the CartographicObject table.
|
GraObjID |
GraObjDS |
Name |
|
11 |
26 |
thick line (1.5 pt), solid |
|
3 |
26 |
medium thin line (0.35 pt), standard short dash |
|
4 |
26 |
medium thin line (0.35 pt), solid |
|
5 |
26 |
medium line (0.5 pt), standard short dash |
|
6 |
26 |
medium line (0.5 pt), solid |
|
7 |
26 |
medium line (0.5 pt), dash-dot |
|
18 |
26 |
medium thin line (0.35 pt), dotted |
|
14 |
26 |
thick line(1.75 pt), dotted |
|
10 |
26 |
thick line (1.5 pt), standard medium dash |
|
13 |
26 |
very thick line (2.5 pt), solid |
|
19 |
26 |
medium line (0.5 pt), dash-dot-dot |
|
20 |
26 |
medium line (0.75 pt), dotted |
|
14 |
411 |
cross hatch, lines at 30° 90° and 150°, separation = 4 pt. |
|
33 |
411 |
vertical hatch, separation = 1 pt. |
|
13 |
411 |
cross hatch, lines at 0° and 90°, separation = 4 pt. |
|
0 |
411 |
Null Pattern |
|
12 |
411 |
cross hatch, lines at 0° and 90°, separation = 3.25 pt. |
|
15 |
411 |
cross hatch, lines at 45° and 135°, separation = 2 pt. |
|
10 |
411 |
cross hatch, lines at 0° and 90°, separation = 2.5 pt. |
|
9 |
411 |
cross hatch, lines at 0° and 90°, separation = 2 pt. |
|
8 |
411 |
cross hatch, lines at 0° and 90°, separation = 1 pt. |
|
1 |
411 |
Solid Color Fill; scale invariant |
|
11 |
411 |
cross hatch, lines at 0° and 90°, separation = 3 pt. |
|
27 |
411 |
hatch, 60°, separation = 1 pt. |
|
32 |
411 |
horizontal hatch, separation = 3 pt. |
|
31 |
411 |
horizontal hatch, separation = 1 pt. |
|
30 |
411 |
hatch, 60°, separation = 4 pt. |
|
29 |
411 |
hatch, 60°, separation = 2.5 pt. |
|
28 |
411 |
hatch, 60°, separation = 1.75 pt. |
|
16 |
411 |
cross hatch, lines at 45° and 135°, separation = 2.5 pt. |
|
26 |
411 |
hatch, 45°, separation = 4 pt. |
|
25 |
411 |
hatch, 45°, separation = 1.75 pt. |
|
24 |
411 |
hatch, 135°, separation = 4 pt. |
|
22 |
411 |
hatch, 135°, separation = 1.75 pt. |
|
21 |
411 |
hatch, 120°, separation = 1.75 pt. |
|
20 |
411 |
cross hatch, lines at 60° and 120°, separation = 4 pt. |
|
17 |
411 |
cross hatch, lines at 45° and 135°, separation = 3 pt. |
|
18 |
411 |
cross hatch, lines at 45° and 135°, separation = 3.25 pt. |
|
19 |
411 |
cross hatch, lines at 60° and 120°, separation = 2 pt. |
|
23 |
411 |
hatch, 135°, separation = 3.25 pt. |
|
5 |
412 |
Open circle |
|
1 |
412 |
Solid triangle |
|
2 |
412 |
Query |
|
3 |
412 |
Perpendicular hash |
|
4 |
412 |
X pattern |
|
6 |
412 |
Alternating slash |
|
6 |
420 |
Arial, Normal, Spacing: 1, JUST_LEFT, 11 point, PMS-Black |
|
3 |
420 |
Arial, Normal, Spacing: 1, JUST_LEFT, 8 point, PMS-Black |
|
12 |
420 |
AzGSArial, Normal, Spacing: 1, JUST_LEFT, 7 point, PMS-Black |
|
19 |
420 |
Arial, Bold, Spacing: 1, JUST_LEFT, 7 point, PMS-Black |
|
2 |
420 |
Arial, Normal, Spacing: 1, JUST_LEFT, 7 point, PMS-Black |
|
8 |
420 |
Arial, Normal, Spacing: 1, JUST_LEFT, 14 point, PMS-Black |
|
1 |
420 |
Arial, Normal, Spacing: 1, JUST_LEFT, 6 point, PMS-Black |
|
11 |
420 |
AzGSArial, Normal, Spacing: 1, JUST_LEFT, 6 point, PMS-Black |
|
32 |
420 |
Arial, Italic, Spacing: 1, JUST_LEFT, 12 point, PMS-Black |
|
13 |
420 |
AzGSArial, Normal, Spacing: 1, JUST_LEFT, 8 point, PMS-Black |
· GraObjDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by GraObjID. Domain: 26 = the DataSetID for the GraphicLine table; 411 = the DataSetID for the GraphicPattern table; 412 = the DataSetID for the GraphicLineOrnamentated table; 420 = the DataSetID for the GraphicTextFormat table.
· ColorID: Number, long integer. This field contains an integer value that represents a specific color. It is a foreign key that links to the GraObjID field of the Color table in the RoskrugeWaterman database. Domain: Color codeset – RoskrugeWaterman database.
· ColorDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by ColorID. Domain: 23 = the DataSetID for the Color table.
· OriginDate: Date/Time, short date. This field contains a date value, in the mm/dd/yy format, that records when the record was created. This information provides more detailed information on the time that records were originally entered, supplementing the information in the associated TrackingRecord table. Domain: Valid date.
· Comment: Memo. This field contains text that provides additional descriptive information about a record. Domain: Free text.
Classification Concept Table
The ClassificationConcept table is a collection of terminology definitions—a term with a
definition. These terms are used to classify other objects in all parts of the
database. Each concept is identified by its unique identifier (ConceptID -
DatasetID pair). Thus the name of the concept may be changed without
updating other links.
Database Table Fields
· ConceptID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each classification object in the ClassificationConcept table. Domain: >0 and <1016, no duplicates.
· DatasetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the ClassificationConcept dataset. Domain: 1 = the DataSetID for the ClassificationConcept table.
· TrackingID: Integer, width 16. This field contains an integer value that uniquely identifies the origin tracking for each record. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Integer, width 16. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID. Domain: 18 = the DataSetID for the TrackingRecord table.
· Name: Text, width 255. This field contains a text string that provides a descriptive name for each classification concept. Domain: Free text.
· ParentID: Number, long integer. This field contains an integer value that represents the concept type. Semantically this is equivalent to the parent of the concept and the links between classification concepts and parent concepts defines the classification concept hierarchy. This hierarchy is represented by the HierarchyRelationship table for use in general database queries. Inclusion of this attribute with each classification concept facilitates management of a single, simple tree hierarchy for classification concepts, but future development may allow a more complex concept hierarchy with multiple parent links. The ParentID is a foreign key that links to the ConceptID field in this same table. Domain: ClassificationConcept codeset – RoskrugeWaterman database.
· ParentDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by ConceptTypeID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· OriginDate: Date/Time, short date. This field contains a date value, in the mm/dd/yy format, that records when the record was created. This information provides more detailed information on the time that records were originally entered, supplementing the information in the associated TrackingRecord table. Domain: Valid date.
· Definition: Text, width 255. This field contains a text string that defines each classification concept. Domain: Free text.
Color Table
The Color table defines RGB values for colors used in the
default symbolization. The RGB values were derived from the Pantone® [Pantone®,
Inc., 1991] color swatch library in Adobe Illustrator®, and represent red,
green, and blue values that approximate Pantone® colors for onscreen viewing.
Database Table Fields
· ColorID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each color in the Color table. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the Color dataset. Domain: 23 = the DataSetID for this table in the DataSetAZ dataset.
· Name: Text, width 255. This field contains a text string that uniquely identifies each color by Pantone® name (PMS-466), or by a string concatenated from a color description and the RGB values for that color (Blue (R39,G146,B182)). Domain: Pantone color names from the Pantone® [Pantone®, Inc., 1991] color swatch library, or free text.
· CMYK: Text, width 25. This optional field contains a string concatenated from the CMYK color values for a particular color. Domain: A sequence of four numbers each consisting of three integers ranging from 0 to 255.
· RGB: Text, width 25. This optional field contains a string concatenated from the RGB color values for a particular color. Domain: A sequence of three numbers each consisting of three integers ranging from 0 to 255.
· R: Number, integer. This field contains an integer value that represents the red color intensity for the screen display of a particular color. Domain: An integer from 0 to 255.
· G: Number, integer. This field contains an integer value that represents the green color intensity for the screen display of a particular color. Domain: An integer from 0 to 255.
· B: Number, integer. This field contains an integer value that represents the blue color intensity for the screen display of a particular color. Domain: An integer from 0 to 255.
DataSetAZ Table
The DataSetAZ table identifies each dataset included in, or
referenced by, the RoskrugeWaterman database. A dataset is any
collection of data that is held in an individual file or table. Examples
include individual Arc/Info coverages, ESRI shape files, tables in Microsoft
Access databases, dBase tables in individual .dbf files, and files containing
images (e.g. tiff, jpeg). The contents of the DataSetAZ table define the
‘Arizona Geological Survey’ namespace.
Database Table Fields
· DataSetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each dataset in the DataSetAz table. Domain: >0 and <1016, no duplicates.
· NameSpace: Text, width 50. Compound primary key. This field contains a text string that identifies the agency or organization that owns or maintains the dataset. Domain: ‘Arizona Geological Survey’.
· NameSpaceID: Number, long integer. This field contains an integer value that classifies the NameSpace for each dataset record in the DataSetAz dataset. There is a 1:1 correspondence between values in this field and values in the NameSpace field, i.e. they are redundant. Both a string value and an numeric value are included to facilitate implementation using the convention adopted for this database system that a data object within a particular namespace is identified by a compound primary key consisting of 2 long integers. NameSpaceID is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: 2541 = the ConceptID for the “Arizona Geological Survey” namespace.
· NameSpaceDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by NameSpaceID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· DataSetName: Text, width 255. This field contains a text string that uniquely identifies each dataset. Domain: Free text.
· DataSetTypeID: Number, long integer. This field contains an integer value that classifies each dataset according to a dataset type from the ClassificationConcept table. The dataset type identifies the physical data structure of the dataset (e.g. ArcInfo coverage, Microsoft Access table….). It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: See Table 21.
Table 21. Dataset type codes used in the DataSetAZ table.
|
DataSetTypeID |
Name |
|
2744 |
Classification/Description/Definition
Dataset |
|
2761 |
Generic
Attributed Relationship Dataset |
|
2762 |
Description
Container Dataset |
|
2794 |
Geographic
Dataset |
· DataSetTypeDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by DataSetTypeID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· DataSetSubjectID: Number, long integer. This field contains an integer value that classifies each dataset according to a subject classification term. The subject classification term identifies the domain of interest for the data in the dataset. In future implementations, the dataset subject will be used for error and consistency checking. A more complete key word index for datasets would need to be implemented through a correlation table allowing a many-to-many join between datasets and subjects. The DataSetSubjectID is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: See Table 22.
Table 22. Dataset subject codes used in the DataSetAZ table.
|
DataSetSubjectID |
Name |
|
2759 |
NADM
Implementation Infrastructure |
|
2767 |
AZ
Cordlink base table |
|
3306 |
Graphic
Definition Tables |
|
3336 |
Roskruge
and Waterman Mountains and western Avra Valley |
· DataSetSubjectDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by DataSetSubjectID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· TrackingID: Number, long integer. This field contains an integer value that uniquely identifies the origin tracking for each record. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID for each record. Domain: 18 = the DataSetID for the TrackingRecord table.
· SourceFileTypeID: Number, long integer. This field contains an integer value that classifies each dataset by its physical file type or format. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: See Table 23.
Table 23. Source file type codes used in the DataSetAZ table.
|
SourceFileTypeID |
Name |
|
2542 |
MicroSoft
Access Database Table |
|
2543 |
dBase
Table |
|
2544 |
ESRI
coverage, point |
|
2545 |
ESRI
coverage, arc |
|
2547 |
ESRI
coverage, polygon |
|
2548 |
AV
shape file, point |
|
2549 |
AV
shape file, line |
· SourceFileTypeDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by SourceFileTypeID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· PhysicalAddressTypeID: Number, long integer. This field contains an integer value that classifies the type of physical address that records where each dataset is stored. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: 2726 = DOS-style path name; 2727 = Microsoft Network file path name.
· PhysicalAddressTypeDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by PhysicalAddressTypeID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· PhysicalAddress: Text, width 255. This field contains a text string that identifies the actual physical location of the dataset. Domain: Free text restricted to formats defined by PhysicalAddressTypeID.
· IdentifierFieldName: Text, width 50. This field contains a string that records the name of the field in the DataSet that contains the identifier component of the compound unique identifier for each record. Domain: Restricted to the indexed, primary key field names. This is typically the first field in each dataset, and the field name is typically the table name or an object type name with “ID" appended. Identifier field names always end with the string “ID".
· DataSetFieldName: Text, width 50. This field contains a string that records the name of the field in the DataSet that contains the dataset component of the compound unique identifier for each record. Domain: “CovID”, “DataSetID”, “Namespace”. This is typically the second field in each dataset.
· Comment: Memo. This field contains text that provides additional descriptive information about each dataset. Domain: Free text.
Graphic Line Table
The GraphicLine table contains descriptions of the graphical elements used to symbolize lines. This description is implementation dependent, and is based on attributes used to define line symbols in ArcView 3.2 and Adobe Illustrator.
Database Table Fields
· GraObjID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each line in the GraphicLine dataset. Domain: >0 and <1016, no duplicates.
· DatasetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the GraphicLine dataset. Domain: 26 = the DataSetID for this table in the DataSetAZ dataset.
· Name: Text, width 255. This field contains a descriptive text string that uniquely identifies each type of line and is included for simplification purposes. Domain: Free text.
· Width: Number, single. This field contains a positive real number that specifies line thickness in millimeters. Domain: >0 and <108.
· Scale: Number, long integer. This field contains an integer value that represents the denominator of the map scale at which the graphical specifications of a line are valid. For example, a map scale of 1:12,000 would be recorded as ‘12000’. Domain: >0 and <1016.
· Pattern: Text, width 50. This field contains a sequence of numbers, as a space- or comma-delimited string, that specifies the alternating solid (on) and empty (off) length of line segments, in millimeters, starting with the ‘on’ value, that are repeated to create each line pattern. For example, a string shown as ‘0.36 0.71 1.07 0.71’ defines a repeating line pattern created by a 0.36 mm line segment, followed by a 0.71 mm space, followed by a 1.07 mm line segment, and followed by another 0.71 mm space. This approximates a line with a dot-dash pattern. Domain: A string composed of a series of real numbers separated by spaces.
Graphic Line with Ornamentation Table
The GraphicLineOrnamented table contains descriptions of
symbols used to create ornamented lines (e.g. queries dashed lines, thrust
faults). This description is implementation dependent, and is based on
attributes used to define line symbols in ArcView 3.2 running in a Microsoft
Windows environment.
Database Table Fields
· GraObjID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each style of line ornamentation in the GraphicLineOrnamented dataset. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the GraphicLineOrnamented dataset. Domain: 412 = the DataSetID for this table in the DataSetAZ dataset.
· Name: Text, width 255. This field contains a descriptive text string that uniquely identifies each type of line ornamentation symbol and is included for simplification purposes. Domain: Free text.
· SymbolID: Number, long integer. This field contains an integer value that identifies the graphical object used as an ornament along a decorated line (the SymbolID field is not implemented here but is included for future compatibility). In the implementation environment for this table, these symbols are characters from a font, and SymbolID would identify the index of a symbol in the font dataset specified by SymbolDS. Domain: 0
· SymbolDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by SymbolID (the SymbolDS field is not implemented here but is included for future compatibility). In the implementation environment for this table, SymbolDS would identify a font dataset. Domain: 0.
· Spacing: Number, single. This field contains a number that specifies spacing, in millimeters, between the centers of adjacent line ornamentation symbols. Domain: >0 and <108.
· Scale: Number, long integer. This field contains an integer value that represents the denominator of the map scale at which the graphical specifications of line ornamentation is valid. For example, a map scale of 1:12,000 would be recorded as ‘12000’. Domain: >0 and <1016.
· Pattern: Text, width 50. This field contains a string that records a stream of integer draw or skip intervals. For example, ‘12’ means draw one and skip two. A leading zero, such as in ‘021’, means skip two and draw one. The interval size is dependent on ornament size (the Pattern field is not implemented here but is included for future compatibility). Domain: Free text composed of a single string of integers.
· Offset: Number, single. This field contains a real number that specifies the offset of an ornamentation symbol perpendicular to the line with which it is associated (the Offset field is not implemented here but is included for future compatibility). Domain: >0 and <108.
Graphic Pattern Table
The GraphicPattern table defines the graphical
specifications for polygon fills in the default symbolization.
Database Table Fields
· GraObjID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each polygon fill in the GraphicPattern dataset. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the GraphicPattern dataset. Domain: 411 = the DataSetID for this table in the DataSetAZ dataset.
· Name: Text, width 255. This field contains a descriptive text string that uniquely identifies each type of polygon fill pattern and is included for simplification purposes. Domain: Free text.
· PatternID: Number, long integer. This field contains an integer value that corresponds to the pattern used to create each type of polygon fill pattern. It is a foreign key that links to the GraObjID field of the PatternDefinition table in the RoskrugeWaterman database. (The PatternDefinition table is not included with this database, but the PatternID field is included for future compatibility.) Domain: 0: solid fill; -1: not defined.
· PatternDS: Number, long integer. This field contains an integer value that identifies the dataset that contains the data object identified by PatternID. Domain: 31 = the DataSetID for the PatternDefinition table.
· Scale: Number, long integer. This field contains an integer value that represents the denominator of the map scale at which the graphical specifications of each polygon fill pattern is valid. For example, a map scale of 1:12,000 would be recorded as ‘12000’. Domain: >0 and <1016.
· Rotation: Number, integer. This field contains an integer value that represents the rotation angle, in degrees, of the graphical pattern for a particular polygon fill. The magnitude of the angle is measured clockwise starting from a compass azimuth of 0º. Domain: 0 to ±360.
Graphic Text Format Table
The GraphicTextFormat table defines the font
specifications (type, style, size...) for cartographic text used in the default
symbolization. This description is implementation dependent, and is based on
attributes used to define text formatting in ArcView 3.2 running in a Microsoft
Windows environment.
Database Table Fields
· GraObjID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each type of text in the GraphicTextFormat dataset. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies the GraphicTextFormat dataset. Domain: 420 = the DataSetID for this table in the DataSetAZ dataset.
· FontName: Text, width 25. This field contains a text string that represents the name of the font used to symbolize a text object. Domain: Any valid font (requires that custom, or non-standard fonts, be distributed with the datasets they accompany). In DI-19, the FontName domain is restricted to ‘AZGSArial’ and ‘Arial’.
· Style: Text, width 16. This field contains a text string that identifies the style of the font used to symbolize a text object. Domain: ‘Normal’; ‘Bold’; ‘Italic’; ‘Bold Italic’. In DI-19, the Style domain is limited to ‘Normal’, ‘Bold’, or ‘Italic’.
· Spacing: Number, single. This field contains a number that specifies the vertical spacing between lines of text. Domain: >0 and <108.
· Alignment: Text, width 25. This field contains an ArcView-generated text string that specifies line justification. Domain: ‘TEXTCOMPOSER_JUST_RIGHT’, ‘TEXTCOMPOSER_JUST_LEFT’, ‘TEXTCOMPOSER_JUST_CENTER’. In DI-19, the Alignment domain is limited to ‘TEXTCOMPOSER_JUST_LEFT’.
· Size: Number, single. This field contains a number that defines the font size, in points, of a text object. Domain: >0 and <108.
· Scale: Number, long integer. This field contains an integer value that represents the denominator of the map scale at which the graphical specifications of a text format is valid. For example, a map scale of 1:12,000 would be recorded as ‘12000’. Domain: >0 and <1016.
· ColorID: Number, long integer. This field contains an integer value that represents a specific color. It is a foreign key that links to the ColorID field of the Color table in the RoskrugeWaterman database. Domain: Color codeset – RoskrugeWaterman database.
· ColorDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by ColorID. Domain: 23 = the DataSetID for the Color table.
Hierarchy Relationship Table
The HierarchyRelationship table represents parent-child relationships. Multiple tree hierarchies may be represented, each identified by a Hierarchy Type, a classification concept that defines the nature of the hierarchy. For implementation simplicity, a hierarchy is represented in this table as a set of links between each parent and all the child objects beneath it in the hierarchy tree (its transitive closure). The depth of any child object in the tree is determined by the number of parent object linked to it. This representation makes response to queries that require all kinds (sub types) of a thing (e.g. ‘all spatial objects’, ‘all map units’) simple to execute. Currently, each child has only one parent.
Database Table Fields
· RelationshipID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each record in the HierarchyRelationship table. Although the compound key {HierarchyTypeID, HierarchyTypeDS, ParentID, ParentDS, ChildID, ChildDS} provides a unique key, the table has a standard {ObjectID, DatasetID} key to allow a relationship to play a role in another relationship using the standard relationship tables. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. Compound primary key. This field contains an integer value that specifies the dataset that contains the data object identified by RelationshipID. Domain: 27 = the DataSetID for the HierarchyRelationship table.
· HierarchyTypeID: Number, long integer. This field contains and integer value that uniquely identifies the kind of hierarchy. This allows the HierarchyRelationship table to represent multiple concept hierarchies as well as other unrelated hierarchies. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: 2478 = ClassificationConceptHierarchy; only one hierarchy is currently represented.
· HierarchyTypeDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by HierarchyTypeID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· ParentID: Number, long integer. First part of compound foreign key that identifies the parent object in the parent-child (IsA) relationship. Because one classification concept hierarchy is the only hierarchy in this database, this field is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: ClassificationConcept codeset – RoskrugeWaterman database.
· ParentDS: Number, long integer. Second part of compound foreign key that identifies the parent object in the parent-child (IsA) relationship. This field contains an integer value that specifies the dataset that contains the data object identified by ParentID. Because one classification concept hierarchy is the only hierarchy in this database, this field has only one value. Domain: 1 = the DataSetID for the ClassificationConcept table.
· ChildID: Number, long integer. First part of compound foreign key that identifies the child object in the parent-child (IsA) relationship. Because one classification concept hierarchy is the only hierarchy in this database, this field is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: ClassificationConcept codeset – RoskrugeWaterman database.
· ChildDS: Number, long integer. Second part of compound foreign key that identifies the child object in the parent-child (IsA) relationship. This field contains an integer value that specifies the dataset that contains the data object identified by ChildID. Because one classification concept hierarchy is the only hierarchy in this database, this field has only one value. Domain: 1 = the DataSetID for the ClassificationConcept table.
· TrackingID: Number, long integer. This field contains an integer value that uniquely identifies the origin tracking for each record. It is a foreign key that links to the TrackingID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecord codeset – RoskrugeWaterman database.
· TrackingDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingID for each record. Domain: 18 = the DataSetID for the TrackingRecord table.
Metadata Relationship Table
The MetadataRelationship table is a relationship table that provides a general mechanism for semantic links between metadata instances. A relationship type identifier links to a classification concept that defines the semantics of the relationship. Constraints on kinds of objects that may play the first and second role, and the number of fillers allowed for each role, will eventually be specified by a ValidRelationshipConstraint data structure, but this part of the database is currently being revised and is not implemented here. In this database, this table is used to implement a many-to-many join between tracking records and citations. Other applications in a more developed database would include relationships like project hierarchy (large project with subprojects), organization successor (when an organization changes name), organization aggregation (to represent individual departments as part of a larger organization), StartDate and EndDate links between Person-Organization affiliations and a metadata dates entity, PersonOrg-ContactInformation links to allow multiple contact addresses and types (phone, internet, surface mail…), Object-LogEntries to allow multiple tracking records to be related to any object, to track revisions, comments etc.
Database Table Fields
· MetadataRelationshipID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each record in the MetadataRelationship table. Although the compound key {RelTypeID, RelTypeDS, FirstRoleID, FirstRoleDS, SecondRoleID, SecondRoleDS} provides a unique key, the table has a standard {ObjectID, DatasetID} key to allow a relationship to play a role in another relationship using the standard relationship tables. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. Compound primary key. This field contains an integer value that specifies the dataset that contains the data object identified by MetadataRelationshipID. Domain: 12 = the DataSetID for the MetadataRelationship table.
· RelTypeID: Number, long integer. This field contains and integer value that uniquely identifies the kind of relationship. This allows the MetadataRelationship table to represent any kind of relationship. The RelType defines the semantics of the relationship. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: 2535 = TrackingRecord-Citation link. The only relationship currently represented, is a link between records in the TrackingRecord table and citations in the _AzGeoBibCite table, allowing a many-to-many relationship between citations and tracking records.
· RelTypeDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by RelTypeID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· FirstRoleID: Number, long integer. First part of compound foreign key that identifies the object in the first role of the metadata relationship. Because only the TrackingRecord-Citation relationship is represented in this database, this field is a foreign key that links to the TrackingRecordID field of the TrackingRecord table in the RoskrugeWaterman database. Domain: TrackingRecordID codeset – RoskrugeWaterman database.
· FirstRoleDS: Number, long integer. Second part of compound foreign key that identifies the object in the first role of the metadata relationship. This field contains an integer value that specifies the dataset that contains the data object identified by FirstRoleID. Because only the TrackingRecord-Citation relationship is represented in this database, this field has only one value. Domain: 18 = the DataSetID for the TrackingRecord table.
· SecondRoleID: Number, long integer. First part of compound foreign key that identifies the object in the second role of the metadata relationship. Because only the TrackingRecord-Citation relationship is represented in this database, this field is a foreign key that links to the RefNum field of the _AzGeoBibCite table in the RoskrugeWaterman database. Domain: RefNum codeset – RoskrugeWaterman database.
· SecondRoleDS: Number, long integer. Second part of compound foreign key that identifies the object in the second role of the metadata relationship. This field contains an integer value that specifies the dataset that contains the data object identified by SecondRoleID. Because only the TrackingRecord-Citation relationship is represented in this database, this field has only one value. Domain: 4 = the DataSetID for the _AzGeoBibCite table.
Pattern Definition Table
The PatternDefinition table is not included in this database.
Person and Organization Table
The PersonOrg table is not included in this database. The values
in DI-19 used from this table are shown in Table 17.
Projects Table
The Projects table is not included in this database. The values in DI-19 used from this table are shown in Table 18.
Tracking Record Table
The TrackingRecord table keeps a record of the intellectual and
physical sources for objects and data by defining links to tables that describe
the processes and activities through which data was created.
Database Table Fields
· TrackingID: Number, long integer. Compound primary key. This field contains an integer value that uniquely identifies each record in the TrackingRecord dataset. Domain: >0 and <1016, no duplicates.
· DataSetID: Number, long integer. This field contains an integer value that uniquely identifies the TrackingRecord dataset. Domain: 18 = the DataSetID for this table in the RoskrugeWaterman database.
· TrackingRecordTypeID: Number, long integer. This field contains and integer value that uniquely identifies the type of origin tracking record. It is a foreign key that links to the ConceptID field of the ClassificationConcept table in the RoskrugeWaterman database. Domain: See Table 24.
Table 24. Tracking Record Type codes used in the TrackingRecord table.
|
ConceptID |
Name |
Definition |
|
2534 |
Origin Tracking Record |
Tracking record that records the origin of a data object or data set |
|
2742 |
Log Entry Tracking Record |
Tracking record type for tracking records that add information about a data entity |
|
2765 |
Termination Tracking Record |
Tracking record that indicates a data object has been superceded by a newer object. |
|
3210 |
Feature-level Origin Tracking Record |
Use as supertype to group tracking records that document origin of individual feature records in datasets. |
|
3211 |
Feature-Level Tracking for DI8 V3 |
Supertype to group feature tracking records for Geologic map of Arizona Database, v3 |
|
3228 |
Feature-Level Tracking for Infrastructure Objects |
Tracking record type for records that track data objects in the infrastructure tables |
|
3231 |
Dataset Origin Tracking |
Tracking records that record facts about the origin of a Dataset, and are inherited by contents of dataset unless feature-level tracking is included for dataset |
· TrackingRecordTypeDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by TrackingRecordTypeID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· Name: Text, width 255. This field contains a descriptive text string that uniquely identifies each origin tracking record and is included for simplification purposes. Domain: Free text.
· LogDate: Date/Time, short date. This field contains a date value, in mm/dd/yy format, that records when an entry was created. Domain: Valid date.
· ActivityID: Number, long integer. A foreign key that links to the ActivityID field of the Activities table in the RoskrugeWaterman database. Domain: See Table 25.
Table 25. Activity ID codes used in the TrackingRecord table.
|
ActivityID |
Name |
Comment |
|
1 |
SMRDataModelDevelopment |
Stephen M. Richard, Arizona Geological Survey, Arizona NADM implementation development |
|
2 |
SMR-DI8V3DevelopmentActivity |
Stephen M. Richard, Arizona Geological Survey, DI-8 Version 3 database development |
|
3 |
TRO-PhoenixNDatabaseDevelopment |
Tim R. Orr, Arizona Geological Survey, Phoenix N, East Half Database development |
|
4 |
Null |
No Activity assigned; Null N Null, None, Null |
|
5 |
BLMMOSSdigitizeMap26 |
BLM activity to produce MOSS version of Reynolds, 1988, AZGS Map26; Jason . Brander, Bureau of Land Management, Digitize Geologic Map of Arizona, using MOSS |
|
8 |
SMRDI8V1 |
Convert MOSS data to ARC, adjust to match ALRIS state outline, minor editing to correct obvious linework problems, edit faults to match contacts better, reclassify some polygons; Stephen M. Richard, Arizona Geological Survey, Edit Map 26 Data to release a |
|
10 |
SMRRoskrugeWatermanDI |
Digitizing, editing, and attribution of geologic information by Stephen M. Richard from data collected for Statemap 1999 contract; Stephen M. Richard, Arizona Geological Survey, Statemap 1999, Waterman Peak 1:24000 quad |
|
11 |
TRO_TheoRoos100KDigitizingandEditing |
table digitizing and editing using ArcInfo; Tim R. Orr, Arizona Geological Survey, TheodoreRoosevelt100KGISV2 |
|
33 |
TRO-GreenValleySurfGeology DatabaseConstruction |
project specific database construction; Tim R. Orr, Arizona Geological Survey, Statemap 1999 Surficial |
|
37 |
TRO-AZGeoMapIndexDatabaseConversion |
Added new fields to match current data structure of AZ_NADM data model. Renamed and reorganized existing fields; Tim R. Orr, Arizona Geological Survey, AZ Geologic Map Index database conversion |
|
38 |
TRODataModelDevelopment |
Tim R. Orr, Arizona Geological Survey, Arizona NADM implementation development |
|
39 |
AY-GreenValleyUnitAssignment |
assignment of map unit names to geologic polygons; Ann Youberg, Arizona Geological Survey, Statemap 1999 Surficial |
|
40 |
TRORoskrugeWatermanDatabaseDevelopment |
project specific database construction; Tim R. Orr, Arizona Geological Survey, Statemap2000PhxDatabases |
|
45 |
RCHRoskrugeWatermanDI |
Digitizing, editing, and attribution of geologic information by Ray Harris from data collected for Statemap 1999 contract; Ray C. Harris, Arizona Geological Survey, Statemap 1999, Roskruge/Waterman Digital Data |
|
46 |
TRORoskrugeWatermanDI |
Digitizing, editing, and attribution of geologic information by Tim Orr from data collected for Statemap 1999 contract; Tim R. Orr, Arizona Geological Survey, Statemap 1999, Roskruge/Waterman Digital Data |
|
47 |
TRORoskrugeWatermanCarto |
Cartographic layout for Roskruge/Waterman digital data browse graphic; Tim R. Orr, Arizona Geological Survey, Statemap 1999, Roskruge/Waterman Digital Data |
|
48 |
SMRRoskrugeWatermanCarto |
Cartographic layout for Roskruge/Waterman digital data browse graphic; Stephen M. Richard, Arizona Geological Survey, Statemap 1999, Waterman Peak 1:24000 quad |
|
49 |
NMBMMRGeochemAnalyses |
Samples were crushed in a steel jaw crusher, split, and ground in a Tema mill using a WC grinding set. Samples were fused into glass disks and analyzed on a Phillips wavelength dispersive x-ray fluorescence spectrometer for major elements. |
|
82 |
PAPRoskrugeWatermanDI |
DI database contributions by Phil Pearthree |
· ActivityDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by ActivityID. Domain: 2 = the DataSetID for the Activities table.
· DataProcMethodID: Number, long integer. It is a foreign key that links to a data processing name and definition in the ClassificationConcept table in the RoskrugeWaterman database. A complete data processing object define the steps in developing a particular data item (digitized spatial feature, record in a data table). In this database the processing steps are not described at a feature level. Domain: 2748 = MS Access Database Construction; 2764 = no processing.
· DataProcMethodDS: Number, long integer. This field contains an integer value that specifies the dataset that contains the data object identified by DataProcMethodID. Domain: 1 = the DataSetID for the ClassificationConcept table.
· Description: Memo. This field contains a description of the people and processes that define each tracking record. Domain: Free text.
REFERENCES
Johnson,
B. R., Brodaric, Boyan, and Raines, G. L., 1998, Digital Geologic Maps Data
Model, V. 4.3: http://ncgmp.usgs.gov/ngmdbproject, U. S. Geological Survey.
Richard,
S. M., and Orr T. R., in prep., Database design for Arizona Geological Survey
Geologic Information Sytem: Tucson, Arizona Geological Survey Open-File Report.
Trapp,
R. A., and Reynolds, S. J., 1998, Physiographic areas in Arizona used by the
Arizona Geological Survey: Tucson, Arizona Geological Survey, Digital
Information Series DI-10, 4 pages, 1 floppy disc.
Trapp,
R. A., Schmidt, N., and Reynolds, S. J., 1996, AZGEOBIB, Version 2.1: A List of
References on the Geology of Arizona: Arizona Geological Survey Open-File
Report OFR-96-01, p. 308.
FIGURES
Figure 1. Entity relationship schema for the RoskrugeWaterman database.