FSUTMS Framework for Integrating Land Use Modeling

Transcription

1 FSUTMS Framework for Integrating Land Use Modeling presented to MTF Data Committee presented by Wade L. White, Whitehouse Group Walter Anderson, Whitehouse Group March 6, 2012

2 Agenda Background Previous Efforts Scope & Schedule of Current Technical Efforts Overview of Other Central Office Ongoing LU Model Efforts University of Florida FDOT Central Office FLUAM Case Studies Statewide-Model / FLUAM Orange County Data / LandSYS Subarea / Community Viz Findings to Date 1

3 Background Scope & Schedule of Current Technical Efforts Identify at Least 1 Rule-based and 1 Empirically-based Model for Integration & Testing with FSUTMS Model Integrate Land Use and Transportation Model Where Possible, Document Where & Why if Not Possible Implement Convergent Feedback Process in FSUTMS Cube Voyager Framework Document Successes, Challenges, Pitfalls and Recommended Approaches Complete Majority of Effort between December 2011 and March

4 Background Previous Efforts FLUAM Developed for Florida s Turnpike Zone-based, Gravity Model Formulation Parameters Estimated from Real World Data LandSYS Developed for Central Office by UF Grid-based, Cellular Automata Formulation Parameters Estimated from Real World Data Community Viz Commercial Product- ArcGIS Extension (~$850) Parcel-based, User Specified Rule Formulation Parameters Asserted 3

5 Case Study #1 FLSWM / FLUAM Before FLUAM 4 After FLUAM

6 Case Study #1 FLSWM / FLUAM Additions to UI Input Files Convergence Configuration 5

7 6 Case Study #1 FLSWM / FLUAM

8 Case Study #1 FLSWM / LUAM Performance ~ 5.5 Hours, Single Core FLUAM Adds about 2 Minutes / Iteration Target Convergence Met on 2 nd Iteration RMSE (FLUAM) Housing=0.10 Employment=0.00 7

9 Case Study #2 Orange County Data / LandSYS LandSys land use model CUBE FSUTMS Transportation model CA model Dababase Raster based land use development Agent model TAZ based household allocation TAZ employment allocation External input Trip generation TAZ data1 TAZ data2 TAZ data3 TAZdata4 Road network Traffic distribution Bus network Mode choice Traffic assignment Traffic flow on road links Travel time between TAZs 8

10 Case Study #2 LandSYS Data Required Land use/cover data DEM files Transportation networks Soil type and soil erosion information Railway station, Airport, Bus Station and CBD locations Census data Employment data Transportation accessibility data (Skim file) Land Price Data

11 10 Case Study #3 Subarea Parcel Data / Community Viz

12 Case Study #3 Community Viz Description Similar to a Spreadsheet / Database Calculation Tool User-Interactive GIS (ArcGIS) Platform Familiar Language for Land Use Planners Outputs Tables, Maps and Renderings with Additional Arc Extensions 11

13 Case Study #3 Community Viz Data Requirements Tax parcel polygon coverage with zoning information. Building coverage with at least; number of dwelling units (for residential zones) or floor area, zoning, and the number of stories. Road centerline data Coverage(s) describing development constraints. These may include; wetlands, floodplains, surface water, conserved lands, etc. Zoning ordinances which provide build-out inputs such as density rules and setback requirements. 12

14 Case Study #3 Community Viz Integration Interactive Nature Precludes Automatic Feedback / Convergence Requires Pre and Post-processsing to Exchange Information with Transportation Model As an ArcGIS Extension, Some Procedures are not readily Exposed for script-based management (i.e. no API for this type of activity) Full Integration Would Require Work with Software Developer Initial Test Data with Hillsborough County Data 13

15 Conclusions to Date With Adequate Documentation, Integration is Possible with Most Fully Automating Feedback Remains a Challenge LU Software Not Particularly Built for It Input / Output Variables Not Necessarily Consistent with FSUTMS Variables- Some translation in Voyager is Required Convergence Should be Based on Zonal Data vs. Network (LU Model less sensitive then Assignment) 14

16 Next Steps Document Three Integration Efforts Steps Required to Prepare Data Steps Needed to Be Added to Models LU & Transportation Differences Resulting from Integration Central Office Refine FLUAM to Include More Policy Variables and Variables Consistent with SWM Requirements Refine LandSYS UI and Evaluate Performance 15