rr_roads

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator:
The original ROADS layer was developed as a coverage named roadsa by Steve Flatt 916-263-1499. Rr_roads.shp was created by Circuit Rider Productions, Inc. Rr_roads represents the portion of the roadsa coverage that describes the roads contained within the Russian River basin. Line features selected from the original source data were based on their spatial location within the extent of the Russian River basin. This metadata file incorporates information that is specific to this layer as well as information that is available in the original metadata file for the ROADS coverage (roadsa.txt). The portions of this metadata file that borrow text from roadsa.txt are indicated in quotation marks.
Publication_Date:
September 2002.
Title: rr_roads
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage: \\DAVID\C$\rrgis_phase_1\Base\rr_roads.shp
Description:
Abstract:
"The 'ROADS' layer is based on the USGS DLG transportation
linework derived from the DLG-3 digital series. The library
layer contains DLG linework as it came from USGS, plus
edited and new linework."
Purpose:
The intended purpose of this dataset is to provide users with a line feature type data layer that describes and illustrates the roads contained within the extent of the Russian River basin.

Supplemental Information:
     
 "Edits included corrections of
coding and additions, deletions and alterations of linework.
This layer contains a second-generation arc attribute table
derived from the DLG major/minor pair scheme. The derived
table is fully described here. The original coding can be
made available upon request. DLG coding is documented in
"Digital Line Graphs From 1:100000-Scale Maps, Data Users
Guide 2, 1985" available from the U.S. Department of the
Interior, U.S. Geological Survey, Reston, Virginia.

The roads layer contains several classes of transportation
features including jeep trails, city streets, thoroughfares,
unpaved roads, state highways, and interstates. Some of the
data is 20 years old; therefore, care should be taken when
using data from areas that have grown in recent years. The
currency of the State highway system (those for which
Caltrans has responsibility) is very good, having been
updated in 1993. The data can be very dense in highly
urbanized counties. Los Angeles County has over 200,000
arcs.

These coverages were processed to the specifications of the
Department of Transportation whose interest was in
"legislative routes". This resulted in some peculiarities in
attribute coding where legislative route names differ from
the route's common name. For example, Sacramento's Business
80 is referred to as State Route 51 in legislative route
parlance. Users searching for Business 80 will either not
find it or will find Interstate 80 (a different roadway)
instead. No attempt has been made to supply aliases for
legislative route numbers, though the attribute file
structure can accommodate them. Also, in areas where a
highway has two names (1 & 101, 70 & 99) the arcs may have
one name, or the other, or neither if the legislative route
number differs from the more common name.

An item has been added to the arc attribute table to identify which
1:100,000 scale quad sheet they originated in, and to make
them unique within the state. They range from 100,000,000 to
214,000,000. The first 3 digits refer to the id numbers
assigned to each 100K quad starting with the northwest-most
quad in the state and ending with the southeast-most quad.
This scheme is mostly for Teale's use in updating, but users
may find it of interest."  

"The roads layer originated from US Geological Survey Digital
Line Graph (DLG) 1:100,000 scale quadrangle series. Since 32
DLG files (which cover 7 and half minutes of latitude) make
up the area represented on a 1:100,000 scale map, 32
separate coverages were generated. All of these coverages
were then appended into one coverage. Roads that crossed the
'neat lines' were not matched or connected. In order to join
these roads together, an edgematching program was run on
these quads, with a snapping tolerance of 20 meters. A final
check was conducted interactively for roads exceeding the
tolerance, and were snapped accordingly. Each 100K road
coverage was appended with the adjoining 100K road coverage,
and edgematched. The coverages were then converted from
single precision to double precision. This procedure
minimized movement of arcs. The projection was also changed
from the Universal Transverse Mercator to Albers. The
coverages were then clipped with the county boundary, with a
tolerance of .001 meters.

All major highways were updated in 1993 through a joint
project with Caltrans. There were various types of updates,
such as recoding former thoroughfares as highways, or vice
versa. We also added newly constructed highways and
realignments. These roads were digitized at 1:24,000 scale.
All post 1994 updates may by found by selecting the item
"updinfo" not equal to zero. To find digitized
roads, select for class equal to 90.

The attribute Route1 contains the 'legislative' route
number. Route2 and Route3 may or may not contain the other
route number assigned to that route. Due to inconsistency of
classifications found among USGS 1:100,000 scale quads, some
infrequently occuring classifications were not preserved in
the attributes in the library, but can be retrieved through
related files.

DATA QUALITY ASSESSMENT:

This layer is only as complete as USGS 1:100,000 quad maps,
some of which date back to the mid 1970s. Recent areas of
growth are not included; however, the information the layer
does have is quite detailed and includes even jeep trails.
The attribute coverage is fairly complete with 5 types and
22 classes of roads; however, not all classifications occur
in each county, and classification of secondary roads can be
somewhat inconsistent between 100k quads."

Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date:
Dates vary based on the original source data (US Geological Survey Digital
Line Graph (DLG) 1:100,000 scale quadrangle series).
Currentness_Reference:
Original source data which illustrated ground conditions consistent with that of the map publication date.
Status:
Progress: Complete.
Maintenance_and_Update_Frequency:
None scheduled.
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -123.387284
East_Bounding_Coordinate: -122.523603
North_Bounding_Coordinate: 39.394162
South_Bounding_Coordinate: 38.298177
Keywords:
Theme:
Theme_Keyword_Thesaurus:
Roads
Theme_Keyword:
Russian River, Sonoma County, Mendocino County
Access_Constraints:
None.
Use_Constraints:
 
