Integrating GIS and CUBE for MetropolitanTransportation Planning

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Integrating GIS and CUBE for MetropolitanTransportation Planning - Presentation Transcript

    1. Integrating GIS And CUBE for Metropolitan Planning Andy Reser, AICP Aaron Crary OKI Regional Council of Governments Cincinnati, OH
    2. Indiana Ohio Kentucky
    3. OKI at a Glance
      • 103 member council representing government, social and civic groups from 198 jurisdictions throughout 8-county Greater Cincinnati area.
      • 35 full-time staff members
      • Tasks
        • Transportation Planning
          • Including air quality
        • Land-Use
        • Water Quality
    4. OKI is a COG and MPO
      • Council of Governments
        • Authority to study and fund regional issues and projects (water quality, land-use)
      • Metropolitan Planning Organization
        • Authority to study and fund transportation issues and projects
      • Local, State and Federal funds
    5. Improve Visualization
      • Fly-thru of project areas
      • GIS/Model Integration
      • Traffic Simulation
    6. Project Fly-thru
    7. GIS/Model Integration - Goals
      • Build and maintain a direct link between the Travel Model and GIS.
      • Improve mapping capability of Travel Model output and improve map quality.
      • Build tools to readily find network errors and for model validation.
    8. OKI Network
      • Consolidated model with Dayton MPO.
      • 3200 network road miles in OKI portion (5400 total).
      • 54 mil DVMT (OKI)
      • ~ 1600 zones and 12000 links (OKI)
      • 308 bus lines (OKI)
      • No passenger rail in base year network.
    9. Build Model/GIS Relationship
      • One-to-one relationship between all highway links and GIS street centerline.
      • Added 3 fields to street centerline: from node, to node, sequence.
      • Moved highway network nodes to match street centerline.
    10.  
    11.  
    12.  
    13. Transit Network
      • Changes made in conjunction with highway network.
      • Script to convert transit lines to shapefile.
        • Text file to shape
    14. Benefits
      • No major development/redesign needed
      • True shape display.
      • Ability to transfer data between the Model and GIS.
      • Modify Network and Street Centerline in one place.
      • Eases development of simulation network (prepare for export to Dynasim)
    15. Tools
      • Compare two networks
      • Cutline/Screenline tool
      • Auto generate maps of Model data
        • Loaded volume and speeds, volume/capacity, level-of-service
    16. GIS/Model Integration Next Steps
      • Support of future year networks
      • Move intersection data from GIS point data to CUBE junction file
      • Store all networks as geodatabase; build networks from geodatabase
    17. How Much Time?
      • Highway network/street centerline modifications = 160 hours
      • Transit network = 80 hours
      • 2 staff plus periodic coordination meetings between GIS and Data Services departments
    18. Methodology
      • Link consolidation
        • What attributes need to be preserved?
        • Shape Nodes
      • True shape display
        • Cube functionality
      • Transit
        • Text file to GIS
    19. Use of GIS data in Simulation
      • GIS data used for:
        • Splitting zones
        • Modifying “stick” network to match shape
        • Within Dynasim, use aerial photos to correct geometry, add turn lanes.
        • GPS data used for bus stops and parking restrictions.
        • 2d and 3d background development:
          • Aerial photos, building footprints, edge of pavement, street labels.
    20. Why use simulation?
      • Traditional regional travel demand model is not sensitive to local improvements such as:
        • signalization
        • new intersection turn lanes
        • Integration of pedestrians and transit
        • Improved geometry
      • Decision-makers can visualize impact; supports charts, graphs, LOS plots
    21. Simulation Development Goals
      • Integrate with current travel demand model and GIS data
      • Most work done in-house; utilize skills of OKI staff
      • Use as an outreach tool in support of OKI’s Corridor Studies or to assist member communities.
    22. Sub-Area Model
      • Extract sub-area and peak period trip table from regional model
      • Refine sub-area by disaggregating zones and adding links (local streets).
      • Distribute zonal vehicle trips to subzonal vehicle trip table.
      • Run sub-area vehicle assignment.
      • Export to Dynasim
    23. Simulation Demo of OKI Projects
    24. Contact Information
      • Andy Reser, AICP - Model Applications Coordinator
      • [email_address]
      • Aaron Crary, Senior GIS Analyst
      • [email_address]
      • Ohio-Kentucky-Indiana Regional Council of Governments
      • Cincinnati, OH
      • 513-621-6300
      • www.oki.org

    + Andrew ReserAndrew Reser, 11 months ago

    custom

    531 views, 0 favs, 0 embeds more stats

    Integrating OKI's GIS street centerline file with C more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 531
      • 531 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 16
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories