roads

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?

Title: roads

Abstract:

All roads on and immediately adjacent to Starkey, classified by road type including open, closed, and abandoned.

1. How should this data set be cited?

   REQUIRED: The name of an organization or individual that developed the data set., REQUIRED: The date when the data set is published or otherwise made available for release., roads.

   Online Links:

   • \\LTS38\C$\GISProjects\Starkey\Starkey.mdb

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -118.628112

   East_Bounding_Coordinate: -118.463071

   North_Bounding_Coordinate: 45.330301

   South_Bounding_Coordinate: 45.173552

3. What does it look like?

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

   Calendar_Date: REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.

   Currentness_Reference:

   REQUIRED: The basis on which the time period of content information is determined.

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 (870)
      • Point (4)
      • Label point (0)

   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.000032
      Ordinates (y-coordinates) are specified to the nearest 0.000032
      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.
      

      Vertical_Coordinate_System_Definition:

      Altitude_System_Definition:

      Altitude_Resolution: 0.000010

      Altitude_Encoding_Method:

      Explicit elevation coordinate included with horizontal coordinates

7. How does the data set describe geographic features?

   roads

   OBJECTID

   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.

   TRN_ALL_

   Internal feature number. (Source: ESRI)

   Sequential unique whole numbers that are automatically generated.

   TRN_ALL_ID

   User-defined feature number. (Source: ESRI)

   DATA

   Shape_Length

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

   Positive real numbers that are automatically generated.

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • REQUIRED: The name of an organization or individual that developed the data set.

2. Who also contributed to the data set?

3. To whom should users address questions about the data?

   Norm Cimon
   USDA Forest Service PNW Experiment Station
   Starkey Data Administrator
   Forestry & Range Sciences Lab
   La Grande, Oregon 97850
   USA
   

   541-962-6551 (voice)
   541-962-6504 (FAX)
   ncimon@fs.fed.us
   

Used to partition traffic flows by road segment and by category.

1. From what previous works were the data drawn?

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

   (process 1 of 1)

   Dataset copied.

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?

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

Access_Constraints: None.

Use_Constraints: None.

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.195

   • Cost to order the data:

Dates:

Last modified: 24-Feb-2004

Metadata author:

REQUIRED: The organization responsible for the metadata information.
c/o REQUIRED: The person responsible for the metadata information.
REQUIRED: The city of the address., REQUIRED: The state or province of the address. REQUIRED: The ZIP or other postal code of the address.

REQUIRED: The telephone number by which individuals can speak to the organization or individual. (voice)

Metadata standard:

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

Metadata extensions used:

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