2007042516242400FALSECreateFeatureclass "Database Connections\etdmsde - etat.sde\ETAT.aaa" LRTP_MAR07_2 # lrtp_mar07_2_Layer SAME_AS_TEMPLATE SAME_AS_TEMPLATE "PROJCS['Albers Conical Equal Area (Florida Geographic Data Library)',GEOGCS['GCS_North_American_1983_HARN',DATUM['D_North_American_1983_HARN',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Albers'],PARAMETER['False_Easting',400000.0],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-84.0],PARAMETER['Standard_Parallel_1',24.0],PARAMETER['Standard_Parallel_2',31.5],PARAMETER['Central_Parallel',24.0],UNIT['Meter',1.0]];-672793.976688 -629671.126188 976.562499090505;0 100000;0 100000" # 0 0 0 "Database Connections\etdmsde - etat.sde\ETAT.aaa\ETAT.LRTP_MAR07_2"Append lrtp_mar07_2_Layer "Database Connections\etdmsde - etat.sde\ETAT.aaa\ETAT.LRTP_MAR07_2" TEST "Database Connections\etdmsde - etat.sde\ETAT.aaa\ETAT.LRTP_MAR07_2"FeatureClassToFeatureClass Q:\downloads\sam\fdot\lrtp\exports\lrtp_mar07_2.shp "Database Connections\etdmsde - etat.sde\ETAT.aaa" LRTP_MAR07_2 # "PRJNAME PRJNAME VISIBLE;PRJ_ID PRJ_ID VISIBLE;PRJ_BEG PRJ_BEG VISIBLE;PRJ_END PRJ_END VISIBLE;PLAN_ORG PLAN_ORG VISIBLE;ETDM_STAGE ETDM_STAGE VISIBLE;PRJ_TYPE PRJ_TYPE VISIBLE;COUNTY COUNTY VISIBLE;LENGTH LENGTH VISIBLE;JURISDCTN JURISDCTN VISIBLE;URB_SERV URB_SERV VISIBLE;BASE_CNFG BASE_CNFG VISIBLE;PLAN_YEAR PLAN_YEAR VISIBLE;NEED_CNFG NEED_CNFG VISIBLE;SHAPE_Leng SHAPE_Leng VISIBLE;PLAN_PHASE PLAN_PHASE VISIBLE;DESCRIPT DESCRIPT VISIBLE;FGDLAQDATE FGDLAQDATE VISIBLE" SAME_AS_TEMPLATE SAME_AS_TEMPLATE # 0 "Database Connections\etdmsde - etat.sde\ETAT.aaa\ETAT.LRTP_MAR07_2"FeatureClassToFeatureClass "Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07" Q:\downloads\sam\fdot\lrtp\exports_4_meta LRTP_MAR07.shp # "PRJNAME PRJNAME true true false 150 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,PRJNAME,-1,-1;PRJ_ID PRJ_ID true true false 10 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,PRJ_ID,-1,-1;PRJ_BEG PRJ_BEG true true false 50 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,PRJ_BEG,-1,-1;PRJ_END PRJ_END true true false 50 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,PRJ_END,-1,-1;PLAN_ORG PLAN_ORG true true false 50 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,PLAN_ORG,-1,-1;ETDM_STAGE ETDM_STAGE true true false 20 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,ETDM_STAGE,-1,-1;PRJ_TYPE PRJ_TYPE true true false 150 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,PRJ_TYPE,-1,-1;COUNTY COUNTY true true false 30 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,COUNTY,-1,-1;LENGTH LENGTH true true false 8 Double 11 19 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,LENGTH,-1,-1;JURISDCTN JURISDCTN true true false 50 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,JURISDCTN,-1,-1;URB_SERV URB_SERV true true false 6 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,URB_SERV,-1,-1;BASE_CNFG BASE_CNFG true true false 15 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,BASE_CNFG,-1,-1;PLAN_YEAR PLAN_YEAR true true false 4 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,PLAN_YEAR,-1,-1;NEED_CNFG NEED_CNFG true true false 15 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,NEED_CNFG,-1,-1;SHAPE_LENG SHAPE_LENG true true false 8 Double 11 19 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,SHAPE_LENG,-1,-1;PLAN_PHASE PLAN_PHASE true true false 50 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,PLAN_PHASE,-1,-1;DESCRIPT DESCRIPT true true false 150 Text 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,DESCRIPT,-1,-1;FGDLAQDATE FGDLAQDATE true true false 36 Date 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,FGDLAQDATE,-1,-1;AUTOID AUTOID true true false 4 Long 0 10 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,AUTOID,-1,-1;LEN LEN false false true 0 Double 0 0 ,First,#,Database Connections\ETDMSDE - ETAT.sde\ETAT.fdot\ETAT.LRTP_MAR07,SHAPE.LEN,-1,-1" # Q:\downloads\sam\fdot\lrtp\exports_4_meta\LRTP_MAR07.shp20070412141501002007050416285300{9CB55F9A-BA1B-4438-A4CC-140A549688ED}enThis dataset contains Long Range Transportation Plans (LRTPs) contributed by various Metropoloitan Planning Organizations (MPOs). Under federal legslation (Transportation Equity Act for the 21st Century, or TEA-21), MPO's, which oversee transportation planning for urban areas with populations greater than 50,000, are also required to develop LRTPs. LRTPs are 20-year plans which guide transportation plans and investments. The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes.Florida Metropolitan Planning Organizations20070327LRTP_MAR07vector digital dataState of FloridaFlorida Metropolitan Planning Organizationspublication date3/27/07CompleteAs needed-87.429040-79.87225130.98319124.49281561959.790000791475.510000164285.310000775395.690000NONElong range transportation plantransportation planningISO 19115 Topic CategorytransportationNONETHE 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.htmlSHAPEFILEWeb site: http://www.fgdl.orgTechnical Support: http://www.fgdl.org/fgdlfeed.htmlFor FGDL Software: http://www.fgdl.org/software.htmlFGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.htmlFGDL Mailing Lists: http://www.fgdl.org/fgdl-l.htmlmailing address

