joecastiglione
commented
1 year ago ODOT: I wasn't thinking visitor with the term air passenage model. Maybe we should call this a visitor model / treatment. A visitor treatment would have a lot of value to ODOT. Maybe this is just written guidance on how to add visitors to a model as opposed to a model in itself. Example ODOT adds visitors by creating a special sub group of visitor added to the sythetic population.
SFCTA: I think an important principle guiding Activitysim development should be that enhancements and features can be used by many / most / all the regions. Visitor models will almost by necessity will be region specific (eg. there's not a Golden Gate Bridge in the Atlanta region). To a lesser extent, the same may be true about airports (ie. airports may have very different time-of-day profiles based on region size, airport function (hub vs non-hub), etc).
Met Council: Given the importance of regional airports on the surrounding transportation network, we're concerned that the ancillary models we have been using are too simplistic, and are interested in exploring if bringing into ActivitySim would improve how we model trips to airports. If tying into a visitor model proves too region-specific, we'd advocate for looking to see if there are enough commalities to still pursue an ActivitySim airport model.
SANDAG: We have both airpassenger and visitor models. We are considering a GrandCentral hub with potential people mover built to link between the hub and the airport. Our existing airport model has been used in the GrandCentrl project evaluation. It would be nice to have a 'common' airport model that is expandable to allow regional specifics to be added.
MTC: Interested in learning more about the options.
Ohio: I'm unclear whether this is a special generator model or part of the visitor model. I put comments in the visitor model item.
guyrousseau
Model additional travel markets such as airport trips, vistors, universities (see other item), freight (see other item), etc. This can take several forms, including aggregate, disaggregate, trip-based, tour-based, etc. Several DOTs and MPOs have additional demand models, including some disaggregate models. The disaggregate models tend to be custom / protype-type software and would benefit from a management plan such as the ActivitySim consortium. Developing and maintaining additional model components would likely require consensus around methods.
Build a good starting point model for use in multiple regions (including regions with multiple airports)