USGS 1:24,000 DLG Roads

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: St Johns River Water Management District
Originator: U.S. Geological Survey EROS Data Center (EDC)
Publication_Date: October 2002
Publication_Time: Unknown
Title: USGS 1:24,000 DLG Roads
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Palatka, Florida
Publisher: St. Johns River Water Management District
Other_Citation_Details:
Original DLG source US Geological Survey Sioux Falls, SD 57198 USA
Online_Linkage:
Server=earth; Service=port:5150; User=gislib; Version=SDE.DEFAULT
Description:
Abstract:
The DLG/SDTS data were created by reformating DLG-O data into the SDTS standard. The SDTS transportation catagory quads that are within St Johns River Water Management District were downloaded from the USGS site and then mapjoined into a District wide coverage. This layer also includes those quads that were processed by CognoCarta GIS.

Digital line graph (DLG) data are digital representations of cartographic information. DLGs of map features are converted to digital form from maps and related sources. Large-scale DLG data are derived from USGS 1:20,000-, 1:24,000-, and 1:25,000-scale 7.5 minute topographic quadrangle maps and are available in nine categories: (1) hypsography, (2) hydrography, (3) vegetative surface cover, (4) non-vegetative features, (5) boundaries, (6) survey control and markers, (7) transportation, (8) manmade features, and (9) Public Land Survey System. All DLG Data distributed by the USGS - Level 3 (DLG-3), which means the data contain a full range of attribute codes, have full topological structuring, and have passed certain quality-control checks.

Purpose:
DLG's depict information about geographic features on or near the surface of the Earth, terrain, and political and administrative units. These data were collected as part of the National Mapping Program
Supplemental_Information:
There are two tiles in Northeast Florida, Edgewater and New Smyrna Beach that have both arc errors and attribute errors. When the USGS DOQQ is placed behind the arcs it cannot be determined what polygons or arcs match each other along the western part of the border of these two tiles. The explaination to this was given by the USGS as follows: "The New Smyrna Beach quad was part of the Palatka, FL NAD27->NAD83 conversion only. The Edgewater, FL quad was part of the Orlando, FL Digital Limited Update -- archived into the data base in April, 2000 When exterior edge alignment was performed on the Orlando project, the (unrevised) New Smyrna Beach hydro file was pulled from the data base and the edge flags set. Because of the edge flag change, as the Orlando project was archived into the data base, the New Smyrna Beach file was also resubmitted." Full explanation of Revision Standards can be found at: <http://rockyweb.cr.usgs.gov/nmpstds/dlgstds.html> under Part 1: Template Development and Use, Standards for 1:24,000-Scale Digital Line Graphs and Quadrangle <http://rockyweb.cr.usgs.gov/nmpstds/acrodocs/dlgqmap/1dqm0401.pdf>
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: unknown
Currentness_Reference: ground condition
Status:
Progress: In work
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -82.633235
East_Bounding_Coordinate: -80.279000
North_Bounding_Coordinate: 30.879803
South_Bounding_Coordinate: 27.366069
Keywords:
Theme:
Theme_Keyword_Thesaurus: SJRWMD-GIS Metadata Thesaurus
Theme_Keyword: Digital Line Graphs (DLG)
Theme_Keyword: transportation
Theme_Keyword: roads
Theme_Keyword: major roads
Theme_Keyword: interstate highways
Theme_Keyword: state highways
Theme_Keyword: U. S. highways
Theme_Keyword: turnpikes
Theme_Keyword: local roads
Theme_Keyword: large scale
Place:
Place_Keyword_Thesaurus: SJRWMD-GIS Metadata Thesaurus
Place_Keyword: Florida
Place_Keyword: St. Johns River Water Management District
Place_Keyword: Counties
Place_Keyword: Alachua County
Place_Keyword: Baker County
Place_Keyword: Bradford County
Place_Keyword: Brevard County
Place_Keyword: Clay County
Place_Keyword: Duval County
Place_Keyword: Flagler County
Place_Keyword: Indian River County
Place_Keyword: Lake County
Place_Keyword: Marion County
Place_Keyword: Nassau County
Place_Keyword: Okeechobee County
Place_Keyword: Orange County
Place_Keyword: Osceola County
Place_Keyword: Polk County
Place_Keyword: Putnam County
Place_Keyword: Seminole County
Place_Keyword: St. Johns County
Place_Keyword: Volusia County
Access_Constraints: None
Use_Constraints:
The St. Johns River Water Management District prepares and uses information for its own purposes and this information may not be suitable for other purposes. This information is provided "as is". Further documentation of this data can be obtained by contacting: St. Johns River Water Management District, Division of Integrated Application Systems, Post Office Box 1429, Palatka, Florida, 32178-1429, (386) 329-4500.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: St. Johns River Water Management District
Contact_Position: GIS Data Manager, Information Resources Department
Contact_Address:
Address_Type: mailing address
Address: P.O Box 1429
City: Palatka
State_or_Province: FL
Postal_Code: 32178-1429
Contact_Voice_Telephone: (386) 329-4500
Contact_Electronic_Mail_Address: gis_support@sjrwmd.com
Hours_of_Service: 0800 - 1700 EST
Browse_Graphic:
Browse_Graphic_File_Name: <http://intraweb/gisdoc/cf/smms0/gifimages/sdtsdlgrds.gif>
Browse_Graphic_File_Type: GIF
Native_Data_Set_Environment:
Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 3; ESRI ArcCatalog 8.3.0.800

Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report: Refer to Positional_Accuracy element
Logical_Consistency_Report:
Topological requirements include: lines must begin and end at node points, lines must connect to each other at nodes, lines do not extend through nodes, left and right areas are defined for each line element and are consistent throughout the file, and the lines representing the limits of the file (neatline) are free of gaps. The tests of logical consistency were performed by the USGS PROSYS program. The Neatline was generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region were ignored and all data crossing these geographically straight lines were clipped at the neatline. Data within a specified tolerance of the neatline were snapped to the neatline. Neatline straightening aligned the digitized edges of the digital data with the generated neatline, that is, with the longitud/latitude lines in geographic coordinates. All internal areas were tested for closure using PROSYS.
Completeness_Report:
For Digital Revision Status = Not Revised: Data completeness reflects the content of the source quadrangle. Features may have been eliminated or generalized on the source graphic, due to scale and legibility constraints. For Digital Revision Status = Limited Update: This file has undergone limited update digital revision. The file contains only: those features that are photoidentifiable on monoscopic source, supplemented with limited ancillary source, and those features, present on the original source quadrangle, that can not be reliably photoidentified but that are not considered particularly prone to change. For Digital Revision Status = Standard Update: This file has undergone standard update digital revision. The data completeness of this file meets NMD Standards for feature content.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report: For Digital Revision Status = Not Revised
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
For Hypsography, Hydrography, and Survey Control and Markers Only: For digital Revision Status = Not revised:
Lineage:
Source_Information:
Source_Scale_Denominator: 24,000
Type_of_Source_Media: stable-base material
Source_Citation_Abbreviation: map1
Source_Contribution: spatial and attribute information
Process_Step:
Process_Description:
SDTS transportation datasets were downloaded from the USGS ftp site by individual quads. On completion of the download, the quads were converted into coverages using the sdts2cov.aml provided by the USGS. Topology was checked and any corrections required were made to the quads. Inorder to mapjoin all the quads certain items required removal using the DROPITEMS command in ARC/INFO. The number of items that were dropped varied by quad only those items consistent with all quads were retained. The quads were appended together and neatlines removed. The coverage was randomly checked for edgematching and cleaned using a fuzzy tolerance of 0.5. Detailed methodology and amls used can be found under enclosures.
Process_Date: OCT 2002
Process_Step:
Process_Description:
For Digital Revision Status = Not digitally revised: This Digital Line Graph was digitized from the USGS source quadrangle, by either the National Mapping Division, one of their cooperators or one of their contractors. The digital data were produced by one of the following methods, which all resulted in a scanning/digital resolution of at least 0.001 inches. Stable base scanning process: the resulting raster data were vectorized and then attributed on an interactive editing station: paper map scanning process: the resulting raster data were vectorized and then attributed on an interactive editing station. The stable base resulting raster data were then manually digitized and attributed on an interactive editing station. The paper map resulting raster data were then manually digitized and attributed on an interactive editing station. Manually digitizing from either a stable-based copy of the graphic material or a paper map using a digitizing table to capture the digital data; attribution was performed either as the data were digitized or on an interactive editing station after the digitizing was completed. The determination of the DLG production method was based on vaious criteria, including feature density, featuer symbology, and availability of production systems. Four control points corresponding to the four corners of the quadrangle were used for registration during data collection. An eight parameter projective transformation was performed on the coordinates used in the data collection and editing systems to register the digital data to the internal coordinates. The DLG data were checked for position and/or classification by one or more of the following processes: - comparing plots of the digital data to the graphic source or to the digital raster scan.
Source_Used_Citation_Abbreviation: map1
Process_Date: Unknown
Process_Step:
Process_Description:
For Digital Revision Status = Limited Update: This file has undergone limited update digital revision. Limited update revision uses monoscopic imagery and limited ancillary source with no field verification.
Source_Used_Citation_Abbreviation: DOQ1, DOQ2, DOQ3, DOQ4
Process_Date: Unknown
Process_Step:
Process_Description:
For Digital revision Status = Standard Update: This file has undergone standard update digital revision. Standard update revision uses stereoscopic imagery, with field verification.
Source_Used_Citation_Abbreviation: DOQ1, DOQ2, DOQ3, DOQ4
Process_Date: Unknown
Process_Step:
Process_Description:
Cognocarta process: Once individual tiles were downloaded from the USGS and converted into Arc Coverages using Scott Whitaker's (Mapping Division, USGS) sdts2acov.aml, the neatline was removed. Step two was to EDGEMATCH the coverages using the ARC feature class. Coverages were then MAPJOINED and BUILT to rebuild topology
Source_Used_Citation_Abbreviation: boundary
Process_Date: Unknown
Process_Step:
Process_Description: Dataset copied.

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: 396038
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: Point
Point_and_Vector_Object_Count: 4

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Transverse Mercator
Transverse_Mercator:
Scale_Factor_at_Central_Meridian: 0.999600
Longitude_of_Central_Meridian: -81.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.100000
Ordinate_Resolution: 0.100000
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: D_North_American_1983_HARN
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Datum_Name: National Geodetic Vertical Datum of 1929
Altitude_Resolution: 1.000000
Altitude_Distance_Units: meters
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates
Depth_System_Definition:
Depth_Datum_Name: Mean lower low water
Depth_Resolution: 1
Depth_Distance_Units: meters
Depth_Encoding_Method: Attribute values

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: GISLIB.TRANS_RDS_24K_USGS_2002
Attribute:
Attribute_Label: OBJECTID
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: ENTITY_LABEL
Attribute_Definition: transportation attribute code
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: ENTITY_DEF
Attribute_Definition: description of transportation feature and defines entity label
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Whole numbers that are automatically generated.
Attribute:
Attribute_Label: ARBITRARY_EXT
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Whole numbers that are automatically generated.
Attribute:
Attribute_Label: RELATION_TO_GROU
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Whole numbers that are automatically generated.
Attribute:
Attribute_Label: VERTICAL_RELATIO
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Whole numbers that are automatically generated.
Attribute:
Attribute_Label: OPERATIONAL_STAT
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Positive real numbers that are automatically generated.
Attribute:
Attribute_Label: ACCESS_RESTRICTI
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: OLD_RAILROAD_GRA
Attribute_Definition_Source: ESRI
Attribute:
Attribute_Label: WITH_RAILROAD
Attribute:
Attribute_Label: COVERED
Attribute:
Attribute_Label: HISTORICAL
Attribute:
Attribute_Label: LIMITED_ACCESS
Attribute:
Attribute_Label: PHOTOREVISED
Attribute_Definition: indicates if there has been a photo revision
Attribute:
Attribute_Label: LANES
Attribute_Definition: Number of lanes
Attribute:
Attribute_Label: ROAD_WIDTH
Attribute_Definition: width of road
Attribute:
Attribute_Label: BEST_ESTIMATE
Attribute:
Attribute_Label: FUNCTIONAL_CLASS
Attribute:
Attribute_Label: ROUTE_NUMBER
Attribute_Definition: Primary route number
Attribute:
Attribute_Label: ROUTE_NUMBER1
Attribute_Definition: Alternate or additional route number
Attribute:
Attribute_Label: ROUTE_NUMBER2
Attribute_Definition: Alternate or additional route number
Attribute:
Attribute_Label: ROUTE_NUMBER3
Attribute_Definition: Alternate or additional route number
Attribute:
Attribute_Label: ROUTE_TYPE
Attribute:
Attribute_Label: ROUTE_TYPE1
Attribute:
Attribute_Label: ROUTE_TYPE2
Attribute:
Attribute_Label: ROUTE_TYPE3
Attribute:
Attribute_Label: CARTO
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: SHAPE.LEN
Attribute_Definition: Length of feature in internal units.
Overview_Description:
Entity_and_Attribute_Overview:
DLG3 Attibute codes are used to describe the physical and cultural characteristics of DLG node, line, and area elements. Attribute codes are used to reduce redundant information, provide enough reference information to support integration with larger data base, and describe the relationships between cartographic elements. Each DLG element has one or more attribute codes composed of a three digit major code and a four digit minor code. For example, with the 1:24000-scale DLG data, the line attribute code 050 0412 has a major code (050), meaning hydrography, with a minor code (0412) meaning stream.

