The specifications for mandatory tour scheduling are hard-coded forcing the school and university specification to use the same specification file. In the Atlanta implementation, school and university use different specifications.

It would nice if the model treated the spec more flexibly similar to the way the the location models define the spec.

I could imagine a situation where the mandatory specs are defined in the mandatory_tour_scheduling.yaml as follow:

SPEC:
  work: tour_scheduling_work.csv
  school: tour_scheduling_school.csv
  univ: tour_scheduling_university.csv