Attribute D4c, which is the frequency of transit service and found within the input file zone_transit_service.csv does not affect output variables such as mode shares and VMT. VisionEval formally defined attribute D4c as the “aggregate frequency of transit service within 0.25 miles of block group boundary per hour during evening peak period (Ref: EPA 2010 Smart Location Database).” For our 712 bzones, values ranged from 0 to 305 (e.g., values included 0, 0.1, 4.1, 11.6, 12.1, 24.2, 69.5, 137, and so forth). Then we increased D4c for 123 of these 712 zones (where we expected transit service to increase) by varying amounts from 2% to 260%. None of the 158 output variables, such as the number of transit trips, were affected. (If you want more details, please let me know, or if you want to see supporting data, this was scenario 6a in the publication https://www.virginiadot.org/vtrc/main/online_reports/pdf/22-R21.pdf).
Attribute D4c, which is the frequency of transit service and found within the input file zone_transit_service.csv does not affect output variables such as mode shares and VMT. VisionEval formally defined attribute D4c as the “aggregate frequency of transit service within 0.25 miles of block group boundary per hour during evening peak period (Ref: EPA 2010 Smart Location Database).” For our 712 bzones, values ranged from 0 to 305 (e.g., values included 0, 0.1, 4.1, 11.6, 12.1, 24.2, 69.5, 137, and so forth). Then we increased D4c for 123 of these 712 zones (where we expected transit service to increase) by varying amounts from 2% to 260%. None of the 158 output variables, such as the number of transit trips, were affected. (If you want more details, please let me know, or if you want to see supporting data, this was scenario 6a in the publication https://www.virginiadot.org/vtrc/main/online_reports/pdf/22-R21.pdf).