Entable Label coding:

Entity_label Description ----------- ---------- 1700005 Cul-de-sac 1700201 Primary route, class 1, symbol undivided 1700202 Primary route, class 1, symbol divided by centerline 1700203 Primary route, class 1, divided, lanes separated 1700204 Primary route, class 1, one-way, other than divided highway 1700205 Secondary route, class 2, symbol undivided 1700206 Secondary route, class 2, symbol divided by centerline 1700207 Secondary route, class 2, symbol divided, lanes separated 1700208 Secondary route, class 2, one-way, other than divided highway 1700209 Road, class 3, symbol undivided 1700210 Road, class 4 1700211 Trail 1700212 Road, class 5, four-wheel drive 1700213 Footbridge 1700214 Road ferry crossing 1700217 Road, class 3, symbol divided by centerline 1700218 Road, class 3, symbol divided, lanes separated 1700219 Road, class 4, one-way 1700221 Road, class 3, one-way 1700222 Road in transition 1700223 Road in service facility, rest area, or viewpoint 1700401 Traffic circle 1700402 Ramp in interchange 1700403 Tollgate 1700404 Weigh station 1700405 Nonstandard section of road

Entity_and_Attribute_Detail_Citation:
U.S. Department of the Interior, U.S. Geological Survey, 1987 Digital Line Graphs from 1:24000-Scale Maps--Data Users Guide 1; Reston, Virginia Softcopies in ASCII, Wordperfect, and PostScript Format available at: <ftp://mapping.usgs.gov/pub/ti/DLG/>. U.S. Department of the Interior, U.S. Geological Survey, 1990, Standards for Digital Line Graphs, Reston, VA, 1994.

Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: St. Johns River Water Management District
Contact_Position: GIS Data Manager, Information Resources Department
Contact_Address:
Address_Type: mailing address
Address: Post Office Box 1429
City: Palatka
State_or_Province: Florida
Postal_Code: 32178-1429
Country: USA
Contact_Voice_Telephone: (386) 329-4500
Contact_Electronic_Mail_Address: gis_support@sjrwmd.com
Hours_of_Service: 0800-1700 EST
Resource_Description: Downloadable Data
Distribution_Liability:
The St. Johns River Water Management District prepares and uses information for its own purposes and this information may not be suitable for other purposes. This information is provided "as is". Further documentation of this data can be obtained by contacting: St. Johns River Water Management District, Division of Integrated Application Systems, Post Office Box 1429, Palatka, Florida, 32178-1429, (386) 329-4500.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: ARCE
Format_Version_Number: v8.2
Format_Specification: ARC/INFO Export Format - UNIX Compression
File_Decompression_Technique: Winzip
Transfer_Size: 119.224
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://www.sjrwmd.com>
Offline_Option:
Offline_Media: CD-ROM
Fees: $40 per CD
Ordering_Instructions:
There is no charge for downloading data from the DISTRICT web site at <http://www.sjrwmd.com>. Data can be orded on CD-ROM as instructed on the web site.
Turnaround: 10 working days
Custom_Order_Process:
1. Use the DISTRICT website: <http://www.sjrwmd.com> to download data, or 2. Call or email to organizations listed under Distributor. Spatial data are in ARC/INFO interchange formats.
Technical_Prerequisites:
Internet access / Unzip, Winzip / To import coverage: ESRI ArcInfo workstation, ArcView 3.2X Import 7.1 Utility, or ArcToolBox. / To use coverage: ESRI ArcInfo, ArcView, ArcGIS 8.2, or ArcExplorer; AutoCAD 2002 Map or Land Development Desktop.

Metadata_Reference_Information:
Metadata_Date: 20030527
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: St. Johns River Water Management District
Contact_Position: GIS Data Manager, Information Resources Department
Contact_Address:
Address_Type: mailing address
Address: Post Office Box 1429
City: Palatka
State_or_Province: Florida
Postal_Code: 32178-1429
Country: USA
Contact_Voice_Telephone: (386) 329-4500
Contact_Electronic_Mail_Address: gis_support@sjrwmd.com
Hours_of_Service: 0800-1700 EST
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.33 on Fri Nov 07 16:14:43 2003