Tools to Develop or Convert MOVES Inputs
The following tools are designed to help users develop inputs to MOVES and post-process the output.
On this page:
- Tools to develop MOVES3 inputs
- Tools to post-process output for project-level analyses
- Tools to develop special case MOVES3 inputs
- Tool to generate EMISFACT portion of an AERMOD input file
Age Distribution Projection Tool for MOVES3 (XLTM) (xltm)
(Note: right click to save link for downloading the tool file.)
- This tool creates projections of future year age distributions based on current local age distributions. It uses the same underlying age distribution projection algorithm as MOVES3 and is based on data in the Energy Information Administration’s Annual Energy Outlook 2021.
- This tool uses Annual Average Daily Vehicles Miles Travelled (AADVMT) at the HPMS level to calculate type of day, monthly and yearly VMT by HPMS class.
- It generates the HPMSVTypeYear, monthVMTFraction, and dayVMTFraction tables from AADVMT and user-provided monthly/weekend-day adjustment factors.
- The tool provides the user with the default temporal allocation tables if local inputs are not known.
- Starting with MOVES2014a, users may supply AADVMT as a direct input to MOVES. However, this tool is still provided as a convenience for users who wish to construct an input database containing annual VMT data.
Other tools to develop MOVES3 inputs are included in the model. Use the “Tools” menu in the MOVES interface to access:
- Multiple Run Spec File Creator: Creates new run specification files using the currently loaded information as a template, making substitutions for county, year, and database selections driven by a user-supplied control file.
- Process Done Files: An advanced feature, used in networked setups where MOVES workers independently process TODO files into DONE files. This tool is typically not needed for most user setups.
- Convert MOVES2014a/b Input Database to MOVES3: This tool converts MOVES2014a and MOVES2014b input databases for County, Project, and Nonroad runs into the MOVES3 format. The converter instructions also explain the additional work needed before using the converted input databases with MOVES3.
- Convert MOVES2014 Input Database to MOVES3: This tool converts MOVES2014 input databases for County, Project, and Nonroad runs into the MOVES3 format. Additional work is needed before using the converted input databases with MOVES3.
- Build NLEV Input Database: This tool builds an input database to be used by Ozone Transport Commission (OTC) states to model the early introduction of NLEV standards in those states. This tool creates a special input database which contains a set of alternate HC, CO, and NOx start and running emission rates based on EPA analysis of the NLEV program.
- Build LEV Input Database: This tool builds an input database to be used by states that chose to adopt California LEV standards in place of federal standards. This tool creates a special input database which contains a set of alternate HC, CO, NOx, and PM start and running emission rates based on EPA and CARB analysis of the LEV programs.
- ONI Tool: The Off-Network Idle tool calculates default off-network idle activity for use with County Scale in Emission Rates mode based on other county inputs; that is, the tool will generate off-network idle activity consistent with what MOVES would use in Inventory mode.
EPA has developed several scripts to automate the process of calculating MOVES emission factors for use in air quality modeling. Each script automates the post-processing steps described in:
- Sections 4.4.7 and 4.6 of Transportation Conformity Guidance for Quantitative Hot-spot Analyses in PM2.5 and PM10 Nonattainment and Maintenance Areas (EPA-420-B-10-040, December 2010)
- and Sections 2.3.7 and 2.5 of Using MOVES in Project-Level Carbon Monoxide Analyses (PDF) (59 pp, 2M, EPA420-B-10-041, December 2010).
These scripts are included in the post-processing menus of MOVES3, MOVES2014 and MOVES2010b.
- The tool allows states to perform two of the calculations described in the VMT Offset Demonstration guidance (PDF) (7 pp, 830 K, EPA-420-B-12-053, August 2012, About PDF). As discussed in this guidance, these calculations “freeze” control measures in place as they existed in the 2011 base year for the 2008 ozone NAAQS, and either assume that there is growth in VMT through the attainment year, 2026, or there is no growth in VMT through the attainment year. Results of these calculations do not include the effects of post-2011 emission controls (e.g., Tier 3).
- See the README.pdf file in the download package for instructions on how to install and use this tool.
Nonroad Retrofit Tool (XLTM) (14 MB, July 2018)
- This tool is used to help quantify emission reductions from nonroad retrofit projects as explained in section 2.7 of Diesel Retrofit and Replacement Projects: Quantifying and Using Their Emission Benefits in SIPs and Conformity - Guidance for State and Local Air and Transportation Agencies (PDF) (65 pp, 1.0 MB, EPA-420-B-18-017, March 2018)
- It simplifies the creation of a MOVES nonroad retrofit input table by creating a template for that table and then filling that table based on user input.
- Instructions are included with the tool.
EPA has developed a tool to automate the process of generating the EMISFACT portion of an AERMOD input file using MOVES3 output. The tool is intended to be used as part of a quantitative PM hot-spot analysis, as described in EPA’s Transportation Conformity Guidance for Quantitative Hot-spot Analyses in PM2.5 and PM10 Nonattainment and Maintenance Areas (PDF) (160 pp, 3 MB, EPA-420-B-15-084, November 2015)
- readme.txt – Describes how to “install” the tool as well as providing instructions on using it for PM hot-spot analyses
- MOVES2AERMOD input data
- Link_Sources.csv – Define a mapping of MOVES links to AERMOD sources
- Source_Area.csv – Define the area of each MOVES link
- Traffic_Distribution – Define the peak/off-peak mapping for each of 24 hours, and four seasons
- MOVES2AERMOD.sql – This file should be placed in the appropriate MOVES folder as described in the readme.txt file
- Transit_exercise_out – An example database containing output from 16 MOVES runs used to test the MOVES2AERMOD tool