USGS Home
Contact USGS
Search USGS

Surficial and Bedrock Geologic Map Database of the Kelso 7.5 Minute Quadrangle, San Bernardino County, California

Frequently-anticipated questions:

• What does this data set describe?
  1. How should this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
• How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

What does this data set describe?

Title:

Surficial and Bedrock Geologic Map Database of the Kelso 7.5 Minute Quadrangle, San Bernardino County, California

Abstract:

This geologic map database describes geologic materials for the Kelso 7.5 Minute Quadrangle, San Bernardino County, California. The area lies in eastern Mojave Desert of California, within the Mojave National Preserve. Geologic units in the area consist of Proterozoic metamorphic rocks, Cambrian-Neoproterozoic sedimentary rocks, Mesozoic plutonic and hypabyssal rocks, Tertiary basin fill, and Quaternary surficial deposits. This Report consists of 3 parts: 1) the documentation of the report, including a geologic discussion, 2) digital spatial data in the form of 2 ARC/INFO coverages, and 3) a printable geologic map

1. How should this data set be cited?

   Bedford, David R. , 2003, Surficial and Bedrock Geologic Map Database of the Kelso 7.5 Minute Quadrangle, San Bernardino County, California: Open-File Report O3-501, U.S. Geological Survey, Menlo Park, CA.

   Online Links:

   • <http://geopubs.wr.usgs.gov/open-file/of03-501>

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -115.752736

   East_Bounding_Coordinate: -115.623733

   North_Bounding_Coordinate: 35.126339

   South_Bounding_Coordinate: 34.998637

3. What does it look like?

   <http://geopubs.wr.usgs.gov/open-file/of03-501/kelso_browse.jpg> (JPEG)

   Thumbnail

4. Does the data set describe conditions during a particular time period?

   Calendar_Date: 2003

   Currentness_Reference: ground condition

5. What is the general form of this data set?

   Geospatial_Data_Presentation_Form: vector digital data

6. How does the data set represent geographic features?
   1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • Complete chain (1817)
      • Label point (679)
      • GT-polygon composed of chains (679)
      • Point (16)
   2. What coordinate system is used to represent geographic features?

      Grid_Coordinate_System_Name: Universal Transverse Mercator

      Universal_Transverse_Mercator:

      UTM_Zone_Number: 11

      Transverse_Mercator:

      Scale_Factor_at_Central_Meridian: 0.999600

      Longitude_of_Central_Meridian: -117.000000

      Latitude_of_Projection_Origin: 0.000000

      False_Easting: 500000.000000

      False_Northing: 0.000000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000008
      Ordinates (y-coordinates) are specified to the nearest 0.000008
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.
      

7. How does the data set describe geographic features?

   kls-geol.aat

   Arc attributes for coverage 'kls-geol' (Faults, depositional contacts, and rock units) (Source: This Report)

   FID

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   Shape

   Feature geometry. (Source: ESRI)

   Coordinates defining the features.

   FNODE#

   Internal node number for the beginning of an arc (from-node). (Source: ESRI)

   Whole numbers that are automatically generated.

   TNODE#

   Internal node number for the end of an arc (to-node). (Source: ESRI)

   Whole numbers that are automatically generated.

   LPOLY#

   Internal node number for the left polygon. (Source: ESRI)

   Whole numbers that are automatically generated.

   RPOLY#

   Internal node number for the right polygon. (Source: ESRI)

   Whole numbers that are automatically generated.

   LENGTH

   Length of feature in internal units. (Source: ESRI)

   Positive real numbers that are automatically generated.

   KLS-GEOL#

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   KLS-GEOL-ID

   User-defined feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   LTYPE

   Linetype: the type of line represented, such as faults and contacts (Source: This Report)

   Value	Definition
   contact, approximately located	Boundary between two mapped units that has been observed but the location is not precise
   contact, certain	Boundary between two mapped units that was observed, the location of which is well known and is described in Positional_Accuracy
   contact, concealed, queried	Boundary between two mapped units that was inferred and is believed to be buried, the location of which is approximately within 30 m.
   contact, eolian gradational	Boundary between two mapped units that is transitional in properties between the mapped units through eolian processes, the location of which is approximate and may vary with in the direction of eolian transport
   contact, gradational	Boundary between two mapped units that is transitional over an area.
   dike, TKa	an intrusive dike that is mappable only as a linear feature, composed of map unit Tka
   fault, approximately located	Structural boundary between mapped units or structural discontinuity within a mapped unit that has experienced relative offset. Locational accuracy is approximate, and described in Positional_Accuracy.
   fault, certain	Structural boundary between mapped units or structural discontinuity within a mapped unit that has experienced relative offset. Locational accuracy is well located, and described in Positional_Accuracy.
   fault, concealed	Structural boundary between mapped units or structural discontinuity within a mapped unit that has experienced relative offset. The fault is obscured by overlying map units, so it is not well-located as described in Positional_Accuracy, but is constrained to within about 120 meters on the ground.
   fault, concealed, queried	Structural boundary between mapped units or structural discontinuity within a mapped unit that has experienced relative offset. The fault is obscured by overlying map units, so it is not well-located as described in Positional_Accuracy, but is constrained to within about 150 meters on the ground. Existence of the fault is inferred from lineaments or structural relations elsewhere.
   levee	an artificial linear feature that generally alters the movement of surface water flow
   map boundary, certain	Enumerated_Domain_Value_Definition: Edge of mapped area, used to bound polygons at the edge of the map database. Locational confidence is described in Positional_Accuracy
   normal fault, approximately located	Structural boundary between mapped units or structural discontinuity within a mapped unit that has experienced significant normal, or vertical, relative offset. Locational accuracy is approximate, and described in Positional_Accuracy.
   normal fault, certain	Structural boundary between mapped units or structural discontinuity within a mapped unit that has experienced significant normal, or vertical, relative offset. Locational accuracy is well located, and described in Positional_Accuracy.
   normal fault, concealed	Structural boundary between mapped units or structural discontinuity within a mapped unit that has experienced significant normal, or vertical, relative offset. The fault is obscured by overlying map units, so it is not well-located as described in Positional_Accuracy, but is constrained to within about 120 meters on the ground.

   kls-geol.pat

   Polygon attributes for coverage 'kls-geol' (Faults, depositional contacts, and rock units) (Source: This Report)

   FID

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   Shape

   Feature geometry. (Source: ESRI)

   Coordinates defining the features.

   AREA

   Area of feature in internal units squared. (Source: ESRI)

   Positive real numbers that are automatically generated.

   PERIMETER

   Perimeter of feature in internal units. (Source: ESRI)

   Positive real numbers that are automatically generated.

   KLS-GEOL#

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   KLS-GEOL-ID

   User-defined feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   PTYPE

   Geologic unit attribute (Source: This Report)

   Value	Definition
   CZcb	See Description of Map Units in This Report
   CZp	See Description of Map Units in This Report
   CZwc	See Description of Map Units in This Report
   CZwcl	See Description of Map Units in This Report
   CZwcm	See Description of Map Units in This Report
   CZwcu	See Description of Map Units in This Report
   Cbk	See Description of Map Units in This Report
   Ccc	See Description of Map Units in This Report
   Ccc?	See Description of Map Units in This Report
   Ccl	See Description of Map Units in This Report
   Cz	See Description of Map Units in This Report
   KJag	See Description of Map Units in This Report
   KJd	See Description of Map Units in This Report
   KJmd	See Description of Map Units in This Report
   Kgd	See Description of Map Units in This Report
   Kte	See Description of Map Units in This Report
   Kte+Ktk	See Description of Map Units in This Report
   Ktgd	See Description of Map Units in This Report
   Ktk	See Description of Map Units in This Report
   Ktp	See Description of Map Units in This Report
   Qia	See Description of Map Units in This Report
   Qia+Qyae	See Description of Map Units in This Report
   Qia1	See Description of Map Units in This Report
   Qia2	See Description of Map Units in This Report
   Qia2+Qya	See Description of Map Units in This Report
   Qia2/Qoa	See Description of Map Units in This Report
   Qiae1	See Description of Map Units in This Report
   Qiae2	See Description of Map Units in This Report
   Qiag	See Description of Map Units in This Report
   Qiag3	See Description of Map Units in This Report
   Qiag3+Qyag3	See Description of Map Units in This Report
   Qiag3?	See Description of Map Units in This Report
   Qya+Qia	See Description of Map Units in This Report
   Qya1+Qya3	See Description of Map Units in This Report
   Qya3	See Description of Map Units in This Report
   Qya3+Qia	See Description of Map Units in This Report
   Qya3+Qya1	See Description of Map Units in This Report
   Qya3+Qya2	See Description of Map Units in This Report
   Qya3+Qya2+Qya1	See Description of Map Units in This Report
   Qya3+Qya4	See Description of Map Units in This Report
   Qya3+Qya4+Qya2+Qya1	See Description of Map Units in This Report
   Qya4	See Description of Map Units in This Report
   Qya4+Qya3	See Description of Map Units in This Report
   Qyad	See Description of Map Units in This Report
   Qyae	See Description of Map Units in This Report
   Qyae+Qiae	See Description of Map Units in This Report
   Qyae3+Qya1+Qya2	See Description of Map Units in This Report
   Qyae3+Qya2+Qya1	See Description of Map Units in This Report
   Qyae3+Qyae4	See Description of Map Units in This Report
   Qyae3+Qyae4+Qya2+Qya1	See Description of Map Units in This Report
   Qyag1+Qyag3	See Description of Map Units in This Report
   Qyag2	See Description of Map Units in This Report
   Qyag3	See Description of Map Units in This Report
   Qyag3+Qiag3	See Description of Map Units in This Report
   Qyag3+Qiag3+Qyag4	See Description of Map Units in This Report
   Qyag3+Qyag1	See Description of Map Units in This Report
   Qyag3+Qyag2	See Description of Map Units in This Report
   Qyag3+Qyag4	See Description of Map Units in This Report
   Qyag3/Qia	See Description of Map Units in This Report
   Qyag3/Qiag	See Description of Map Units in This Report
   Qyag3/Qyag4	See Description of Map Units in This Report
   Qyag4	See Description of Map Units in This Report
   Qyag4+Qiag3+Qyag3	See Description of Map Units in This Report
   Qyag4+Qyag3	See Description of Map Units in This Report
   Qyc	See Description of Map Units in This Report
   Qyc/CZp	See Description of Map Units in This Report
   Qyc/CZwc	See Description of Map Units in This Report
   Qyc/Cz?	See Description of Map Units in This Report
   Qyc/Zj	See Description of Map Units in This Report
   Qye	See Description of Map Units in This Report
   Qye/Qia	See Description of Map Units in This Report
   Qye/Qya	See Description of Map Units in This Report
   Qye/Qya+Qia	See Description of Map Units in This Report
   Qye/Qya3	See Description of Map Units in This Report
   Qye/Qya3+Qya1	See Description of Map Units in This Report
   Qye/Qyae3+Qyae4+Qya2+Qya1	See Description of Map Units in This Report
   Qye/Qyag3	See Description of Map Units in This Report
   Qye/Qyag3+Qyag1	See Description of Map Units in This Report
   Qye/Qyw	See Description of Map Units in This Report
   Qyw1	See Description of Map Units in This Report
   Qyw2+Qyw1	See Description of Map Units in This Report
   Qyw3	See Description of Map Units in This Report
   Qyw3+Qyw1	See Description of Map Units in This Report
   Qyw3+Qyw2	See Description of Map Units in This Report
   TKa	See Description of Map Units in This Report
   Tbr	See Description of Map Units in This Report
   Tfg	See Description of Map Units in This Report
   Tfgn	See Description of Map Units in This Report
   Xgg	See Description of Map Units in This Report
   Xgs	See Description of Map Units in This Report
   Xgu	See Description of Map Units in This Report
   Zj	See Description of Map Units in This Report
   Zj?	See Description of Map Units in This Report
   Zs?	See Description of Map Units in This Report
   Zsl	See Description of Map Units in This Report
   Zsm	See Description of Map Units in This Report
   Zsu	See Description of Map Units in This Report
   af	See Description of Map Units in This Report

   kls-str.pat

   Point features in coverage 'kls-str' (Geologic structure layer - strike and dips, fold axis, etc) (Source: This Report)

   FID

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   Shape

   Feature geometry. (Source: ESRI)

   Coordinates defining the features.

   AREA

   Area of feature in internal units squared. (Source: ESRI)

   Area is always zero for point coverages. Values are automatically generated.

   PERIMETER

   Perimeter of feature in internal units. (Source: ESRI)

   Perimeter is always zero for point coverages. Values are automatically generated.

   KLS_STR7#

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   KLS_STR7-ID

   User-defined feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   PTTYPE

   The type of structural measurement (Source: This Report)

   Value	Definition
   bedding	Strike and dip of stratigraphic bedding
   crumpled bedding	Strike and Dip of bedding with small-scale folds or crumples
   fault dip	Strike and dip of a fault plane
   fold axis	Trend and plunge of a fold axis for folded beds
   foliation	Strike and dip of foliated beds
   joint	Strike and dip of jointed massive rocks
   slickenside	Trend and plunge for lineated fault features
   small anticline	Trend and Plunge of small (~10m2) anticlinal fold axis
   small syncline	Trend and Plunge of small (~10m2) synclinal fold axis
   vertical bedding	Strike (Dip = 90) of vertical beds
   vertical foliation	Strike (Dip = 90) of vertical foliation

   DIP

   The Dip value (or plunge for linear features) of a structural measurement (Source: This Report)

   Range of values
   Minimum:	0
   Maximum:	90

   STRIKE

   The strike value (or plunge for linear features) of a structural measurement (Source: This Report)

   Range of values
   Minimum:	0
   Maximum:	360

   Entity_and_Attribute_Overview:

   The primary layer is the geology layer (kls-geol), which consists of both polygon features and arc features that describes map units (polygons), and depositional contacts, faults (which may or may not be polygon bounding features) and map boundaries.

   Map units (polygons) are described in the polygon attribute table (kls-geol.pat). The identities of the map units are recorded in the PTYPE field by map label (i.e. Qia). For a description of the map units, consult the PostScript or PDF explanation pamphlets in this report or the printable map sheet.

   Geologic lines (arcs) are recorded as strings of vectors and are described in the arc attribute table (kls-geol.aat). They define the boundaries of the map units, the faults, and the map boundaries. These distinctions, including the geologic identities of the unit boundaries, are recorded in the LTYPE field. Attributes for geologic lines generally follow a scheme of the type of geologic line (i.e. fault), followed by a locational and/or scientific modifier (i.e. approx. located or queried).

   Entity_and_Attribute_Detail_Citation: This Report

Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • David R. Bedford
2. Who also contributed to the data set?
3. To whom should users address questions about the data?

   David R. Bedford
   U.S. Geological Survey
   Geologist
   345 Middlefield Rd MS973
   Menlo Park, CA 94025
   USA
   

   650-329-4924 (voice)
   650-329-4936 (FAX)
   dbedford@usgs.gov
   

