6.2. Inventory Files

6.2. Inventory Files
Prev	Chapter 6. SMOKE Input Files	Next

6.2.1. Overview
6.2.2. ARDAY: Area source day-specific emissions
6.2.3. ARHOUR: Area source hour-specific emissions
6.2.4. ARINV: Area-source annual or average-day emissions
6.2.5. MBINV: Mobile-source activity and emissions
6.2.6. PTDAY: Point source day-specific emissions
6.2.7. PTHOUR: Point source hour-specific emissions
6.2.8. PTINV: Point source annual or average day emissions

The directories where the inventory files should be stored are listed in Table 6.1, “Inventory File Locations”. The table also lists the programs that use each input file.

6.2.1. Overview

6.2.1.1. Inventory list files
6.2.1.2. File format header
6.2.1.3. Required and optional fields
6.2.1.4. Header records

6.2.1.1. Inventory list files

Area-, mobile-, and point-source inventories are provided to SMOKE as ASCII text files using the logical file names ARINV, MBINV, and PTINV, respectively. These files may either contain the actual inventory data (i.e. source characteristics, emissions data, and other information) or they can contain a list of file names with full paths (i.e. /apps/smoke/data/inventory/nei02/area/arinv.txt); in the latter case, we call the file a “list file”. When the inventory is a list file, SMOKE will open and read the data in each of the listed files and combine the data into one inventory. You may also choose to separate your data into multiple files, splitting the data by country or into EGU versus nonEGU point sources, or to reduce the individual file sizes. Some inventory formats require that a list file is used; this will be noted in the format descriptions.

6.2.1.2. File format header

All area-, mobile-, and point-source inventory files must include information specifying the file format being used. This is accomplished using a header entry, either in each individual inventory file or in the list file, if one is being used. Valid format options are:

#CEM indicates that the file is in CEM format
#LIST indicates that the file is a list file
#LIST GRID indicates that the file is a list of global gridded emission inventory files
#FF10 indicates that the file is in FF10 (Flat File 10) format is shared between different source categories for annual/monthly or daily/hourly and point/nonpoint/nonroad/onroad data. The user specifies the data provided using this command in the header: FF10_[HOURLY|DAILY]_[NONPOINT|POINT|NONROAD|ONROAD].
#ORL indicates that the file is in ORL format (usually used for toxics inventories)
#ORL NONPOINT indicates that the file is in ORL format for nonpoint sources
#ORL FIRE indicates that the file is in ORL format for fires sources
#ORL FIREEMIS indicates that the file is in ORL format for day-specific fires sources

6.2.1.3. Required and optional fields

Inventory files can include both required and optional fields. In the format tables for each file, required fields are labeled “required”; optional fields are labeled either “recommended”, “optional”, or “not used by SMOKE”. For column-specific file formats, you may leave blank the fields that are optional. List-directed files, on the other hand, must have a default value (usually -9) for these fields.

6.2.1.4. Header records

The ORL and FF10 formats used for the area-, mobile-, and point-source inventories require a set of header records at the beginning of each file. The general format of the header records is:

command parm1 parm2 ... parm n

The command field starts in the first column of the row. The remainder of the line is list-directed, with each field separated by blanks. The specific header commands vary by source category and format and are listed in Table 6.12, “Inventory header commands for ORL, and FF10 formats”.

Table 6.12. Inventory header commands for ORL, and FF10 formats

Command Parameter Description and Values

#FF10_ACTIVITY

#FF10_[NONPOINT|POINT|NONROAD|ONROAD]

#FF10_[HOURLY|DAILY]_[NONPOINT|POINT|NONROAD|ONROAD]

#ORL

#ORL NONPOINT

#ORL FIRE

#ORL FIREEMIS

N/A

#TYPE File type First nonblank character after #TYPE to the last character of the line. For on-road mobile activity data, the word “activity” must appear in this header entry; otherwise, SMOKE assumes that the file contains emissions data.

#COUNTRY Country name Valid names are those in the COSTCY or GEOCODE_LEVEL[1-4](FF10 Format only) file(s) (US, CANADA, MEXICO, etc.)

#YEAR Data year Number from 1900 to 2200

#DESC Description Description of the data (not used by SMOKE)

#DATA or #POLID

data1 data2 ... data n

In wild/Rx fires ORL format files (#ORL FIRE (“Section 6.2.8.3, “ORL FIRE Format””) and day-specific #ORL FIREEMIS file (“Section 6.2.6.2, “ORL FIREEMIS Emission Format””), it defines a complete list of pollutant names from day-specific ORL FIREEMIS files; “data1” is the first pollutant name or CAS number, “data2” is the second pollutant name( or CAS number ), and so on.

Sample header records are given for each file in their respective sections.