MJ - Monitor Collocation Period¶
Submission of this transaction is recommended for collocated monitors when the raw data for both monitors is submitted to AQS. When the raw data is posted to production, the post process will also create collocated QA pair records when the raw data falls within collocation period for the specific monitors.
Examples:
MJ|I|06|001|1001|88101|1|20021104|20030415||Y
MJ|I|TT|614|7001|44201|1|20020701|||Y
Format¶
Seq. |
Name |
Description |
Formatting Rules |
Required |
Key |
|---|---|---|---|---|---|
1 |
Monitor Collocation Period transaction identifier. |
Must = MJ |
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 begin date when a collocated monitor pair recorded precision and accuracy data. |
YYYYMMDD. |
Always |
Y |
|
9 |
The end date when a collocated monitor pair recorded precision and accuracy data. |
YYYYMMDD. |
No |
||
10 |
The distance, in meters, between the samplers. |
Decimal. |
No |
||
11 |
Indicates if the monitor is the primary of the pair. |
Must = Y or N. |
Always |