This data set contains the FDOT Work Program roadways. This data was created based on linear referencing, using the five year work program spreadsheet in conjunction with RCI Basemap Roads.
To be used in EST
The work program spreadsheet is used by the FDOT to report on its Work Program of road, bridge, freight logistics and passenger operations, maintenance, planning, research, and other transportation related projects. The Department strives to maintain the stability of the Work Program; however, updated cost estimates, revised schedules, and other events outside the Department's control, such as changes in revenue estimates, all necessitate modifications to the Work Program during the course of the year. Users of the data contained in the accompanying file should bear this in mind and may wish to consider confirming project specific information with the Department's District Offices (Or at our Work Program Application site) for changes that may have occurred since the last posting.
publication date
431 Architecture Building
GeoPlan relied on the integrity of the attribute information within the original data.
This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology
This data is provided 'as is' by GeoPlan and is complete to our knowledge.
This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan
Spatial and Attribute Information
GeoPlan center acquired the following work program spreadsheet in July 2015: http://www2.dot.state.fl.us/fmsupportapps/WorkProgram/Support/Download.aspx The Item Segment field was used from the above spreadsheet to execute linear referencing to create line work from the spreadsheet records. The event theme used for the linear referencing command was the RCI_GAMING layer. This layer is generated daily based on a csv file that is received daily from FDOT work program and is created via linear referencing with RCI Basemap as the event theme. The particular csv file that was used was: GISROAD20150708.CSV Records were removed that had BEGIN_MILE = 0 AND END_MILE = 0 (Please note: COUNTY_CODE = 99 are now present, in FDOT_WP_2014 and earlier these records were removed) The RCI Basemap that was used was from July 2015.
Internal feature number.
ESRI
Feature geometry.
ESRI
This field indicates the District where the project is located.
FDOT
This field is the identifying sequential number assigned to each work program item. This number is assigned by the system. This is a six digit field in character format, with numeric data.
FDOT
The Item segment may be used to segment a project for scheduling or funding reasons. Item segments may be used when the boundaries of construction projects are different from the PE and/or ROW phase of a 'Project', or it is desirable to use the same item number to track projects along a corridor. For example, the department may want or need to let different segments at different times. Item segments may not cross county lines, except for district wide items.
FDOT
County Code
FDOT
County Name
FDOT
This represents the Local Name of the roadway or other.
FDOT
This represents the beginning milepost to 3 decimal places.
FDOT
This represents the ending milepost to 3 decimal places.
FDOT
This field describes the length of the project to 3 decimal places.
FDOT
Type of Work
FDOT
Phase name. Three letter code and written description.
FDOT
The year range of the record (Department's Fiscal Year Range is July through June. Example: Fiscal Year 2013 = 7/1/2012 - 6/30/2013)
FDOT
The dollar amount (to the nearest dollar) of the record.
FDOT
Further Description of the Project.
FDOT
Undefined by Source
FDOT
Item number and item segment combined. This field created by concatenating WPITEM and WPITMSEG.
GeoPlan
Three letter phase code concatenated with year
GeoPlan
Three letter phase code.
GeoPlan
This field is created from the linear referencing command. Values indicate if there were errors during linear referencing process.
GeoPlan
GeoPlan added field based on phase name
GeoPlan
Date GeoPlan acquired data from source.
GeoPlan
Unique ID added by GeoPlan
GeoPlan
Length in meters
GeoPlan
431 Architecture PO Box 115706
The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist. Furthermore, the GIS data available in the FGDL are provided 'as is'. The University of Florida GeoPlan Center makes no warranties, guaranties or representations as to the truth, accuracy or completeness of the data provided by the data sources. The University of Florida GeoPlan Center makes no representations or warranties about the quality or suitability of the materials, either expressly or implied, including but not limited to any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. The University of Florida GeoPlan Center shall not be liable for any damages suffered as a result of using, modifying, contributing or distributing the materials. A note about data scale: Scale is an important factor in data usage. Certain scale datasets are 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:125000 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 analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: http://geoplan.ufl.edu/education.html
431 Architecture Building