What is the best methodology to use multiple custom domains to accommodate county-specific registration data and/or fuel requirements?
The methodology is fairly simple. Each independent area (county) should be modeled separately with its own run specification and input database using the County Data Manager. You can execute each run specification manually or use the batch mode to execute all of the run specifications at once. The results from each run specification can be routed into the same output database so that the results from each county will be found in the same output tables for easy analysis and aggregation. Q: Where do I find the SourceTypePopulation table? I have found a sourcetypeagepopulation Table under the MOVESEXECUTION Database, but I am unable to find the template for the SourceTypePopulation table mentioned on page 49 of the MOVES User Guide. Does a template of the table even exist before the population data is imported? As I understand it data could reside an temporary databases, worker, or other system databases, but I should only modify tables and data in my user created scenario specific databa