431 Architecture PO Box 115706

GainesvilleFlorida32611-5706Florida Geographic Data Library (FGDL)Web site: http://www.fgdl.orgMicrosoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.1.1332LRTP_MAR0761959.79791475.51775395.69164285.311-87.540057-79.90073730.98686625.4263041enFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local time1625 Summit Lake DriveTallahasseeFL32317850.574.3197URS CorporationMark Dietrich20070504http://www.esri.com/metadata/esriprof80.htmlESRI Metadata ProfileISO 19115 Geographic Information - MetadataDIS_ESRI1.0datasetThis data is intended for use with a Geographic Information Systems or Remote Sensing software package.DOWNLOADABLE DATATHE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE 'MATERIALS') ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE 'DATA PROVIDERS'). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED 'AS IS'. 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 MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. 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.Florida Geographic Data Library (FGDL)mailing address

431 Architecture PO Box 115706

GainesvilleFlorida32611-5706United StatesWeb site: http://www.fgdl.orgTechnical Support: http://www.fgdl.org/fgdlfeed.htmlFor FGDL Software: http://www.fgdl.org/software.htmlFGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.htmlMailing list for FGDL: http://www.fgdl.org/fgdl-l.html1.3851.385This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlanThis data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlanThis data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topologyThis 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.publication dateSpatial and Attribute InformationVariesBayBrevard MPOBroward MPOCharlotte MPOEscambia-Santa_Rosa MPOGainesville MPOHernando MPOHillsborough MPOIndian_River MPOJacksonville (First Coast) MPOLakeSumter MPOLeeCollier MPOMartin St Lucie County MPOMiamiDade MPOOcalaMarion MPOOkaloosa Walton MPOOrlando MPOPalm_Beach MPOPasco MPOPinellas MPOPolk MPOSarasotaManatee MPOVolusia MPOLRTP 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.shp2007This 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_MAR0720070327Received 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>20070404coordinate pair0.0020480.002048metersAlbers Conical Equal Area24.00000031.500000-84.00000024.000000400000.0000000.000000Albers Conical Equal AreaHPGNGeodetic Reference System 806378137.000000298.257222GCS_North_American_1983_HARND_North_American_1983_HARNGeodetic Reference System 806378137.000000298.257222002file://\\Darwin\qaqc\downloads\sam\fdot\lrtp\exports_4_meta\LRTP_MAR07.shpLocal Area Network1.385ShapefileVectorSimplePolylineFALSE3085FALSEFALSEString3085Albers Conical Equal Area (Florida Geographic Data Library)3085LRTP_MAR07Feature Class3085LRTP_MAR07.DBFPRJNAMEPRJNAMEString150Name of ProjectPRJ_IDPRJ_IDString10Identifier assigned by planning organization that uniquely identifies the project within their organizationPRJ_BEGPRJ_BEGString50Bounding location marking the beginning point of the projectPRJ_ENDPRJ_ENDString50Bounding location marking the end point of the projectPLAN_ORGPLAN_ORGString50Name of planning organization ETDM_STAGEETDM_STAGEString20Indicates the stage of the ETDM process which the project is enteringPRJ_TYPEPRJ_TYPEString150Type of transportation projectCOUNTYCOUNTYString30Name of county in which project is locatedLENGTHLENGTHNumber1911Length of planned project, in milesJURISDCTNJURISDCTNString50Entity with maintenance responsibilityURB_SERVURB_SERVString6Indicates whether or not the project segment is in an urban service area, if one exists within the countyBASE_LANEBASE_LANENumber2Total number of existing lanes on roadBASE_CNFGBASE_CNFGString15Existing lane configurationPLAN_YEARPLAN_YEARString44-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_LANENEED_LANENumber2Number of lanes in Needs AssessmentNEED_CNFGNEED_CNFGString15Lane configuration in Needs AssessmentPLAN_PHASEPLAN_PHASEString50Planning PhaseDESCRIPTDESCRIPTString150GeoPlan added field based on PRJNAMEGeoPlanFGDLAQDATEFGDLAQDATEDate8Date GeoPlan acquired dataGeoPlanAUTOIDAUTOIDNumber10Unique ID added by GeoPlanGeoPlan20070504