Geodataset Name:       MAJRDS_APR06
Geodataset Type:       SHAPEFILE
Geodataset Feature:    LINE

DATA SOURCE(S):                    Florida Department of Transportation
SCALE OF ORIGINAL SOURCE MAPS:     1:24,000
DATE OF AUTOMATION OF SOURCE:      20060401
GEODATASET EXTENT:                 State of Florida

FEATURE ATTRIBUTE TABLES:

Datafile Name: MAJRDS_APR06.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
FID	Internal feature number.
Shape	Feature geometry.
ROADWAY	Road system designation used by RCI as the roadway identifier.
BEGIN_POST	Start measure of the route in miles from RCI.
END_POST	End measure of the route in miles from RCI.
NAME	Name Posted or known local street name
FUNCLASS	Federal Functional Classification code characterizing the service provided 00 = Roadway feature 01 = Principal Arterial-Interstate RURAL 02 = Principal Arterial-Other RURAL 06 = Minor Arterial RURAL 07 = Major Collector RURAL 08 = Minor Collector RURAL 09 = Local RURAL 11 = Principal Arterial-Interstate URBAN 12 = Principal Arterial-Freeways and Expressways 14 = Other Principal Arterial URBAN 16 = Minor Arterial URBAN 17 = Collector URBAN 19 = Local URBAN
DESCRIPT	Description based on the Federal Functional Classification code
USROUTE	Lowest numerical posted US Route number
STROUTE	Lowest numerical posted State Road number. FDOT roads are categorized as Interstate, U.S Route, State and County roads and are collectively called the "State Highway System" (SHS). All SHS roads have a state road number, indicated with a prefix of SR. County roads are also included in this characteristic, with a prefix of CR. If a road transfers from the SHS, the State Road Number is changed to a County Road Number in the database by changing the SR prefix to OS (Old State Road Number). After one year, the OS is changed to CR.
RD_STATUS	Status of the roadway or section or roadway. Pending (new construction anticipated to be added to the SHS). Active (route owned and maintained by FDOT)-Inactive (route kept for historic purposes). Active/Exclusive (ramps,frontage roads, etc.). Active/Off System (NOT part of the SHS and NOT maintained by FDOT). Active with Combination (roadway segment with two or more status values)
LENGTH	Length in meters
FGDLAQDATE	Date FGDL acquired data.

USER NOTES:

GeoPlan relied on the integrity of the attribute information within the original data.

The RCI is a computerized database of physical and administrative data related to the roadway networks that are either maintained by or are of special interest to the Department. In addition to data required by the Department, the RCI contains other data as required for special Federal and State reporting obligations. The RCI is maintained by District and Central Office personnel. While there are many other important databases maintained by the Department (several that contain more highly technical data such as bridge specifications, highway design, or pavement) the RCI remains the largest database with over 1 million records. (Chapter 1 Page 1 RCI Office Handbook)

A note concerning data scale: Scale is an important factor in data usage. Certain scale datasetsare not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data. 1:24000 scale datasets 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 datasets are recommended for projects that are at the multi-county or regional level. 1:250000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References sectionand the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: http://www.geoplan.ufl.edu/education.html

REFERENCES:

http://www.dot.state.fl.us/planning/statistics/RCI/default.htm

DATA LINEAGE SUMMARY:

The data set was taken from the Florida Department of Transportation Statistics Office from the following webpage: http://www.dot.state.fl.us/planning/statistics/gis The data set was originally downloaded in April 2006 as the RCI basemap. Specificinstructions, created by URS Corporation and the GeoPlan Center, were carried out. The data set is then to be updated on a regular basis. The data was originally in TM Zone 17, Nad83, units meters. The data was projected to Albers HPGN. -Download the most recent Statewide ARC/Info basemap coverage -Join the road status descriptions to the status event table -Add a Route Event theme using the road status descriptions -Add a Route Event theme using the local names -Add a Route Event theme using the State Road Numbers -Add a Route Event theme using the Federal Highway Numbers -Add a description field to be associated with the Functional Classification values based on the following values: FUNCLASS DESCRIPT 00 - Roadway Feature 01 RURAL - Principal Arterial--Interstate 02 RURAL - Principal Arterial--Other 06 RURAL - Minor Arterial 07 RURAL - Major Collector 08 RURAL - Minor Collector 09 RURAL - Local 11 URBAN - Principal Arterial--Interstate 12 URBAN - Principal Arterial--Other Freeways and Expressways 14 URBAN - Other Principal Arterial 16 URBAN - Minor Arterial 17 URBAN - Collector 19 URBAN - Local -Add a Route Event theme using the FDOT Functional Classifications -Select the primary route events from the "stroute Events" layer -Select the primary route events from the "usroute Events" layer -Use the ArcGIS 9.1 Route Events GeoProcessing Wizard to merge all route events -Export from Route Event to Shapefile -Select the existing roadways from the "Roadway_road_status Events" layer -Combine the "localnam Events" layer with the "stroute Events" layer -Finally, add the following fields: USROUTE, text, 8 STROUTE, text, 8 RD_STATUS, text, 25 LENGTH, double, precision 18, scale 11 -Delete the columns "ROUTE," "ROUTE2," and "DESCR2." -Project the shape file to the standard FGDL projection. -Update the Length field with the length (in meters) for each segment -Create a shapefile without any remaining zero-length features. Process Date: 20060401

MAP PROJECTION PARAMETERS:

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:

Florida Department of Transportation Transportation Statistics Office
FDOT
Mail Station 27, 605 Suwannee Street
Tallahassee, Florida
32399-0450
(850) 414-4848


www.dot.state.fl.us

Michael Dancy, Paul O'Rourke, Mark Welsh

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