Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change VE-State area type policy inputs #187

Open
mrspeel opened this issue Jun 2, 2022 · 0 comments
Open

Change VE-State area type policy inputs #187

mrspeel opened this issue Jun 2, 2022 · 0 comments

Comments

@mrspeel
Copy link

mrspeel commented Jun 2, 2022

I'd like to improve the VE-State policy inputs, which differ from VE-RSPM because they are bzone level. In VE-State, since bzones are sythesized, a different input geography must be used. Currently the VE-State inputs use area type (center, inner, outer, fringe) for the following input files. The problem is that area type is not known until the bzones are synthesized, so it is hard to control how these inputs are applied.

  • TDM/IMP (marea_travel-demand-mgt_by_area-type.csv)
  • Parking (marea_parking-cost_by_area-type.csv)
  • Car Service coverage (marea_carsvc_availability.csv)
  • Group Quarters (azone_gq_pop-prop_by_area-type.csv)

One solution is to add a "control total" for these policies at the more aggregate MArea level. This could replace or add to the the existing area type inputs. If the area type inputs are retained, they may need to change to be a relative factor for applying the policies in different areas that are scaled up/down to match the new marea control total.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant