# APPENDIX D0

Technical Support Document Mobile Source Highway Emissions Inventory

Executive Summary

Bureau of Air Quality Department of Environmental Protection

### [ This page intentionally left blank

. ]

# APPENDIX D

The Johnstown Nonattainment Area

for the 1997 Annual and 2006 24-Hour PM 2.5 

# NAAQS: Emissions Inventory Using MOVES2010a

Technical Support Document Mobile Source Highway Emissions Inventory

Executive Summary

January 2013 Prepared for:

Mobile Sources Section, Bureau of Air Quality Pennsylvania Department of Environmental Protection

PO Box 8468 Harrisburg, PA 17105-8468

Prepared by:

Michael Baker, Jr., Inc.

1304 Concourse Drive Linthicum, MD 21090

410-689-3400

### Johnstown Nonattainment Area: Mobile Source Emissions Inventory Executive Summary January 2013



# Exhibit of Contents

SUMMARY ....................................................................................................................... ........................................... 1

M OTOR V EHICLE E MISSIONS

.............................................................................................................................. ....... 1

A NALYSIS M ETHODOLOGY

.............................................................................................................................. .......... 2

DATA SOURCES AND ANALYSIS TOOLS ............................................................................................... ............ 4

A NALYSIS T OOLS

.............................................................................................................................. ........................ 4

T RAFFIC D ATA S OURCE /F LEET D ATA I NPUTS ........................................................................................................... 5

T RAFFIC G ROWTH A SSUMPTIONS

.............................................................................................................................. 7

V EHICLE P OPULATION G ROWTH A SSUMPTIONS ........................................................................................................ 8

I/M AND F UEL P ARAMETERS

.............................................................................................................................. ....... 8

M ETEOROLOGY D ATA

.............................................................................................................................. ................. 9

V EHICLE T ECHNOLOGY P ROGRAMS ........................................................................................................................ 10

RESOURCES ..................................................................................................................... ........................................ 11



# List of Exhibits

E XHIBIT 1: S UMMARY OF A PPENDICES ........................................................................................................................... 1

E XHIBIT 2: M OTOR V EHICLE E MISSIONS U SING MOVES2010 A .................................................................................... 2

E XHIBIT 3: S UMMARY OF A NALYSIS T OOLS ................................................................................................................... 4

E XHIBIT 4: PPSUITE P ROCESS

.............................................................................................................................. ........ 5

E XHIBIT 5: VMT G ROWTH A SSUMPTIONS ...................................................................................................................... 8



# Summary of Appendices

Appendix D-1: Mobile Source Highway Emissions Inventory – An Explanation of Methodology

Appendix D-2: Emission Results for PM2.5 (PM2.5, PM10, VOC, CO, NOx, SO2, NH3) (By Year, Road Type, Source Type and Process)

Appendix D-3: MOVES Sample Input FilesJ ohnstown Nonattainment Area Emissions Inventory: Executive Summary 1 

## SUMMARY

This technical appendix supports the PM 2.5 State Implementation Plan (SIP) for the Johnstown area. The

area consists of:

 Cambria County;

 Indiana County including the townships of We st Wheatfield, Center, East Wheatfield, and Armagh Borough and Homer City Borough.

To meet emission inventory requirements of section 172(c)(3) of the Clean Air Act, a regional mobile source highway inventory has been prepared for direct and precursor PM 2.5 emissions. Emissions are estimated for the 2002, 2007, 2017 and 2025 analysis years. The pollutants included in the inventory are primary emissions (including condensibles) of PM 2.5 and PM 10 and the precursor emissions of VOC, CO, NOx, SO 2 , and NH 3

.

On March 2, 2010, EPA officially released MOVES2010a to be used for all SIP submittals and future transportation conformity analyses after a grace peri od through March 2, 2012. On February 15, 2012, EPA extended the grace period to Ma rch 2, 2013. This state implementation plan provides emission inventory for the 2002, 2007, 2017 and 2025 analysis years using MOVES2010a.

Appendix D has been provided to summarize the met hodology and analysis results for the motor vehicle emissions inventory. To complement this execu tive summary, attachments have been provided with additional detail regarding the analysis methodol ogy, the MOVES input parameters, and the output vehicle miles of travel (VMT) and emission results for the region. These include:



### Exhibit 1: Summary of Appendices

Appendix Title Description

D-1 Explanation of Methodology Provides a detailed summary of the methodology used to

calculate the VMT and emissions.

D-2 ( PM 2.5 , PM 10 ,VOC, CO, NOx,

SO 2 , and NH 3 )

Emission Results Provides annual emission exhibits by county, road type, source type and process categ ories in 2002, 2007, 2017

and 2025.

D-3 MOVES Sample Input File Provides examples of the MOVES input files.



## Revised Emissions Inventory

A summary of the motor vehicle emissions for the Johnstown Area is provided in Exhibit 2 . The emission estimates for all pollutants have been developed using the MOVES2010a emission model and latest planning assumptions. Emissions have b een estimated for 2002, 2007, 2017 and 2025.J ohnstown Nonattainment Area Emissions Inventory: Executive Summary 2 

### Exhibit 2: Motor Vehicle Em issions Using MOVES2010a (Short Tons/Year)

Pollutants/

Year PM 2.5 PM 10 VOC CO NOX SO2 NH3

Cambria

2002 138.61 163.46 1,947.34 25,211.70 4,583.52 96.13 65.92

2007 111.61 136.53 1,605.59 18,342.18 3,460.17 26.56 56.84

2017 54.60 81.24 815.45 11,519.52 1,551.85 9.69 37.96

2025 40.62 70.69 527.03 9,914.01 979.51 9.74 36.82

Indiana (Partial)

2002 18.79 21.36 195.19 2,588.61 606.73 12.14 7.28

2007 19.76 22.60 164.63 1,859.14 550.78 3.31 6.18

2017 6.91 9.48 83.16 1,136.56 216.82 1.08 4.27

2025 3.81 6.25 50.55 918.09 109.98 0.98 3.83

Nonattainment Area Total

2002 157.40 184.82 2,142.53 27,800.31 5,190.24 108.27 73.20

2007 131.37 159.13 1,770.22 20,201.32 4,010.95 29.88 63.02

2017 61.51 90.72 898.61 12,656.08 1,768.67 10.76 42.23

2025 44.43 76.93 577.59 10,832.10 1,089.50 10.72 40.66



## Analysis Methodology

Guidance documents from EPA were used to develop th e base and future year emissions inventories for

the Johnstown Nonattainment Area . They include:

 Policy Guidance on the Use of MOVES2010 for SIP Development, Transportation Conformity, and Other Purposes , US EPA Office of Air and Radiation, EPA-420-B-09- 046, December 2009.

 Technical Guidance on the Use of MOVES2010 for Emission Inventory Preparation in State Implementation Plans and Transportation Conformity , US EPA Office of Air and Radiation, and Office of Transportation a nd Air Quality, EPA-420-B-10-023, April

2010.

 Motor Vehicle Emission Simulato r, User Guide for MOVES2010a, EPA-420-B-10-036, August 2010.

The highway mobile source emission inventory was de veloped using available travel data and EPA’s MOVES2010a emission model. The methodologies used to produce the emission data conform to the recommendations provided in EPA’s Technical Guidance . A mix of local data and national default (internal to MOVES2010a) data has been used for th is submission. Local data has been used for the primary data items that have a significant impact on emissions. These include:

 Vehicle miles of travel (VMT) by vehicle type.

 Average speed distribution.

 Vehicle type mixes.

 Source type population (for light-duty vehicles).

 Vehicle age distribution.J ohnstown Nonattainment Area Emissions Inventory: Executive Summary 3  Hourly distributions.

 Meteorology data.

 Inspection/Maintenance program.

 Fuel supply.

For this submission, the 2002 base year traffic data source and environmental assumptions are consistent with past analyses and submissions. For the rest of the years, most local data inputs to the analysis process reflect the latest planning assumptions based on 2008 data obtained from the Pennsylvania Department of Transportation (PennDOT), the Bur eau of Motor Vehicles, and other local/national

sources. Newer data was available and was used for tr affic forecast growth rates, control strategies (e.g. Inspection-Maintenance programs), vehicle age distributions and fuel characteristics.

The analysis methodology is consistent with past statewide inventory efforts including the 2008 National Emissions Inventory (NEI) submission. This incl udes the use of custom post processing software to calculate hourly speeds and prepare key traffic input files to the MOVES2010a emission model. A detailed methodology is provided in Appendix D-1 . The following sections address the key input data sources and analysis tools used for the emi ssions inventory for the Johnstown Area.J ohnstown Nonattainment Area Emissions Inventory: Executive Summary 4 

## DATA SOURCES AND ANALYSIS TOOLS

This section provides a summary of the key input data and analysis tools used for producing the emissions inventory. The key elements to the modeling protoc ol are described in the sections below. A more detailed description of the analysis process and t ools is provided in the methodology reports in Appendix

D-1 through D-3

.



## Analysis Tools

The mobile vehicle emissions inventory analysis u tilizes several key software/programs for producing the county emissions totals. These tools are outlined in Exhibit 3

.



### Exhibit 3: Summary of Analysis Tools

Tool Purpose

MOVES2010a Produces emission rates for primary emissions (including condensibles) of PM 2.5

and PM 10 and the precursor emissions of VOC, CO, NOx, SO 2 , and NH 3

PPSUITE Processes the highway data; Calculates hourly congested speeds for each state roadway segment; Prepares MOVES2010a input files; Processes MOVES2010a output files into a summary report.

CENTRAL Provides a batch menu driven process to execute PPSUITE, MOVES2010a and other MYSQL steps.

The inventory reflects the highway mobile sour ce emission estimations using EPA’s MOVES2010a emission model. EPA’s MOVES model was officially released on March 2, 2010 and was followed with a revised version (MOVES2010a) in August 2010. Subseque nt to the start of this analysis, EPA released a newer version, MOVES2010b, in April 2012; however, the emission rates for criteria pollutants remain consistent to previous versions . The MOVES2010a model provides a more robust estimate of emissions as compared to its predecessor MOBILE6.2. MOVES2010a has been integrated with local traffic, vehicle fleet, environmental, fuel, and control strategy data to estimate emissions.

PPSUITE represents an enhanced version of the Post Processor for Air Quality (PPAQ) software system that has been used for previous inventory and confor mity submissions in Pennsylvania. The software has undergone significant revisions to ensure consiste ncy with the MOVES2010a. PPSUITE was used to calculate hourly congested speeds fo r each roadway link, apply vehicle type fractions, aggregate VMT, prepare MOVES2010a traffic-related input files and process MOVES2010a outputs.

The PPSUITE software and process methodologies are consis tent with that used for state inventories and transportation conformity analyses throughout Pennsylvania. Exhibit 4 summarizes the key functions of

PPSUITE.J ohnstow n CENTR A

in batch m

custom M steps incl u



## Tra ff ic

Traffic V highway provide a with past

The dat a Pennsylv a Highway

PennDO T reported t
total.

Special p r The tow n designati o segments
These st a owned ro a

n Nonattainme n A L is a menu

m ode. The s
M YSQL step s

u ding file na m



## Data Sou r

V olume Data

data source f

a

“snapshot” o triennial up d

a includes t h

a nia. To ac c

Performanc e
T ’s RMS are

t o FHWA. F

r ocessing is r e

n ships withi n

o n descripti o

and used t o

a te roadway s

a dways.

n t Area Emissi o - driven softw a

s oftware allo w

s into the pr o

m ing and sto r



## r

ce/Fleet D

: The PennD O

f or the coun t

o f the region

d ates of traffi

h e average a

c ount for ad d

e Monitorin g adjusted to m
F or analysis y

e quired to es t

n the partial

o ns. Using

o identify w h

s egments we r

o ns Inventory: a re platform

w s users to e

o cess. CEN T

r age automati



## D ata Inpu t

O T Roadwa y

t y and functi al roadway s c data). The

a nnual daily

d itional local

g System ( H

m atch the an n

y ear 2007, V

t imate travel i

area were i d GIS, towns h

h ich road se g

r e used for t 

### Exhibit 4: P

Executive Su m that executes

xecute runs f

T RAL provi d

o n.



## t s

y Manageme n onal class V

s ystem and tr

2008 data is

traffic (A A roadway V M

H PMS) VM T

n ual 2002 a n V MT is adjus t

i n the partial

d entified bas

h ip boundari e

g ments fell w

t he analysis o 

### P PSUITE P

m mary s the PPSUIT

f or a variety

d es importan t

n t System (R M

V MT estimat e

r affic volume

also integrat

A DT) volu m
M T and to e n
T totals, th e

n d 2008 HP M

ted to match

county porti o ed on the n o

e s were ove r

w ithin the n o

o f VMT and 

### P rocess

T E and MOV E of input opt i

t quality co n

M S) data se r

e s. The dat a

s in 2002 an

t ed with traf fi

m es for all s

n sure consist e

e VMT tota l

M S VMT tot a h the annual 2

o ns of the no n onattainmen t

r -laid on th e

o nattainmen t

d emissions fo E S2010a pro c i ons and inte g

n trol and ass u

r ves as the p r

a source is u s