Why was the data set created?

Documents surficial deposits, soil development characteristics and geomorphic relationships, along with bedrock composition and structure.

How was the data set created?

1. From what previous works were the data drawn?
2. How were the data generated, processed, and modified?

   Date: Unknown (process 1 of 1)

   The geologic map was heads up digitized in ArcMap using DOQ and Landsat7 imagery, GPS locations of field observations, as well as traditional field methods such as stereo photography.

How reliable are the data; what problems remain in the data set?

1. How well have the observations been checked?

   map units, contacts, or faults are attributed with an appended '?' if their designation is assumed and not definite.

2. How accurate are the geographic locations?

   Horizontal_Positional_Accuracy_Report: Accuracy of line locations is carried in the database and displayed by different line symbols (solid vs. dashed lines) in the cartographic display. For the purpose of this database, solid lines represent contacts and faults located with an accuracy greater than 10 m and commonly greater than 5 m. Dashed lines represent two kinds of less certainly located features, each distinguished in the database: 1) contacts and faults located with an accuracy of 10 to 15 m, 2) contacts that represent gradational boundaries between adjacent units. Gradational contacts represent interleaving of sediments and smooth gradations in characteristics such as percentage of eolian sand. In general, these gradations take place over distances of 50 to 150 m. Lineaments and fold axes are lines whose positions do not affect location of polygons; they are located with an accuracy of 25 m.

