Blank emis_type

I am seeking guidance on SMOKE FF10 formats in which the emis_type column is blank (“”). This is not listed in the MOVES emissions process table in the SMOKE documentation.

This occurs in NEI SMOKE FF10 for years 2020 and 2014.

Hi,

Can you share which specific FF10 you are viewing?

I found these on the EPA GAFTP site. See following links

The blanks in emis_type indicate that the emissions values are summarized rather than related to a specific process in MOVES.

If you need the emis_type populated for 2020 I suggest using the 2020ha2 emissions modeling platform inventory, which contains emissions consistent with the 2020NEI at the county-pollutant level. Note that the SCCs also differ.
https://gaftp.epa.gov/Air/emismod/2020/2020emissions/2020ha2_onroad_SMOKE-MOVES_emissions_FF10_22sep2023.zip

An inventory containing emis_type consistent with the 2014NEI onroad inventory is not readily available. One option for 2014 onroad emissions is the 2014fd platform inventory with the caveat that this uses a different MOVES run than the 2014 NEI.
https://gaftp.epa.gov/air/emismod/2014/v2/2014fd/emissions/2014fd_SMOKE_MOVES_onroad_ff10.zip

1 Like

We stopped including EMIS_TYPE in the newer inventories as we were not using it for anything.

You can try looking in the modeling platform files which have some more detailed SCCs than the NEI flat files.

The modeling platform files are available for various years through this link:

https://gaftp.epa.gov/Air/emismod/

@eyth.alison @james.beidler, thank you for your responses.

If I am compiling multiple NEI years from SMOKE FF10, should I do do anything to combine the process types?

Hi, sorry for the delay. Are you attempting to differentiate the emissions by process type? If not then just sum across processes to get an onroad emissions total.

@james.beidler, thanks for getting back to me.

I need to break out specific pollutants but if I can document which process types are included and verify that they are included for all relevant years, summarizing up should work for my needs.

Would this also hold true for other places where SMOKE FF10 is used, like EQUATES datasets?

Yes, this will hold true for any onroad inventories for EQUATES.