n d 2008 (con s fi c signal loc a

s tate roadw a

e ncy with re p l s estimated

a ls respectiv e 2 007 HPMS

n attainment a r -maintenanc e

e PennDOT

- maintenance

fo r non-local

5 c esses

g rates

u rance

r imary

s ed to

s istent

a tions.

a ys in

p orted

from

e ly, as

VMT

r ea.

e area

RMS

area.

state-J ohnstown Nonattainment Area Emissions Inventory: Executive Summary 6 The RMS roadway data contains some local segment s (those which are state-owned and function as local roads). Since the RMS database does not contain a comprehensive representation of local roads, local VMT is typically reconciled to the reported HPMS lo cal VMT for each county in Pennsylvania. However, HPMS VMT is only reported at the county-level. Fo r the partial areas the following methods were used

to estimate local VMT:

 Option 1: Calculate local VMT based on local road segments in RMS database (as discussed this could underestimate local VMT)

 Option 2: Using GIS, determine the fraction of CENSUS TIGER roadway local mileage in the nonattainment-maintenance area as compared to the county total. This fraction is then applied to the county HPMS local VMT.

 Option 3: Determine the fraction of populatio n in the nonattainment-maintenance area as compared to the total county population. This fr action is then applied to the county HPMS local

VMT.

The three above methods were analyzed for each nona ttainment area and the highest values were chosen to ensure that local VMT was not under-represented in the analysis. These values were used to estimate emissions for the partial nonattainment-maintenance area. Note, based on more recent snapshots of RMS data, revised CENSUS TIGER roadway coverage fil es, and updated population estimates, the amount of partial area VMT may differ from previous SIP submissions.

Seasonal Adjustments : Within MOVES, annual VMT is split to monthly sub-totals and then to weekdays and weekends using seasonal factors. Th e monthly seasonal factors are developed from data contained in the documents, 2002 Pennsylvania Traffic Data and 2008 Pennsylvania Traffic Data

, prepared by PennDOT’s Bureau of Planning and Research (BPR). The seasonal and daily factors provided in this document are based on statistical analyses of 2002 and 2008 traffic counts taken at permanent and in-pavement ATR (automatic tra ffic recorder) locations throughout the state.

Congested Speeds : Based on the average annual daily traffic, a single set of hourly speed distributions are estimated by the PPSUITE post processing system and input to MOVES. To disaggregate the daily RMS volumes to hourly volumes, auto and truck hourly pattern data from PennDOT’s 2002 Pennsylvania Traffic Data and 2008 Pennsylvania Traffic Data reports are used to determine the temporal variations in

traffic volumes.

Vehicle Population : Vehicle population is a key input that has an important impact on start and evaporative emissions. MOVES2010a requires the num ber of vehicles by 13 source types to determine evaporative emissions. State 2002 and 2008 vehicle re gistration data (consistent with past triennial updates of traffic data) was used to estimate vehicl e population for light-duty vehicles and school buses. The data was split to source types using MOVES2010a default population data. For transit buses, data from PennDOT and the National Transit Database (NTD) was used to estimate transit bus populations by county. For all other heavy-duty vehicles, PPSUITE calculates vehicle population based on the analysis year VMT for each source type and default MOVES2010a ratios of VMT and source type population (e.g. the number of miles per vehicle by source type).

VMT by Source Type : The total VMT is disaggregated to the 13 MOVES2010a source types. For this inventory, the vehicle mix was calculated for each county and functional class grouping utilizing a

combination of:

 2002 and 2008 RMS truck percentages

 2008 PennDOT and NTD transit data

 2008 school bus registration dataJ ohnstown Nonattainment Area Emissions Inventory: Executive Summary 7 EPA’s MOVES2010a default distribution of VMT by s ource type was used to determine the remaining source type VMT percentages. The development of vehicle type pattern data input to the MOVES2010a

software is described in more detail in Appendix D-1

.

Vehicle Age Distribution: Vehicle age distributions are required to be input by 13 source types. The distributions reflect the percentage of vehicles in the fleet up to 31 years old. The 2002 vehicle age

distributions have been used for the 2002 emissions inventory. A recent 2010 registration download from PennDOT’s Bureau of Motor Vehicles Registration Databa se has indicated a substantially older fleet than recorded in the 2002-2008 period. As a result, the 20 10 vehicle age distributions have been used for this inventory. Due to insufficient data, only data for lig ht-duty vehicles are used as local inputs; and heavyduty vehicle ages are calculated using the internal MOVES2010a defaults for each Pennsylvania County. The registration data download is based on MOBILE6.2 vehicle categories. The data was converted to source types using the EPA convertor spreadsheets provided with the MOVES2010a emission model.



## Traffic Growth Assumptions

Traffic growth forecasting plays a pivotal role in estim ating future year emissions for the region. There are many uncertainties affecting projections of tra ffic growth including the current economic conditions, potential fuel prices, the impacts of natural gas indu stry activities in many counties throughout the state, and the future growth in population and employment. Growth rates for this emissions inventory were

based on an assessment of available data sources incl uding the regional travel model maintained by the Johnstown Metropolitan Planning Organization and Pe nnDOT’s BPR growth rate forecasting system.

All SIP mobile source highway inventories include the review and assessment of county-specific growth rates from a PennDOT study originally comple ted in 2005 and documented in the report, Statistical Evaluation of Projected Traffic Gr owth, Traffic Growth Forecasting System: Final Report, March 14,

2005 . As part of that study, a statewide traffic growth forecasting system was developed that incorporates traffic data from PennDOT’s Traffic Information Syst em and socioeconomic forecasts. That forecasting system is maintained by the PennDOT BPR and is upda ted on a periodic basis. This system was last updated in December of 2009 to develop new statistical relationships between historic VMT growth and population (thru 2008). The forecast population was estimated from the Woods and Poole data “2010 State Profile”. The results of the study have been shared between PennDOT, PaDEP, and other Interagency Consultation Group members, including th e Pennsylvania Transportation - Air Quality Work Group (which also includes EPA, FHWA, and represen tatives from larger MPOs within the state).

The growth rates from the PennDOT BPR forecasting sy stem are evaluated against other available data including travel model growth and other insights. For the development of MVEB s, upper estimates of the VMT growth range are used for the forecast analyses. From an air quality perspective, the use of the upper boundary is conservative, and provides for f actors outside PennDOT or PaDEP control (e.g., potential socio-economic growth above current forecasts, fleet age distributions, vehicle type distribution)

that influence motor vehicle emissions. Exhibit 5 summarizes the assumed projected growth of VMT for future analysis years in the Johnstown Nonattainment Area

.J ohnstown Nonattainment Area Emissions Inventory: Executive Summary 8 

### Exhibit 5: VMT Growth Assumptions

Analysis

Year Total Growth

from 2002 Annualized Growth Rate

from Previous Year

Cambria

2002 ---- ----

2007 3.0% 0.6%

2017 20.0% 1.3%

2025 35.8% 1.6% Indiana (Partial)

2002 ---- ----

2007 2.2% 0.4%

2017 15.8% 1.1%

2025 23.8% 1.0%



## Vehicle Population Growth Assumptions

Vehicle population growth forecasting plays an importan t key role in determining emissions for future years for the region. For this inventory, vehicl e population was forecasted considering the growth from

three different sources:

 Household growth

 Population Growth

 VMT Growth

The household and population data were obtained from the PennDOT study documented in the report as discussed above, Statistical Evaluation of Proj ected Traffic Growth, Traffic Growth Forecasting System: Final Report, March 14, 2005. The forecast household and populati on were estimated from the Woods and Poole data “2010 State Profile”. The final growth rate was calculated assuming the highest growth rate of household and population data but then limiti ng it to the VMT growth rate. This methodology has been used for past conformity analyses and has b een accepted using the interagency consultation process (Pennsylvania Air Quality Workgroup).



## I/M and Fuel Parameters

I/M Program: The inspection maintenance (I/M) program inputs to the MOVES2010a model are based on past and current programs within each county (all Pennsylvania I/M programs are based on county boundaries). All analysis years include Pennsylvania’s statewide program. The MOVES2010a model has simplified the I/M program input parameters co mpared to MOBILE6.2. The default I/M program parameters included in MOVES2010a were examined for each county and necessary changes made to the defaults to match the actual local program.

In order to assure that emission controls are worki ng properly, vehicle inspection and maintenance (I/M) programs have been adopted in some nonattainment areas. These programs have the added benefit of improving the fuel efficiency of vehicles. The Pe nnsylvania inspection and maintenance (I/M) program was upgraded and expanded throughout the state with a phase-in period starting in September 2003 and fully implemented by June 2004.

The program requirements vary by region (five regions) and include on-board diagnostics (OBD) technology that uses the vehicle’s computer for mode l years 1996 and newer to identify potential engineJ ohnstown Nonattainment Area Emissions Inventory: Executive Summary 9 and exhaust system problems that could affect emissions. The program, named PAOBDII, is implemented by region, as follows:

 Philadelphia Region - Bucks, Chester, Delaware, Montgomery and Philadelphia Counties

 Pittsburgh Region - Allegheny, Beaver, Washington and Westmoreland Counties

 South Central and Lehigh Valley Region - Berks, Cumberland, Dauphin, Lancaster, Lebanon, Lehigh, Northampton and York Counties

 North Region - Blair, Cambria, Centre, Erie, Lackawanna, Luzerne, Lycoming, and Mercer

Counties

The OBDII program is implemented in Philadelphia a nd Pittsburgh along with tailpipe (idle in Pittsburgh and idle and ASM in Philadelphia) and gas cap tests. Tests in other regions include:

 Subject vehicles registered in the South Central and Lehigh Valley counties receive the visual, OBD and gas cap tests.

 Subject vehicles registered in the North region recei ve a gas cap test and visual inspection.

 Subject vehicles registered in the other 42 counti es (67 total counties) receive a visual inspection as part of the annual safety inspection.

Fuel Assumptions : The MOVES2010a default fuel formulation and fuel supply data were reviewed and updated based on available local volumetric fuel prope rty information. The gasohol market penetration and RVP values were updated but M OVES2010a default data was used for the remaining parameters. Updated assumptions included:

 Using 8.7 RVP for summer months.

 Conventional gasoline used throughout the year for analysis years 2002.

 32% market share of conventional gasoline and 68% market share of 10% ethanol used throughout the year for analysis year 2007.

 10% ethanol used throughout the year for analysis years 2017 and 2025.



## Meteorology Data

Updated weather information has been obtained from WeatherBank, Inc. ( www.weatherbank.com ). The 10-year (1998-2008) average minimum and maximum m onthly temperature and relative humidity values were obtained for each of the 9 airport locations in Pennsylvania.

The MOVES2010a model requires temperature and relative humidity data for each hour of the day and for all the 12 months for the annual analysis. EPA’s data converters were used to convert minimum and maximum daily temperatures to an hourly temperat ure profile that could be input to MOVES2010a. These assumptions are consistent with the 2008 NEI inventory submission.J ohnstown Nonattainment Area Emissions Inventory: Executive Summary 10 

## Vehicle Technology Programs

Federal Programs

Current federal vehicle emissions control and fuel programs are incorporated into the MOVES2010a software. These include the National Program standa rds covering model year vehicles through 2016. Modifications of default emission rates are required to reflect the early implementation of the National Low Emission Vehicle Program (NLEV) program in Pennsylvania. To reflect these impacts, EPA has released instructions and input files that can be used to model these impacts. This inventory utilized the August 2010 version of the files ( http://www.epa.gov/oms/models/moves/tools.htm ).

State Programs

The Pennsylvania Clean Vehicles (PCV) Program, a dopted in 1998, incorporated the California Low Emission Vehicle Program (CA LEVII) by reference, a lthough it allowed automakers to comply with the NLEV program as an alternative to this Pennsylvania program until MY 2006. Beginning with MY 2008, “new” passenger cars and light-duty trucks with a gr oss vehicle weight rating (GVWR) of 8,500 pounds or less that are sold or leased and titled in Pennsylva nia must be certified by the California Air Resources Board (CARB) or be certified for sale in all 50 states. For this program, a “new” vehicle is a qualified vehicle with an odometer reading less than 7,500 miles. PaDEP and PennDOT worked with the automobile manufacturers, dealers and other interest ed business partners and finalized procedures for complying with these new requirements. DEP focuses its outreach effort with the manufacturers and dealers regarding what vehicles can be offered for sal e and how to certify that the vehicles are compliant. PennDOT’s role is to ensure licensing and registra tion records include these certifications of compliance or that the vehicle owner qualifies for an exemptio n to the requirements. In all cases, DEP will use information obtained during PennDOT ’s title and registration process to oversee and audit, as needed,

certain vehicle title transactions to dete rmine compliance to the program.

The impacts of this program are modeled for all an alysis years beyond 2008 using the same instructions and tools as downloaded for the early NLEV analysis. EPA provided input files to reflect the CAL LEVII program. Modifications to those files were made to reflect a 2008 start date for Pennsylvania.J ohnstown Nonattainment Area Emissions Inventory: Executive Summary 11 

## RESOURCES

Motor Vehicle Emission Simulato r, User Guide for MOVES2010a, EPA-420-B-10-036, August 2010.

Technical Guidance on the Use of MOVES2010 for Emission Inventory Preparation in State Implementation Plans and Transportation Conformity , US EPA Office of Air and Radiation, and Office of Transportation and Air Quality , EPA-420-B-10-023, April 2010.

2008 Pennsylvania Traffic Data, PennDOT Bureau of Planning and Research, 2008.

Policy Guidance on the Use of MOVES2010 for SIP Development, Transportation Conformity

, and Other Purposes , US EPA Office of Air and Radiation, EPA-420-B-09-046, December 2009.

Instructions for Using LEV and NLEV Inputs for MOVES, US EPA, EPA-420-B-10-003a, August 2010.

Statistical Evaluation of Projected Traffic Growth, Traffic Growth Forecasting System: Final Report, Michael Baker Jr., Inc., March 14, 2005.

Metrological Data from Weather Bank, Inc., www.weatherbank.com

# APPENDIX D 1

Mobile Source Highway Emissions Inventory

An Explanation of Methodology

Bureau of Air Quality Department of Environmental Protection

### [ This page intentionally left blank

. ]

# APPENDIX D-1

Johnstown Area - An Explanation of MethodologyAn Explanation of Methodology 

### Explanation of Methodology January 2013



# TABLE OF CONTENTS

INTRODUCTION .................................................................................................................. ..................................... 1

O VERVIEW OF E MISSIONS I NVENTORIES .................................................................................................................... 1

H IGHWAY V EHICLE E MISSION I NVENTORIES ............................................................................................................. 1

WHERE DOES PENNSYLVANIA OBTAIN ITS DATA? ..................................................................................... 4

S UMMARY OF MOVES I NPUTS

.............................................................................................................................. .... 4

V EHICLE M ILES OF T RAVEL (VMT) ......................................................................................................................... . 5

A DJUSTMENTS TO R OADWAY D ATA .......................................................................................................................... 8

V EHICLE T YPE P ROCESSING

.............................................................................................................................. ........ 9

V EHICLE F LEET AND P OPULATION D ATA ................................................................................................................ 10

E NVIRONMENTAL

, F UEL AND T ECHNOLOGY A SSUMPTIONS .................................................................................... 11

SPEED/EMISSION ESTIMA TION PROCEDURE ........................................................................................... ... 12

V OLUME /VMT D EVELOPMENT

.............................................................................................................................. . 12

S PEED /D ELAY D ETERMINATION

.............................................................................................................................. 15

HPMS AND VMT A DJUSTMENTS ............................................................................................................................ 1 6

MOVES E MISSIONS R UN

.............................................................................................................................. .......... 17

RESOURCES ..................................................................................................................... ........................................ 18

HIGHWAY VEHICLE INVENTORY GLOSSARY ............................................................................................ . 19



## List of Exhibits

E XHIBIT 1: S UMMARY OF PPSUITE P ROCESS ................................................................................................................ 3

E XHIBIT 2: MOVES L OCAL D ATA I NPUT S UMMARY ..................................................................................................... 4

E XHIBIT 3: P ENN DOT U RBAN /R URAL AND F UNCTIONAL C LASS C ODES ....................................................................... 6

E XHIBIT 4: E MISSION F ACTOR VS

. S PEED V ARIANCES (PM2.5) ..................................................................................... 7

E XHIBIT 5: MOVES S OURCE T YPES AND HPMS V EHICLE G ROUPS .............................................................................. 9

E XHIBIT 6: PPSUITE S PEED / E MISSION E STIMATION P ROCEDURE .............................................................................. 13A ppendix D-1 1 

## INTRODUCTION

The purpose of this document is to explain how the Pennsylvania Department of Environmental Protection (Department) estimates emissions from highway vehicles for inclusion in its emission inventories and State Implementation Plans.



## Overview of Emissions Inventories

The Department’s inventories generally cat egorize emissions into four categories:

 Highway vehicles.

 Stationary sources (major industrial, commercial and utility sources).

 Area sources (smaller industrial/co mmercial sources, consumer products).

 Nonroad mobile sources (includi ng construction and agricultural equipment, lawn and garden equipment).

An evaluation of emissions from point, area, and mobile sources is needed to develop a complete inventory needed for a maintenance demonstration plan. This documen tation addresses the mobile source activity and emissions for base and future years used to support such a demonstration.

Of all of the sources of air pollution, only the emissions of some stationary sources are measured directly and continuously through instrumentation. Emission s from all other sources must be modeled based on available local data, including those from highway vehi cles. In their very simplest form, estimates of emissions follow the following pattern:

Emission rate x activity level = emissions per time period (usually day or year)

Most emission rates have been de veloped by the U.S. Environmental Protection Agency (EPA), in cooperation with industry and states, and are compiled and documented into key references or emission models. These include Compilation of Air Pollution Emission Factors (AP-42), the Motor Vehicle Emission Simulator (MOVES) model, and the NONROAD model. Adding up the products of the emission rates and activity levels for all sources of a given pollutant constitutes the emission inventory for that pollutant.



## Highway Vehicle Emission Inventories

Highway vehicles contribute significantly to air pollution, particularly to ground- level ozone, which is the most persistent air pollutant in Pennsylvania. Ground-level 

### ozone is not emitted directly to the atmosphere, but is formed by photochemical reactions between volatile organic compounds (VOCs) and oxides of nitrogen (NO

x 

### ) in the presence of sunlight. The long, hot, humid days of summer are particularly conducive to ozone forma tion, so ozone levels are of concern primarily during the months of May through September. Both VOCs and NOx are emitted from highway vehicles. In addition, fine particulates are also emitted directly by motor vehicles as a result of the combustion process (tailpipe emissions), re-entrained and transportation constr uction dust; and formed through reactions in the atmosphere among the precursors VOC, CO, NOx, NH3 and SOx. Pennsylvania’s PM-related emission inventory efforts focus on these pollutants.A ppendix D-1 2 Obviously, direct measurement of emission levels from all vehicles in use is impossible. In comparison to highway vehicles, estimating residential heating em issions is a fairly simple calculation because there is a constant emission rate and a fairly simple me asure of activity. However, for highway vehicles estimating the emission rate and activity levels of al l vehicles on the road during a typical summer day is a complicated endeavor.

If every vehicle emitted the same amount of polluti on all the time, one could simply multiply those emission standards (emission rate in grams of polluti on per mile) times the vehicle miles traveled (VMT) to estimate total emissions. But emission rates from all vehicles vary over the entire range of conditions under which they operate. These variables include ai r temperature, speed, traffic conditions, operating mode and fuel characteristics. The inventory must also account for non-exhaust or evaporative emissions. In addition, the fleet is composed of several genera tions and types of vehicles with different emission control technologies. This requires the estimation al gorithm include the composition of the fleet (vehicle ages and types).

In order to estimate both the rate at which emissions are being generated and to calculate vehicle miles traveled (activity level), Pennsylvania examines its ro ad network and fleet to estimate vehicle activity. For ozone-related inventories, this is done for a t ypical summer weekday. For carbon monoxide (CO) and particulate matter (PM) emission inventories, this may be done for a typical winter weekday, summer weekday and/or annual conditions. No t only must this be done for a baseline year, but it must also be projected into the future. This process involves a large qua ntity of data and is extremely complex.

Computer models have been devel oped to perform these calculations by simulating the travel of vehicles on the Commonwealth’s roadway system. The models al so generate emissions ra tes (also called emission factors) for different vehicle types for area-specific conditions, and then combine them in summary form. The area-specific conditions include vehicle and highw ay data, plus control measure characteristics and future year projections of all variables. The key m odels used to generate this mobile source emissions inventory are:

MOVES: EPA’s MOVES model was officially released on March 2, 2010 and was followed with a revised version (MOVES2010a) in August 2010. The MOVES model provides a more robust estimate of emissions as compared to its predecessor MOBILE6.2. MOVES calculates average in-use fleet emissions for each of thirteen categories of vehicles under vari ous conditions affecting in-use emission levels (e.g., ambient temperatures, average tra ffic speeds, gasoline volatility) as specified by the model user.

For this mobile source inventory, Pennsylvania used MOVES2010a as approved by EPA. MOVES can be used to estimate national, state, and county leve l inventories of criteria air pollutants, precursors, greenhouse gas emissions, and some mobile source air toxics from highway vehicles. Additionally, MOVES can make projections for energy consump tion (total, petroleum-based, and fossil-based).

PPSUITE: For the Department’s highway emissions inventory, a post processor named PPSUITE (formerly named PPAQ - Post Processor for Air Quality) is used, which consists of a set of programs that perform the following functions:

 Analyzes highway operating conditions.

 Calculates highway speeds.

 Compiles vehicle miles of travel (VMT) and vehicle type mix data.

 Prepares MOVES runs and processes MOVES outputs.

PPSUITE is a widely used and accepted tool for estim ating speeds and processing emissions rates. The software is based upon accepted transportation engin eering methodologies. For example, PPSUITE uses speed and delay estimation procedures based on planning methods provided in the Highway CapacityA ppendix D Manual

, a and anal y

The PPS U

summari z County D

The follo

emission s speed c a

recomme n

 P

C

0 4

 T

S t

R

2 0

The proc e fullest ex t
emission s

D -1 a report prep a

y sis technique

U ITE process

z es the key f u D ata Manager

w ing section

s inventory.

a lculation pr o

n dations pro v

P olicy Guida n C onformity, a n

4 6, Decemb e

T

echnical Gu i

t ate Impleme

R adiation, an d

0 10.

e ss has focu s

t ent. This i n

s and applyin g a red by the T s for capacit y

is integral t o

u nctions of P (CDM).



### Exhi b

s summarize

This includ e

o cess. Th e

v ided by EP A

n ce on the U

n d Other Pu r

e r 2009.

i dance on th e ntation Plan s d Office of T

s ed on devel o

n cludes the u s

g a robust cal T ransportatio n

y and level-o f

o producing k

P PSUITE an d



### b it 1: Sum m

the key dat a

e s a summar y

e emission d

A in key polic y

U

se of MO V

rp oses , US E P

e Use of MO

s and Trans p T ransportati o

o ping an emi s

s e of availab culation pro c n Research B o f -service anal y

k ey input file s d the traffic- r



### m ar y of PPS U

a and metho d

y of local da t
d ata and p r

y and technic a

V

ES2010 for

P A Office o f

VES2010 fo r

p ortation Co nf

o n and Air Q

s sions invent

le local data

ess to estima t o ard (TRB) s

y ses of the tr a

s to the MO V

r elated input



### U ITE Proc e

d ologies use d

t a sources a n

r ocess has b al guidance a

SIP Devel o f Air and Ra d

r Emission I n nf

ormity , US Q uality, EP A

t ory using th e

for items th a

t e hourly tra f s ummarizing

a nsportation s

V ES emissio n

files prepare



### e ss

d to produce

n d a step-byb een develo p

a s provided b e

o

pment, Tra n d iation, EPA

n ventory Pre p EPA Office

A -420-B-10-0 2

e available t o

a t have a si g f fic speeds. current kno w

s ystem.

n model. Ex h

d for the M O

the mobile s step review o

p ed accordi n

e low:

n sportation

- 420-B-09-

p aration in

of Air and

2 3, April

o ols and data

g nificant imp a

3 w ledge

h ibit 1

O VES

s ource

o f the

n g to

to its

a ct onA ppendix D-1 4 

## WHERE DOES PENNSYLVANIA OBTAIN ITS DATA?

Summary of MOVES Inputs

A large number of inputs to MOVES are needed to fully account for the numerous vehicle and environmental parameters that affect emissions. These include traffic flow characteristics (as determined from the PPSUITE software), vehicle descriptions, fuel parameters, inspection/maintenance program parameters, and environmental variables. MOVES in cludes a default national database of meteorology, vehicle fleet, vehicle activity, fuel, and emission c ontrol program data for every county; but EPA cannot certify that the default data is the most current or b est available information for any specific area. As a result, local data is recommended for use for an alyses supporting state implementation plans (SIPs).

A mix of local and default data is used for this invent ory. Local data sources are used for all inputs that have a significant impact on calculated emission rates. Exhibit 2 summarizes Pennsylvania-specific inputs assembled and used for this inventory. Th ese data items are discussed in the following sections.



### Exhibit 2: MOVES Local Data Input Summary

Traffic Vehicle Fuel Inspection Environmental Data Descriptions Parameters Maintenance Variables

Vehicle Type Vehicle Type RVP Start Year Ho urly VMT Mix Model Years Temperatures

Vehicle Vehicle Age Sulfur Test Standards, Population Distribution Level Source Types, Humidity Frequency

VMT Average Speeds Ethanol Stringency, Fractions (PPSUITE) Volume Waiver Rate, (PPSUITE) Compliance

Road Type Hourly Refueling

Distribution Dist ributions Controls (PPSUITE)

Ramp

Fraction (PPSUITE)

Emission RatesA ppendix D-1 5 

## Vehicle Miles of Travel (VMT)

The VMT input to emissions calculations for Pennsy lvania is based on information from the Roadway Management System (RMS) maintained by the Pennsylvania Department of Transportation’s (PennDOT’s) Bureau of Planning and Research (BPR). PennDOT obtains this information from periodic

visual and electronic traffic counts. RMS data is dynamic, since it is continually reviewed and updated from new traffic counts and field visits conducted by PennDOT. Information on roadways included in the National Highway System is reviewed at least annuall y, while information on other roadways is reviewed at least biennially.

On a triennial basis, a current “snapshot” of the RM S database is taken and downl oaded to provide an upto-date record of the Commonwealth’s highway sy stem for estimating emissions. This emissions inventory is based on the most curre nt snapshot of the RMS data.

The RMS database contains all state highways, in cluding the Pennsylvania Turnpike, divided into segments approximately 0.5 miles in length. These segments are usually divided at important intersections or locations where there is a change in the physical characteristic s of the roadway (e.g. the number of lanes changes). There are approximately 99,000 state highway segments for the 67 Pennsylvania counties contained in the RMS. E ach of these segments contains an abundance of descriptive data, but only the following inform ation is extracted for emission calculations:

 Lanes.

 Distances.

 Volumes representing Average Annual Daily Traffic (AADT).

 Truck percentages.

 PennDOT urban/rural classifications.

 PennDOT functional class codes.

 Number of signals (based on linkage to PennDOT GIS signal location data).

RMS volumes and distances are used in calculating hi ghway VMT totals for each county. As discussed in the next section, adjustments are needed to c onvert the volumes to refl ect annual conditions. In addition, the traffic volumes must be forecast to suppor t future year emission inventories. Lane values and traffic signals are an important input for de termining the congestion and speeds for individual highway segments. Truck percentages are used in th e speed determination process and are used to split volumes to individual vehicle types used by the MOVES software.

Road segments are classified by function, as well as whet her it is located in an urban, small urban or rural area, as indicated below in Exhibit 3. The PennDOT urban/rural (UR) and functional classes (FC) are important indicators of the type and function of each roadway segment. The variables provide insights

into other characteristics not contained in the RMS data that are used for speed and emission calculations.A ppendix D-1 6 

### Exhibit 3: PennDOT Urban/Rura l and Functional Class Codes

Urban/Rural Code 1=Rural

2=Small Urban

3=Urban

Functional Class Rural Functional Classes Used Urban Functional Classes Used

For Rural Areas For Small Urban and Urban Areas

------------------------------------- ------------------------------------------ 1=Rural Freeway 11=Urban Freeway 2=Rural Other Principal Arterial 12=Urban Expressway 6=Rural Minor Arterial 14=Urban Principal Arterial 7=Rural Major Collector 16=Urban Minor Arterial

8=Rural Minor Collector 17=Urban Collector

9=Rural Local 19=Urban Local

Additional Network Information: The PPSUITE software system allows for many additional variables

other than those available in the RMS database. Using these variables improves the ability of the Department to incorporate real roadway conditions in to its estimates. The variables include information regarding free-flow speeds and capacities, signal charact eristics and other physical roadway features that can affect a roadway’s calculated congested speed. This data can be determined from lookup tables based on a roadway segment’s urban/rural code and func tional class. Much of the lookup table data was developed from information contained in the Highway Capacity Manual , PennDOT information on speeds and signal densities, and other engineering judgment.

MOVES Traffic Inputs: The PPSUITE software uses RMS traffic data to prepare key inputs to the MOVES emission model including:

 VMT.

 Travel speeds.

 Road type distributions.

 Ramp fractions.

VMT is the primary traffic input that affects emissi on results. The roadway segment distances and traffic volumes are used to prepare estimates of VMT. PP SUITE performs these calculations and outputs the MOVES annual VMT input file to the County Data Manager (CDM).

Emissions for many pollutants (including PM and precursors) vary significantly with travel speed. For PM, higher emission rates are associated with lower speeds and lower rates are associated with higher speeds, as illustrated in Exhibit 4. To obtain the b est estimate of vehicle speeds, the Department uses the PPSUITE set of programs, whose primary function is to calculate speeds and to organize and simplify the handling of large amounts of data needed for calculating speeds and for preparing MOVES input files. The PPSUITE software prepares the MOVES vehicle hour s of travel (VHT) by speed bin file which summarizes the distribution of speeds across all links into each of 16 MOVES speed bins for each hour of the day. This robust process ensures that MOVES emis sion rates are used to the fullest extent and is

consistent with the methods and recommendations provided in EPA’s Technical Guidance on the Use of MOVES2010 for Emissions Inventory Preparation in State Implementation Plans and Transportation Conformity

.A ppendix D In MOV E

MOVES d

1 O

2 R

3 R

4 U

5 U

The off-n

emission s input, as d equating t

 M

 M

 M

 M

For this i n the defin e

Since ra m the Free w technical

D -1 

### E x

E S, typical d

d efines five d

O ff-Network

. R ural Restric t

R ural Unrest r U rban Restri c U rban Unres t

etwork road t

s . Off-netw o d iscussed in a

t he PennDO T

M OVES Roa d

M OVES Roa d

M OVES Roa d

M OVES Roa d

n ventory, the

e d equivalenc

m ps are not d i

w ay VHT is

guidance. 

### x hibit 4: E m

d rive cycles

d ifferent road

. t ed Access.

r icted Access

.

c ted Access.

t ricted Acces s

t ype include s

o rk activity i

a following s e
T functional c l

d Type (2) = P

d Type (3) = P

d Type (4) = P

d Type (5) = P

MOVES ro a ies.

i rectly repres Ramp VHT

. Source: F

Source Emi s 

### m ission Fac t

and associat types as foll o

.

s

.

s emissions f r n MOVES i

e ction. The r l ass with eac h

P ennDOT Fu n
P ennDOT Fu n
P ennDOT Fu n
P ennDOT Fu n

a d type distri b

ented within

. This is c o F igure 3 from Imp l

s sion Estimates, A i 

### t or vs. Spe e

ed operating

o ws:

r om vehicle s t s primarily d

r emaining dis

h MOVES ro

n ctional Clas s

n ctional Clas s

n ctional Clas s

n ctional Clas s

b ution file is

the RMS da t

o nsistent wit h l ications of the MO

i r & Waste Mana g 

### e d Variance

g conditions v

tarts, extend e d etermined b

s tribution am o ad type as fo l

s (1).

s (2,6,7,8,9).

s (11,12).

s (14,16,17,1 9

automaticall y

t abase infor m h the recom m O VES2010 Model

g ement Associatio n 

### s (PM2.5)

vary by the

e d idle activi t
b y the Sourc e

o ng road typ e l lows:

9 ).

y generated b

m ation, it is a s

m endations p on Mobile

n , July 2010.

type of roa d

t y, and evap o

e Type Pop u

e s is determi n

b y PPSUITE

s sumed that 8

p rovided in E

7 d way.

o rative

u lation

n ed by

using

8 % of

E PA’sA ppendix D-1 8 

## Adjustments to Roadway Data

Before the RMS data can be used by PPSUITE for speed and emission calculations, several adjustments and additions must be made to the roadway da ta. These adjustments ar e summarized below.

HPMS Adjustments: According to EPA guidance, baseline inventory VMT computed from the RMS highway segment volumes must be adjusted to be consistent with Highway Performance Monitoring System (HPMS) VMT totals. The HPMS VMT reported for Pennsylvania is a subsystem of the RMS established to meet the data reporting requirements of the Federal Highway Administration (FHWA) and to serve as PennDOT’s official source of highway in formation. Although it has some limitations, the HPMS system is currently in use in all 50 states and is being improved under FHWA direction.

Although the HPMS VMT and the roadway data used fo r an inventory emissions analysis are both based on data from the RMS system, differences do exist betw een them and include the following. First, the HPMS and inventory roadway data are “snapshots” of th e RMS data taken at different times. Since the RMS is dynamic, changing constantly due to new data , differences will result betw een the data used for calculating HPMS VMT totals and the inventory data u sed for an emissions analysis. Second, since the RMS does not contain many of the local roadways, local road estimates of HPMS VMT are obtained through alternative procedures developed by PennDOT . To account for such differences, adjustment factors are calculated and used to adjust the inve ntory roadway data to the reported HPMS VMT totals

submitted to FHWA. The VMT contained in the HPMS reports are considered to represent average annual daily traffic (AADT).

Adjustment factors are calculated which adjust th e base year RMS download VMT to the reported HPMS totals for that year. These factors are developed for each county and functional class combination and are also applied to all future year runs. Adjustme nts for the “higher” functional classes (e.g. Freeway, Arterials - major routes) are close to 1.000 since HP MS VMT is derived from RMS information, and the only difference in the data is that the “snapshot” for the emission calculations is taken at a different time

than for the HPMS. “Lower” classes (e.g. local roads) require greater ad justment since a large part of the local system is not under state jurisdiction and is not in the RMS database. There is, of course, a significant amount of local road mileage in the state. It is assumed that those local streets that are in RMS are representative of all local streets in their area with respect to volume and speed, so that roadway mileage adjustment is appropriate.

Seasonal Adjustments to Volumes: The RMS contains AADT volumes that are an average of all days in the year, including weekends and holidays. PM and CO analyses require volumes representing monthly average conditions (needed for producing annual totals). Therefore, the RMS volumes must be seasonally adjusted. Seasonal factors were developed for each functional class and urban/rural code based on yearly count information prepared by PennDOT’s BPR. These factors are applied to the existing RMS AADT volumes to produce the monthly volumes. The same f actors are also used to develop the MOVES daily and monthly VMT fraction files.

Hourly Adjustments: Speeds and emissions vary considerab ly depending on the time of day. Therefore, it is important to estimate the pattern by which roadway volume varies by hour of the day. The 24-hour pattern data provides PPSUITE with info rmation used to split the daily roadway segment volumes to each of the 24 hours in a day. Pattern data is in the form of a percentage of the daily volumes for each hour. Distributions are provided for each c ounty and functional class gr ouping. This data is developed from 24-hour count data compiled by PennDOT’s BPR, according to the process in the agencies annual traffic data reports. The same factors are also used to develop the MOVES hourly

fraction file.A ppendix D-1 9 Traffic Volume Forecasts: Traffic growth forecasting plays a pivotal role in estimating future year emissions for the region. There are many uncertainti es affecting projections of traffic growth, including the current economic conditions, potential fuel prices, the impacts of Marcellus Shale activities in many counties throughout the state, and the future growth in population and employment. Growth rates for the Department’s emissions inventories are based on an assessment of available data sources which include:

 PennDOT BPR growth rate forecasting system.

 Regional travel model, if available.

 Estimates of Marcellus Shale related activity growth, if applicable.

All SIP mobile source highway inventories include the review and assessment of county-specific growth rates from a PennDOT study originally comple ted in 2005 and documented in the report, Statistical Evaluation of Projected Traffic Gr owth, Traffic Growth Forecasting System: Final Report, March 14,

2005 . As part of that study, a statewide traffic growth forecasting system was developed that incorporates traffic data from PennDOT’s Traffic Information Syst em and socioeconomic forecasts. That forecasting system is maintained by the PennDOT BPR and is updated on a periodic basis to develop new statistical relationships between historic VMT growth a nd population and updated demographic forecasts from Woods and Poole, Inc. The growth rates from th e PennDOT BPR forecasting system are evaluated against other available data including trav el model growth and other insights.



## Vehicle Type Processing

Emission rates within MOVES vary significantly by the type of vehicle. The MOVES model produces emissions and rates by thirteen MOVES vehicle source types. However, VMT is input to MOVES by six HPMS vehicle groups. Exhibit 5 summarizes the distinction between each classification scheme.



### Exhibit 5: MOVES Source Type s and HPMS Vehicle Groups

SOURCE TYPES HPMS Class Groups 11 Motorcycle 10 Motorcycle 21 Passenger Car 20 Passenger Car 31 Passenger Truck 30 Passenger/Light Truck 32 Light Commercial Truck 40 Buses 41 Intercity Bus 50 Single Unit Trucks

42 Transit Bus 60 Combination Trucks

43 School bus

51 Refuse Truck 52 Single Unit Short-haul Truck 53 Single Unit Long-haul Truck

54 Motor Home

61 Combination Short-haul Truck 62 Combination Long-haul Truck

The process used for this inventory includes a met hod to disaggregate the RMS traffic volumes to the thirteen source types and then to r ecombine the estimates to the six HPMS vehicle classes. Vehicle type pattern data is used by PPSUITE to divide the hour ly roadway segment volumes to the thirteen MOVES source types. Similar to the 24-hour pattern data, this data contains percentage splits to each source type for every hour of the day. The vehicle type pattern data for this inventory is developed from several

sources of information:A ppendix D-1 10  PennDOT truck percentages from the RMS database.

 Hourly distributions for trucks and tota l traffic compiled by PennDOT’s BPR.

 Transit data from PennDOT and the National Transit Database.

 School bus registration data from PennDOT’s Bure au of Motor Vehicles Registration Database.

The vehicle type pattern data is developed for each county and functional class combination. First, RMS truck percentages are averaged for all roadways with in a county and functional class grouping. Using this percentage data, the total roadway volume for any seg ment is divided to auto and truck vehicle type categories. The transit data and school bus data is used to further disaggregate trucks, resulting in four vehicle groups (light-duty, school, transit, and other heavy-duty).

From these groups, MOVES default Pennsylvania county VMT distributions by source type are used to divide the four groups into each of the MOVES sour ce types. PennDOT hourly distributions for trucks and total traffic are used to create source type pe rcentage breakdowns for each hour of the day.

Vehicle Type Capacity Analysis Factors : Vehicle type percentages are provided to the capacity analysis section of PPSUITE to adjust the speeds in res ponse to trucks. That is, a given number of larger trucks take up more roadway space than a given number of cars, and this is accounted for in the speed estimation process by adjusting cap acity using information from the Highway Capacity Manual

.



## Vehicle Fleet and Population Data

The information on the vehicle fleet including the number and age of vehicles has a significant impact on forecasted start and evaporative emissions within MOVES. The MOVES Model requires the population of vehicles by the thirteen source type categories. Pe nnsylvania county vehicle registration data is used to estimate vehicle population for light-duty vehicles and school buses. The data is split to source types using MOVES2010a default Pennsylva nia county population data. For transit buses, data from PennDOT and the National Transit Database (NTD) is used to estimate county transit bus totals. Other heavy-duty vehicle population values are based on VMT for each sour ce type using the vehicle mix and pattern data discussed previously. The PPSUITE software automa tically applies default MOVES2010a ratios of VMT and source type population (e.g. the number of mil es per vehicle by source type) to the local VMT estimates to produce vehicle population.

Vehicle population is forecast based on projected household and population growth from Woods and Poole Inc. for each Pennsylvania county. The growth rate methodology includes:

 Choosing the highest growth rate between population and households.

 Limiting growth as to not exceed the VMT growth assumptions.

Vehicle Age: Vehicle age distributions are input to MOVES for each county by the thirteen source types. The distributions reflect the percentage of vehicles in the fleet up to 31 years old. The most recent available registration download from PennDOT’s Bur eau of Motor Vehicles Registration Database has been used for the inventory. Due to insufficient da ta, only information for light-duty vehicles are used as local inputs; and, heavy-duty vehicles use the inte rnal MOVES2010a national defaults. The registration data download is based on MOBILE6.2 vehicle categories. As a result, the data was converted to source types using the EPA convertor spreadsheets pr ovided with the MOVES2010a emission model.A ppendix D-1 11 

## Environmental, Fuel and Technology Assumptions

Information on environmental, fuel, vehicle technol ogy and other control strategy assumptions were determined based on a review of MOVES2010a default information by the PaDEP.

Fuel Parameters: The same vehicle will produce different emi ssions using a different type of gasoline. Fuel control strategies can be powerful emission reduction mechanisms. The MOVES2010a default fuel formulation and fuel supply data were reviewed and updated based on available local volumetric fuel property information. The gasohol market penetra tion and RVP values were updated for all the counties. MOVES2010a default data was used for the rest of the parameters.

Refueling Emissions : MOVES also allows users to calculate refueling emissions, the emissions created when vehicles are refueled at service stations. Pennsylvania includes refueling emissions in its area source inventory and not in its highway vehicle invent ory. Refueling emissions are not included in the highway emissions inventory.

Vehicle Emission Inspection/Maintenance (I/M) Parameters: MOVES allows users to vary inputs depending on the I/M program in place for the area. The inputs include:

 Program start year.

 Stringency level.

 First and last model years subject to the program.

 Waiver rates.

 Compliance rates.

 Program type (test-only, test-and-repair, etc.) and effectiveness.

 Frequency of inspection (annual, biennial).

 Vehicle type coverage.

 Test type (idle, loaded, etc.)

The MOVES2010a default Pennsylvania assumptions were reviewed and modifications were made per actual program parameters.

Environmental Variables: Evaporative emissions are influenced significantly by the temperatures of the surrounding air. Hourly temperatures have been compiled for each county based on information from WeatherBank, Inc. to specify temperatures from nine airports within the state. Ozone analysis temperature and humidity values were determined us ing the procedures documented in EPA’s technical guidance. Minimum and maximum temperatures for each month were converted to hourly temperatures using EPA convertors supplied with the MOVES2010a model.

A summary of the MOVES related inputs used for the inventory and future year estimates are attached

with the submission.A ppendix D-1 12 

## SPEED/EMISSION ESTIMATION PROCEDURE

The previous sections have summarized the input da ta used for computing speeds and emissions for Pennsylvania. This section explai ns how PPSUITE and MOVES uses that input data to produce emission estimates. Exhibit 6 summarizes PPSUITE’s analysis procedure used for each of the RMS highway segments in the state.

Producing an emissions inventory w ith PPSUITE requires a process of di saggregation and aggregation. Data is available and used on a very small scale -- individual 1⁄2 mile roadway segments 24 hours of the day. This data needs to be processed individually to determine the distribution of vehicle hours of travel (VHT) by speed and then aggregated by vehicle cl ass to determine input VMT to the MOVES emission

model.



## Volume/VMT Development

Before speeds can be calculated and MOVES run, volumes acquired from RMS must be adjusted and disaggregated. Such adjustments include factori ng to future years, seasonal adjustments, and disaggregating daily volumes to each hour of the day and to each of the thirteen MOVES source types.

Determine Future Year Volumes : The RMS database contains up-to-date current year volumes. However, to conduct a future year analysis, these volum es must be factored to the year being analyzed. Growth factors have been prepared for each county and functional class grouping. These growth factors are applied to the base year RMS volumes to obtain future year estimates that can be utilized by

PPSUITE.

Example:

A typical freeway link in the RMS database is I-80 segment 2500 in Luzerne County, Pennsylvania. This link has an urban/rural code=1 which indicates the link is in a rural area, and a functional class=1 indicating a rural freeway.

The average annual daily traffic (AADT) from the RMS database for this link in 2008 is 12,077 vehicles/day.

Growth factors have been developed to factor the 2008 volume to future years. For example, to factor the 2008 volume to the year 2014, a growth factor of 1.282 would yield:

2014 volume = 12,077 vehicles/day x 1.282 = 15,483 vehicles/dayA ppendix D-1 13 

### Exhibit 6: PPSUITE Speed / Em ission Estimation Procedure

Data From PPSUITE Input Files PPSUITE Analysis Process Data from Roadway Source (RMS)

The Following is Performed For Each RMS Roadway Segment

Percent Pattern Distributions Expand to 24 hourly volum es RMS AWDT Adjusted Volumes

Apply VMT Adjustments Adjust Volumes for Peak Spreading (V/C thresholds for spreading)

Vehicle Type Patterns Disaggregate to Vehicle Type RMS Truck Percentages

Transit Data

School Bus Data

Calculate Link & Signal Capacities Roadway Attributes (Lanes, FC code, UR code) Speed/Capacity Lookup Table

Calculate Link Calculate Midblock Speed Approach Delay

Apply Post Speed VMT Adjustments

Prepare MOVES CDM Files

VHT by Annual RoadType SourceType Hourly Ramp Speed Bin VMT Frac tions Population Fractions Fractions

Per VMT
<Optional>

Off-line File Preparation

Vehicle Age Distribution Run MOVES Importer to convert county input data Hourly into MYSQL data format Temps/Humidity

I/M

Parameters

Fuel Run MOVES

ParametersA ppendix D-1 14 Seasonal Adjustments : PPSUITE takes the input daily volumes from RMS (which represents annual average daily traffic (AADT)) and seasonally adjusts th e volumes to an average weekday in July. This adjustment utilizes factors developed for each functi onal class and urban/rural code. VMT can then be calculated for each link using th e adjusted weekday volumes.

Example:

Again, assume the rural freeway link: I-80 segmen t 2500 in Luzerne County, Pennsylvania. The AADT for this link in 2008 is 12,077 vehicles/day.

Seasonal factors have been developed for urban/rural code and functional class combinations. For an urban/rural code=1 and a functional class=1, the factor to convert from AADT to an average weekday in July is = 1.15.

Average Weekday July Volume = 12,077 x 1.15 = 13,889 vehicles/day.

Total VMT (daily) for this link is calculated as volume x distance. The distance of this link as

obtained from RMS is 0.296 miles.

2008 VMT = 13,889 vehicles/day x 0.296 miles = 4,111 vehicle-miles / day.

Disaggregation to 24 Hours : After seasonally adjusting the link volume, the volume is split to each hour of the day. This allows for more accurate speed calculations (effects of congested hours) and allows PPSUITE to prepare the hourly VMT and speeds for input to the MOVES model.

Example:

To support speed calculations and emission estimates by time of day, the July weekday volume is disaggregated to 24 hourly volumes. Temporal patterns were previously developed from PennDOT count data and input to PPSUITE. For the I-80 rural freeway link with morning peak volumes similar to evening peak hours (neutral), the following temporal pattern is applied:

0 1 2 3 4 5 6 7 8 9 101357911131517192123
Hour of DayPercent of Daily

Using the I-80 segment, typical hourly volumes which result include: 8-9 a.m. 6.0% x (4,111 vehicle miles/ 0.296mi.) = 833 vehicles/hour (vph) 12-1 p.m. 5.0% x (4,111 vehicle .miles/ 0.296mi.) = 694 vph 5-6 p.m. 6.3% x (4,111 vehicle miles/ 0.296mi.) = 875 vphA ppendix D-1 15 After dividing the daily volumes to each hour of th e day, PPSUITE identifies hours that are unreasonably congested. For those hours, PPSUITE then spreads a portion of the volume to other hours within the same peak period, thereby approximating the “peak spr eading” that normally occurs in such over-capacity

conditions.

Disaggregation to Vehicle Type : EPA requires VMT estimates to be prepared by source type, reflecting specific local characteristics. As a result, for Penns ylvania’s emission inventory runs, the hourly volumes are disaggregated to the thirteen MOVES source ty pes based on count data assembled by PennDOT in

combination with MOVES defaults.

Example:

Disaggregation of the total I-80 VMT to the various source types would include the following:

Total Volume 8-9 am = 833 vph

Source Type Volume 8-9 am: Motorcycle 11 0.5% 4 vph Passenger Car 21 54.7% 456 vph Passenger Truck 31 27.9% 232 vph Light Commercial Truck 32 9.3% 78 vph Intercity Bus 41 0.1% 1 vph Transit Bus 42 0.1% 1 vph School bus 43 0.1% 1 vph Refuse Truck 51 0.0% 0 vph Single Unit Short-haul Truck 52 2.2% 19 vph Single Unit Long-haul Truck 53 0.3% 2 vph Motor Home 54 0.1% 1 vph Combination Short-haul Truck 61 1.9% 16 vph Combination Long-haul Truck 62 2.6% 22 vph



## Speed/Delay Determination

EPA recognizes that the estimation of vehicle speeds is a difficult and complex process. Because emissions are so sensitive to speeds, it recommends sp ecial attention be given to developing reasonable and consistent speed estimates; it also recommends th at VMT be disaggregated into subsets that have roughly equal speed, with separate emission factors for each subset. At a minimum, speeds should be estimated separately by road type.

The computational framework used for this analysis meets and exceeds that recommendation. Speeds are individually calculated for each roadway segment and hour and include the delays encountered at signals. Rather than accumulating the roadway segments into a particular road type and calculating an average speed, each individual link hourly speed is represente d in the MOVES vehicle hours of travel (VHT) by speed bin file. This MOVES input file allows the specification of a distribution of hourly speeds.

For example, if 5% of a county’s arterial VHT operates at 5 mph during the AM peak hour and the remaining 95% operates at 65 mph, this can be re presented in the MOVES speed input file. For the model runs, distributions of speeds are input to MOVES by road type and source type by each hour of the day; VMT and VHT is accumulated by the same groupi ngs for the application of the emission factors to produce resulting emission totals.A ppendix D-1 16 To calculate speeds, PPSUITE first obtains initial capacities (how much volume the roadway can serve before heavy congestion) and free-flow speeds (spe eds assuming no congestion) from the speed/capacity lookup data. As described in prev ious sections, this data contains default roadway information indexed by the urban/rural code and functional class. For ar eas with known characteristics, values can be directly coded to the RMS database and the speed/capacity da ta can be overridden. However, for most areas where known information is not available, the sp eed/capacity lookups provide valuable default information regarding speeds, capacities, signal characte ristics, and other capacity adjustment information used for calculating congested delays and speeds. An effort has been made to enhance the RMS data with traffic signal locations using other GIS signal data available from PennDOT’s Bureau of Highway Safety and Traffic Engineering.

Example:

The speed/capacity lookup table is used to obtain important data used for link speed calculations. For the I-80 link with an urban/rural code = 1 (rural) and a functional class = 1 (freeway), the lookup table provides information including the following:

freeflow speed = 65 mph capacity = 1800 vph per lane number of signals = 0 (per RMS linkage to GIS traffic signal locations)

This information is used along with the physical characteristics of the ro adway to calculate the delay (including congestion) to travel this link during each hour of the day:

For example: The I-80 link is calculated to have a travel time, including delay of 17.76 seconds

for the 8-9am hour.

Total travel time, in vehicle hours, for the 8-9am hour is calculated as:

VHT (8-9am) = 17.76 seconds x 833vph / 3600 sec/hr = 4.12 vehicle hours.

The result of this process is an estimated average tr avel time for each hour of the day for each highway segment. The average time can be multiplied by th e volume to produce vehicle hours of travel (VHT).



## HPMS and VMT Adjustments

Volumes must also be adjusted to account for di fferences with the HPMS VMT totals, as described previously. VMT adjustment factors are provided as input to PPSUITE, and are applied to each of the roadway segment volumes. These factors were de veloped from the latest HPMS download (conducted triennially); however, they are also applied to any fu ture year runs. The VMT added or subtracted to the RMS database assumes the speeds calculated using the original volumes for each roadway segment for each hour of the day.A ppendix D-1 17 Example:

Using the Luzerne County I-80 rural freeway link example, the daily assigned volume is adjusted

to account for reconciliation with the HPMS VM T. RMS VMT (in AADT) for Luzerne County rural freeways totals 962,559 vehicle miles in 2008. HPMS VMT (in AADT) as supplied by PennDOT and reported to FHWA totals to 990,088 vehicle miles for the rural freeways. A factor is developed by dividing the HPMS VMT by the RMS VMT:

HPMS adjustment factor for Luzerne County rural freeways = 990,088 / 962,559 = 1.029.

This factor is held constant in all future years. As an example, this adjustment is made to the I-80 freeway link VMT for the 8-9am hour after speed calculations are made, and produces the final July weekday VMT for this hour used for Ozone runs.

I-80 Link VMT (8-9am) = 833vph x 0.296 miles x 1.029 = 254 vehicle miles.



## MOVES Emissions Run

After computing speeds and aggregating VMT and VHT , PPSUITE prepares traffic-related inputs needed to run EPA’s MOVES software, which is used to es timate emission factors in grams of pollutant per vehicle mile and to produce total emissions based on input VMT to the model. The process uses MOVES2010a, the officially released emissions model that was obtained directly from EPA.

The MOVES inputs prepared by PPSUITE include the following:

 Vehicle Type VMT.

 Vehicle Population.

 VMT fractions.

 Average speed distributions.

 Road Type Distribution.

 Ramp Fractions.

These files are text formatted files with a *.csv exte nsion. The files are provided as inputs within the MOVES county data importer. In addition the re maining MOVES input data including temperatures, I/M programs, fuel and vehicle ages are prepared manually outside of the PPSUITE process.

The MOVES county importer is run in batch mode. Th is program converts all data files into the MYSQL formats used by the MOVES model. At that point a MOVES run specification file (*.mrs) is created which specifies options and key data locations for th e run. MOVES is then executed in batch mode.

MOVES can be executed using either the inventory or rate-based approaches. For this highway emissions inventory, MOVES is applied using the inventory-based approach. Under this method, actual VMT and population are provided as inputs to the model; MOVES is responsible for producing the total emissions for the region. Under the rate-based appr oach, MOVES would produce emission factors, after which PPSUITE would apply the emission factors to th e link data and calculate total regional emissions.A ppendix D-1 18 

## RESOURCES

MOVES model

Modeling Page within EPA’s Office of Mobile Sources Website (http://www.epa.gov/omswww/models.htm) contains a downloadable model, MOVES users guide and

other information.

Motor Vehicle Emission Simulato r, User Guide for MOVES2010a, EPA-420-B-10-036, August 2010.

Technical Guidance on the Use of MOVES2010 for Emission Inventory Preparation in State Implementation Plans and Transportation Conformity , US EPA Office of Air and Radiation, and Office of Transportation and Air Quality , EPA-420-B-10-023, April 2010.

Policy Guidance on the Use of MOVES2010 for SIP Development, Transportation Conformity

, and Other Purposes , US EPA Office of Air and Radiation, EPA-420-B-09-046, December 2009.

Traffic Engineering

Highway Capacity Manual, Transportation Research Board, presents current knowledge and techniques for analyzing the transportation system.

Traffic Data Collection and Fact or Development Report, 2008 Data, Pennsylvania Department of Transportation, Bureau of Planning and Research.A ppendix D-1 19 

## Highway Vehicle Inventory Glossary

AADT: Average Annual Daily Traffic, average of ALL days.

AWDT: Average Weekday Daily Traffic.

Basic emission rates: MOBILE emission rates based on the app licable Federal emission standards and the emission control technologies characteriz ing the fleet in various model years.

Emission rate or factor: Expresses the amount of pollution emitted per unit of activity. For highway vehicles, usually in grams of pollutant emitted per mile driven.

FC: Functional code, applied in data management to road segments to identify their type (freeway, local, etc.).

Fuel volatility: The ability of fuel components to evaporate, thus entering the atmosphere as pollution. Fuel volatility is usually measured as Reid Vapor Pr essure (RVP) in pounds per square inch. The lower the RVP, the less volatile the fuel.

Growth factor: Factor used to convert volumes to future years.

HPMS: Highway Performance Monitoring System, PENNDOT ’s official source of highway information

and a subset of RMS.

I/M: Vehicle emissions inspection/maintenance program s ensure that vehicle emission controls are in good working order throughout the life of the vehicle. The programs require vehicles to be tested for emissions. Most vehicles that do not pass must be repaired.

MOBILE: The model EPA has developed and which Pennsylvania uses to estimate emissions from highway vehicles.

MOVES: The latest model EPA has developed with which Pennsylvania uses to estimate emissions from highway vehicles.

Pattern data: Extrapolations of traffic patterns (such as how traffic volume on road segment types varies by time of day, or what kinds of vehicles tend to use a road segment type) from segments with observed data to similar segments.

PPSUITE: Post-Processor for Air Quality, a set of progr ams that estimate speeds and processes MOBILE

emission rates.

RMS: Roadway Management System, a database maintain ed by PENNDOT from traffic counts and field

visits.

Segment (also referred to as link): Division of roadway in the PENNDOT Roadway Management System. Usually represents 0.5 mile segments of roadway.

UR: Urban/rural code, applied in data management to identify whether a road segment is urban, small

urban or rural.A ppendix D-1 20 VHT: Vehicle hours traveled

.

VMT: Vehicle miles traveled. In modeling terms, it is the simulated traffic volumes times link length.

Vehicle Type : One of eight types, distinguished primarily by fuel type and/or weight, used in MOBILE modeling.

Source Type : One of thirteen types, distinguished primarily by weight, used in MOVES modeling.

Road Type: Functional code, applied in data management to road segments to identify their type (rural/urban highways, rura l/urban arterials, etc.)

County Data Manager: User interface developed to simplify importing specific local data for a single county or a user-defined custom domain without requ iring direct interaction with the underlying MySQL

database.

# APPENDIX D 2

Highway Emissions Estimates 2007, 2017, 2025 (Provided in Electronic Form Only)

Bureau of Air Quality Department of Environmental Protection

### [ This page intentionally left blank

. ]

# APPENDIX D-2 Johnstown Area Emission Summary Tables

A ppendix D-2-1

2002 Annual Emissions

Emission Summar y Emission Summary by Road Type Emission Summary by Source Typ e Emission Summary by Proces s



### A ppendix D-2-2

2007 Annual Emissions

Emission Summar y Emission Summary by Road Type Emission Summary by Source Typ e Emission Summary by Proces s



### A ppendix D-2-3

2017 Annual Emissions

Emission Summar y Emission Summary by Road Type Emission Summary by Source Typ e Emission Summary by Proces s



### A ppendix D-2- 4

2025 Annual Emissions

Emission Summar y Emission Summary by Road Type Emission Summary by Source Typ e Emission Summary by Proces s

# APPENDIX D 3

MOVES Input Parameter Summary

Bureau of Air Quality Department of Environmental Protection

### [ This page intentionally left blank

. ]APPENDIX D-3Johnstown Area MOVES Sample Input FilesAppendixD‐31MOVES Run Specification File SettingsSample xml file format<moves><importer mode="county" ><filters><geographicselections>(Specify County to be run)<geographicselection type="COUNTY" key="42021" description="PENNSYLVANIA - Cambria County"/></geographicselections><timespan><year key="2025"/><month id="00"/><day id="2"/><day id="5"/><beginhour id="1"/><endhour id="24"/><aggregateBy key="Hour"/></timespan><onroadvehicleselections><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="62" sourcetypename="CombinationLong-haul Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="61" sourcetypename="CombinationShort-haul Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="41" sourcetypename="Intercity Bus"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="32" sourcetypename="Light Commercial Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="54" sourcetypename="Motor Home"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="11" sourcetypename="Motorcycle"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="21" sourcetypename="Passenger Car"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="31" sourcetypename="Passenger Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="51" sourcetypename="Refuse Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="43" sourcetypename="School Bus"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="53" sourcetypename="Single UnitLong-haul Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="52" sourcetypename="Single UnitShort-haul Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="42" sourcetypename="Transit Bus"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="62" sourcetypename="Combination Long-haul Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="61" sourcetypename="Combination Short-haul Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="41" sourcetypename="Intercity Bus"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="32" sourcetypename="Light Commercial Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="54" sourcetypename="Motor Home"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="11" sourcetypename="Motorcycle"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="21" sourcetypename="Passenger Car"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="31" sourcetypename="Passenger Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="51" sourcetypename="Refuse Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="43" sourcetypename="School Bus"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="53" sourcetypename="Single Unit Long-haul Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="52" sourcetypename="Single Unit Short-haul Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="42" sourcetypename="Transit Bus"/></onroadvehicleselections><offroadvehicleselections></offroadvehicleselections><offroadvehiclesccs></offroadvehiclesccs><roadtypes><roadtype roadtypeid="1" roadtypename="Off-Network"/><roadtype roadtypeid="2" roadtypename="Rural Restricted Access"/><roadtype roadtypeid="3" roadtypename="Rural Unrestricted Access"/><roadtype roadtypeid="4" roadtypename="Urban Restricted Access"/><roadtype roadtypeid="5" roadtypename="Urban Unrestricted Access"/></roadtypes></filters><databaseselection servername="localhost" databasename="42021_2025_00_25_Avgann_mi"/><agedistribution>AppendixD‐32<description><![CDATA[]]></description><parts><sourceTypeAgeDistribution>(Specify Age Distribution datafile name for county being run)<filename>C:\PAMOVES\MOVESInputs\AgeDistribution\10Reg_RepCty\2025\42027_2025_SourceTypeAgeDistribution.csv</filename></sourceTypeAgeDistribution></parts></agedistribution><avgspeeddistribution><description><![CDATA[]]></description><parts><avgSpeedDistribution>(Specify Average Speed Distribution data file name for county being run – Asprepared by PPSUITE post processor)<filename>C:\PAMOVES\Out\PA_2025_Avgann_Inv\\42021_2025_00_25_Avgann\CDM\avgSpeedDistribution.csv</filename></avgSpeedDistribution></parts></avgspeeddistribution><imcoverage><description><![CDATA[]]></description><parts><imcoverage>(Specify I/M Parameters file name for county being run)<filename>C:\PAMOVES\MOVESInputs\IM\42000_2025_IMCoverage.csv</filename></imcoverage></parts></imcoverage><fuel><description><![CDATA[]]></description><parts><FuelSupply>(Specify Fuel Supply data file name for county being run)<filename>C:\PAMOVES\MOVESInputs\Fuel\MOVES2010a\42000_2012_FuelSupply.csv</filename></FuelSupply><FuelFormulation>(Specify Fuel Formulation data file name for county being run)<filename>C:\PAMOVES\MOVESInputs\Fuel\42000_FuelFormulation_MOVES2010a.csv</filename></FuelFormulation></parts></fuel><zonemonthhour><description><![CDATA[]]></description><parts><zoneMonthHour>(Specify Meteorology data filename for county being run)<filename>C:\PAMOVES\MOVESInputs\Meteorology\2008\42021_2008_met.csv</filename></zoneMonthHour></parts></zonemonthhour><roadtypedistribution><description><![CDATA[]]></description><parts><roadTypeDistribution>(Specify Road Type Distribution datafile name for county being run – As prepared by PPSUITE post processor)<filename>C:\PAMOVES\Out\PA_2025_Avgann_Inv\\42021_2025_00_25_Avgann\CDM\roadTypeDistribution.csv</filename></roadTypeDistribution></parts></roadtypedistribution><sourcetypepopulation><description><![CDATA[]]></description><parts><sourceTypeYear>(Specify Vehicle Populationdata file name for county being run)AppendixD‐33<filename>C:\PAMOVES\Out\PA_2025_Avgann_Inv\\42021_2025_00_25_Avgann\CDM\SourceTypePopulation.csv</filename></sourceTypeYear></parts></sourcetypepopulation><rampfraction><description><![CDATA[]]></description><parts><roadType>(Specify Ramp Fractions data file name for county being run – As prepared by PPSUITE post processor)<filename>C:\PAMOVES\MOVESInputs\RampFraction\rampfraction_defaults.csv</filename></roadType></parts></rampfraction><vehicletypevmt><description><![CDATA[]]></description><parts>(Specify Annual VMT and VMT Fractions file names for county being run – As prepared byPPSUITE post processor)<hpmsVTypeYear><filename>C:\PAMOVES\Out\PA_2025_Avgann_Inv\\42021_2025_00_25_Avgann\CDM\hpmsVTypeYear.csv</filename></hpmsVTypeYear><monthvmtfraction><filename>C:\PAMOVES\MOVESInputs\MonthDayHourFractions\2025_MonthFraction\42021_2025_MonthVMTFraction.csv</filename></monthvmtfraction><dayvmtfraction><filename>C:\PAMOVES\MOVESInputs\MonthDayHourFractions\dayvmtfraction_avgday.csv</filename></dayvmtfraction><hourvmtfraction><filename>C:\PAMOVES\Out\PA_2025_Avgann_Inv\\42021_2025_00_25_Avgann\CDM\hourvmtfraction.csv</filename></hourvmtfraction></parts></vehicletypevmt></importer></moves>Sample mrs file format<runspec><description><![CDATA[MOVES2010 RunSpec Created by CENTRAL4 Scenario: CAMB 2025 ANNAVG Avgann Emission Inventory with user's data]]></description><modelscale value="INV"/><modeldomain value="SINGLE"/><geographicselections>(Specify County to be run)<geographicselection type="COUNTY" key="42021" description="PENNSYLVANIA - Cambria County"/></geographicselections><timespan><year key="2025"/><month id="1"/><month id="2"/><month id="3"/><month id="4"/><month id="5"/><month id="6"/><month id="7"/><month id="8"/><month id="9"/><month id="10"/><month id="11"/><month id="12"/><day id="2"/>AppendixD‐34<day id="5"/><beginhour id="1"/><endhour id="24"/><aggregateBy key="Hour"/></timespan><onroadvehicleselections><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="11" sourcetypename="Motorcycle"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="21" sourcetypename="PassengerCar"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="31" sourcetypename="PassengerTruck"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="32" sourcetypename="Light Commercial Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="11" sourcetypename="Motorcycle"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="21" sourcetypename="Passenger Car"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="31" sourcetypename="Passenger Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="32" sourcetypename="Light Commercial Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="11" sourcetypename="Motorcycle"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="21" sourcetypename="Passenger Car"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="31" sourcetypename="Passenger Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="32" sourcetypename="Light Commercial Truck"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="41" sourcetypename="IntercityBus"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="42" sourcetypename="Transit Bus"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="43" sourcetypename="School Bus"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="41" sourcetypename="Intercity Bus"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="42" sourcetypename="Transit Bus"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="43" sourcetypename="School Bus"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="41" sourcetypename="Intercity Bus"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="42" sourcetypename="Transit Bus"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="43" sourcetypename="School Bus"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="51" sourcetypename="Refuse Truck"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="52" sourcetypename="Single Unit Short-haul Truck"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="53" sourcetypename="Single Unit Long-haul Truck"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="54" sourcetypename="Motor Home"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="61" sourcetypename="Combination Short-haul Truck"/><onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="62" sourcetypename="Combination Long-haul Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="51" sourcetypename="Refuse Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="52" sourcetypename="Single Unit Short-haul Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="53" sourcetypename="Single Unit Long-haul Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="54" sourcetypename="Motor Home"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="61" sourcetypename="Combination Short-haul Truck"/><onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="62" sourcetypename="Combination Long-haul Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="51" sourcetypename="Refuse Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="52" sourcetypename="Single Unit Short-haul Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="53" sourcetypename="Single Unit Long-haul Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="54" sourcetypename="Motor Home"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="61" sourcetypename="Combination Short-haul Truck"/><onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="62" sourcetypename="Combination Long-haul Truck"/></onroadvehicleselections><offroadvehicleselections></offroadvehicleselections><offroadvehiclesccs></offroadvehiclesccs><roadtypes><roadtype roadtypeid="1" roadtypename="Off-Network"/><roadtype roadtypeid="2" roadtypename="Rural Restricted Access"/><roadtype roadtypeid="3" roadtypename="Rural Unrestricted Access"/><roadtype roadtypeid="4" roadtypename="Urban Restricted Access"/><roadtype roadtypeid="5" roadtypename="Urban Unrestricted Access"/></roadtypes><pollutantprocessassociations><pollutantprocessassociation pollutantkey="2" pollutantname="Carbon Monoxide (CO)" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="2" pollutantname="Carbon Monoxide (CO)" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="2" pollutantname="Carbon Monoxide (CO)" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="2" pollutantname="Carbon Monoxide (CO)" processkey="16" processname="Crankcase StartExhaust"/><pollutantprocessassociation pollutantkey="2" pollutantname="Carbon Monoxide (CO)" processkey="17" processname="Crankcase Extended Idle Exhaust"/>AppendixD‐35<pollutantprocessassociation pollutantkey="2" pollutantname="Carbon Monoxide (CO)" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="3" pollutantname="Oxides of Nitrogen" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="3" pollutantname="Oxides of Nitrogen" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="3" pollutantname="Oxides of Nitrogen" processkey="15" processname="Crankcase RunningExhaust"/><pollutantprocessassociation pollutantkey="3" pollutantname="Oxides of Nitrogen" processkey="16" processname="Crankcase Start Exhaust"/><pollutantprocessassociation pollutantkey="3" pollutantname="Oxides of Nitrogen" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="3" pollutantname="Oxides of Nitrogen" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="79" pollutantname="Non-Methane Hydrocarbons" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="79" pollutantname="Non-Methane Hydrocarbons" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="79" pollutantname="Non-Methane Hydrocarbons" processkey="11" processname="Evap Permeation"/><pollutantprocessassociation pollutantkey="79" pollutantname="Non-Methane Hydrocarbons" processkey="12" processname="Evap FuelVapor Venting"/><pollutantprocessassociation pollutantkey="79" pollutantname="Non-Methane Hydrocarbons" processkey="13" processname="Evap FuelLeaks"/><pollutantprocessassociation pollutantkey="79" pollutantname="Non-Methane Hydrocarbons" processkey="15" processname="CrankcaseRunning Exhaust"/><pollutantprocessassociation pollutantkey="79" pollutantname="Non-Methane Hydrocarbons" processkey="16" processname="CrankcaseStart Exhaust"/><pollutantprocessassociation pollutantkey="79" pollutantname="Non-Methane Hydrocarbons" processkey="17" processname="CrankcaseExtended Idle Exhaust"/><pollutantprocessassociation pollutantkey="79" pollutantname="Non-Methane Hydrocarbons" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="11" processname="Evap Permeation"/><pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="12" processname="Evap FuelVapor Venting"/><pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="13" processname="Evap FuelLeaks"/><pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="15" processname="CrankcaseRunning Exhaust"/><pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="16" processname="CrankcaseStart Exhaust"/><pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="17" processname="CrankcaseExtended Idle Exhaust"/><pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="90" processname="ExtendedIdle Exhaust"/><pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="11" processname="Evap Permeation"/><pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="12" processname="Evap Fuel Vapor Venting"/><pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="13" processname="Evap Fuel Leaks"/><pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="16" processname="Crankcase Start Exhaust"/><pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="90" processname="ExtendedIdle Exhaust"/><pollutantprocessassociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5 - Total" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5 - Total" processkey="2" processname="StartExhaust"/><pollutantprocessassociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5 - Total" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5 - Total" processkey="16" processname="Crankcase Start Exhaust"/><pollutantprocessassociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5 - Total" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5 - Total" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="116" pollutantname="Primary PM2.5 - Brakewear Particulate" processkey="9" processname="Brakewear"/><pollutantprocessassociation pollutantkey="112" pollutantname="Primary PM2.5 - Elemental Carbon" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="112" pollutantname="Primary PM2.5 - Elemental Carbon" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="112" pollutantname="Primary PM2.5 - Elemental Carbon" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="112" pollutantname="Primary PM2.5 - Elemental Carbon" processkey="16" processname="Crankcase Start Exhaust"/><pollutantprocessassociation pollutantkey="112" pollutantname="Primary PM2.5 - Elemental Carbon" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="112" pollutantname="Primary PM2.5 - Elemental Carbon" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="111" pollutantname="Primary PM2.5 - Organic Carbon" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="111" pollutantname="Primary PM2.5 - Organic Carbon" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="111" pollutantname="Primary PM2.5 - Organic Carbon" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="111" pollutantname="Primary PM2.5 - Organic Carbon" processkey="16" processname="Crankcase Start Exhaust"/><pollutantprocessassociation pollutantkey="111" pollutantname="Primary PM2.5 - Organic Carbon" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="111" pollutantname="Primary PM2.5 - Organic Carbon" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5 - Sulfate Particulate" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5 - Sulfate Particulate" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5 - Sulfate Particulate" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5 - Sulfate Particulate" processkey="16" processname="Crankcase Start Exhaust"/><pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5 - Sulfate Particulate" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5 - Sulfate Particulate" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="117" pollutantname="Primary PM2.5 - Tirewear Particulate" processkey="10" processname="Tirewear"/><pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="100" pollutantname="Primary Exhaust PM10 - Total" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="100" pollutantname="Primary Exhaust PM10 - Total" processkey="2" processname="StartExhaust"/><pollutantprocessassociation pollutantkey="100" pollutantname="Primary Exhaust PM10 - Total" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="100" pollutantname="Primary Exhaust PM10 - Total" processkey="16" processname="Crankcase Start Exhaust"/>AppendixD‐36<pollutantprocessassociation pollutantkey="100" pollutantname="Primary Exhaust PM10 - Total" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="100" pollutantname="Primary Exhaust PM10 - Total" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="106" pollutantname="Primary PM10 - Brakewear Particulate" processkey="9" processname="Brakewear"/><pollutantprocessassociation pollutantkey="102" pollutantname="Primary PM10 - Elemental Carbon" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="102" pollutantname="Primary PM10 - Elemental Carbon" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="102" pollutantname="Primary PM10 - Elemental Carbon" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="102" pollutantname="Primary PM10 - Elemental Carbon" processkey="16" processname="Crankcase Start Exhaust"/><pollutantprocessassociation pollutantkey="102" pollutantname="Primary PM10 - Elemental Carbon" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="102" pollutantname="Primary PM10 - Elemental Carbon" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="101" pollutantname="Primary PM10 - Organic Carbon" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="101" pollutantname="Primary PM10 - Organic Carbon" processkey="2" processname="StartExhaust"/><pollutantprocessassociation pollutantkey="101" pollutantname="Primary PM10 - Organic Carbon" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="101" pollutantname="Primary PM10 - Organic Carbon" processkey="16" processname="Crankcase Start Exhaust"/><pollutantprocessassociation pollutantkey="101" pollutantname="Primary PM10 - Organic Carbon" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="101" pollutantname="Primary PM10 - Organic Carbon" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="105" pollutantname="Primary PM10 - Sulfate Particulate" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="105" pollutantname="Primary PM10 - Sulfate Particulate" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="105" pollutantname="Primary PM10 - Sulfate Particulate" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="105" pollutantname="Primary PM10 - Sulfate Particulate" processkey="16" processname="Crankcase Start Exhaust"/><pollutantprocessassociation pollutantkey="105" pollutantname="Primary PM10 - Sulfate Particulate" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="105" pollutantname="Primary PM10 - Sulfate Particulate" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="107" pollutantname="Primary PM10 - Tirewear Particulate" processkey="10" processname="Tirewear"/><pollutantprocessassociation pollutantkey="116" pollutantname="Primary PM2.5 - Brakewear Particulate" processkey="9" processname="Brakewear"/><pollutantprocessassociation pollutantkey="117" pollutantname="Primary PM2.5 - Tirewear Particulate" processkey="10" processname="Tirewear"/><pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="31" pollutantname="Sulfur Dioxide (SO2)" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="31" pollutantname="Sulfur Dioxide (SO2)" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="31" pollutantname="Sulfur Dioxide (SO2)" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="31" pollutantname="Sulfur Dioxide (SO2)" processkey="16" processname="Crankcase Start Exhaust"/><pollutantprocessassociation pollutantkey="31" pollutantname="Sulfur Dioxide (SO2)" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="31" pollutantname="Sulfur Dioxide (SO2)" processkey="90" processname="Extended IdleExhaust"/><pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="90" processname="Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="1" processname="Running Exhaust"/><pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="2" processname="Start Exhaust"/><pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="15" processname="Crankcase Running Exhaust"/><pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="16" processname="Crankcase Start Exhaust"/><pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="17" processname="Crankcase Extended Idle Exhaust"/><pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="90" processname="Extended Idle Exhaust"/></pollutantprocessassociations><databaseselections><databaseselection servername="localhost" databasename="early_NLEV" description=""/><databaseselection servername="localhost" databasename="calevii08" description=""/></databaseselections><inputdatabase servername="" databasename="" description=""/><uncertaintyparameters uncertaintymodeenabled="false" numberofrunspersimulation="0" numberofsimulations="0"/><geographicoutputdetail description="COUNTY"/><outputemissionsbreakdownselection><modelyear selected="false"/><fueltype selected="false"/><emissionprocess selected="true"/><onroadoffroad selected="true"/><roadtype selected="true"/><sourceusetype selected="true"/><movesvehicletype selected="false"/><onroadscc selected="false"/><offroadscc selected="false"/><estimateuncertainty selected="false" numberOfIterations="2" keepSampledData="false" keepIterations="false"/><sector selected="false"/><engtechid selected="false"/><hpclass selected="false"/></outputemissionsbreakdownselection>(Specify outputdatabase file name for county being run)<outputdatabase servername="localhost" databasename="42021_2025_00_25_Avgann_mo" description=""/>><outputtimestep value="Month"/>AppendixD‐37<outputvmtdata value="true"/><outputsho value="true"/><outputsh value="true"/><outputshp value="true"/><outputshidling value="true"/><outputstarts value="true"/><outputpopulation value="true"/>(Specify input database file name for county being run)<scaleinputdatabase servername="localhost" databasename="42021_2025_00_25_Avgann_mi" description=""/><pmsize value="0"/><outputfactors><timefactors selected="true" units="Hours"/><distancefactors selected="false" units="Miles"/><massfactors selected="false" units="Grams" energyunits="Million BTU"/></outputfactors><savedata></savedata><donotexecute></donotexecute><generatordatabase shouldsave="false" servername="" databasename="" description=""/><donotperformfinalaggregation selected="false"/><lookuptableflags scenarioid="" truncateoutput="false" truncateactivity="false"/><internalcontrolstrategies><internalcontrolstrategy classname="gov.epa.otaq.moves.master.implementation.ghg.internalcontrolstrategies.rateofprogress.RateOfProgressStrategy"><![CDATA[useParameters No]]></internalcontrolstrategy></internalcontrolstrategies></runspec>

# APPENDIX D 4

MOVES Input/Output Files (Provided in Electronic Form Only)

Bureau of Air Quality Department of Environmental Protection

### [ This page intentionally left blank

. ]