FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: FLORIDA DEPARTMENT OF TRANSPORTATION DISTRICTS Geodataset Name: DOTBND Geodataset Type: Shapefile Geodataset Feature: Polygon Feature Count: 7 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): University of Florida GeoPlan Center SCALE OF ORIGINAL SOURCE MAPS: 100000 DATE OF AUTOMATION OF SOURCE: 19990100 GEODATASET EXTENT: |
FEATURE ATTRIBUTE TABLES:
Datafile Name: DOTBND.DBF
ITEM NAME | WIDTH | TYPE | N. DECIMAL DEGREES |
FID
|
4 | OID | --- |
Shape
|
0 | Geometry | --- |
DOTDIST
|
2 | Number | --- |
DESCRIPT
|
50 | String | --- |
OBJECTID
|
10 | Number | --- |
AUTOID
|
10 | Number | --- |
SHAPE_AREA
|
19 | Float | 11 |
SHAPE_LEN
|
19 | Float | 11 |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
FID |
Internal feature number. |
|
Shape |
Feature geometry. |
|
DOTDIST |
FDOT District Number |
|
DESCRIPT |
FDOT District |
|
OBJECTID |
ESRI Unique ID |
|
AUTOID |
FGDL Unique ID |
|
SHAPE_AREA |
Area of feature in internal units squared. |
|
SHAPE_LEN |
Length of the line segment |
Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s." |
Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s." |
Relied on the integrity of the attribute information within the original data layer. |
|
This dataset provides location and attribute information on the FDOT district boundaries. |
|
|
THE DATA INCLUDED IN THIS APPLICATION ARE BASED ON INTERPRETATION OF AVAILABLE INFORMATION AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. Scale is an important factor in data usage. Certain scale data sets are not suitable for some projects, analysis, or modeling purposes. Please be sure you are using the best available data. 1:24000 scale data sets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale data sets are recommended for projects that are at the multi-county or regional level. 1:250000 scale data sets are recommended for projects that are at the regional or state level or larger. |
|
The process step describes, in general, the process used in the production of data sets. The originating agencies created the original spatial coverage. GeoPlan, during the QA/QC process included the following aspects: (1) Reprojected data to FGDL Albers (2) Set Precision to DOUBLE (3) Set Tolerances to FGDL Standards. (4) Descript item was added and set equal to the DOTDIST Process Date: 20000000 |
Projection ALBERS Datum HPGN Units METERS Spheroid GRS1980 1st Standard Parallel 24 0 0.000 2nd Standard Parallel 31 30 0.000 Central Meridian -84 00 0.000 Latitude of Projection's Origin 24 0 0.000 False Easting (meters) 400000.00000 False Northing (meters) 0.00000
DATA SOURCE CONTACT (S):
Name: Abbr. Name: Address: Phone: Web site: E-mail: Contact Person: Phone: E-mail: |
FGDL 431 Architecture Building PO Box 115706 Gainesville, FL 232611-5706 (352) 3920997 |
Name: FLORIDA GEOGRAPHIC DATA LIBRARY Abbr. Name: FGDL Address: Florida Geographic Data Library 431 Architecture Building PO Box 115706 Gainesville, FL 32611-5706 Web site: http://www.fgdl.org Contact FGDL: Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html