FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION
ETDM PROJECT SEGMENT SPATIAL VIEW
Geodataset Name: SV_SEGMENTS Geodataset Type: SDE Spatial View Geodataset Feature: LINE
GENERAL DESCRIPTION:
This dataset contains planned transportation projects that are being reviewed through the Efficient Transportation Decision Making (ETDM) Process.
DATA SOURCE(S): Florida Department of Transportation (FDOT)
Florida Metropolitan Planning Organizations (MPOs)
SCALE OF ORIGINAL SOURCE MAPS: Varies
DATE OF AUTOMATION OR SOURCE: 2002 with on-going updates
GEODATASET EXTENT: State of Florida
FEATURE ATTRIBUTE TABLES
Alias Type Precision Width Indexed? --------------------------------------------------------------------- SHAPE SHAPEMULTIPOINT 0 0 false PK_PROJECT DOUBLE 5 11 false PRJNAME CHAR 0 150 false ETDM_STAGE CHAR 0 20 false COST DOUBLE 2 14 false MODE_ROADWAY CHAR 0 1 false MODE_TRANSIT CHAR 0 1 false MODE_BIKE CHAR 0 1 false MODE_PEDESTRIAN CHAR 0 1 false TOTAL_LENGTH FLOAT 3 7 false PROJECT_TYPE CHAR 0 30 false PLAN_ORG CHAR 0 50 false PK_SEGMENT DOUBLE 5 11 false CURR_YEAR SHORT 0 4 false CURR_AADT LONG 0 8 false CURR_LANES SHORT 0 2 false CURR_CONFIG CHAR 0 15 false LRTP_YEAR SHORT 0 4 false COST_AADT LONG 0 8 false COST_LANES LONG 0 8 false COST_CONFIG CHAR 0 15 false NEED_AADT LONG 0 8 false NEED_LANES SHORT 0 2 false NEED_CONFIG CHAR 0 15 false STREET_NAME CHAR 0 30 false FROM_STREET CHAR 0 30 false TO_STREET CHAR 0 30 false SEGMENT_LENGTH FLOAT 3 7 false ROADWAY_FCLASS CHAR 0 60 false
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
ITEM DESCRIPTION
SHAPE Field automatically generated in ArcSDE to store
information about the feature shape
PK_PROJECT Primary Key from projects table that uniquely
identifies the project throughout the ETDM process
PRJNAME Project name
ETDM_STAGE Current stage of the project in the ETDM process
COST Estimated project cost from the Needs Plan
MODE_ROADWAY "Y", if project includes roadway mode of transportation
MODE_TRANSIT "Y", if project includes transit mode of transportation
MODE_BIKE "Y", if project includes bicycle mode of transportation
MODE_PEDESTRIAN "Y", if project includes pedestrian mode of transportation
TOTAL_LENGTH Total project length in miles
PROJECT_TYPE Type of project:
New Alignment
Widening
Traffic Operation Enhancement
PLAN_ORG Name of organization planning the project
FK_SEGMENT Primary Key from segments table that uniquely
identifies the project segment throughout the ETDM process
CURR_YEAR 4-digit year when current conditions were observed
CURR_AADT Existing traffic volume
CURR_LANES Existing number of lanes
CURR_CONFIG Existing lane configuration
LRTP_YEAR Long Range Transportation Plan year
COST_AADT LRTP cost affordable traffic volume
COST_LANES LRTP cost affordable number of lanes
COST_CONFIG LRTP cost affordable lane configuration
NEED_AADT Traffic volume in Needs Plan
NEED_LANES Number of lanes in Needs Plan
NEED_CONFIG Lane configuration in Needs Plan
STREET_NAME Street name of project segment location
FROM_STREET Bounding street marking the beginning of the segment
TO_STREET Bounding street marking the end of the segment
SEGMENT_LENGTH Length of the segment, in miles
ROADWAY_FCLASS Roadway functional classification. Not applicable if the project
mode does not include roadway.
USER NOTES:
This data set is intended for planning purposes only. Line work locations represent the general vicinity of the proposed project and are not intended for design or construction.
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: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 section and 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
FGDL QUALITY ASSURANCE STATUS:
-Projected data to FGDL Albers
-Set Precision to DOUBLE
-Set Tolerances to FGDL Standards
-Added DESCRIPT item based on LOCALNAME, STROUTE, and USROUTE
-Added CLASS item based on road type
REFERENCES:
DATA LINEAGE SUMMARY:
Project segments are incorporated into the ETDM project database from information provided by FDOT districts and MPOs. Three mechanisms are available for updating the ETDM project database:
A spatial view was created in ArcSDE to join project and segment attributes to the segment lines. This view is automatically updated when the database is modified.
MAP PROJECTION PARAMETERS
Projection ALBERS Units METERS Datum HPGN Spheroid GRS1980 1st standard parallel 24 0 0.000 2nd standard parallel 31 30 0.000 central meridian -84 0 0.000 latitude of projection's origin 24 0 0.000 false easting (meters) 400000.00000 false northing (meters) 0.00000
DATA SOURCES CONTACT(S):
Name: FDOT Transportation Statistics Office, EMO Office
Abbr.name: FDOT
Address: 605 Suwannee St. MS 37
Tallahassee, FL 32399-0450
Phone: (850) 488-4111 x-119
Web site: www.dot.state.fl.us
Phone: (850) 488-4111 x-119
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