At Default Scale, MOVES calculates VMT and VPOP for each county in the RunSpec by applying the corresponding zoneroadtype and zone fractions to the national VMT and VPOP values. It is impractical to use user-supplied VMT and VPOP at Default Scale because there is no way to supply the zoneroadtype and zone tables at this scale, so MOVES will always multiply the VMT and VPOP values (regardless if they are the national default values or user-supplied) by the default zoneroadtype and zone fractions.
An upcoming feature in MOVES4.0.1 is the addition of the "Zone" tab to the Default Data Manager. This tab can be used to supply custom ZoneRoadType and Zone tables at Default Scale, which can be used in conjunction with user-supplied VMT and VPOP values.
When using this new MOVES4.0.1 feature, if a single county is selected in the RunSpec, ZoneRoadType should have a SHOAllocFactor of 1.0 for each road type, and Zone should have 1.0 for all of the "AllocFactor" columns. This will, in effect, allocate 100% of the VMT and VPOP (supplied through the Vehicle Type VMT and Source Type Population tabs, respectively) to the selected county.
If more than one county is selected in the RunSpec:
Supply VMT and VPOP inputs that reflect the combined VMT and VPOP for all selected counties.
Calculate each individual county's proportion of the combined VMT.
In ZoneRoadType, supply these values for each county's SHOAllocFactor on each road type. (The SHOAllocFactor column should sum to 4.0, because there are 4 road types in this table.)
In Zone, supply these values for each county's "AllocFactor" columns.
If state preaggregation is used, the VMT and VPOP inputs should reflect the total state VMT and VPOP, and the ZoneRoadType and Zone tables should be populated following the instructions above for multiple counties, as if each county in the state was selected individually in the RunSpec. At runtime, MOVES will use these allocation factors as weighting values when preaggregating other inputs, such as meteorology data. The output will be at the state level.
Note: Default scale input databases, while they can be created via the Create Input Database panel, are supplied in the RunSpec via the Advanced Features panel.
At Default Scale, MOVES calculates VMT and VPOP for each county in the RunSpec by applying the corresponding zoneroadtype and zone fractions to the national VMT and VPOP values. It is impractical to use user-supplied VMT and VPOP at Default Scale because there is no way to supply the zoneroadtype and zone tables at this scale, so MOVES will always multiply the VMT and VPOP values (regardless if they are the national default values or user-supplied) by the default zoneroadtype and zone fractions.
An upcoming feature in MOVES4.0.1 is the addition of the "Zone" tab to the Default Data Manager. This tab can be used to supply custom ZoneRoadType and Zone tables at Default Scale, which can be used in conjunction with user-supplied VMT and VPOP values.
When using this new MOVES4.0.1 feature, if a single county is selected in the RunSpec, ZoneRoadType should have a SHOAllocFactor of 1.0 for each road type, and Zone should have 1.0 for all of the "AllocFactor" columns. This will, in effect, allocate 100% of the VMT and VPOP (supplied through the Vehicle Type VMT and Source Type Population tabs, respectively) to the selected county.
If more than one county is selected in the RunSpec:
If state preaggregation is used, the VMT and VPOP inputs should reflect the total state VMT and VPOP, and the ZoneRoadType and Zone tables should be populated following the instructions above for multiple counties, as if each county in the state was selected individually in the RunSpec. At runtime, MOVES will use these allocation factors as weighting values when preaggregating other inputs, such as meteorology data. The output will be at the state level.
Note: Default scale input databases, while they can be created via the Create Input Database panel, are supplied in the RunSpec via the Advanced Features panel.