3. How accurate are the heights or depths?
4. Where are the gaps in the data? What is missing?

   Complete

5. How consistent are the relationships among the observations, including topology?

   Geologic lines attributed as a 'contact' do not separate geologic map units of the same type, and are not considered as 'dangles'. All geologic polygons are attributed with map unit designators found in the Description of Map Units

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: None

Use_Constraints:

Acknowledgement of the U.S. Geological Survey; uses of this digital geologic map should not violate the spatial resolution of the data. Although the digital form of the data removes the constraint imposed by the scale of a paper map, the detail and accuracy inherent in map scale are also present in the digital data.

1. Who distributes the data set? (Distributor 1 of 2)

   U.S. Geological Survey
   c/o Kelso Database
   Database Coordinator
   345 Middlefield Rd MS973
   Menlo Park, CA 94025
   USA
   

   650-329-2923 (voice)
   

2. What's the catalog number I need to order this data set?

   Downloadable Data

3. What legal disclaimers am I supposed to read?

   This report is preliminary and has not been reviewed for conformity with U.S. Geological Survey editorial standards or with the North American Stratigraphic Code. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.

   This database, identified as "Surficial and Bedrock Geologic Map Database of the Kelso 7.5 Minute Quadrangle, San Bernardino County, California," has been approved for release and publication by the Director of the USGS. Although this database has been subjected to rigorous review and is substantially complete, the USGS reserves the right to revise the data pursuant to further analysis and review. Furthermore, it is released on condition that neither the USGS nor the United States Government may be held liable for any damages resulting from its authorized or unauthorized use.

