MC - Monitor Type¶
The monitor type transaction allows the user to set the admistrative classifiation of a monitor.
Rules¶
The monitor type assignment for a production monitor cannot be changed, (i.e., updated or deleted), in a manner that would leave any portion of that monitor’s sample periods without a monitor type assignment.
Examples:
MC|I|06|001|0007|88101|3|SLAMS|20110301|
MC|I|TT|614|7004|81102|1|TRIBAL|20020701|
Format¶
Seq. |
Name |
Description |
Formatting Rules |
Required |
Key |
|---|---|---|---|---|---|
1 |
Monitor Type Info transaction identifier. |
Must = MC |
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 |
The monitor’s administrative classification as determined by the purpose for the monitor in the agency sampling strategy. |
Must exist in MONITOR TYPES reference table. |
Always |
Y |
|
9 |
The date on which the monitor type assignment went into effect. |
YYYYMMDD. |
Always |
Y |
|
10 |
The date on which the monitor type assignment ceased being in effect. |
YYYYMMDD. |
No |