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