You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ODOT has land use designations called "Place Types". They help us communicate how land use has been coded in models with local jurisdictions. Place Types is just a classification of land use data, as; low density, residential, employment, mixed, TOD...
ODOT has a process to build a Place Type html visualizer off of a model's land use information in a shapefile. What this task / issue would address, is embedding ODOT's place type code into the ABM setup, and adding several elements to the python script that interfaces with VIsum to export the zone shape information and the several data elements about the zones that the place type script (process) requires, and then build the generation (run) of the place types html into each ABM run, so that a standard ABM output is a place type html layer.
The text was updated successfully, but these errors were encountered:
ODOT has land use designations called "Place Types". They help us communicate how land use has been coded in models with local jurisdictions. Place Types is just a classification of land use data, as; low density, residential, employment, mixed, TOD...
ODOT has a process to build a Place Type html visualizer off of a model's land use information in a shapefile. What this task / issue would address, is embedding ODOT's place type code into the ABM setup, and adding several elements to the python script that interfaces with VIsum to export the zone shape information and the several data elements about the zones that the place type script (process) requires, and then build the generation (run) of the place types html into each ABM run, so that a standard ABM output is a place type html layer.
The text was updated successfully, but these errors were encountered: