Digital Map of Active Traces of the Hayward Fault

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?
  3. What similar or related data should the user be aware of?
• 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?

1. How should this data set be cited?

   Lienkaemper, James J. , and U.S. Geological Survey, 2006, Digital Map of Active Traces of the Hayward Fault: Data Series xxx, U.S. Geological Survey, Reston, VA.

   Online Links:

   • htttp://pubs.usgs.gov

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -122.369989

   East_Bounding_Coordinate: -121.898119

   North_Bounding_Coordinate: 38.003109

   South_Bounding_Coordinate: 37.478319

3. What does it look like?

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

   Calendar_Date: 2006

   Currentness_Reference: 2006

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):

      • String (432)

   2. What coordinate system is used to represent geographic features?

      Grid_Coordinate_System_Name: Universal Transverse Mercator

      Universal_Transverse_Mercator:

      UTM_Zone_Number: 10

      Transverse_Mercator:

      Scale_Factor_at_Central_Meridian: 0.999600

      Longitude_of_Central_Meridian: -123.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.000128
      Ordinates (y-coordinates) are specified to the nearest 0.000128
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1927.
      The ellipsoid used is Clarke 1866.
      The semi-major axis of the ellipsoid used is 6378206.400000.
      The flattening of the ellipsoid used is 1/294.978698.
      

7. How does the data set describe geographic features?

   hf2006

   FID

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   Shape

   Feature geometry. (Source: ESRI)

   Coordinates defining the features.

   FNODE_

   TNODE_

   LPOLY_

   RPOLY_

   LENGTH

   codednotes

   FRANK

   y_off_age

   STRAND

   LOC_CER_TX

   LOC_CER_NU

   FTR_MAPPED

   geomorph

Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • James J. Lienkaemper
   • U.S. Geological Survey

2. Who also contributed to the data set?

   James J. Lienkaemper U.S. Geological Survey

3. To whom should users address questions about the data?
   James J. Lienkaemper
   U.S. Geological Survey
   Geophysicist
   

   jlienk@usgs.gov
   

Why was the data set created?

This map is a revision of the previous (Lienkaemper, 1992) map of the Hayward fault, brought up to date as a digital database coordinated with other Quaternary fault mapping projects

How was the data set created?

1. From what previous works were the data drawn?

2. How were the data generated, processed, and modified?

   (process 1 of 1)

   Metadata imported.

   Data sources used in this process:

   • C:\DOCUME~1\JAMESL~1\LOCALS~1\Temp\xml1BA.tmp

3. What similar or related data should the user be aware of?

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 observations, including topology?

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: Acknowledge by citation; inform users if modified.

1. Who distributes the data set?[Distributor contact information not provided.]

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

   Downloadable Data

3. What legal disclaimers am I supposed to read?

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

     Data format:	Size: 0.051

   • Cost to order the data:

Who wrote the metadata?

Dates:

Last modified: 23-Nov-2005

Metadata author:

James J. Lienkaemper
U.S. Geological Survey
Geophysicist
USGS MS977
Menlo Park, CA 94025
USGS

650 329-5642 (voice)
jlienk@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>