The responsibility of the risks associated in regards to the results and representations of using this type of spatial data is understood by the user. In all cases, the user should refer to the associated metadata files or the original source data for accuracy, currentness and appropriate contact information. CRP shall not have any liability to any person or entity with respect to liability, loss or damage caused or alleged to be caused directly or indirectly by information contained in this file.
 
Native_Data_Set_Environment:
Microsoft Windows 2000 Version 5.1 (Build 2600) ; ESRI ArcCatalog 8.2.0.700

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 17618

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Grid_Coordinate_System:
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_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000256
Ordinate_Resolution: 0.000256
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: rr_roads
Attribute:
Attribute_Label: FID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
"FNODE# : The id number of the node feature that represents
the beginning point (the From NODE) of the arc.

TNODE# : The id number of the node feature that represents
the ending point (To NODE) of the arc.

LPOLY# : The <coverage name># id of the polygon that lies to the
left of this arc when facing in the direction of the
TNODE.

This is blank if there is no polygon topology.


RPOLY# : The <coverage name># id of the polygon that lies to the
right of this arc when facing in the direction of the
TNODE.

This is blank if there is no polygon topology.

LENGTH : The length of the arc in coverage units.

ROADSA# : The software-assigned unique integer identification number.

ROADSA-ID : A user-assigned identification number.

DLG-ID: Originally used to hold DLG ID number; some arcs
have been added and changed which has resulted in duplicate
id numbers in this item.

HDLG-ID: Original DLG ID number + (nnn * 1,000,000) where
nnn is the number of the 1:100000 scale quad in
which the arc resides, numbered from 100 in the
northwest of the state to 214 in the southeast.

TYPE: Refers to type of road:
100 Interstate Highway
200 US Highway
300 State Highway
500 Interchange
900 Other

ROUTE1-3: Route numbers of interstates, state routes, or US
routes

ROUTE1: Legislative route number (see User Notes). May
or may not correspond to the common route numbers
seen on highway maps and road signs.

ROUTE2: Other route numbers which may apply to this arc

ROUTE3: Other route numbers which may apply to this arc

Note: The Caltrans project only involved updating the
legislative routes. Consequently, ROUTE2 and ROUTE3 were
not closely checked for accuracy.

CLASS: Refers to the USGS classsification of roads:

Class Value Description
----------- -----------
10 Class 1; Primary Route-undivided

11 Class 1; Primary Route-divided by centerline

12 Class 1; Primary Route-divided, lanes separated

13 Class 1; Primary Route-one way, other than divided
highway

20 Class 2; Secondary Route-undivided

21 Class 2; Secondary Route-divided by centerline

22 Class 2; Secondary Route-divided, lanes separated

23 Class 2; Secondary Route-one way, other than
divided highway

30 Class 3; Thoroughfares, County Roads-mostly paved

31 Class 3; Thoroughfares, County Roads-divided by
centerline

32 Class 3; Thoroughfares, County Roads-divided,
lanes separated

33 Class 3; Thoroughfares, County Roads-one way

40 Class 4; Residential Roads, unimproved, unpaved
roads

43 Class 4; Residential Roads, unimproved, unpaved
roads-one way

49 Class 4; Originally not coded; assumed to be
class 4 based on neighboring arcs

50 Class 5; Other than four-wheel-drive vehicle;
example - hiking trails

51 Class 5; Four wheel drive vehicle

59 Class 5; Originally not coded; assumed to be class 5
based on neighboring arcs

60 Interchanges: They have their own classification

70 Miscellaneous UGSG classifications

80 In service facility or rest area

90 Roads that were newly digitized or roads recoded as
a highway by Caltrans

STATUS: A Caltrans designation:

1 - Constructed; (paved or unpaved)

2 - Adopted; Not yet constructed. Approved for
construction

3 - Proposed; Not yet constructed. Construction is
proposed

UPDINFO: Update information in the format mmyy.nn
Month and year of update (mmyy), followed by an agency code
indicating the updater:

0 - has not been updated; data is from USGS (mmyy)

01 - updated by Caltrans (mmyy.01)

02 - updated by Teale Data Center -- GIS Lab (mmyy.02)

Examples: 1290.02 - Updated in December of 1990 by Caltrans staff
1093.01 - Updated in October of 1993 by Teale staff

HWYRAMP: Flag for highways and ramps:

0 - other than a highway or a ramp
1 - highway or ramp

TAG: Used to flag tile boundaries."

 

Distribution_Information:
Resource_Description: Downloadable Data
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 5.295

Metadata_Reference_Information:
Metadata_Date: 20020824
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Circuit Rider Productions, Inc.
Contact_Person:
David Bennett
Contact_Address:
Address_Type:
Mailing: 9619 Old Redwood Highway
City: Windsor
State_or_Province: California.
Postal_Code: 95492.
Contact_Voice_Telephone:
707.838.6641
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
 
 

Generated by mp version 2.7.3 on Sat Aug 24 19:59:58 2002