MN - Monitor Network Affiliation¶
This transaction is used to specify a monitor’s network affiliation(s).
Network affiliations are created for specific date ranges, and multiple affiliations can be specified for a single monitor at the same time.
Examples:
MN|I|06|001|0012|88101|3|NEAR ROAD|20140201|
MN|I|TT|W44|0901|68103|5|CSN SUPPLEMENTAL|20010815|
Format¶
Seq. |
Name |
Description |
Formatting Rules |
Required |
Key |
---|---|---|---|---|---|
1 |
Monitor Network Affiliation transaction identifier. |
Must = MN |
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 |
Monitoring network associated with monitor (e.g. NCORE, PAMS, NATTS) |
Must exist in MONITORING NETWORKS table. |
Always |
||
9 |
Beginning of date range where the monitor is affiliated with the specified network. |
YYYYMMDD. |
Always |
Y |
|
10 |
End of date range where the monitor affiliated with the specified network. |
YYYYMMDD. |
No |