The Non-Point, On-Road, and Non-Road Emissions are generated using the Area Bridge Tool. As with all the Bridge Tools, the records between tables are “linked” to the child records by a set of columns that uniquely define the record from the “parent” table. Please note that you cannot “switch” how you identify the records between the “parent” and the “child”. Once you choose a method of identification, you must be consistent throughout. We will discuss the columns that define the unique records in a table, show the “parent” table, and show what “child” tables are available. These pieces of information will provide you a map of what tables you will need to populate to create a successful XML file.

The Location table is the top-level table for the Area version of the Bridge Tool, and has no “parent” table. There are multiple ways that a Location can be defined in EIS. The three primary methods are by FIPS State and County Codes, by Tribal Codes, and by Shape Identifiers (“shapes” are sub-county designations of area that are valid for only a handful of source classification codes (SCCs), such as railroad lines). The Location record’s only “child” table is the EmissionsProcess table. A Location record is uniquely identified by the following:

• State and County FIPS Code
OR
• Tribal Code
OR
• Shape Identifier

It should be noted that technically the Location record can also be uniquely defined by the Census Block number or by a Census Tract number. However, to date, no records have ever been defined this way. For purposes of this discussion, we will only consider the above mentioned methods of identifying a location record.

EmissionsProcess has the Location record as the “parent” and has several “child” tables to which it may be connected:

• DeleteReportingPeriod (no children exist beyond this table)
• ReportingPeriod
• ControlApproach

Records in the EmissionsProcess table are uniquely identified by the Location unique key plus the following:

• Source Classification Code (SCC)
• Emissions Type Code (this field may be null)

ReportingPeriod has the EmissionsProcess record as the “parent” and has several “child” tables to which it may be connected:

• OperatingDetails (no children exist beyond this table)
• Emissions (no children exist beyond this table)
• SupplementalParameter (no children exist beyond this table)

Records in the Area ReportingPeriod table are uniquely identified by the EmissionsProcess unique key plus the following:

• ReportingPeriodTypeCode

ControlApproach has the EmissionsProcess record as the “parent” and has several “child” tables to which it may be connected:

• ControlPollutant (no children exist beyond this table)
• ControlMeasure (no children exist beyond this table)

Records in the ControlApproach table are uniquely identified by the EmissionsProcess unique key. No additional items are required to make the record unique.