Geodataset Name:       LRTP_MAR07
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         3085

DATA SOURCE(S):                    Florida Metropolitan Planning Organizations
SCALE OF ORIGINAL SOURCE MAPS:     Varies
DATE OF AUTOMATION OF SOURCE:      20070327
GEODATASET EXTENT:                 State of Florida

FEATURE ATTRIBUTE TABLES:

Datafile Name: LRTP_MAR07.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
PRJNAME	Name of Project
PRJ_ID	Identifier assigned by planning organization that uniquely identifies the project within their organization
PRJ_BEG	Bounding location marking the beginning point of the project
PRJ_END	Bounding location marking the end point of the project
PLAN_ORG	Name of planning organization
ETDM_STAGE	Indicates the stage of the ETDM process which the project is entering
PRJ_TYPE	Type of transportation project
COUNTY	Name of county in which project is located
LENGTH	Length of planned project, in miles
JURISDCTN	Entity with maintenance responsibility
URB_SERV	Indicates whether or not the project segment is in an urban service area, if one exists within the county
BASE_LANE	Total number of existing lanes on road
BASE_CNFG	Existing lane configuration
PLAN_YEAR	4-digit year of Cost Feasible horizon year (For example, if the projects are proposed for the 2025 LRTP, then the plan year would be 2025.)
NEED_LANE	Number of lanes in Needs Assessment
NEED_CNFG	Lane configuration in Needs Assessment
PLAN_PHASE	Planning Phase
DESCRIPT	GeoPlan added field based on PRJNAME
FGDLAQDATE	Date GeoPlan acquired data
AUTOID	Unique ID added by GeoPlan

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 data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes.

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

THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. 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:

LRTP data was collected from various MPOs by Mark Dietrich of URS Corporation. The following is the MPO name with the name of the the shapefile the MPO contributed Gainesville - LRTP_proj.shp Hernando - 2025_CA_Roadwa Hillsborough - 2025hwyCA04.sh Indian_River - CAImprovements Jacksonville - Jax_1stC_nerpm LakeSumter - 2025_Improveme LeeCollier - Lee_Collier30. Martin County MPO - No Response MiamiDade - priority_ii-iv OcalaMarion - LRTP2025.shp OkaloosaWalton - owtpo_needs30. Orlando - 2025_fundament Palm_Beach - 2030CF.shp Pasco - 2009_2025_Add_ Pinellas - Resending Polk - fdot_polk_2030 SarasotaManatee - sm2030_ff_proj St. Lucie County MPO - No Response Volusia - LRTP Lines.shp Process Date: 2007 This data was received from mark dietrich at URS Corporation. Data was received via email in March 2007. The data was in Albers HPGN and was called State_LRTP_070316_original.shp Data was imported into a pGDB and field structure was changed to match data format specifications of ETDM project data. -delete shape_length -calc all len_mile = 0 -delete objectid -dissolve on all fields -clean up PRJ_FROM and PRJ_TO -use crosswalk to upload data to pGDB (DESC_ causes problems so i increased prj_type from 30 to 150 char) -update Length field in miles -load to sde -added field FUND_TYPE, PLAN_PHASE -added FGDLAQDATE and DESCRIPT -renamed layer to LRTP_MAR07 Process Date: 20070327 Received data from two addtional MPOs (Martin St Lucie and Pinellas) via email from Mark Deitrich of URS Corporation. Martin St Lucie: Received email from Mark Dietrich with data. Projected lrtp_segs.shp to Albers HPGN then dissolved shapefile. Put data into pGDB then appended to SDE layer LRTP_MAR07. here is the Cross-Walk... LRTP_MAR07 - MARTIN St Lucie PRJNAME - PRJ_NAME PRJ_ID - PROJ_ID PRJ_BEG - PRJ_BEG PRJ_END - PRJ_END PLAN_ORG - "MARTIN ST LUCIE" ETDM_STAGE - <None> PRJ_TYPE - NDS_DESC COUNTY - COUNTY (why is "FDOT" in County) LENGTH - calc on my own JURISDCTN - has JURIS field but unpopulated URB_SERV - has field U__r for Rural or Urban - not sure if this is equivalent to urban service boundary BASE_CNFG - EC_LANES - this is existing lanes PLAN_YEAR - <none> NEED_CNFG - NDS_LANES PLAN_PHASE - LRTP_DESC (i think) FUND_TYPE - possibly NON_REG_RO - Roadway Ownership Pinellas Data Received email from Mark Dietrich with data. Dissolved Long Range Transportation Plan centerlines.shp then joined with data from Long Range_Transportation_Plan_attributes.xls. All records match up and no data is lost on dissolve except for SEGMENTID = 2221 note: projection file was wrong with original data Put data into pGDB then appended to SDE layer LRTP_MAR07. here is the Cross-Walk... LRTP_MAR07 - Pinellas PRJNAME - ONSTREET PRJ_ID - SEGMENTID PRJ_BEG - FROMNODE PRJ_END - TONODE PLAN_ORG - calc "Pinellas" ETDM_STAGE - <none> PRJ_TYPE - <none> COUNTY - <none> LENGTH - calc in miles JURISDCTN - <none> URB_SERV - <none> BASE_CNFG - LANECNT PLAN_YEAR - calc 2025 NEED_CNFG - <none> SHAPE_LENG - <none> PLAN_PHASE - <none> Process Date: 20070404

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:

URS Corporation


Tallahassee, FL
32317
850.574.3197




Mark Dietrich

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