The PTDAY file is the input point-source inventory file for day-specific data. The file must be a list file (see Section 8.2.1.1, “Inventory list files”) and the files listed in the PTDAY file must be in the format shown in Table 8.20, “FF10 Format for individual point day-specific data files” and Table 8.21, “Format for individual day-specific data files for fires : ORL FIREEMIS”. The contents of the day-specific data files vary depending on whether the PTINV file is in FF10 or ORL FIRE format. The day-specific files can have a #COUNTRY header entry to set the country code (see
Section 8.2.1.4, “Header records”). If no #COUNTRY header is used, then SMOKE will use the default country code of 0 (which corresponds to the United States
in the default COSTCY file).
This FF10 format uses the header described in Section 8.2.1.4, “Header records”. For daily or hourly specific emissions, the user specifies the data provided using this command in the header: FF10_DAILY_POINT.
Sample header records for daily point source data are shown below:
#FORMAT FF10_DAILY_POINT #COUNTRY US #YEAR 2005 #DESC Point Daily Source Inventory #DESC FF10 Point Daily format
Table 8.20. FF10 Format for individual point day-specific data files
| Position | Name | Type | Description |
|---|---|---|---|
| 1 | COUNTRY | Char(2) | 2 character code: e.g., US (required) |
| 2 | FIPS | Int | Five-digit FIPS code for state and county (required) |
| 3 | TRIBAL_CODE | Char(3) | Tribal code (optional; not currently used by SMOKE) |
| 4 | FACILITY_ID | Char | Plant identification code (required; this is the same as the State Facility Identifier in the NIF) |
| 5 | UNIT_ID | Char | Point Identification Code (15 characters maximum) (required; this is the same as the Emission Unit ID in the NIF) (required) |
| 6 | REL_POINT_ID | Stack Identification Code (15 characters maximum) (recommended; this is the same as the Emissions Release Point ID in the NIF) | |
| 7 | PROCESS_ID | Char | Segment Identification Code (a.k.a DOE Plant ID) (15 characters maximum) (recommended; this is the same as the Process ID in the NIF) |
| 8 | SCC | Char(10) | SCC (required) |
| 9 | POLL | Char(16) | Pollutant Code (required) |
| 10 | OP_TYPE_CD | Char(20) | Operating type code for startup/shutdown/upset (optional; not currently used by SMOKE) |
| 11 | CALC_METHOD | Int | CALC_METHOD (optional; not currently used by SMOKE) |
| 12 | DATE_UPDATED | Int | Updated date in format of YYYYMMDD (optional; not currently used by SMOKE) |
| 13 | MONTH | Int | Month of inventory (required) |
| 14 | MONTHTOT | Real | Monthly Total (short tons/month) (required) |
| 15 | DAYVAL1 | Real | Daily emissions for day 1 (short tons/day) (required) |
| 16 | DAYVAL2 | Real | Daily emissions for day 2 (short tons/day) (required) |
| 17 | DAYVAL3 | Real | Daily emissions for day 3 (short tons/day) (required) |
| .. | .. | ||
| 45 | DAYVAL31 | Real | Daily emissions for day 31 (short tons/day) (required) |
| 46 | COMMENT | Char | (optional) |
The SMOKE requires that the sources in the day-specific fires inventory format (#ORL FIREEMIS) PTDAY file also be in the PTINV file described in Section 8.2.8.3, “ORL FIRE Format”. The values of the fields that are common to the day-specific data and the master (annual) data from PTINV are used to match exactly by country/state/county code, fire identification, location identification, and SCC. Default daily
ACRESBURNED and FUEL_LOAD input are required to internally estimate heat flux for the fire-specific plume-rise computation. Fire duration information,
such as BEGHOUR and ENDHOUR are used to adjust the hourly temporal profile.
Detail script setting information for fires emission modeling is described in Section 4.4.17, “Plume Rise Calculation for Fires”.
NOTE: All inventory pollutant names need to be listed in the master (annual) PTINV and the day-specific PTDAY files using a header record #DATA. Sample header records are shown below:
#ORL FIREEMIS #TYPE Day-specific Point Source Inventory for FIRES #COUNTRY US #YEAR 2002 #DESC FIPS,FIREID,LOCID,SCC,DATA,DATE,DATAVALUE,BEGHOUR,ENDHOUR
The format for the data records is shown in Table 8.21, “Format for individual day-specific data files for fires : ORL FIREEMIS”.
Table 8.21. Format for individual day-specific data files for fires : ORL FIREEMIS
| Position | Name | Type | Description |
|---|---|---|---|
| A | FIPS | Int | State and County code (required) |
| B | FIREID | Char | Fire idenfication code (required) |
| C | LOCID | Char | Location identification code (required) |
| D | SCC | Char | SCC Flaming or Smoldering (required) |
| E | DATA | Char | The pollutant codes, "ACRESCBURNED", or "FUEL_LOAD" (16 characters) (required) |
| F | DATE | Char | MM/DD/YY format. Years less than 70 are treated as century 2000 (8 characters) (required) |
| G | DATAVALUE | Real | If the value of "DATA" is a particular pollutant, then this value represents the daily emissions associated with the particular pollutant (required) |
| H | BEGHOUR | Int | Hour of the day that the fire began (0 to 23) (required) |
| I | ENDHOUR | Int | Hour of the day that the fire ended (0 to 23) (required) |