FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION

TITLE: FLORIDA DEPARTMENT OF TRANSPORTATION FIVE YEAR WORK PROGRAM - ENVIRONMENTAL PHASE - 2019

Geodataset Name:       FDOT_WP_ENV_2019
Geodataset Type:       SDE Feature Class
Geodataset Feature:    Polyline
Feature Count:         591
GENERAL DESCRIPTION:
This data set contains the FDOT Adopted Work Program (2020 - 2024) roadways designated as in the Environmental phase. These are projects where multiple alternatives are being evaluated. This data was created based on linear referencing, using the five year work program spreadsheet in conjunction with RCI Basemap Roads. This data was created based on linear referencing, using the five year work program spreadsheet in conjunction with RCI Basemap Roads.
DATA SOURCE(S):                    University of Florida GeoPlan Center
SCALE OF ORIGINAL SOURCE MAPS:     24000
GEODATASET EXTENT:                 State of Florida
PUBLICATION DATE: 2019 TIME PERIOD OF CONTENT: 2019 DOWNLOAD LINK: http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: FDOT_WP_ENV_2019
ITEM NAME WIDTH TYPE
OBJECTID
4 OID
Shape
4 Geometry
DISTRICT
2 String
WPITEM
6 String
WPITMSEG
2 String
COUNTY_CODE
255 String
COUNTY_NAME
12 String
DESCRIPTION
100 String
BEGIN_MILE
8 Double
END_MILE
8 Double
LENGTH
8 Double
PROJECT_TYPE
50 String
PHASE_NAME
50 String
FISCAL_YEAR
8 Double
AMOUNT
8 Double
BOXNAME
50 String
CATEGORY
50 String
WPITEM_SEG
8 Double
PHASE_YEAR
8 String
PHASE
3 String
LOC_ERROR
50 String
DESCRIPT
50 String
FGDLAQDATE
36 Date
AUTOID
4 Integer
SHAPE.LEN
0 Double

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description
OBJECTID Internal feature number.

Shape Feature geometry.

DISTRICT This field indicates the District where the project is located.

WPITEM 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.

WPITMSEG 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.

COUNTY_CODE County Code

COUNTY_NAME County Name

DESCRIPTION This represents the Local Name of the roadway or other.

BEGIN_MILE This represents the beginning milepost to 3 decimal places.

END_MILE This represents the ending milepost to 3 decimal places.

LENGTH This field describes the length of the project to 3 decimal places.

PROJECT_TYPE Type of Work

PHASE_NAME Phase name. Three letter code and written description.

FISCAL_YEAR 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)

AMOUNT The dollar amount (to the nearest dollar) of the record.

BOXNAME Further Description of the Project.

CATEGORY Undefined by Source

WPITEM_SEG Item number and item segment combined. This field created by concatenating WPITEM and WPITMSEG.

PHASE_YEAR Three letter phase code concatenated with year

PHASE Three letter phase code.

LOC_ERROR This field is created from the linear referencing command. Values indicate if there were errors during linear referencing process.

DESCRIPT GeoPlan added field based on phase name

FGDLAQDATE Date GeoPlan acquired data from source.

AUTOID Unique ID added by GeoPlan

SHAPE.LEN Length in meters


USER NOTES:
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.
GeoPlan relied on the integrity of the attribute information within
the original data.
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.

To be used in EST

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

FDOT only

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

REFERENCES:


DATA LINEAGE SUMMARY:
GeoPlan center acquired the work program spreadsheet in July 2019
from Roger Kreisel of FDOT.

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: 
GISROAD20190715.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 2019.
Process Date: 20190715

Individual phases were selected out from the work program spreadsheet. The following phases were exported to a new layer: CST = CONSTRUCTION DSB = DESIGN BUILD ENV = ENVIRONMENTAL PDE = PROJECT DEVELOPMENT AND ENVIRONMENT PE = PRELIMINARY ENGINEERING PLN = PLANNING ROW = RIGHT OF WAY The layers were renamed to the following: FDOT_WP_CST FDOT_WP_DSB FDOT_WP_ENV FDOT_WP_PDE FDOT_WP_PE FDOT_WP_PLN FDOT_WP_ROW Process Date: 20190715
Metadata imported. Process Date: 20190725
Dataset copied. Process Date: 20190725
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:
University of Florida GeoPlan Center
GeoPlan
431 Architecture Building
Gainesville, FL
32611
n/a

www.fgdl.org data@fgdl.org Sam Palmer

FGDL CONTACT:
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