USGS 1:24,000 DLG Roads

Data format: SDE Feature Class

File or table name: GISLIB.TRANS_RDS_24K_USGS_2002

Coordinate system: Transverse Mercator

Theme keywords: Digital Line Graphs (DLG), transportation, roads, major roads, interstate highways, state highways, U. S. highways, turnpikes, local roads, large scale

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.

FGDC and ESRI Metadata:

Metadata elements shown with blue text are defined in the Federal Geographic Data Committee's (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM). Elements shown with green text are defined in the ESRI Profile of the CSDGM. Elements shown with a green asterisk (*) will be automatically updated by ArcCatalog. ArcCatalog adds hints indicating which FGDC elements are mandatory; these are shown with gray text.

Identification Information:


Citation:
Citation information:
Originators: St Johns River Water Management District, U.S. Geological Survey EROS Data Center (EDC)


Title:
USGS 1:24,000 DLG Roads
*File or table name: GISLIB.TRANS_RDS_24K_USGS_2002


Publication date: October 2002
Publication time: Unknown
*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

*Language of dataset: en


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

Local bounding coordinates:
*Left bounding coordinate: 343859.502422
*Right bounding coordinate: 568919.502422
*Top bounding coordinate: 3416281.412492
*Bottom bounding coordinate: 3027970.812492

Keywords:
Theme:
Theme keywords: Digital Line Graphs (DLG), transportation, roads, major roads, interstate highways, state highways, U. S. highways, turnpikes, local roads, large scale
Theme keyword thesaurus: SJRWMD-GIS Metadata Thesaurus

Place:
Place keywords: Florida, St. Johns River Water Management District, Counties, Alachua County, Baker County, Bradford County, Brevard County, Clay County, Duval County, Flagler County, Indian River County, Lake County, Marion County, Nassau County, Okeechobee County, Orange County, Osceola County, Polk County, Putnam County, Seminole County, St. Johns County, Volusia County
Place keyword thesaurus: SJRWMD-GIS Metadata Thesaurus

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 dataset format: SDE Feature Class
*Native data set environment:
Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 3; ESRI ArcCatalog 8.3.0.800


Back to Top
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.

Process date: Unknown


Source used citation abbreviation:
map1


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.

Process date: Unknown


Source used citation abbreviation:
DOQ1, DOQ2, DOQ3, DOQ4


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.

Process date: Unknown


Source used citation abbreviation:
DOQ1, DOQ2, DOQ3, DOQ4


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

Process date: Unknown


Source used citation abbreviation:
boundary


Process step:
Process description:
Dataset copied.

Back to Top
Spatial Data Organization Information:


*Direct spatial Rreference method: Vector


Point and vector object information:
SDTS terms description:
*Name: GISLIB.TRANS_RDS_24K_USGS_2002
*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

ESRI terms description:
*Name: GISLIB.TRANS_RDS_24K_USGS_2002
*ESRI feature type: Simple
*ESRI feature geometry: Polyline
*ESRI topology: FALSE
*ESRI feature count: 396038
*Spatial index: TRUE
*Linear referencing: FALSE


Back to Top
Spatial Reference Information:


Horizontal coordinate system definition:
Coordinate system name:
*Projected coordinate system name: NAD_1983_UTM_Zone_17N
*Geographic coordinate system name: D_North_American_1983_HARN

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

Back to Top
Entity and Attribute Information:


Detailed description:
*Name: GISLIB.TRANS_RDS_24K_USGS_2002


Entity type:
*Entity type label: GISLIB.TRANS_RDS_24K_USGS_2002
*Entity type type: Feature Class
*Entity type count: 396038

Attribute:
*Attribute label: OBJECTID
*Attribute alias: OBJECTID
*Attribute definition:
Internal feature number.
*Attribute definition source:
ESRI

*Attribute type: OID
*Attribute width: 4
*Attribute precision: 10
*Attribute scale: 0


Attribute domain values:
*Unrepresentable domain:
Sequential unique whole numbers that are automatically generated.


Attribute:
*Attribute label: ENTITY_LABEL
*Attribute alias: ENTITY_LABEL
Attribute definition:
transportation attribute code
Attribute definition source:
ESRI

*Attribute type: String
*Attribute width: 7
*Attribute precision: 0
*Attribute scale: 0


Attribute domain values:
Unrepresentable domain:
Coordinates defining the features.


Attribute:
*Attribute label: ENTITY_DEF
*Attribute alias: ENTITY_DEF
Attribute definition:
description of transportation feature and defines entity label
Attribute definition source:
ESRI

*Attribute type: String
*Attribute width: 60
*Attribute precision: 0
*Attribute scale: 0


Attribute domain values:
Unrepresentable domain:
Whole numbers that are automatically generated.


Attribute:
*Attribute label: ARBITRARY_EXT
*Attribute alias: ARBITRARY_EXT
Attribute definition source:
ESRI

*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute domain values:
Unrepresentable domain:
Whole numbers that are automatically generated.


Attribute:
*Attribute label: RELATION_TO_GROU
*Attribute alias: RELATION_TO_GROU
Attribute definition source:
ESRI

*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute domain values:
Unrepresentable domain:
Whole numbers that are automatically generated.


Attribute:
*Attribute label: VERTICAL_RELATIO
*Attribute alias: VERTICAL_RELATIO
Attribute definition source:
ESRI

*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute domain values:
Unrepresentable domain:
Whole numbers that are automatically generated.


Attribute:
*Attribute label: OPERATIONAL_STAT
*Attribute alias: OPERATIONAL_STAT
Attribute definition source:
ESRI

*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute domain values:
Unrepresentable domain:
Positive real numbers that are automatically generated.


Attribute:
*Attribute label: ACCESS_RESTRICTI
*Attribute alias: ACCESS_RESTRICTI
Attribute definition source:
ESRI

*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute domain values:
Unrepresentable domain:
Sequential unique whole numbers that are automatically generated.


Attribute:
*Attribute label: OLD_RAILROAD_GRA
*Attribute alias: OLD_RAILROAD_GRA
Attribute definition source:
ESRI

*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: WITH_RAILROAD
*Attribute alias: WITH_RAILROAD


*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: COVERED
*Attribute alias: COVERED


*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: HISTORICAL
*Attribute alias: HISTORICAL


*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: LIMITED_ACCESS
*Attribute alias: LIMITED_ACCESS


*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: PHOTOREVISED
*Attribute alias: PHOTOREVISED
Attribute definition:
indicates if there has been a photo revision

*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: LANES
*Attribute alias: LANES
Attribute definition:
Number of lanes

*Attribute type: SmallInteger
*Attribute width: 2
*Attribute precision: 2
*Attribute scale: 0


Attribute:
*Attribute label: ROAD_WIDTH
*Attribute alias: ROAD_WIDTH
Attribute definition:
width of road

*Attribute type: SmallInteger
*Attribute width: 2
*Attribute precision: 3
*Attribute scale: 0


Attribute:
*Attribute label: BEST_ESTIMATE
*Attribute alias: BEST_ESTIMATE


*Attribute type: String
*Attribute width: 1
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: FUNCTIONAL_CLASS
*Attribute alias: FUNCTIONAL_CLASS


*Attribute type: String
*Attribute width: 2
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: ROUTE_NUMBER
*Attribute alias: ROUTE_NUMBER
Attribute definition:
Primary route number

*Attribute type: String
*Attribute width: 7
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: ROUTE_NUMBER1
*Attribute alias: ROUTE_NUMBER1
Attribute definition:
Alternate or additional route number

*Attribute type: String
*Attribute width: 7
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: ROUTE_NUMBER2
*Attribute alias: ROUTE_NUMBER2
Attribute definition:
Alternate or additional route number

*Attribute type: String
*Attribute width: 7
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: ROUTE_NUMBER3
*Attribute alias: ROUTE_NUMBER3
Attribute definition:
Alternate or additional route number

*Attribute type: String
*Attribute width: 7
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: ROUTE_TYPE
*Attribute alias: ROUTE_TYPE


*Attribute type: String
*Attribute width: 9
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: ROUTE_TYPE1
*Attribute alias: ROUTE_TYPE1


*Attribute type: String
*Attribute width: 9
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: ROUTE_TYPE2
*Attribute alias: ROUTE_TYPE2


*Attribute type: String
*Attribute width: 9
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: ROUTE_TYPE3
*Attribute alias: ROUTE_TYPE3


*Attribute type: String
*Attribute width: 9
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: CARTO
*Attribute alias: CARTO


*Attribute type: String
*Attribute width: 5
*Attribute precision: 0
*Attribute scale: 0


Attribute:
*Attribute label: SHAPE
*Attribute alias: SHAPE
*Attribute definition:
Feature geometry.
*Attribute definition source:
ESRI

*Attribute type: Geometry
*Attribute width: 4
*Attribute precision: 0
*Attribute scale: 0


Attribute domain values:
*Unrepresentable domain:
Coordinates defining the features.


Attribute:
*Attribute label: SHAPE.LEN
*Attribute alias: SHAPE.LEN
Attribute definition:
Length of feature in internal units.

*Attribute type: Double
*Attribute width: 0
*Attribute precision: 0
*Attribute scale: 0


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.

Back to Top
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.


Back to Top
Metadata Reference Information:


*Metadata date: 20030527


*Language of metadata: en


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

Back to Top
Binary Enclosures:


Thumbnail:

Back to Top