4. How can I download or order the data?
   • Availability in digital form:

     Data format:	ARCE Size: 0.928
     Network links:	<http://geopubs.wr.usgs.gov/open-file/of03-501> <ftp://wrgis.wr.usgs.gov/pub/open-file/of03-501>

   • Cost to order the data: None
   • Special instructions:

     All files for this report can be accessed via the World Wide Web at: <http://wrgis.wr.usgs.gov/open-file/of03-501> or through File Transfer Protocol (FTP) at <ftp://wrgis.wr.usgs.gov/pub/open-file/of03-501/>

   ---

1. Who distributes the data set? (Distributor 2 of 2)

   U.S. Geological Survey Information Services
   25286 Denver Federal Center
   Denver, Colorado 80225
   USA
   

   303-202-4700 (voice)
   303-202-4693 (FAX)
   

2. What's the catalog number I need to order this data set?

   Downloadable Data

3. What legal disclaimers am I supposed to read?

   This report is preliminary and has not been reviewed for conformity with U.S. Geological Survey editorial standards or with the North American Stratigraphic Code. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.

   This database, identified as "Surficial and Bedrock Geologic Map Database of the Kelso 7.5 Minute Quadrangle, San Bernardino County, California," has been approved for release and publication by the Director of the USGS. Although this database has been subjected to rigorous review and is substantially complete, the USGS reserves the right to revise the data pursuant to further analysis and review. Furthermore, it is released on condition that neither the USGS nor the United States Government may be held liable for any damages resulting from its authorized or unauthorized use.

4. How can I download or order the data?

Who wrote the metadata?

Dates:

Last modified: 11-Dec-2003

Metadata author:

David R. Bedford
U.S. Geological Survey
Geologist
345 Middlefield Rd MS973
Menlo Park, CA 94025
USA

650-329-4924 (voice)
650-329-4936 (FAX)
dbedford@usgs.gov

Metadata standard:

FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

Metadata extensions used:

• <http://www.esri.com/metadata/esriprof80.html>