MG - Monitor Road¶
The monitor’s relationship to nearby streets may be described by using the MG transaction.
Rules¶
Road referenced by these transactions must first be defined with the Site Road transaction.
If either tangent road number or distance from monitor is valued, the other must also be valued. Similarly, one may not be deleted without also deleting the other.
Examples:
MG|I|06|001|0007|88101|3|1|70.1
MG|I|TT|405|7416|11101|1|1|35
Format¶
Seq. |
Name |
Description |
Formatting Rules |
Required |
Key |
---|---|---|---|---|---|
1 |
Monitor Tangent Roads transaction identifier. |
Must = MG |
Always |
||
2 |
Indicator for Insert, Update, or Delete action. |
Must = I, U, or D |
Always |
||
3 |
The FIPS state code of the monitor, or “TT” to indicate that the next field on the transaction is a Tribal code. |
Must exist in STATES Reference Table or be ‘TT’ for Tribal Site |
Always |
Y |
|
4 |
The FIPS County Code of the site. If the previous field on the transaction contains “TT”, then the Tribal Code of the site. |
Must exist in COUNTIES (for state) or TRIBAL_AREAS Reference table |
Always |
Y |
|
5 |
Four digit number to uniquely identify site in county and/or tribe. |
Must exist in SITES table with {State Code, county Code} or Tribal Code |
Always |
Y |
|
6 |
The AQS parameter code assigned to the monitor in AQS. |
Must exist in PARAMETERS reference table. |
Always |
Y |
|
7 |
Parameter Occurrence Code: One or two digit number identifying a specific monitor for a parameter at the site. |
Must exist in MONITOR table for non-Insert actions. |
Always |
Y |
|
8 |
Number from Site record identifying a nearby street. |
Must exist in site tangent street table. |
Always |
Y |
|
9 |
The distance in meters between the sensing of air sampling equipment at a monitoring site and the nearest edge of the roadway. |
Decimal. |
Unless Delete |