EPA-454/B-94-006
ft
AIRS User's Guide
Volume AQ2:
Air Quality Data Coding
U. S. Environmental Protection Agency
Office of Air Quality Planning and Standards
Monitoring and Data Analysis Division
National Air Data Branch
Research Triangle Park, North Carolina 27711
February 1994
2}
o
P/'.r:"!ON AGENCY
, D.C. ?:>•'. ,C
-------
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
Table of Contents
1.0 Introduction 1-1
2.0 Overview of Data Coding and Validation 2-1
2.1 Submit Function Processes 2-3
2.1.1 LOAD Process 2-3
2.1.2 EDIT Process 2-5
2.1.3 CORRECT Process 2-7
2.2 AIRS Transactions 2-8
2.3 General Coding Instructions 2-9
3.0 Common Fields 3-1
3.1 Overview 3-1
3.2 TRANS TYPE and TRANS ID 3-2
3.3 ACT 3-4
3.4 STATE 3-7
3.5 COUNTY 3-8
3.6 SITE 3-9
4.0 Site Transactions (Al through AT) 4-1
4.1 Transaction Type Al - Site Information - Part 1 4-6
4.1.1 SUPPORT AGENCY 4-7
4.1.2 STREET ADDRESS 4-8
4.1.3 DATE SITE ESTABLISHED 4-9
4.1.4 DATE SITE TERMINATED 4-10
4.1.5 HQ EVAL DATE 4-11
4.1.6 REGIONAL EVAL DATE 4-12
4.2 Transaction Type A2 - Site Information - Part 2 4-13
4.2.1 CITY 4-14
4.2.2 AQCR 4-15
4.2.3 MSA 4-16
4.2.4 AIR BASIN 4-17
4.2.5 ELEVATION MSL 4-18
4.2.6 COMPASS SECTOR 4-19
4.2.7 DISTANCE CITY 4-20
4.2.8 LOC SET 4-21
4.2.9 LAND USE 4-22
4.2.10 DIP GMT 4-23
4.2.11 TYPE MET SITE 4-24
4.2.12 MET SITE ID 4-25
4.2.13 DISTANCE SITE 4-26
4.2.14 DIRECTION SITE 4-27
4.2.15 STATE OR LOCAL ID 4-28
Table of Contents ii December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.3 Transaction Type A3 - Site Information - Part 3
4.3.1 SEQUENCE NUMBER
4.3.2 STREET NUMBER
4.3.3 STREET Data
4.3.3.1 STREET NAME
4.3.3.2 TYPE ROAD
4.3.3.3 TRAFFIC FLOW
4.3.3.4 YEAR OF TRAFFIC FLOW
4.3.3.5 DIRECTION TO STREET . ,
4.3.4 SITE LOCATION TYPE
4.3.5 MSA REPRESENTED
4.3.6 CMSA REPRESENTED
4.3.7 OPEN PATH NUMBER
4.3.8 OPEN PATH Data
4.3.8.1 DIR TO TRANSMITTER ..
4.3.8.2 BEAM LENGTH
4.3.8.3 TRANSMITTER HEIGHT .
4.3.8.4 RECEIVER HEIGHT
4.3.8.5 MIN BEAM HEIGHT
4.3.8.6 MAX BEAM HEIGHT
4.3.8.7 LAND USE UNDER PATH .
4.4 Transaction Type A4 - Site Information - Part 4 .
4.4.1 UTMZONE
4.4.2 UTM EASTING
4.4.3 UTM NORTHING
4.4.4 LATITUDE
4.4.5 LONGITUDE
4.4.6 METHOD OF DETERMINATION . . .
4.4.7 DATUM
4.4.8 SCALE
4.4.9 ESTIMATE OF ACCURACY
4.5 Transaction A5 - Location Description
4.6 Transaction Type A6 - Site Comments (Line 1) .
4.7 Transaction Type A7 - Site Comments (Line 2) .
4-29
4-31
4-32
4-33
4-34
4-35
4-36
4-37
4-38
4-39
4-40
4-41
4-42
4-43
4-45
4-46
4-47
4-48
4-49
4-50
4-51
4-52
4-54
4-56
4-58
4-60
4-62
4-63
4-64
4-65
4-66
4-67
4-68
December 1993
in
Table of Contents
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.0 Monitor Transactions (Fl through F5) 5-1
5.1 Common Fields 5-6
5.1.1 PARAMETER 5-6
5.1.2 POC 5-7
5.1.3 MONITOR-ID 5-8
5.2 Transaction Type FI - Monitor Data - Part 1 5-9
5.2.1 MONITOR TYPE 5-10
5.2.2 DATE TYPE EFF 5-13
5.2.3 ANALYZ LAB 5-15
5.2.4 COLLECT LAB 5-16
5.2.5 REPORT ORG 5-17
5.2.6 RO EFFECTIVE DATE 5-18
5.2.7 DATE SAMPLING BEGAN 5-20
5.2.8 DATE SAMPLING ENDED 5-21
5.2.9 AUDIT DATE 5-23
5.2.10 PROJECT CLASS 5-24
5.2.11 ACTION TYPE 5-25
5.2.12 ACTION TYPE REASON 5-26
5.2.13 DOMINANT SOURCE 5-27
5.2.14 MEASUREMENT SCALE 5-28
5.2.15 MONITOR TYPE OBJECTIVE 5-29
5.2.16 NONATTAINMENT AREA 5-30
5.2.17 URBAN AREA REPRESENTED 5-32
5.2.18 PAMS REQ SAMPLING FREQ 5-33
5.2.19 MONITOR OPEN PATH NUMBER 5-34
5.3 Transaction Type F2 - Monitor Data - Part 2 5-35
5.3.1 STREET INFORMATION 5-36
5.3.1.1 MONITOR STREET NUMBER 5-37
5.3.1.2 DISTANCE FROM ROAD 5-38
5.3.2 REF METHOD USED 5-39
5.3.3 REF METHOD USED DATE 5-W
5.3.4 SITE CRITERIA MET
5.3.5 DATE SITE CRITERIA MET
5.3.6 QA PLAN
5.3.7 QA EFFECTIVE DATE 5-44
5.3.8 PROBE LOCATION CODE 5-46
5.3.9 PROBE HEIGHT 5-47
5.3.10 HORIZONTAL DISTANCE 5-48
5.3.11 VERTICAL DISTANCE 5-49
5.3.12 UNRESTRICTED AIR FLOW 5-50
5.3.13 OBSTRUCTION DESCRIPTION 5-51
5.3.13.1 TYPE OBSTRUCTION 5-52
5.3.13.2 DIRECTION FROM MONITOR 5-53
5.3.13.3 DISTANCE FROM INLET 5-55
5.3.13.4 HEIGHT OF OBSTRUCTION 5-57
Table of Contents iv December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.4 Transaction Type F3 - Monitor Data - Part 3 5-59
5.4.1 MONITORING AREA 5-60
5.4.2 WORST SITE 5-61
5.4.3 SURROGATE FLAG 5-62
5.4.4 NUM SCH SAMPLE MO 5-63
5.4.5 REQ SAMPLING FREQ 5-65
5.4.6 RSF EFFECTIVE DATE 5-66
5.4.7 SHORT TERM SCH SAT 5-67
5.4.8 SHORT TERM COMP DATE 5-68
5.4.9 FIRST EXCEED CORRECTION 5-69
5.5 Transaction Type F4 - MONITOR COMMENTS (Line 1) 5-70
5.6 Transaction Type F5 - MONITOR COMMENTS (Line 2) 5-71
6.0 SLAMS Transactions (M, N, P, R, S, T, U, and V) 6-1
6.1 Common Fields 6-7
6.1.1 PARAMETER 6-7
6.1.2 POC 6-8
6.1.3 Monitor Identification Code 6-9
6.2 Transaction Type M - SLAMS Paniculate Information 6-10
6.2.1 INT 6-12
6.2.2 UNITS 6-13
6.2.3 YEAR 6-14
6.2.4 DP 6-15
6.2.5 WEIGHTED ARTTH MEAN 6-16
6.2.6 SUM CRIT 6-17
6.2.7 SAMPLING DATA 6-18
6.2.7.1 SF 6-19
6.2.7.2 OBS-24HR 6-20
6.2.7.3 ADD SAMP DAYS 6-21
6.2.7.4 DATE SF BEGAN 6-22
6.3 Transaction Type N - SLAMS Paniculate Exceedances 6-23
6.3.1 INT 6-25
6.3.2 UNITS 6-26
6.3.3 YEAR 6-27
6.3.4 EX OCC 6-28
6.3.5 DP 6-29
6.3.6 EXCEEDANCE DATA 6-30
6.3.6.1 EXCEEDANCE VALUE 6-31
6.3.6.2 EXCEEDANCE DATE 6-32
6.4 Transaction Type P - SLAMS S02 Data 6-33
6.4.1 INT 6-35
6.4.2 UNITS 6-36
6.4.3 YEAR 6-37
6.4.4 OBS-1 HR 6-38
6.4.5 OBS-24 HR 6-39
6.4.6 DP 6-40
6.4.7 24-HOUR FIRST MAX 6-41
December 1993
Table of Contents
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.4.8 24-HOUR FIRST MAX DATE 6-42
6.4.9 24-HOUR SEC MAX 6-43
6.4.10 24-HOUR SEC MAX DATE 6-44
6.4.11 3-HOUR FIRST MAX 6-45
6.4.12 3-HOUR FIRST MAX TIME 6-46
6.4.13 3-HOUR SEC MAX 6-47
6.4.14 3-HOUR SEC MAX TIME 6-48
6.4.15 3-HOUR EXCEEDANCE 6-49
6.4.16 24-HOUR EXCEEDANCE 6-50
6.4.17 ARITHMETIC MEAN 6-51
6.4.18 SUM CRTT 6-52
6.5 Transaction Type R - SLAMS CO Data 6-53
6.5.1 INT 6-55
6.5.2 UNITS 6-56
6.5.3 YEAR 6-57
6.5.4 OBS-1 HR 6-58
6.5.5 DP 6-59
6.5.6 1-HOUR FIRST MAX 6-60
6.5.7 1-HOUR FIRST MAX TIME 6-61
6.5.8 1-HOUR SEC MAX 6-62
6.5.9 1-HOUR SEC MAX TIME 6-63
6.5.10 8-HOUR FIRST MAX 6-64
6.5.11 8-HOUR FIRST MAX TIME 6-65
6.5.12 8-HOUR SEC MAX 6-66
6.5.13 8-HOUR SEC MAX TIME 6-67
6.5.14 1-HOUR EXCEEDANCE 6-68
6.5.15 8-HOUR EXCEEDANCE 6-69
6.6 Transaction Type S - SLAMS N02 Data 6-70
6.6.1 INT 6-72
6.6.2 UNITS 6-73
6.6.3 YEAR 6-74
6.6.4 OBS-1 HR 6-75
6.6.5 OBS-24 HR 6-76
6.6.6 DP 6-77
6.6.7 1-HOUR FIRST MAX 6-78
6.6.8 1-HOUR FIRST MAX TIME 6-79
6.6.9 1-HOUR SEC MAX 6-80
6.6.10 1-HOUR SEC MAX TIME 6-81
6.6.11 24-HOUR FIRST MAX 6-82
6.6.12 24-HOUR FIRST MAX DATE 6-83
6.6.13 24-HOUR SEC MAX 6-84
6.6.14 24-HOUR SEC MAX DATE 6-85
6.6.15 ARITHMETIC MEAN 6-86
6.6.16 SUM CRIT 6-87
Table of Contents vi December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
6.7 Transaction Type T - SLAMS O3 Data 6-88
6.7.1 INT 6-90
6.7.2 UNITS 6-91
6.7.3 YEAR 6-92
6.7.4 OBS-1 HR 6-93
6,7.5 DP 6-94
6.7.6 Ozone Maximum Values 6-95
6.7.7 1-HOUR FIRST MAX 6-96
6.7.8 1-HOUR FIRST MAX TIME 6-97
6.7.9 1-HOUR SEC MAX 6-98
6.7.10 1-HOUR SEC MAX TIME 6-99
6.7.11 1-HOUR THIRD MAX 6-100
6.7.12 1-HOUR THIRD MAX TIME 6-101
6.7.13 1-HOUR FOURTH MAX 6-102
6.7.14 1-HOUR FOURTH MAX TIME 6-103
6.7.15 1-HR EXCEEDANCE 6-104
6.8 Transaction Type U - SLAMS Pb Data 6-105
6.8.1 INT 6-107
6.8.2 UNITS 6-108
6.8.3 YEAR 6-109
6.8.4 METHOD 6-110
6.8.5 DP 6-112
6.8.6 Lead Quarterly Statistics 6-113
6.8.6.1 NO. OF SAMPLES 6-114
6.8.6.2 ARTTH MEAN 6-115
6.8.6.3 SUM CRTT 6-116
6.9 Transaction Type V - SLAMS Method and Frequency Data 6-117
6.9.1 INT 6-119
6.9.2 YEAR 6-120
6.9.3 METHOD 6-121
6.9.4 FREQUENCY 6-122
6.9.5 EXC FLAG 6-125
7.0 Raw Data Transactions (1, 2, and 3) 7-1
7.1 Common Fields 7-7
7.1.1 PARAMETER 7-7
7.1.2 PARAMETER OCCURRENCE CODE 7-8
7.1.3 Monitor Identification Code 7-9
7.1.4 INT 7-10
7.1.5 UNITS 7-11
7.1.6 METHOD 7-12
7.1.7 YEAR 7-13
December 1993 vii Table of Contents
-------
4ft
AIRS User's Guide
Air Quality Data Coding Volume AQ2
7.2 Transaction Type 1 - Hourly Data 7-14
7.2.1 MONTH 7-17
7.2.2 DAY 7-18
7.2.3 ST HR 7-19
7.2.4 DP 7-21
7.2.5 SAMPLE VALUE 7-22
7.2.6 VF 7-25
7.2.7 Statistical Tests 7-27
7.2.7.1 Pattern Tests 7-27
7.2.7.2 Gap Test 7-30
7.2.7.3 Pattern and Gap Failure Report 7-31
7.3 Transaction Type 2 - Daily Data 7-33
7.3.1 MONTH 7-35
7.3.2 DAY 7-36
73.3 START HOUR 7-37
7.3.4 SF 7-38
7.3.5 DP (Decimal Position) 7-39
7.3.6 SAMPLE VALUE 7-40
7.3.7 VF 7-42
7.3.8 Statistical Tests 7^*3
7.4 Transaction Type 3 - Composite Data 7-45
7.4.1 PERIOD CODE 7^17
7.4.2 NO. OF SAMPLES 7-48
7.4.3 COMP TYPE 7-49
7.4.4 DP 7-50
7.4.5 SAMPLE VALUE 7-51
7,4.6 VF 7-52
8.0 Special Transactions (Z and 4) 8-1
8.1 Common Fields 8-3
8.1.1 PARAMETER 8-4
8.1.2 PARAMETER OCCURRENCE CODE 8-5
8.1.3 Monitor Identification Code 8-6
8.1.4 INT 8-7
8.1.5 UNITS 8-8
8.1.6 METHOD 8-9
8.2 Transaction Type Z - Minimum Detectable Value 8-10
8.2.1 BEGIN YEAR/BEGIN MON 8-13
8.2.2 END YEAR/END MON 8-14
8.2.3 DP 8-15
8.2.4 MIN DET VALUE 8-16
8.3 Transaction Type 4 - Missing Data Reason (Null Data) 8-17
8.3.1 BEGIN DATE 8-19
8.3.2 END DATE 8-21
8.3.3 REASON CODE 8-23
Table of Contents viii December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
9.0 Precision/Accuracy Transactions (8 and 9) 9-3
9.1 Common Fields 9-7
9.1.1 PARAMETER 9-7
9.1.2 PARAMETER OCCURRENCE CODE 9-8
9.1.3 Monitor Identification Code (Monitor-ID) 9-9
9.1.4 INT 9-10
9.1.5 UNITS 9-11
9.1.6 METHOD 9-12
9.1.7 YEAR 9-13
9.1.8 MONTH 9-14
9.1.9 DAY 9-15
9.2 Transaction Type 8 - Precision Data 9-16
9.2.1 DP 9-18
9.2.2 ACTUAL DESIGNATED 9-19
9.2.3 INDICATED COLLOCATED MON1 9-22
9.2.4 INDICATED COLLOCATED MON2 9-25
9.2.5 INDICATED COLLOCATED MON3 9-27
9.2.6 INDICATED COLLOCATED MON4 9-29
9.2.7 INDICATED COLLOCATED MON5 9-31
9.3 Transaction Type 9 - Accuracy Data 9-33
9.3.1 TYPE AUDIT 9-35
9.3.2 LOCAL PRIMARY STANDARD 9-36
9.3.3 AUDIT CLASSIFICATION 9-37
9.3.4 DP 9-39
9.3.5 ACTUAL LEVEL-1 9-40
9.3.6 INDICATED LEVEL-1 9-42
9.3.7 ACTUAL LEVEL-2 9-44
9.3.8 INDICATED LEVEL-2 9-46
9.3.9 ACTUAL LEVEL-3 9^8
9.3.10 INDICATED LEVEL-3 9-50
9.3.11 ACTUAL LEVEL-4 9-52
9.3.12 INDICATED LEVEL-4 9-54
9.3.13 ACTUAL LEVEL-5 9-56
9.3.14 INDICATED LEVEL-5 9-58
9.3.15 ZERO SPAN 9-60
Appendix A. Alphabetical List of Error Messages A-l
December 1993
IX
Table of Contents
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
List of Figures
Figure 2-1. Sample LOAD Summary Report 2-3
Figure 2-2. Sample EDIT Error Report 2-4
Figure 2-3. Sample CORRECT Screen 2-6
Figure 4-1. Coding Form for Transaction Types Al - A7 4-4
Figure 5-1. Coding Form for Transaction Types Fl - F5 5-5
Figure 6-1. Coding Form for Transaction Type M - SLAMS TSP/PM-10 Data 6-11
Figure 6-2. Coding Form for Transaction Type N - SLAMS TSP/PM-10 Exceedances 6-24
Figure 6-3. Coding Form for Transaction Type P - SLAMS S02 Data 6-34
Figure 6-4. Coding Form for Transaction Type R - SLAMS CO Data 6-54
Figure 6-5. Coding Form for Transaction Type S - SLAMS NO2 Data 6-71
Figure 6-6. Coding Form for Transaction Type T - SLAMS 03 Data 6-89
Figure 6-7. Coding Form for Transaction Type U - Pb Data 6-106
Figure 6-8. Coding Form for Transaction Type V - SLAMS Method and Frequencies .... 6-118
Figure 7-1. Coding Form for Transaction Type 1 7-16
Figure 7-2. Sample Patterns and Gap Failure Report 7-32
Figure 7-3. Coding Form for Transaction Type 2 7-34
Figure 7-4. Shewhart Failure Report 7-44
Figure 7-5. Coding Form for Transaction Type 3 7-46
Figure 8-1. Coding Form for Transaction Type Z 8-12
Figure 8-2. Coding Form for Transaction Type 4 8-18
Figure 9-1. Coding Form for Transaction Types 8 and 9 9-6
List of Tables
Table 7-1. Conversion Factors for the Pattern and Gap Tests 7-28
Table 7-2. Threshold Values for the Pattern Tests 7-29
Table of Contents
December 1993
-------
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
1.0 Introduction
This manual explains how to use the Air Quality Data Storage Subsystem of AIRS, the Aerometric
Information Retrieval System. AIRS is a computer-based system for handling the storage and retrieval
of information pertaining to airborne pollutants. It is administered by the U.S. Environmental Protection
Agency, Office of Air Quality Planning and Standards, Monitoring and Data Analysis Division, National
Air Data Branch (NADB), located in Durham, North Carolina. AIRS is installed on the IBM computer
system at EPA's National Computer Center in Research Triangle Park, North Carolina. AIRS employs
the ADABAS database management system to manage its data files and the CICS teleprocessing monitor
to provide the interface between user and programs.
Volume AA1 of this User's Guide provides a high-level introduction to AIRS and a list of people to
contact for information or assistance. Volume AQ1 contains the AQ data dictionary and file descriptions.
This Volume AQ2 describes coding of air quality (AQ) data transactions. Volumes AQ3 and AQ4
describe how to use the AQ Subsystem Data Storage and Data Retrieval Functions. Volume AQS
describes Ad hoc Data Retrieval.
Volume GC1 contains the Geo-Common Subsystem data dictionary. Volume GC2 contains listings and
description of the codes used in AIRS. Volumes GC3 and GC4 describe the storage and retrieval of Geo-
Common data.
Volumes AF1 through AFS pertain to the Facility Subsystem and Volumes AMI through AM4 pertain
to the Mobile Source Subsystem.
This volume of the AIRS User's Guide describes the various transactions used to create, modify, or delete
data in the AIRS Air Quality Subsystem. It is intended for those individuals who are responsible for
maintaining the air quality data for their respective organizations.
The remainder of this volume is organized as follows:
Section 2 - Overview of Data Coding and Validation
Section 3 — Common Fields
Section 4 - Site Transactions (Al, A2, A3, A4, A5, A6, A7)
Section 5 - Monitor Transactions (Fl, F2, F3, F4, F5)
Section 6 - SLAMS Transactions (M,N,P,R,S,T,U,V)
Section 7 - Raw Data Transactions (1,2,3)
Section 8 - Special Transactions (Z,4)
Section 9 — Precision/Accuracy Transactions (8,9)
December 1993
1-1
Introduction
-------
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
2.0 Overview of Data Coding and Validation
The AIRS Air Quality Subsystem contains data submitted to NADB by the state and local agencies and
EPA organizations. This data corresponds to that previously handled by the SAROAD system. It
includes descriptions of air monitoring sites and monitoring equipment, measured concentrations of air
pollutants and related parameters, and calculated summary and statistical information. This is called air
quality (or "AQ") data throughout the rest of this volume.
Reporting agencies submit AQ data as formatted transactions on magnetic tape or other storage media.
The data storage processes of the AIRS AQ Subsystem load the data into screening files; validate the data
on those files; allow the user to correct any erroneous data and exclude from the update any incomplete
or unreasonable data; allow the AIRS Database Administrator (ADBA) to examine the data, exclude data,
and update the Air Quality files with the corrected input data; to archive to tape old air quality data; and
to reload archived air quality data.
The AQ data storage processes operate on the input data transactions while they reside in a 'screening
file'. Each data storage user group of AIRS has a screening file for that organization's transactions. The
records of an input transaction file are first loaded into a screening file. The transaction records Stay in
this file while the authorized users examine and modify them through the AQ data storage processes.
The transactions are edited and corrected by the user and examined by the ADBA, who may exclude data
from updating the database (this is particularly true for SLAMS summary data and certain types of NAMS
data).
The contents of a screening file are edited using information stored in the AIRS database, including the
Air Quality summary, raw data, and site files and the GEO-COMMON File. Several of the processes
write a message or control information into the Table File. These messages alert the user to the status
of submitted jobs. Printed reports provide details about EDIT errors that may later be fixed by using
CORRECT. The modified contents of a screening file are used to update the Air Quality files.
The AQ data storage processes may be grouped according to the functions they perform, as described in
the following paragraphs:
December 1993
2-1
Overview
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
The Submit Function provides the means by which local, state, and EPA users of AIRS supply and
validate transactions for loading data into AIRS or for altering data previously loaded. Four processes
comprise the Submit Function:
LOAD puts transaction records into the user's screening file
EDIT performs validation checks of the transaction records
CORRECT allows correction of records that fail validation checks
If
NOTIFY informs the ADBA that a screening file is ready to be used in an update.
Each of the four processes is invoked from the AIRS Top Level User Session by appropriate menu
selections.
The Update Function is the means through which the AIRS Database Administrator updates the database
with validated transaction records in the AIRS user's screening files. The three main processes of the
Update Function are:
SCAN examines a screening file and provides statistics about the numbers and
types of transactions
EXCLUDE allows the ADBA to selectively exclude and de-exclude screening file
records from the UPDATE process
UPDATE applies Air Quality transactions to the AIRS database.
The update processes are available only to the ADBA, and are invoked from the AIRS Top Level User
Session by appropriate menu selections.
AIRS also has three utility processes that allow AIRS users and the ADBA to examine messages
concerning other data storage processes, and let the ADBA archive and de-archive AQ data. The three
Utility processes are:
MESSAGE displays any messages for the user or ADBA that are in message records
in the Table File
ARCHIVE allows the ADBA to remove data from the Air Quality files for storage
on tape
DEARCHIVE allows the ADBA to load archived data from tape into the Air Quality
files.
Each of the three processes is invoked from the AIRS Top Level User Session by appropriate menu
selections.
Overview 2-2 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
2.1 Submit Function Processes
The main features of the LOAD, EDIT, and CORRECT processes are described below. Refer to Volume
AQ3 of the User's Guide for more detailed descriptions of what they do and how to use them.
2.1.1 LOAD Process
LOAD is a batch process which may be initiated from the Air Quality "submit menu" by an AIRS user.
Air Quality transaction records are read from the dataset specified by the user and written into that user's
screening file. A printed report is generated that summarizes the processing performed in terms of the
number of transaction records by type or category. Figure 2-1 shows an example of the LOAD report.
A message is sent to the user of the screening file via the Table File, indicating that the LOAD has been
done.
Since the purpose of the LOAD process is simply to transfer transaction records from a user's input
dataset to a screening file, the only checking of record content is to identify record types for summary
statistics. AH records of the input dataset are written into the screening file, and no screening file records
are over-written by input records. Several additional fields are appended to each input record when it
is written to the screening file. These fields are used by other data storage processes to identify the
record and to keep track of its status. Refer to Volume GC2 of the User's Guide for details of the
screening record format.
09/30/93
AMP010
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
LOAD SUMMARY REPORT
FOB SCREENING FILE ODEVSF10
INPUT TRANSACTION FILE: SYS87105.T104133.IIAOOO.TADLOADO.R0000007
TRANSACTION TYPE
SITE
MONITOR
SLAMS
HOURLY
DAILY
COMPOSITE
PRECISION
ACCURACY
INVALID
A1-A7
F1-F5
M.N.P,
1
2
3
B
9
R-V
TOTAL
NUMBER
3
14
204
111
104
116
12
1
571
PAGE:
1ST VOLUME: 814467
Figure 2-1. Sample LOAD Summary Report
December 1993
2-3
Overview
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
09/10/93
ANP050
AEROHETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
EDIT ERROR REPORT
FOR SCREENING FILE ANADBA10
PAGE:
RECORD KEY
RECORD t + 1 » 2 > 3-
TRANSACTION
3—* 4-
00003850 03-063-0001-1ZK6-1-86-3-01- -
00003851 03-063-0001-12126-1-86-3-02- -
.+ ....«.—l-—»—-2—-
-I 3030630001121Z61C002091860107410023
ERROR - INVALID STATE COOE
WARNING - CANNOT VERIFY COUNTY COOE
-I 3030630001121ZS1C002091860207410024
E*W"
ERROR - INVALID STATE CODE
WARNING • CANNOT VERIFY COUNTY CODE
00003852 03-063-0001-12126-1-86-3-03- - -I 3030630001121261C002091860306410025
00003853 03-063-0001-12126-1-86-3-04- -
ERROR - INVALID STATE CODE
WARNING - CANNOT VERIFY COUNTY COOE
-I 3030630001121261C001091860406410026
E*W"
ERROR - INVALID STATE CODE
WARNING - CANNOT VERIFY COUNTY CODE
00003854 03-063-0001-12126-1-86-3-06- - -I 3030630001I21261C002091860606420029
00003855 03-063-0001-12126-1-86-3-06- -
ERROR - INVALID STATE CODE
WARNING - CANNOT VERIFY COUNTY COOE
-I 3030630001121261C002091860607420030
E.y.«
ERROR - INVALID STATE CODE
WARNING - CANNOT VERIFY COUNTY COOE
000038S6 03-063-0001-12126-1-86-3-07- - -1 3030630001121261C002091860702420031
ERROR - INVALID STATE COOE
WARNING - CANNOT VERIFY COUNTY CODE
ERROR
•8 LEVEL
I 1
I 1
I 1
I 1
I 1
I 1
I 1
00003854 03-063-0001-12126-1-86-3-06-
00003855 03-063-0001-12126-1-86-3-06-
-I 303063000U212G1C002091860606420029
-1 3030630001121261C002091860607420030
2 RECORDS ERROR - DUPLICATE RECORDS
I 2
: 2
00003857 03-063.0001-12126-1-86-3-08-
-I 3030630001121261C002091860806420032
£*W"
ERROR - INVALID STATE COOE
WARNING - CANNOT VERIFY COUNTY CODE
I 1
Figure 2-2. Sample EDIT Error Report
Overview
2-4
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
2.1.2 EDIT Process
EDIT is a batch process that may be initiated from the Air Quality submit menu by an AIRS user. Air
Quality transaction records in die user's screening file are examined and edit/validation checks are
applied. The purpose of EDIT is to ensure that only 'good' data gets into the database. A printed report
is generated that lists each record mat failed the checks and the reason(s) why it failed.
Three levels of edit/validation checks may be applied to transaction records in a screening file. Level-1
editing determines whether the individual fields of a record have appropriate values. An invalid state
code, for example, would be a level-1 edit error. Level-2 editing checks the relationships among fields
or records. Duplicate transaction records is an example of a level-2 edit error. Level-3 editing includes
statistical tests for anomalies in the transaction data and checks of the relationships among the transaction
records and the AIRS Database. For example, a level-3 edit error would occur if a transaction record
specified deletion of data that did not exist in the database. All fields of a transaction record must pass
level-1 editing before the record can participate in level-2 editing, and interdependent records must pass
level-2 edit checks before they are eligible for level-3 editing. The report produced by EDIT identifies
the level of edit errors. An AIRS user may specify the highest level of editing to be applied to the
records in a screening file each time the EDIT process is invoked.
Figure 2-2 is a sample EDIT error report. Each field of the input transaction that contains an error is
marked with an E (error) or W (warning) indication, with asterisks used to fill out the length of the field
in error. For example, a five-position field in error would be marked "£****". An error indication
results when EDIT finds something wrong. A warning occurs when EDIT cannot do the necessary
validation because of another error. The validity of the field in question cannot be determined until the
other error is corrected.
Error messages listed in the EDIT error report are explained in subsequent chapters of this volume.
Errors pertinent to specific fields are listed with the description and coding instructions for the fields.
Errors that do not apply to specific fields or that apply to groups of fields are listed in the introductory
part of the chapter dealing with the relevant transaction type.
December 1993
2-5
Overview
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
11-03-88
A]ItS Air Quality Sul-iystem - CORRECT
OCSCSF01
Normal Node
HOURLY Data Trans. Type: 1
10*: 12345678 Key: 37-067-0092-81102-1-87-1-01-02-00-1 Edit Level: 3
Excluded? (Y/N): M
Stete-County-Site: 37 067 0092
Parameter-FCC: 81102 1
Action Code: I
Interval Code: 2
Sampling TY-MH-DO: 87 01 02
Unlta Code: 008
Start Hour: 00
Method Code: 014
Decimal Position: 4
Value Sample
Number Value
It
3:
5:
7:
Validity
Flag
Value Sample
tluifcer Value
2:
4:
6:
8:
1310
ilTT
Validity
Flag
Figure 2-3. Sample CORRECT Screen
Overview
2-6
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
2.1.3 CORRECT Process
CORRECT is an on-line process that may be invoked from the Air Quality submit menu by an AIRS
user. Air Quality transaction records in the user's screening file may be modified in order to correct
edit/validation errors identified by the EDIT process or to correct some other problem known to the user.
CORRECT does not generate a printed report or a message in the Table File.
The CORRECT process allows one to "browse" in one's own screening file viewing its contents, and to
modify, delete, or add transaction records. A particular record or group of records may be selected for
display on the user's terminal screen. As each record is displayed, the user may do nothing to it, alter
the contents of its data fields, or delete the record. The user may also set (or clear) an indicator that
causes the record to be excluded temporarily from EDIT and UPDATE processing, while retaining it in
die file. The same kinds of operations may also be applied to groups of records using "global"
commands that specify the identities (keys) of the records to be affected and the actions to be applied.
New transaction records may also be inserted into the screening file. Level-1 edit checks are applied to
inserted and modified records, and any errors are indicated on the user's screen. Edit checks are not
applied to each record modified by a global command, but to the command itself. Any records that have
passed leveI-2 or level-3 edit checks and are interdependent with a record affected by CORRECT
processing will be reset to level-1.
Figure 2-3 is a sample CORRECT screen. In addition to the display of the input transaction, error
messages are listed on the screen. The fields in error should be changed to contain valid data. For an
explanation of a given error message, refer to the section of this volume that describes the field in error.
December 1993
2-7
Overview
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
2.2 AIRS Transactions
Twenty-seven types of card-image transactions are used to provide data and control information for
updating the AIRS database. Detailed instructions for coding individual transactions and interpreting
EDIT error messages are presented in Chapters 3 through 9. The following table shows how the various
transaction types are related.
Transaction Type
Related Transaction Records Have The Same.
Site (A1,A2,A3,A4,A5,A# Site-ID (state, county, site codes)
A7)
Monitor (F1,F2,F3,F4,F5) Monitor-ID (site-ID, parameter, and POC codes)
SLAMS (M,N,P,R,S,T,U,V) Monitor-ID, year, transaction type (any of codes M through V)
Raw Data:
Hourly (1)
Daily (2)
Composite (3)
Monitor-ID, year, month, transaction type 1
AND type 4 transactions with the same monitor-ID
Monitor-ID, year, month, transaction type 2
AND type 4 transactions with the same monitor-ID
Monitor-ID, year, period, transaction type 3
Special:
Minimum Detectable
Value (Z)
Null Value (4)
Precision/Accuracy (8,9)
Monitor-ID, transaction type Z
Monitor-ID, transaction type 4
Monitor-ID, year, month, transaction type
Overview
2-8
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
2.3 General Coding Instructions
Four general types of values are used to code air quality transactions: codes, dates, numeric data, and
alphanumeric data.
Codes must be entered on transactions exactly as they are stored in the GEO-COMMON File or as they
are listed in the instructions in this volume. (See Volume GC2 of the User's Guide for a listing of codes
in the GEO-COMMON File.) For example, a county code is three digits, and you must code all three
digits of the code, including any leading zeros. The instructions for fields that take a code value include
the term "code" in the list of field attributes.
Dates are entered in YYMMDD or YYMM format. YY is year Oast two digits), MM is month number,
and DD is day of month. Each part must be two digits. The instructions for fields that take a date value
include the term "date" in the list of field attributes.
Numeric values must be entered right-justified in the field. You do not have to include leading zeros.
For example, to express a PROBE HEIGHT of ten meters, you could enter either "010" (leading zero)
or " 10" (leading blank), but you could not enter "10 " (trailing blank). The instructions for fields that
take a numeric value include the term "numeric" in the list of field attributes.
Alphanumeric values should be entered left-justified in the field. There are no other requirements for
this type of data. The instructions for these fields include the term "character" in the list of field
attributes.
The asterisk (*) is used to signify deletion of a field. You must code an asterisk in every position of the
field to be deleted. Deletion of a field is usually done with a MODIFY transaction (that is, action code
is "M"). Deletion is never allowed with an INSERT transaction (action code "I").
Certain fields are known as required fields, and they must have a value on the transaction. Some fields
are always required, while other fields are required only under certain conditions. For example, action
code is always required; it must be coded on every transaction. Monitor type, on the other hand, is
required on an INSERT transaction but it is optional on a MODIFY transaction. The coding instructions
in subsequent chapters identify fields as optional or required and specify the conditions when a value is
required on the transaction.
December 1993
2-9
Overview
-------
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
3.0 Common Fields
3.1 Overview
The 27 AIRS transaction formats contain certain fields in common. These common fields are described
in this chapter; the unique fields for each transaction are described in the following chapters.
December 1993
3-1
Common Fields
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
3.2 TRANS TYPE (Transaction Type) and TRANS ID (Transaction-ID)
Site and Monitor transactions have a TRANS ID as well as a TRANS TYPE. The other transactions have
only a TRANS TYPE.
This identifies the format of the transaction.
Attributes: TRANS TYPE - 1 character code
Required
TRANS ID - 1 character code
Required
Coding Instructions:
For Site and Monitor transactions:
Place a valid Transaction Type in column 1 and a valid Transaction-ID in column 79.
Valid TRANS TYPES are: A for Site transactions
F for Monitor transactions
Valid TRANS IDs are: 1-7 for Site transactions
1-5 for Monitor transactions
For all other transactions:
Place a valid Transaction Type in column 1.
Valid TRANS TYPEs are:
M,N,P,R,S,T,U,V - SLAMS transactions
1,2,3 ~ Raw data transactions (Hourly, Daily, Composite)
Z,4 — Special transactions (Minimum Detectable Value, Null Data)
8,9 - Precision/Accuracy transactions
Common Fields 3-2 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
Error Messages:
ERROR - INVALID TRANSACTION-ID
TRANS ID must be 1-7 for Site transaction, 1-5 for Monitor transaction
ERROR - INVALID TRANSACTION-TYPE
TRANS TYPE must be A, F, M, N, P, R-V, Z, M, 8 or 9.
December 1993
3-3
Common Fields
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
3.3 ACT (Action Code)
This code indicates the type of database processing to be performed by this transaction.
Attributes: 1 character code
Required
Coding Instructions:
Place an I, M, or D in cokimn 80.
The type of database processing performed depends on action code and transaction type. The following
table lists all the valid combinations of action code and transaction type. If a combination does not appear
in the table, it is invalid. For example, action code D is not allowed for transaction types A2 through
A7.
Transaction Type
Al -A7
Al
Fl -F5
Fl
M,N,P,R,S,T,U,V
M,N,P,R,S,T,U
1,2,3
Action Qpde
I
M
D
I
M
D
I
M
D
I
Database Processing
Insert a new site into the Site file.
Change or delete one or more fields within a site record.
Delete a site from the Site file (you must also delete all
of its monitors).
Insert a new monitor into the Site file.
Change or delete one or more fields within a monitor
record in the Site file.
Delete a monitor from the Site file (you must delete all
its SLAMS and raw data first).
Insert a new record into the SLAMS file.
Replace the contents of a record in the SLAMS file (all
fields).
Delete a record from the SLAMS file.
Insert new values into the raw data files.
Common Fields
3-4
December 1993
-------
AIRS User's Guide
Volume AQ2
Transaction Type Action Code
M
D
Z I
M
D
4 I
M
D
8 I
M
D
9 I
M
D
Air Quality Data Coding
Database Processing
Change or delete existing values in the raw data files.
Delete existing values from the raw data files.
Insert a new minimum detectable value in the raw data
files for a specified time interval.
Change an existing minimum detectable value in the raw
data files for a specified time interval.
Delete an existing minimum detectable value in the raw
data files for a specified time interval.
Insert a missing value reason code in the raw data files
for a specified time interval.
Change existing missing value reason codes in the raw
data files for a specified time interval.
Delete existing missing value reason codes from the raw
data files for a specified time interval.
Insert a new precision value in the Raw Data files for a
specified time interval.
Change or Delete an existing precision value in the Raw
Data data flies.
Delete existing precision values for a specified time
interval from the Raw Data data files.
Insert a new accuracy value in the Raw Data files for a
specified time interval.
Change or Delete an existing accuracy value in the Raw
Data data files.
Delete existing accuracy values for a specified time
interval from the Raw Data data files.
December 1993
3-5
Common Fields
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
Error Messages:
ERROR - INVALID ACTION CODE
ACT must be I, M, or D and valid for the transaction type. Refer to the listing above.
Common Fields 3-6 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
3.4 STATE
STATE is a FIPS code that identifies one of the 50 states, U.S. territories, or Washington, D.C.
Attributes:
Coding Instructions:
2 digit code
Required
Place a valid FIPS state code in columns 2-3. A code is valid if it exists in the AIRS GEO-COMMON
File. Valid codes are listed in Volume GC2 of the of the AIRS User's Guide.
Error Message:
ERROR - INVALID STATE CODE
STATE must be in the GEO-COMMON File.
December 1993
3-7
Common Fields
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
3.5 COUNTY
COUNTY is a FIPS code that identifies a county or the equivalent geo-political entity, such as a parish
or independent city.
Attributes: 3 digit code
Required
Coding Instructions:
Place a valid county code in columns 4-6. A code is valid if it exists in combination with STATE in the
AIRS GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
Error Messages:
ERROR - INVALID COUNTY CODE
COUNTY must be in the GEO-COMMON File in combination with STATE.
WARNING - CANNOT VERIFY COUNTY CODE
COUNTY cannot be verified because STATE is invalid.
Common Fields 3-8 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
3.6 SITE
SITE is a numeric code that uniquely identifies each air monitoring site within a county. There is no
requirement that site numbers be assigned continuously or in any particular order. Local organizations
are thus free to allocate site numbers in any way they chose as long as there is no duplication within a
county.
A specific SITE code is associated with a specific physical location and address. Any change in address
requires a new SITE code to be assigned. This address change could include a change from the roof of
one building to another. A change in location on the same roof should not normally require a new SITE
code. Although an address change would routinely mean a new SITE code, some changes that do not
change the site's location in respect to surrounding sources and its measurement scale, would require no
change. EPA Regional Office should be consulted for assistance in determining whether a new SITE
code is required.
Attributes:
4 digit code
Required
Coding Instructions:
Place a four digit numeric SITE code in columns 7-10. Use leading zeros as needed.
Error Message:
ERROR - INVALID SITE CODE
SITE must be numeric.
December 1993
3-9
Common Fields
-------
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.0 Site Transactions (Al through AT)
This set of seven transactions is used to update site information in the Site File.
Type Al contains site information in the following fields:
SUPPORT AGENCY
STREET ADDRESS
DATE SITE ESTAB
DATE SITE TERM
HQ EVAL DATE
REGIONAL EVAL DATE
Type A2 contains site information in the following fields:
CITY
AQCR
MSA
AIR BASIN
ELEVATION MSL
COMPASS SECTOR
DISTANCE CITY
LOCATION SETTING
LAND USE
DIFFERENCE GMT
TYPE MET SITE
MET SITE ID
DISTANCE SITE
DIRECTION SITE
STATE OR LOCAL ID
Type A3 contains site information in the following fields:
SEQUENCE NUMBER
STREET NUMBER
STREET NAME
TYPE ROAD
TRAFFIC FLOW
YEAR OF TRAFFIC FLOW
DIRECTION TO STREET (AT CLOSEST POINT TO SITE)
SITE LOCATION TYPE
December 1993
4-1
Site Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
MSA REPRESENTED (PAMS ORIENTED)
CMSA REPRESENTED
OPEN PATH NUMBER
DIR TO TRANSMITTER (FROM RECEIVER)
BEAM LENGTH (IN METERS)
TRANSMITTER HEIGHT (IN METERS)
RECEIVER HEIGHT ON METERS)
MIN BEAM HEIGHT (IN METERS)
MAX BEAM HEIGHT (IN METERS)
LAND USE UNDER PATH
Type A4 contains site information in the following fields:
UTM ZONE
UTM EASTING
UTM NORTHING
LATITUDE
LONGITUDE
METHOD OF DETERMINATION
DATUM
SCALE
ESTIMATE OF ACCURACY
Type AS contains site information in the following field:
LOCATION DESCRIPTION
Type A6 contains site information in the following field:
SITE COMMENTS (LINE 1)
Type A7 contains site information in the following field:
SITE COMMENTS (LINE 2)
Figure 4-1 shows the coding form for transaction types Al through A7.
INSERT transactions (i.e., transactions with action code "I") are used to create a site that does not exist
in the Site File. Types Al - AS are required to INSERT a site; Types A6 - A7 are optional. A site can
not be inserted unless at least one Monitor is inserted at the same time using monitor transactions (types
Fl - F3).
DELETE transactions (i.e., transactions with action code "D") are used to remove sites from the Site
File. The DELETE action code is allowed only for type Al transactions. A site may not be deleted if
any monitors for that site remain in the Site File. You must delete the site and its last monitor(s) at the
same time.
Site Transactions 4-2 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
MODIFY transactions (i.e., transactions with action code "M") are used to change the contents of site-
specific fields in the Site file. Blank fields on a MODIFY transaction are ignored; they do not affect the
Site File. The values coded on a MODIFY transaction replace the values of the corresponding fields in
the Site File. If no value existed previously, the value from the transaction is inserted into the record
of the Site File. Values may also be deleted from the Site File by coding asterisks ("*") in every
position of the corresponding fields of a transaction. (Some fields, which are identified in the following
subsections, cannot be deleted because they are required fields. Only optional fields may be deleted.)
The following error messages pertain to the site transactions:
ERROR - ATTEMPT TO ADD SITE DATA FOR AN EXISTING SITE
The site-ID (STATE, COUNTY, SITE) specified on an INSERT transaction already exists in the
Site file.
ERROR - ATTEMPT TO ADD SITE WITHOUT ADDING MONITOR
A site is being added for which no monitor is being added.
ERROR - ATTEMPT TO CHANGE SITE DATA THAT DOES NOT EXIST
The site-ID (STATE, COUNTY, SITE) specified on a MODIFY transaction does not exist in the
Site file.
ERROR - ATTEMPT TO DELETE SITE DATA THAT DOES NOT EXIST
The site-ID (STATE, COUNTY, SITE) specified on a DELETE transaction does not exist in the
Site file.
ERROR - ATTEMPT TO DELETE SITE WITHOUT DELETING ALL MONITORS
A monitor that is not being deleted exists for the site being deleting.
ERROR - DUPLICATE RECORDS
There are two or more transactions with the same site, transaction type, transaction-ID, and
action code.
December 1993
4-3
Site Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
£
a
i
o
o
I
il
I
S
I
2
I
«
s
SSI3SUI
uuuu ouoo
!l8l358i
liifisie
Illlssl!
Figure 4-1. Coding Form for Transaction Types Al - A7 (1 of 2)
Site Transactions
4-4
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
1 I
si-
o
9
ui
o
i!
if
(••mil
arECOMMEWrSIUNEl)
E
i
P
^
??
4
1C
a
C
Jt
e
s
c
p
c
£
5
&
z
<
X
3
S
*
S
7
&
?
9
2
3
?
3;
1
1
?
S
7
3
e
5
?
*
*
A
91
f
X
3
H
<•
-
-
j;!
A
S
s
N
K
!C
£
IS
R
^
£
9
'H
'S
«
r
—
»
•7
•^
<•
—
*^
••
-
<
Figure 4-1. Coding Form for Transaction Types Al - A7 (2 of 2)
December 1993
4-5
Site Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.1 Transaction Type Al - Site Information - Part 1
The fields described in this section are validated for insert (I) and modify (M) transactions, but not for
delete (D) transactions. The STATE, COUNTY, and SITE fields are always validated, as described in
Section 3 above.
For a modify transaction, at least one of the following fields must be non-blank:
SUPPORT AGENCY
STREET ADDRESS
DATE SITE ESTAB
DATE SITE TERM
HQ EVAL DATE
REG EVAL DATE
If a type Al MODIFY transaction lacks a value for all of these fields, the following message is generated:
ERROR - ALL FIELDS BLANK ON MODIFY
When inserting a new site, types Al through AS with minimal data must be present. A minimal type Al
transaction has values for the following fields:
STATE
COUNTY
SITE
SUPPORT AGENCY
SITE ADDRESS
DATE SITE ESTAB
If a type Al INSERT transaction lacks a value for any of these fields, the following message is generated:
ERROR - REQUIRED "Al" TRANSACTION MISSING
Transaction Type Al 4-fi December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.1.1 SUPPORT AGENCY
SUPPORT AGENCY identifies the agency responsible for the operation of the monitoring site.
Attributes:
3 digit code
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 11-13. A code is valid if it exists in
combination with the STATE code in the GEO-COMMON File. Valid codes are listed in Volume GC2
of the AIRS User's Guide.
Error Messages:
ERROR - CANNOT DELETE SUPPORT-AGENCY
SUPPORT AGENCY is a required field and cannot be deleted. Remove the asterisks from this
field of the MODIFY transaction. If this is the only field coded on the transaction, delete the
transaction.
ERROR - INVALID SUPPORT-AGENCY
The code for SUPPORT AGENCY is not correct. Valid codes for each state are in the GEO-
COMMON File. Refer to the listing of valid codes in Volume GC2 of the AIRS User's Guide.
ERROR - SUPPORT-AGENCY CANNOT BE BLANK
SUPPORT AGENCY is required for an INSERT transaction.
WARNING - CANNOT VERIFY SUPPORT-AGENCY
SUPPORT AGENCY must be checked in combination with the STATE code. If the STATE field
of this transaction is invalid, SUPPORT AGENCY cannot be checked.
December 1993
4-7
Transaction Type Al
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.1.2 STREET ADDRESS
STREET ADDRESS specifies the building/street location of the monitoring site.
Attributes: 40 characters
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
In columns 14-53, enter the STREET ADDRESS of the site. Any non-blank value is valid.
Error Messages:
ERROR - CANNOT DELETE STREET-ADDRESS
STREET ADDRESS is a required faeld and cannot be deleted. Remove the asterisks from this
field of the MODIFY transaction.
ERROR - STREET-ADDRESS CANNOT BE BLANK
STREET ADDRESS is required for an INSERT transaction.
Transaction Type Al 4-8 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.1.3 DATE SITE ESTABLISHED
DATE SITE ESTABLISHED is the date on which a monitoring site began collecting air quality data.
Attributes:
6 digit date
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
In columns 54-59, enter the DATE SITE ESTABLISHED in YYMMDD format. The date must be
between January 1, 1957, and a year after the current date.
Error Messages:
ERROR - CANNOT DELETE DATE-SITE-ESTAB
DATE SITE ESTABLISHED is a required field and cannot be deleted. Remove the asterisks
from this field of the MODIFY transaction.
ERROR - DATE-SITE-ESTAB CANNOT BE BLANK
DATE SITE ESTABLISHED is required for an INSERT transaction.
ERROR - INVALID DATE-SITE-ESTAB
The DATE SITE ESTABLISHED must be a valid Gregorian date within the range given in the
coding instructions above.
December 1993
4-9
Transaction Type Al
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.1.4 DATE SITE TERMINATED
DATE SITE TERMINATED is the date on which a monitoring site ceased to operate.
Attributes: 6 digit date
Optional
Coding Instructions:
To INSERT or MODIFY, enter the desired date in YYMMDD format in columns 60-65. The date must
be between January 1,1957, and the current date, and it must be later than DATE SITE ESTABLISHED
if that field is valued. In addition, for a MODIFY, the date must be greater than or equal to the latest
DATE SAMPLING ENDED for the monitor(s).
To delete, use a MODIFY transaction with columns 60-65 filled with asterisks.
Error Messages:
ERROR - ALL MONITORS NOT TERMINATED
On a MODIFY, the DATE SITE TERMINATED must be a valid Gregorian date within the
range given above. It must also be greater than or equal to the latest DATE SAMPLING
ENDED for the monitor(s). All monitors must have a DATE SAMPLING ENDED.
ERROR - CANNOT CHANGE DATE-SITE-TERMINATED TO EARLIER THAN
DATE-SAMPLING-ENDED
On a MODIFY, the DATE SITE TERMINATED cannot be earlier than the latest DATE
SAMPLING ENDED for any of the monitors at that site.
ERROR - INVALID DATE-SITE-TERM
The DATE SITE TERMINATED must be a valid Gregorian date within the range given above.
It must also be greater than DATE SITE ESTABLISHED.
If this field is being deleted with a MODIFY transaction, there must be an asterisk in each
position of the field.
Transaction Type Al 4-10 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.1.5 HQEVALDATE
HQ EVAL DATE is the date of the most recent headquarters evaluation of the site.
Attributes:
Coding Instructions:
6 digit date
Optional
To INSERT or MODIFY, code the desired date in YYMMDD format in columns 66-71. The date must
be between January ]., 1980 (when NAMS monitoring regulations were promulgated), and the current
date.
To DELETE, use a MODIFY transaction with columns 66-71 filled with asterisks.
Error Message:
ERROR - INVALID HQ-EVAL-DATE
The HQ EVAL DATE must be a valid Gregorian date within the range given above.
If this field is being deleted with a MODIFY transaction, there must be an asterisk in each
position of the field.
December 1993
4-11
Transaction Type Al
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.1.6 REGIONAL EVAL DATE
REGIONAL EVAL DATE is the date of the most recent regional evaluation of the site for siting criteria.
Attributes: 6 digit date
Optional
Coding Instructions:
To INSERT or MODIFY, enter the desired date in YYMMDD format in columns 72-77. The date must
be between January 1, 1980 (when NAMS monitoring regulations were promulgated), and the current
date.
To DELETE, use a MODIFY transaction with columns 72-77 filled with asterisks.
Error Message:
ERROR - INVALID REGIONAL-EVAL-DATE
The REGIONAL EVAL DATE must be a valid Gregorian date within the range given above.
If this field is being deleted with a MODIFY transaction, there must be an asterisk in each
position of the field.
Transaction Type Al 4-12 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.2 Transaction Type A2 - Site Information - Part 2
The fields described below are validated for insert (I) and modify (M) transactions. (Delete (D) is not
a valid action for type A2 transactions.)
For a modify transaction, at least one of the following fields must be non-blank:
CITY
AQCR
MSA
AIR BASIN
ELEVATION MSL
COMPASS SECTOR
DISTANCE CITY
LOCATION SETTING
LAND USE
DIFFERENCE GMT
TYPE MET SITE
MET SITE ID
DISTANCE SITE
DIRECTION SITE
STATE OR LOCAL ID
If this condition is not met, the following message is generated:
ERROR - ALL FIELDS BLANK ON MODIFY
When inserting a new site, transaction types Al through AS with values for a minimal number of fields
must be present. A minimal type A2 transaction has values for the following fields:
STATE
COUNTY
SITE
CITY
AQCR
MSA
LOCATION SETTING
LAND USE
If a type A2 INSERT transaction lacks a value for any of these fields, the following message is generated:
ERROR - REQUIRED "A2H TRANSACTION MISSING
December 1993
4-13
Transaction Type A2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.2.1 CITY
CITY indicates the city within whose legal boundaries the site is located.
Attributes: 5 digit code
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid FIPS city code in columns 11-15. A CITY code is valid if the
STATE/COUNTY/CITY combination exists in the GEO-COMMON File. Valid CITY codes are listed
in Volume GC2 of the AIRS User's Guide.
If the site is not within a city, use code 00000 (zeros).
Error Messages:
ERROR - CANNOT DELETE CITY
CITY is a required field and cannot be deleted. Remove the asterisks from this field of the
MODIFY transaction.
ERROR - INVALID CITY
The CITY is not numeric.
The combination of STATE, COUNTY, and CITY does not exist in the FIPS-REL-AREA
portion of the GEO-COMMON File.
WARNING - CANNOT VERIFY CITY
CITY must be checked in combination with STATE and COUNTY. If STATE or COUNTY is
invalid, CITY cannot be checked. Refer to the listing of valid codes in Volume GC2 of the AIRS
User's Guide.
Transaction Type A2 4-14 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.2.2 AQCR
AQCR identifies in which of the 247 Air Quality Control Regions the site is located.
Attributes:
3 digit code
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid AQCR code in columns 16-18. For U.S. states and territories,
a code is valid if the combination STATE/COUNTY/AQCR exists in the GEO-COMMON File. For
GEMS countries, a value of "000" is valid. Valid codes are listed in Volume GC2 of the AIRS User's
Guide.
Error Messages:
ERROR - CANNOT DELETE AQCR
AQCR is a required field and cannot be deleted. Remove the asterisks from this field of the
MODIFY transaction.
ERROR - INVALID AQCR
AQCR cannot be blank for an INSERT transaction. For U.S. states and territories, it is valid
if the combination of STATE, COUNTY, and AQCR exists in the GEO-COMMON File. For
GEMS countries, a value of "000" is valid.
WARNING - CANNOT VERIFY AQCR
AQCR must be checked in combination with STATE and COUNTY. If STATE or COUNTY
is invalid, AQCR cannot be checked.
December 1993
4-15
Transaction Type A2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.2.3 MSA
MSA indicates in which Metropolitan Statistical Area (MSA) the site is located.
Attributes: 4 digit code
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid MSA code in columns 19-22. A code is valid if the
STATE/COUNTY/MSA combination exists in the GEO-COMMON File. Valid codes are listed in
Volume GC2 of the AIRS User's Guide.
If a site is not within a Metropolitan Statistical Area, use code 0000 (zeros).
Error Messages:
ERROR - CANNOT DELETE MSA
MSA is a required field and cannot be deleted. Remove the asterisks from this field of the
MODIFY transaction.
ERROR - INVALID MSA
MSA cannot be blank for an INSERT transaction. The combination of STATE, COUNTY, and
MSA does not exist in the GEO-COMMON File.
WARNING - CANNOT VERIFY MSA
MSA must be checked in combination with STATE and COUNTY. If STATE or COUNTY is
invalid, MSA cannot be checked. Refer to the listing of valid codes in Volume GC2 of the AIRS
User's Guide.
Transaction Type A2 4-16 December 1993
-------
AIRS User's Guide
Volume AQ2
t Air Quality Data Coding
4.2.4 AIR BASIN
AIR BASIN indicates in which geographical area of California the site is located.
Attributes:
Coding Instructions:
2 digit code
Optional
To INSERT or MODIFY, place a valid AIR BASIN code in columns 23-24. AIR BASIN can only be
used with State '06* (California). A code is valid if it exists in the GEO-COMMON File. Valid codes
are listed in Volume GC2 of the AIRS User's Guide.
To DELETE, place asterisks in columns 23-24 of a MODIFY transaction.
Error Messages:
ERROR - AIR-BASIN ONLY FOR STATE 06
AIR BASIN can only be used if the State code on the transaction is 06.
ERROR - INVALID AIR-BASIN
AIR BASIN must be in the GEO-COMMON File.
December 1993
4-17
Transaction Type A2
-------
AIRS User's Guide
Air Quality Data Coding, Volume AQ2
4.2.5 ELEVATION MSL
ELEVATION MSL is the elevation in meters above Mean S"a Level (MSL) of the site.
Attributes: 5 digit numeric
Optional
Coding Instructions:
To INSERT or MODIFY,'code an integer value less than 20,000 right-justified in columns 25-29.
To DELETE, place asterisks in columns 25-29 of a MODIFY transaction.
Error Message:
ERROR - INVALID ELEVATION-MSL
For an INSERT transaction, ELEVATION MSL may be blank, an unsigned numeric value right
justified in the field, or a signed numeric value of the form -nnnn.
For a MODIFY transaction, ELEVATION MSL may be asterisks or one of the values allowed
for an INSERT transaction.
Transaction Type A2 4-18 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.2.6 COMPASS SECTOR
COMPASS SECTOR represents the true (as opposed to magnetic) direction of the site from the central
business district. If the site is within the central business district, COMPASS SECTOR indicates the
direction the probe faces.
Attributes:
2 character
Optional
Coding Instructions:
To INSERT or MODIFY, enter the appropriate value left justified, space filled into columns 30-31.
To DELETE, place asterisks in columns 30-31 of a MODIFY transaction.
Valid COMPASS SECTOR values are:
E
N
NE
NW
S
SE
SW
W
east
north
northeast
northwest
south
southeast
southwest
west
Error Message:
ERROR - INVALID COMPASS-SECTOR
For an INSERT transaction, COMPASS SECTOR may be blank. If it is valued, it must be one
of the values listed above.
For a MODIFY transaction, COMPASS SECTOR may be blank, asterisks, or one of the values
listed above.
December 1993
4-19
Transaction Type A2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.2.7 DISTANCE CITY
DISTANCE CITY is the distance in kilometers of the site from the center of the downtown central
business district of the city in which the site is located.
Attributes: 3 digit numeric
Optional
Coding Instructions:
To INSERT or MODIFY, place an integer value greater than 0 and less than 1,000 right justified in
columns 32-34.
To DELETE, place asterisks in columns 32-34 of a MODIFY transaction.
Error Message:
ERROR - INVALID DISTANCE-CITY
For an INSERT transaction, DISTANCE CITY must be blank or a valid numeric value as
defined above.
For a MODIFY transaction, DISTANCE CITY must be blank, asterisks, or a valid numeric value
as defined above.
Transaction Type A2 4-20 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.2.8 LOG SET (Location Setting)
LOG SET is a location setting code that indicates the type of environment in which the site is located.
Attributes:
1 character code
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid code in column 35. A code is valid if it exists in the GEO-
COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
Error Messages:
ERROR - CANNOT DELETE LOCATION-SETTING
LOG SET is a required field and cannot be deleted. Remove the asterisk from this field of the
MODIFY transaction.
ERROR - INVALID LOCATION-SETTING
LOG SET is required for an INSERT transaction. It must be in the GEO-COMMON File.
December 1993
4-21
Transaction Type A2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.2.9 LAND USE
LAND USE identifies the prevalent land use within one-quarter mile of the site.
Attributes: 1 character code
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid code in column 36. A code is valid if it exists in the GEO-
COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
Error Messages:
ERROR - CANNOT DELETE LAND-USE
LAND USE is a required field and cannot be deleted. Remove the asterisk from this field of the
MODIFY transaction.
ERROR - INVALID LAND-USE
LAND USE cannot be blank on an INSERT transaction. It must be in the GEO-COMMON File.
Transaction Type A2 4-22 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.2.10 DIP GMT
DIP GMT is the difference in hours between standard time at the site and Greenwich Mean Time (GMT).
Attributes:
Coding Instructions:
2 digit numeric
Optional
Although all states except GUAM (66) are behind GMT, and GUAM (66) is ahead of GMT, DIP GMT
takes no sign. For example, GUAM (66), which is 10 hours ahead of GMT would be coded as 10, just
as Hawaii (IS), which is 10 hours behind GMT, would be coded as 10.
To INSERT or MODIFY, place the appropriate value in columns 37-38.
To DELETE, place asterisks in columns 37-38 of a MODIFY transaction.
Error Messages:
ERROR - INVALID DIFFERENCE-GMT
DIP GMT must be blank or numeric for an INSERT transaction.
DIP GMT must be blank, numeric, or asterisks for a MODIFY transaction.
DIP GMT must fall within the maximum and minimum values for the STATE.
WARNING - CANNOT VERIFY DIFFERENCE-GMT
DIP GMT must be checked in combination with STATE. If STATE is invalid, DIP GMT cannot
be checked.
December 1993
4-23
Transaction Type A2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.2.11 TYPE MET SITE
TYPE MET SITE identifies whether meteorological data is collected at this site or another site or whether
the meteorological site is operated by the National Weather Service or the Airport Weather Service.
Attributes: 1 character code
Optional
Coding Instructions:
r
To INSERT or MODIFY, place a valid code in column 39. A code is valid if it exists in the AIRS GEO-
COMMON file. Valid values are listed in Volume GC2 of the AIRS User's Guide.
To DELETE, place asterisks in column 39 of a MODIFY transaction.
Error Messages:
ERROR - INVALID TYPE-MET-SITE
TYPE MET SITE must be in the GEO-COMMON File.
Transaction Type A2 4-24 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.2.12 MET SITE ID
MET SITE ID identifies the AIRS site-ID where meteorological data is collected if not collected at this
site.
Attributes:
Coding Instructions:
9 character code
Optional on INSERT
Optional on MODIFY
To INSERT or MODIFY, place a valid code in columns 40-48. A code is valid if it is a valid
combination of STATE, COUNTY, and SITE in the AIRS SITE File.
To DELETE, place asterisks in columns 40-48 of a MODIFY transaction. You cannot delete MET SITE
ID if TYPE MET SITE = 2.
Error Messages:
ERROR - CANNOT DELETE MET-SITE-ID
MET SITE ID is a required field if TYPE MET SITE = 2.
ERROR • INVALID MET-SITE-ID
On an INSERT transaction when MET SITE ID is valued, it must be a valid combination of
STATE, COUNTY, SITE in the AIRS SITE File.
On a MODIFY transaction when MET SITE ID is not blank or all *'s, it must be a valid
combination of STATE, COUNTY, SITE in the AIRS SITE File.
ERROR - MET-SITE-ID CANNOT BE BLANK
On an INSERT transaction with TYPE MET SITE = 2, MET SITE ID cannot be blank.
ERROR - MET-SITE-ID MUST BE BLANK
On an INSERT transaction with TYPE MET SITE = 1, MET SITE ID must be blank.
December 1993
4-25
Transaction Type A2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.2.13 DISTANCE SITE
DISTANCE SITE identifies the distance the meteorological site identified by MET SITE ID is from this
site in meters.
Attributes: 5 character code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 49-53. The code must be numeric > 0.
To DELETE, place asterisks in columns 49-53 of a MODIFY transaction. You cannot delete
DISTANCE SITE if TYPE MET SITE is greater than 1.
Error Messages:
ERROR - CANNOT DELETE DISTANCE-SITE
DISTANCE SITE is a required field and cannot be deleted if TYPE MET SITE is greater than
1.
ERROR - DISTANCE-SITE CANNOT BE BLANK
On an INSERT transaction with TYPE MET SITE > 1, DISTANCE SITE cannot be blank.
ERROR - DISTANCE-SITE MUST BE BLANK
On an INSERT transaction with TYPE MET SITE = I, DISTANCE SITE must be blank.
ERROR - INVALID DISTANCE-SITE
On an INSERT transaction, DISTANCE SITE must be numeric greater than zero if valued.
On a MODIFY transaction, DISTANCE SITE must be numeric greater than zero unless it is
blank or all *'s.
Transaction Type A2 4-26 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.2.14 DIRECTION SITE
DIRECTION SITE identifies the direction the meteorological site identified in MET SITE ID is from this
site.
Attributes:
Coding Instructions:
2 character code
Optional
To INSERT or MODIFY, place a valid code in columns 54-55. A code is valid if it is a valid
COMPASS SECTOR code. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
To DELETE, place asterisks in columns 54-55 of a MODIFY transaction. You cannot delete
DIRECTION SITE if TYPE MET SITE is greater than 1.
Error Messages:
ERROR - CANNOT DELETE DIRECTION-SITE
DIRECTION SITE is a required field and cannot be deleted if TYPE MET SITE is greater than
1.
ERROR - DIRECTION-SITE CANNOT BE BLANK
On an INSERT transaction with TYPE MET SITE > 1, DIRECTION SITE cannot be blank.
ERROR - DIRECTION-SITE MUST BE BLANK
On an INSERT transaction with TYPE MET SITE = 1, DIRECTION SITE must be blank.
ERROR - INVALID DIRECTION-SITE
On an INSERT transaction if DIRECTION SITE is valued, it must be a valid COMPASS
SECTOR code.
On a MODIFY transaction if DIRECTION SITE is not blank or all *'s, it must be a valid
COMPASS SECTOR code.
December 1993
4-27
Transaction Type A2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.2.15 STATE OR LOCAL ID
STATE OR LOCAL ID identifies the code used by a state or local agency to identify this site if different
from the AIRS site-ID.
Attributes: 10 character code
Optional
Coding Instructions:
To INSERT or MODIFY, place a value in columns 56-55. No edit checks are performed on this field.
Transaction Type A2 4-28 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.3 Transaction Type A3 - Site Information - Part 3
The fields described below are validated for insert (I) and modify (M) transactions. (Delete (D) is not a
valid action for type A3 transactions.)
For a modify transaction, at least one of the following fields must be non-blank:
SEQUENCE NUMBER
STREET data
STREET NUMBER
STREET NAME
TYPE ROAD
TRAFFIC FLOW
YEAR OF TRAFFIC FLOW
DIRECTION TO STREET (AT CLOSEST POINT TO SITE)
LOCATION data
SITE LOCATION TYPE
MSA REPRESENTED (PAMS ORIENTED)
CMSA REPRESENTED
OPEN PATH data
OPEN PATH NUMBER
DIR TO TRANSMITTER (FROM RECEIVER)
BEAM LENGTH (IN METERS)
TRANSMITTER HEIGHT (IN METERS)
RECEIVER HEIGHT (IN METERS)
MIN BEAM HEIGHT (IN METERS)
MAX BEAM HEIGHT ON METERS)
LAND USE UNDER PATH
If this condition is not met, the following message is generated:
ERROR - ALL FIELDS BLANK ON MODIFY
When inserting a new site, Al through A5 transactions with values for a minimal number of fields must
be present. Data is allowed for .up to nine streets around the site and/or open paths from the site;
therefore, there may be up to nine A3 transactions for a particular site. When inserting a new site, at
least one A3 transaction must have complete STREET data. At least one of the following groups of
information must be present:
STREET data
LOCATION data
OPEN PATH data
December 1993
4-29
Transaction Type A3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
A minimal type A3 transaction has values for the following fields
STATE
COUNTY
SITE
SEQUENCE NUMBER
and
STREET data or
LOCATION data or
OPEN PATH data'
If a type A3 INSERT transaction lacks a value for any of these fields, the following message is generated:
ERROR - REQUIRED "A3" TRANSACTION MISSING
If a type A3 MODIFY transaction has a valid STREET NUMBER and asterisks in STREET NAME,
TYPE ROAD, TRAFFIC FLOW, YEAR OF TRAFFIC FLOW, and DIRECTION TO STREET,
STREET data will be deleted from the database for the specified STREET NUMBER. If this is the only
street information for the site, the following message is generated:
ERROR - CANNOT DELETE LAST STREET INFORMATION
When inserting a new site, at least one A3 transaction must have complete STREET data. If none of the
A3 INSERT transactions have valid STREET data, the following message is generated:
ERROR - CANNOT ADD SITE WITHOUT STREET INFORMATION
Transaction Type A3 4-30 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.3.1 SEQUENCE NUMBER
SEQUENCE NUMBER allows the user to enter up to nine A3 transactions for a particular site.
Attributes: 1 digit code
Required on INSERT
Required on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid sequence number in column 11. Valid codes are 1 through 9.
Error Messages:
ERROR - CANNOT DELETE SEQUENCE-NUMBER
SEQUENCE NUMBER is a required field and cannot be deleted. Remove the asterisks from this
field of the MODIFY transaction. If this is the only field coded, delete the transaction.
ERROR - INVALID SEQUENCE-NUMBER
Valid values for SEQUENCE NUMBER are 1 through 9.
December 1993
4-31
Transaction Type A3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.3.2 STREET NUMBER
STREET NUMBER identifies the number of the street around the site for which the data are being
submitted. If STREET NAME, TYPE ROAD, TRAFFIC FLOW, YEAR OF TRAFFIC FLOW, or
DIRECTION TO STREET is valued, STREET NUMBER must be valued. STREET NUMBER is used
to associate detailed street information for the site to streets closest to the monitors at this site.
Attributes: 1 digit code
optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in column 12. Valid codes are numeric greater than 0.
This field cannot be deleted, and therefore cannot contain asterisks in a modify transaction. At least one
A3 INSERT transaction must have a valid STREET NUMBER.
Error Messages:
ERROR - CANNOT DELETE STREET-NUMBER
STREET NUMBER cannot be deleted.
ERROR - DUPLICATE STREET INFORMATION
On an INSERT transaction, there is more than one A3 transaction with the same STREET
NUMBER.
ERROR - INVALID STREET-NUMBER
STREET NUMBER must be numeric greater than 0.
ERROR - STREET-NUMBER CANNOT BE BLANK
If STREET NAME, TYPE ROAD, TRAFFIC FLOW, YEAR OF TRAFFIC FLOW, or
DIRECTION TO STREET is valued, STREET NUMBER must be valued.
On a MODIFY transaction, when STREET NAME, TYPE ROAD, TRAFFIC FLOW, YEAR
OF TRAFFIC FLOW, or DIRECTION TO STREET equals *'s, a valid STREET NUMBER
must be specified.
Transaction Type A3 4-32 December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
4.3.3 STREET Data
To DELETE STREET data, enter a valid STREET NUMBER and place asterisks in the remaining
STREET data fields of a MODIFY transaction. On a MODIFY transaction, when STREET data fields
contain asterisks, the following edit checks are made:
1. Must have a valid STREET NUMBER.
2. All remaining STREET data fields must be *'s:
STREET NAME
TYPE ROAD
TRAFFIC FLOW
YEAR OF TRAFFIC FLOW
DIRECTION TO STREET
On an INSERT transaction, at least one A3 transaction must have complete STREET data.
Error Messages:
ERROR - INVALID STREET-NUMBER
STREET NUMBER must be numeric greater than zero.
ERROR - MUST DELETE ALL STREET DATA
If **s are placed in one of the STREET data fields, *'s must be placed in all of the STREET data
fields.
December 1993 4-33 Transaction Type A3
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
4.3.3.1 STREET NAME
STREET NAME identifies the name of the STREET around the site for which data is being submitted.
Attributes:
Coding Instructions:
20 character code
Optional
To INSERT or MODIFY, place a STREET NAME in columns 13-32. This field must be valued if
STREET NUMBER is valued.
To DELETE this field, see Section 4.3.3, STREET Data.
Error Messages:
ERROR - STREET-NAME CANNOT BE BLANK
If STREET NUMBER is valued, STREET NAME cannot be blank.
Transaction Type A3
4-34
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.3.3.2 TYPE ROAD
TYPE ROAD is a code that indicates the type of road being described by this STREET data group.
Attributes:
1 digit code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in column 33. Valid codes are 1 through 6.
To DELETE this field, see Section 4.3.3, STREET Data.
If STREET NUMBER is blank, this field must be blank. If STREET NUMBER is valued, this field must
be valued.
Error Messages:
ERROR - INVALID TYPE-ROAD
Valid codes are 1 through 6.
ERROR - TYPE-ROAD CANNOT BE BLANK
If STREET NUMBER is valued, TYPE ROAD must be valued.
ERROR - TYPE-ROAD MUST BE BLANK
If STREET NUMBER is blank, TYPE ROAD must be blank.
December 1993
4-35
Transaction Type A3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.3.3.3 TRAFFIC FLOW
TRAFFIC FLOW is the estimated daily traffic volume on a roadway.
Attributes: 6 digit code
Optional
Coding Instructions:
To INSERT or MODIFY, .place a valid code in columns 34-39. A code is valid if it is numeric, greater
than zero.
To DELETE this field, see Section 4.3.3, STREET Data.
If STREET NUMBER is valued, this field must be valued. If STREET NUMBER is blank, this field
must be blank.
Error Messages:
ERROR - INVALID TRAFFIC-FLOW
Valid codes are numeric greater than zero.
ERROR - TRAFFIC-FLOW CANNOT BE BLANK
If STREET NUMBER is valued, TRAFFIC FLOW must be valued.
ERROR - TRAFFIC-FLOW MUST BE BLANK
If STREET NUMBER is blank, TRAFFIC FLOW must be blank.
Transaction Type A3 4-36 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.3.3.4 YEAR OF TRAFFIC FLOW
YEAR OF TRAFFIC FLOW indicates the year of the estimated daily traffic volume on a roadway.
Attributes:
Coding Instructions:
2 digit code
Optional
To INSERT or MODIFY, place a valid code in columns 40-41. Valid values are 57 through current
year.
To DELETE this field, see Section 4.3.3, STREET Data.
If TRAFFIC FLOW is blank, this field must be blank. If TRAFFIC FLOW is valued, this field must
be valued.
Error Messages:
ERROR - INVALID TRAFFIC-YEAR
Valid dates are 57 through current year.
ERROR - TRAFFIC-YEAR CANNOT BE BLANK
If TRAFFIC FLOW is valued, this field must be valued.
ERROR - TRAFFIC-YEAR MUST BE BLANK
If TRAFFIC FLOW is blank, this field must be blank.
December 1993
4-37
Transaction Type A3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.3.3.5 DIRECTION TO STREET
DIRECTION TO STREET identifies the direction from the site to the street.
Attributes: 2 character code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 42-43. A code is valid if it is a valid
COMPASS SECTOR code in the GEO-COMMON File. The codes are listed in Volume GC2 of the
AIRS User's Guide.
To DELETE this field, see Section 4.3.3, STREET Data.
Error Messages:
ERROR - DIRECTION-TO-STREET CANNOT BE BLANK
If STREET NUMBER is valued, this field must be valued.
ERROR - DIRECTION-TO-STREET MUST BE BLANK
If STREET NUMBER is blank, this field must be blank.
ERROR - INVALID DIRECTION-TO-STREET
DIRECTION TO STREET must be a valid COMPASS SECTOR code.
Transaction Type A3 4-38 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.3.4 SITE LOCATION TYPE
SITE LOCATION TYPE identifies the location type for the photochemical assessment monitoring site
in relation to the MSA or CMSA that it represents. This location type is determined by the predominant
wind information as well as pollutant concentrations as defined by the PAMS regulations.
Attributes:
Coding Instructions:
1 digit code
Optional
To INSERT or MODIFY, place a valid code in column 44. A code is valid if it is a valid SITE
LOCATION TYPE in the GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS
User's Guide.
If this field is valued, MSA REPRESENTED or CMSA REPRESENTED must be valued, but not both.
To delete, place an * in column 44. If you delete this field, then MSA REPRESENTED and CMSA
REPRESENTED must also be deleted.
Error Messages:
ERROR - INVALID SITE-LOCATION-TYPE
SITE LOCATION TYPE must be in the GEO-COMMON File.
ERROR - MUST DELETE MSA DATA
If SITE LOCATION TYPE is deleted, MSA REPRESENTED and CMSA REPRESENTED must
be deleted.
ERROR - SITE-LOC INVALID (NO MSA DATA)
If SITE LOCATION TYPE is valued, MSA REPRESENTED or CMSA REPRESENTED must
be valued.
December 1993
4-39
Transaction Type A3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.3.5 MSA REPRESENTED
MSA REPRESENTED identifies which Metropolitan Statistical Area is represented based on the SITE
LOCATION TYPE.
Attributes: 4 digit code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 45-48. A code is valid if it is a valid MSA code
in the GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
If SITE LOCATION TYPE is blank, this field must be blank. If CMSA REPRESENTED is valued, this
field must be blank.
To delete, place *'s in columns 45-48. If this field is deleted, then SITE LOCATION TYPE must also
be deleted.
Error Messages:
ERROR - INVALID MSA-REPRESENTED
MSA REPRESENTED must be valid MSA code in the GEO-COMMON File.
ERROR - MSA-REP INVALID WITH CMSA REP
If CMSA REPRESENTED is valued, this field must be blank.
ERROR - MSA-REPRESENTED MUST BE BLANK.
If SITE LOCATION TYPE is blank, this field must be blank.
Transaction Type A3 4-40 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.3.6 CMSA REPRESENTED
CMS A REPRESENTED identifies which Consolidated Metropolitan Statistical Area is represented based
on the SITE LOCATION TYPE.
Attributes:
Coding Instructions:
4 digit code
Optional
To INSERT or MODIFY, place a valid code in columns 49-52. A code is valid if it is a valid CMSA
code in the GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
If SITE LOCATION TYPE is blank, this field must be blank. If MSA REPRESENTED is valued, this
field must be blank.
To delete, place *'s in columns 49-52. If you delete CMSA REPRESENTED, then SITE LOCATION
TYPE must also be deleted.
Error Messages:
ERROR - CMSA-REPRESENTED MUST BE BLANK
If SITE LOCATION TYPE is blank, this field must be blank.
ERROR - INVALID CMSA
CMSA REPRESENTED must be a valid CMSA code in the GEO-COMMON File.
ERROR - MSA-REP INVALID WITH CMSA REP
If MSA REPRESENTED is valued, CMSA REPRESENTED must be blank.
December 1993
4-41
Transaction Type A3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.3.7 OPEN PATH NUMBER
OPEN PATH NUMBER allows the user to insert data for up to nine different paths for a site. Each
OPEN PATH NUMBER represents a different monitor. The MONITOR OPEN PATH NUMBER
associates die collected data to the OPEN PATH data through the OPEN PATH NUMBER.
Attributes: 1 digit code
Optional
Coding Instructions: ,
To INSERT, place a valid code in column 53. Valid codes are 1 through 9. There may be up to nine
paths from a particular Site. This would require nine different transactions.
This field cannot be *'s on a MODIFY transaction (see OPEN PATH data description).
Error Messages:
ERROR - DUPLICATE OPEN PATH INFORMATION
On an INSERT transaction, there is more than one A3 transaction with the same OPEN PATH
NUMBER.
ERROR * INVALID OPEN-PATH-NUMBER
Valid values are 1 through 9.
ERROR - MONITOR DATA EXISTS FOR THIS OPEN PATH NUMBER
On a MODIFY transaction, a valid OPEN PATH NUMBER was entered with asterisks for the
remaining OPEN PATH data fields to delete this open path from the site information. A monitor
at this site is still associated with this OPEN PATH NUMBER. The MONITOR OPEN PATH
NUMBER must be deleted before the open path can be deleted from the site.
ERROR - OPEN-PATH-NUMBER CANNOT BE BLANK
On a MODIFY transaction, when DIRECTION TO TRANSMITTER, BEAM LENGTH,
TRANSMITTER HEIGHT, RECEIVER HEIGHT, MIN BEAM HEIGHT, MAX BEAM
HEIGHT, and LAND USE UNDER PATH equal *'s, a valid OPEN PATH NUMBER must be
specified.
Transaction Type A3 4-42 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.3.8 OPEN PATH Data
To DELETE OPEN PATH data, enter a valid OPEN PATH NUMBER and place asterisks in the
remaining OPEN PATH data fields of a MODIFY transaction. On a MODIFY transaction, when an
OPEN PATH data field is asterisks, the following edit checks are made:
1. Must have a valid OPEN PATH NUMBER (1 through 9).
2. All remaining OPEN PATH data fields must be *'s:
DIR TO TRANSMITTER
BEAM LENGTH
TRANSMITTER HEIGHT
RECEIVER HEIGHT
MIN BEAM HEIGHT
MAX BEAM HEIGHT
LAND USE UNDER PATH
Error Messages:
ERROR - INVALID OPEN-PATH-NUMBER
Must be a valid OPEN PATH NUMBER (1 through 9).
ERROR - MUST DELETE ALL OPEN-PATH DATA
If an OPEN PATH data field is to be deleted, then all OPEN PATH data fields must be deleted.
4»
December 1993
4-43
Transaction Type A3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.3.8.1 DIR TO TRANSMITTER
DIR TO TRANSMITTER identifies the direction of the transmitter from the receiver at the site.
Attributes: 3 character code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 54-56. A code is valid if it is a valid
COMPASS SECTOR code in the GEO-COMMON File. Valid codes corresponding to a 16-point
compass direction are listed in Volume GC2 of the AIRS User's Guide. If OPEN PATH NUMBER is
blank, this field must be blank. If OPEN PATH NUMBER is valued the field must be valued.
To DELETE DIR TO TRANSMITTER, see Section 4.3.8, OPEN PATH Data.
Error Messages:
ERROR - DIR-TO-TRANSMIT CANNOT BE BLANK
If OPEN PATH NUMBER is valued, this field must be valued.
ERROR • DIR-TO-TRANSMIT MUST BE BLANK
If OPEN PATH NUMBER is blank, this field must be blank.
ERROR - INVALID DIR-TO-TRANSMIT
DIR TO TRANSMITTER must be a valid COMPASS SECTOR code in the GEO-COMMON
File.
Transaction Type A3 4-44 December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
4.3.8.2 BEAM LENGTH (in meters)
BEAM LENGTH identifies the length of the projected beam length between the transmitter and the
receiver at the site.
Attributes: 4 digit code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 57-60. A code is valid if it is numeric. If
OPEN PATH NUMBER is blank, this field must be blank. If OPEN PATH NUMBER is valued, this
field must be valued.
To DELETE BEAM LENGTH, see Section 4.3.8, OPEN PATH Data.
Error Messages:
ERROR - BEAM-LENGTH CANNOT BE BLANK
If OPEN PATH NUMBER is valued, this field must be valued.
ERROR - BEAM-LENGTH MUST BE BLANK
If OPEN PATH NUMBER is blank, this field must be blank.
ERROR - INVALID BEAM-LENGTH
BEAM LENGTH must be numeric if valued.
December 1993 4-45 Transaction Type A3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.3.8.3 TRANSMITTER HEIGHT (in meters)
TRANSMITTER HEIGHT represents the height of the transmitter above ground.
Attributes: 2 digit code
Optional
Coding Instructions:
To INSERT, place a valid code in columns 61-62. A code is valid if it is numeric. If OPEN PATH
NUMBER is blank, this field must be blank. If OPEN PATH NUMBER is valued, this field must be
valued.
To DELETE TRANSMITTER HEIGHT, see Section 4.3.8, OPEN PATH Data.
Error Messages:
ERROR - INVALID TRANSMIT-HEIGHT
TRANSMIT HEIGHT must be numeric if valued.
ERROR - TRANSMIT-HEIGHT CANNOT BE BLANK
If OPEN PATH NUMBER is valued, this field must be valued.
ERROR - TRANSMIT-HEIGHT MUST BE BLANK
If OPEN PATH NUMBER is blank, this field must be blank.
Transaction Type A3 4-46 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.3.8.4 RECEIVER HEIGHT (in meters)
RECEIVER HEIGHT represents the height of the receiver above ground.
Attributes:
Coding Instructions:
2 digit code
Optional
To INSERT or MODIFY, place a valid code in columns 63-64. A code is valid if it is numeric. If
OPEN PATH NUMBER is blank, this Meld mist be blank. If OPEN PATH NUMBER is valued, this
field must be valued.
To DELETE RECEIVER HEIGHT, see Section 4.3.8, OPEN PATH Data.
Error Messages:
ERROR * INVALID RECEIVER-HEIGHT
If RECEIVER HEIGHT is valued, it must be numeric.
ERROR - RECEIVER-HEIGHT CANNOT BE BLANK
If OPEN PATH NUMBER is valued, this field must be valued.
ERROR - RECEIVER-HEIGHT MUST BE BLANK
If OPEN PATH NUMBER is blank, this field must be blank.
December 1993
4-47
Transaction Type A3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.3.8.5 M1N BEAM HEIGHT (in meters)
MIN BEAM HEIGHT identifies die height of the beam (at the lowest point from the ground) being
projected between the receiver and the transmitter at the site.
Attributes: 2 digit code
Optional
Coding Instructions:
f
To INSERT, place a valid code in columns 65-66. A code is valid if it is a numeric > 0 and less than
MAX BEAM HEIGHT. If OPEN PATH NUMBER is blank, this field must be blank. If OPEN PATH
NUMBER is valued, this field must be valued.
To DELETE MIN BEAM HEIGHT, see Section 4.3.8, OPEN PATH Data.
Error Messages:
ERROR - INVALID MIN-BEAM-HEIGHT
If MIN BEAM HEIGHT is valued, it must be numeric greater than zero and less than MAX
BEAM HEIGHT (if valued).
ERROR - MIN-BEAM-HEIGHT CANNOT BE BLANK
If OPEN PATH NUMBER is valued, this field must be valued.
ERROR - MIN-BEAM-HEIGHT MUST BE BLANK
If OPEN PATH NUMBER is blank, this field must be blank.
Transaction Type A3 4-48 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.3.8.6 MAX BEAM HEIGHT (in meters)
MAX BEAM HEIGHT identifies the height of the beam (at the highest point from the ground) being
projected between the receiver and the transmitter at the site.
Attributes:
Coding Instructions:
2 digit code
Optional
To INSERT, place a valid code in columns 67-68. A code is valid if it is a numeric > 0 and greater
than WIN BEAM HEIGHT. If OPEN PATH NUMBER is blank, this field must be blank. If OPEN
PATH NUMBER is valued, this field must be valued.
To DELETE MAX BEAM HEIGHT, see Section 4.3.8, OPEN PATH Data.
Error Messages:
ERROR - INVALID MAX-BEAM-HEIGHT
If MAX BEAM HEIGHT is valued, it must be numeric greater than zero and greater than MIN
BEAM HEIGHT (if valued).
ERROR - MAX-BEAM-HEIGHT CANNOT BE BLANK
If OPEN PATH NUMBER is valued, this field must be valued.
ERROR - MAX-BEAM-HEIGHT MUST BE BLANK
If OPEN PATH NUMBER is blank, this field must be blank.
December 1993
4-49
Transaction Type A3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.3.8.7 LAND USE UNDER PATH
LAND USE UNDER PATH identifies the prevalent land use under the path.
Attributes: 1 character code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 69. A code is valid if it is a valid LAND USE
code in the GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
If OPEN PATH NUMBER is blank, this field must be blank. If OPEN PATH NUMBER is valued this
field must be valued.
To DELETE LAND USE UNDER PATH, see Section 4.3.8, OPEN PATH Data.
Error Messages:
ERROR - INVALID LAND-USE-PATH
LAND USE PATH, if valued, must be a valid LAND USE code in the GEO-COMMON File.
ERROR - LAND-USE-PATH CANNOT BE BLANK
If OPEN PATH NUMBER is valued, this field must be valued.
ERROR - LAND-USE-PATH MUST BE BLANK
If OPEN PATH NUMBER is blank, this field must be blank.
Transaction Type A3 4-50 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.4 Transaction Type A4 - Site Information - Part 4
The fields described below are validated for INSERT (I) and MODIFY (M) transactions. (Delete (D)
is not a valid action for type A4 transactions.)
For a modify transaction, at least one of the following fields must be non-blank:
UTM data
UTM-ZONE
UTM-EASTING
UTM-NORTHING
LAT/LONG data
LATITUDE
LONGITUDE
METHOD OF DETERMINATION
DATUM
SCALE
ESTIMATE OF ACCURACY
If this condition is not met, the following message is generated:
ERROR - ALL FIELDS BLANK ON MODIFY
When inserting a new site, transactions Al through AS with values for a minimal number of fields must
be present. When modifying locational data for an existing site, transaction A4 with values for a minimal
number of fields must be present. A minimal type A4 transaction has values for the following fields:
UTM data or LAT/LONG data
METHOD OF DETERMINATION
DATUM
SCALE
ESTIMATE OF ACCURACY
If neither LAT/LONG data nor UTM data is present on an INSERT, the following error message is
generated:
ERROR - LAT/LONG AND UTM DATA BLANK
If a type A4 INSERT transaction lacks a value for any of these fields, the following message is generated:
ERROR - REQUIRED "A4H TRANSACTION MISSING
4»
December 1993
4-51
Transaction Type A4
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.4.1 UTMZONE
UTM ZONE identifies the zone of the Universal Transverse Mercator (UTM) System, in which a site
is located.
Attributes: 2 digit numeric
Optional
Coding Instructions:
Coordinates must be provided for a site located in a U.S. state or territory. Coordinates may optionally
be provided for international sites.
A site's coordinates may be given either as latitude/longitude or as UTM coordinates, but not both.
When coordinates are provided, the AIRS Update program will compute a site's coordinates in the system
that was not supplied. If you choose to report a site's coordinates using the latitude/longitude system,
do not code this field.
If you choose to report the site's coordinates using latitude/longitude, you must provide values for
LONGITUDE and LATITUDE. If you choose to use the UTM system, you must provide values for each
of UTM ZONE, UTM EASTING, and UTM NORTHING. When you enter a value for any field of
either group, you must enter values for all the fields of that group, regardless of what action you are
performing (insert, modify, or delete).
To INSERT or MODIFY, place the UTM ZONE in columns 11-12, UTM EASTING in columns 13-20,
UTM NORTHING in columns 21-27, and ensure that columns 28-50 (latitude/longitude fields) are blank.
To DELETE, place asterisks in columns 11-27 (thereby deleting all UTM fields), and ensure that columns
28-50 are blank. Both LAT/LONG and UTM data cannot be blank when the site is located in a U.S.
state or territory.
Error Messages:
ERROR - CANNOT DELETE UTM-ZONE
UTM ZONE cannot be deleted by itself. Delete all UTM fields at the same time by coding
asterisks in columns 11-27.
ERROR - INVALID UTM-ZONE
UTM ZONE must be numeric if present.
Transaction Type A4 4-52 December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - LAT/LONG INVALID WITH UTM DATA
UTM EASTING (as well as all other UTM fields) must be blank if LATITUDE or LONGITUDE
is present. Choose either UTM or latitude/longitude as the values to enter, and delete all values
from the other set. When the site is not located in a U.S. state or territory, both sets of
coordinates can be blank.
ERROR - UTM-ZONE CANNOT BE BLANK
UTM ZONE is required if any other UTM field is valued.
WARNING - CANNOT VERIFY UTM DATA
UTM ZONE is checked in combination with STATE. If STATE is invalid, UTM ZONE cannot
be checked.
December 1993 4-53 Transaction Type A4
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.4.2 UTM EASTING
UTM EASTING describes the easting UTM coordinate in meters (i.e., horizontal distance from the
reference edge of the UTM zone) for the site.
Attributes: 8 digit numeric
Optional
Coding Instructions:
t
Coordinates must be provided for a site located in a U.S. state or territory. Coordinates may optionally
be provided for international sites.
A site's coordinates may be given either as latitude/longitude or as UTM coordinates, but not both.
When coordinates are provided, the AIRS Update program will compute a site's coordinates in the system
that was not supplied. If you choose to report a site's coordinates using the latitude/longitude system,
do not code this field.
If you choose to report the site's coordinates using latitude/longitude, you must provide values for
LONGITUDE and LATITUDE. If you choose to use the UTM system, you must provide values for each
of UTM ZONE, UTM EASTING, and UTM NORTHING. When you enter a value for any field of
either group, you must enter values for all the fields of that group, regardless of what action you are
performing (insert, modify, or delete).
To INSERT or MODIFY, place the UTM ZONE in columns 11-12, UTM EASTING in columns 13-20,
UTM NORTHING in columns 21-27, and ensure that columns 28-50 (latitude/longitude fields) are blank.
To DELETE, place asterisks in columns 11-27 (thereby deleting all UTM fields), and ensure that columns
28-50 are blank. Both LAT/LONG and UTM data cannot be blank when the site is located in a U.S.
state or territory.
Error Messages:
ERROR - CANNOT DELETE UTM-EASTING
UTM EASTING cannot be deleted by itself. Delete all UTM fields at the same time by coding
asterisks in columns 11-27.
ERROR - INVALID UTM-EASTING
UTM EASTING must be numeric if present.
Transaction Type A4 4-54 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
ERROR - LAT/LONG INVALID WITH UTM DATA
UTM EASTING (as well as all other UTM fields) must be blank if LATITUDE or LONGITUDE
is present. Choose either UTM or latitude/longitude as the values to enter, and delete all values
from the other set. When the site is not located in a U.S. state or territory, both sets of
coordinates can be blank.
ERROR - UTM-EASTING CANNOT BE BLANK
UTM EASTING is required if any other UTM field is valued.
ERROR - UTM-EASTING OUTSIDE OF STATE
UTM EASTING must fall within the maximum and minimum values for the STATE.
WARNING - CANNOT VERIFY UTM DATA
UTM EASTING is checked in combination with STATE. If STATE is invalid, UTM EASTING
cannot be checked.
December 1993
4-55
Transaction Type A4
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.4.3 UTM NORTHING
UTM NORTHING describes the northing UTM coordinate in meters (i.e., for the Northern Hemisphere,
the vertical distance from the equator; for the Southern Hemisphere, 10,000,000 minus the vertical
distance from the equator) for the site.
Attributes: 7 digit numeric
Optional
Coding Instructions:
Coordinates must be provided for a site located in a U.S. state or territory. Coordinates may optionally
be provided for international sites.
A site's coordinates may be given either as latitude/longitude or as UTM coordinates, but not both.
When you enter a value for any field of either group, the AIRS Update program will compute a site's
coordinates in the system that was not supplied. If you choose to report a site's coordinates using the
latitude/longitude system, do not code this field.
If you choose to report the site's coordinates using latitude/longitude, you must provide values for
LONGITUDE and LATITUDE. If you choose to use the UTM system, you must provide values for each
of UTM ZONE, UTM EASTING, and UTM NORTHING. When you enter a value for any field of
either group, you must enter values for all the fields of that group, regardless of what action you are
performing (insert, modify, or delete).
To INSERT or MODIFY, place the UTM ZONE in columns 11-12, UTM EASTING in columns 13-20,
UTM NORTHING in columns 21-27, and ensure that columns 28-50 (latitude/longitude fields) are blank.
To DELETE, place asterisks in columns 11-27 (thereby deleting all UTM fields), and ensure that columns
28-50 are blank. Both LAT/LONG and UTM data cannot be blank when the site is located in a U.S.
state or territory.
Error Messages:
ERROR - CANNOT DELETE UTM-NORTHING
UTM EASTING cannot be deleted by itself. Delete ail UTM fields at the same time by coding
asterisks in columns 11-27.
ERROR - INVALID UTM-NORTHING
UTM NORTHING must be numeric if present.
Transaction Type A4 4-56 December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - LAT/LONG INVALID WITH UTM DATA
UTM NORTHING (as well as all other UTM fields) must be blank if LATITUDE or
LONGITUDE is present. Choose either UTM or latitude/longitude as the values to enter, and
delete all values from the other set. When the site is not located in a U.S. state or territory, both
sets of coordinates can be blank.
ERROR - UTM-NORTHING CANNOT BE BLANK
UTM NORTHING is required if any other UTM field is valued.
ERROR - UTM-NORTHING OUTSIDE OF STATE
UTM NORTHING must fall within the maximum and minimum values for the STATE.
WARNING - CANNOT VERIFY UTM DATA
UTM NORTHING is checked in combination with STATE. If STATE is invalid, UTM
NORTHING cannot be checked.
December 1993 4-57 Transaction Type A4
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.4.4 LATITUDE (signed)
LATITUDE is the monitoring site's angular distance north or south of the equator measured in degrees
(00-90), minutes (00-60) and seconds (00.0000-60.0000). The associated sign (+/-) specifies the
direction of measurement, either north (+) or south (-).
Attributes: 11 characters (10 numeric)
Optional
Coding Instructions:
Coordinates must be provided for a site located in a U.S. state or territory. Coordinates may optionally
be provided for international sites.
A site's coordinates may be given either as latitude/longitude or as UTM coordinates, but not both.
When coordinates are provided, the AIRS Update program will compute a site's coordinates in the system
that was not supplied. If you choose to report a site's coordinates using the latitude/longitude system,
do not code the UTM fields.
If you choose to report the site's coordinates using latitude/longitude, you must provide values for
LONGITUDE and LATITUDE. If you choose to use the UTM system, you must provide values for each
of UTM ZONE, UTM EASTING, and UTM NORTHING. When you enter a value for any field of
either group, you must enter values for all the fields of that group, regardless of what action you are
performing (insert, modify, or delete).
To INSERT or MODIFY, enter the LATITUDE for the site in sign/degree/minute/second/decimal (+/-
DDMMSSTTTT) format in columns 28-38. You must have a sign (+/-) as the first character. The
decimal portion (rrri) may be blank or numeric greater than zero with the decimal point assumed. You
must also code a value for LONGITUDE (columns 39-50) and ensure that all UTM fields (columns 11-
27) are blank.
To DELETE, place asterisks in columns 28-50 (thereby deleting all latitude/longitude fields), and ensure
that columns 11-27 are blank. Both LAT/LONG and UTM data cannot be blank when the site is located
in a U.S. state or territory.
Error Messages:
ERROR - CANNOT DELETE LATITUDE
LATITUDE cannot be deleted by itself. Delete all latitude/longitude fields at the same time by
coding asterisks in columns 28-38.
Transaction Type A4 4-58 December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - INVALID LATITUDE
LATITUDE must be numeric if present. The DEG (degrees) subfield may have a leading blank,
but the MIN (minutes) and SEC (seconds) subfields each must be coded as two digits. The
decimal portion must be blank or numeric greater than zero. You must enter a sign (+ or -) as
the first character.
ERROR • LAT/LONG INVALID WITH UTM DATA
If UTM ZONE, UTM EASTING, or UTM NORTHING is present, LATITUDE and
LONGITUDE must be blank. Choose either UTM or latitude/longitude as the values to enter,
and delete all values from the other set. When the site is not located in a U.S. state or territory,
both sets of coordinates can be blank.
ERROR - LATITUDE CANNOT BE BLANK
LATITUDE is required if LONGITUDE is valued.
ERROR - LATITUDE OUTSIDE OF COUNTY
LATITUDE must fall within the maximum and minimum values for the COUNTY.
ERROR - LATITUDE OUTSIDE OF STATE
If there are not maximum and minimum LATITUDE values associated with the COUNTY,
LATITUDE must fall within the maximum and minimum values for the STATE.
WARNING - CANNOT VERIFY LAT/LONG
LATITUDE is checked in combination with STATE. If STATE is invalid, LATITUDE cannot
be checked.
December 1993 4-59 Transaction Type A4
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.4.5 LONGITUDE (signed)
LONGITUDE is the monitoring site's angular distance east or west of the prime meridian at Greenwich,
England, measured in degrees (000-180), minutes (00-60) and seconds (00.0000-60.0000). The
associated sign (+/-) specifies the direction of measurement, either east (+) or west (-).
Attributes: 12 characters (11 numeric)
Optional
Coding Instructions:
Coordinates must be provided for a site located in a U.S. state or territory. Coordinates may optionally
be provided for international sites.
A site's coordinates may be given either as latitude/longitude or as UTM coordinates, but not both.
When coordinates are provided, the AIRS Update program will compute a site's coordinates in the system
that was not supplied. If you choose to report a site's coordinates using the latitude/longitude system,
do not code the UTM fields.
If you choose to report the site's coordinates using latitude/longitude, you must provide values for
LONGITUDE and LATITUDE. If you choose to use the UTM system, you must provide values for each
of UTM ZONE, UTM EASTING, and UTM NORTHING. When you enter a value for any field of
either group, you must enter values for all the fields of that group, regardless of what action you are
performing (insert, modify, or delete).
To INSERT or MODIFY, enter the LONGITUDE for the site in sign/degree/minute/second/decimal (+/-
DDDMMSSTTTT) format in columns 39-50. You must have a sign (+/-) as the first character. The
decimal portion (mi) may be blank or numeric greater than zero with the decimal point assumed. You
must also code a value for LATITUDE (columns 28-38) and ensure that alt UTM fields (columns 11-27)
are blank.
To DELETE, place asterisks in columns 28-50 (thereby deleting all latitude/longitude fields), and ensure
that columns 11-27 are blank. Both LAT/LONG and UTM data cannot be blank when the site is located
in a U.S. state or territory.
Error Messages:
ERROR - CANNOT DELETE LONGITUDE
LONGITUDE cannot be deleted by itself. Delete all latitude/longitude fields at the same time
by coding asterisks in columns 28-50.
Transaction Type A4 4-60 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
ERROR - INVALID LONGITUDE
LONGITUDE must be numeric if present. The DEG (degrees) subfield may have a leading
blank, but the MIN (minutes) and SEC (seconds) subfields each must be coded as two digits.
The decimal portion of the seconds field must be blank or numeric greater than zero. You must
enter a sign (+ or -) as the first character.
ERROR - LAT/LONG INVALID WITH UTM DATA
If UTM ZONE,'UTM EASTING, or UTM NORTHING is present, LATITUDE and
LONGITUDE must be blank. Choose either UTM or latitude/longitude as the values to enter,
and delete all values from the other set. When the site is not located in a U.S. state or territory,
both sets of coordinates can be blank.
ERROR - LONGITUDE CANNOT BE BLANK
LONGITUDE is required if LATITUDE is valued.
ERROR - LONGITUDE OUTSIDE OF COUNTY
LONGITUDE must fall within the maximum and minimum values for the COUNTY.
ERROR - LONGITUDE OUTSIDE OF STATE
If there are not maximum and minimum LONGITUDE values associated with the COUNTY,
LONGITUDE must fall within the maximum and minimum values for the STATE.
WARNING - CANNOT VERIFY LAT/LONG
LONGITUDE is checked in combination with STATE. If STATE is invalid, LATITUDE cannot
be checked.
December 1993
4-61
Transaction Type A4
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.4.6 METHOD OF DETERMINATION
METHOD OF DETERMINATION identifies the method used to determine the values for LAT/LONG
fields or UTM fields.
Attributes: 10 character code
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid METHOD OF DETERMINATION code in columns 51-60. A
code is valid if it is a valid LOCATION code in the GEO-COMMON File. Valid codes are listed in
Volume GC2 of the AIRS User's Guide.
Error Messages:
ERROR - CANNOT DELETE METH-OF-DETERM
METHOD OF DETERMINATION is a required field and cannot be deleted. Remove the
asterisks from this field of the MODIFY transaction.
ERROR - INVALID METHOD-OF-DETERM
METHOD OF DETERMINATION code must exist in the GEO-COMMON File.
ERROR - METHOD-OF-DETERM CANNOT BE BLANK
This is a required field for an INSERT transaction.
Transaction Type A4 4-62 December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
4.4.7 DATUM
DATUM identifies a network of monuments and reference points defining a mathematical surface from
which geographic computations can be made. Grid coordinates to determine LAT/LONG should
reference the spatial coordinate information available as the North American Datum of 1983 (NAD83),
although the majority of EPA's data and most base maps for the United States are in NAD27.
Attributes: 2 digit numeric
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid DATUM code in columns 61-62. A code is valid if it is a valid
DATUM code in the GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's
Guide.
Error Messages:
ERROR - CANNOT DELETE DATUM
DATUM is a required field and cannot be deleted. Remove the asterisks from this field of the
MODIFY transaction.
ERROR - DATUM CANNOT BE BLANK
This is a required field for an INSERT transaction.
ERROR - INVALID DATUM
DATUM code must exist in the GEO-COMMON File.
December 1993 4-63 Transaction Type A4
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
4.4.8 SCALE
SCALE identifies the ratio of the map or cartographic product to the true location. The data element for
SCALE should be the "X" value of the 1:X ratio (e.g., if the scale is 1:24,000, the value of die scale data
element should be "24,000"). The United States Geological Survey 1:24,000 is usually the smallest
reasonable scale for locating sub-facility points, such as stacks or pipes. The relative accuracies of maps
as a locational tool decreases as the "X" value increases.
Attributes: 6 characters
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid SCALE code in columns 63-68. A code is valid if it is a valid
LOCATION code in the GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS
User's Guide.
Error Messages:
ERROR - CANNOT DELETE SCALE
SCALE is a required field and cannot be deleted. Remove the asterisks from this field of the
MODIFY transaction.
ERROR - INVALID SCALE
SCALE code must exist in the GEO-COMMON File.
ERROR - SCALE CANNOT BE BLANK
This is a required field for an INSERT transaction.
Transaction Type A4 4-44 December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
4.4.9 ESTIMATE OF ACCURACY
ESTIMATE OF ACCURACY indicates how close to the actual LAT/LONG values the determinations
are.
Attributes: 10 characters
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid ESTIMATE OF ACCURACY code in columns 69-78. The
format is O.OOOOOXXX, where XXX is "DEC", "MIN", or "SEC". The numeric portion must be greater
than zero. A decimal point must be placed in the second position.
Error Messages:
ERROR - CANNOT DELETE EST-OF-ACCURACY
ESTIMATE OF ACCURACY is a required field and cannot be deleted. Remove the asterisks
from this field of the MODIFY transaction.
ERROR - EST-OF-ACCURACY CANNOT BE BLANK
This is a required field for an INSERT transaction.
ERROR - INVALID EST-OF-ACCURACY
EST OF ACCURACY must be in the format O.OOOOOXXX. The numeric portion must be > 0
and XXX must be "DEG", "MIN", or "SEC". A decimal point must be placed in the second
position.
December 1993 4-65 Transaction Type A4
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
4.5 Transaction A5 - Location Description
This transaction has just one field, and i' is validated for INSERT (I) and MODIFY (M) transactions.
It is always required on INSERT. If A4 is present, it is required on MODIFY. (DELETE (D) is not a
valid action for type A5 transactions.)
4.5.1 LOCATION DESCRIPTION
LOCATION DESCRIPTION is a free-format field that may be used in any way you desire. It is
normally used to describe the location that the coordinates represent, e.g., the NE corner of the roof on
Building 5, or the NE street corner at the intersection of First and Main.
Attributes:
68 characters
Required
Coding Instructions:
To INSERT or MODIFY, place the appropriate text in columns 11-78.
To DELETE an existing LOCATION DESCRIPTION, fill columns 11-78 with asterisks on a MODIFY
transaction. (Be sure you fill all columns, or else the asterisks will be stored in the Site File as the
LOCATION DESCRIPTION.
Error Messages:
ERROR - ALL FIELDS BLANK ON MODIFY
For a MODIFY transaction, LOCATION DESCRIPTION is a required field (since it is the only
field), and cannot be blank.
ERROR - LOC CANNOT BE BLANK
For an INSERT transaction, LOCATION DESCRIPTION is a required field and cannot be blank.
Transaction Type A5
4-66
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
4.6 Transaction Type A6 - Site Comments (Line 1)
This transaction has just one field, and it is validated for INSERT (I) and MODIFY (M) transactions.
(Delete (D) is not a valid action for type A6 transactions. If there are not SITE COMMENTS, do not
submit this transaction.
4.6.1 SITE COMMENTS
SITE COMMENTS is a free-format field that may be used in any way you desire. It is normally used
to describe special features of a site.
Attributes:
Coding Instructions:
68 characters
Optional
To INSERT or MODIFY, place the appropriate text in columns 11-78. For a MODIFY transaction, any
alteration to the current SITE COMMENTS will completely replace that comment. Therefore, any
change will require that the entire field be re-entered. SITE COMMENTS (Line 1) is entered in the
database as a field separate from SITE COMMENTS (Line 2). The Line 2 comment may be used as a
continuation of Line 1, if additional comment space is needed.
To DELETE existing SITE COMMENTS, fill columns 11-78 with asterisks on a MODIFY transaction.
(Be sure you fill all columns, or else the asterisks will be stored in the Site File as SITE COMMENTS.
If there are no SITE COMMENTS for a new site, do not submit this transaction.
Error Messages:
ERROR - ALL FIELDS BLANK ON MODIFY
For a MODIFY transaction, SITE COMMENTS is a required field (since it is the only field),
and cannot be blank.
ERROR - SITE COMMENTS CANNOT BE BLANK
4
For an INSERT transaction, SITE COMMENTS is a required field and cannot be blank.
December 1993
4-67
Transaction Type A6
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
4.7 Transaction Type A7 - Site Comments (Line 2)
This transaction has just one field, and it is validated for INSERT (I) and MODIFY (M) transactions.
(Delete (D) is not a valid action for type A7 transactions. If there are not SITE COMMENTS, do not
submit this transaction.
4.7.1 SITE COMMENTS
SITE COMMENTS is a free-format field that may be used in any way you desire. It is normally used
to describe special features of a site.
Attributes:
Coding Instructions:
68 characters
Optional
To INSERT or MODIFY, place the appropriate text in columns 11-78. For a MODIFY transaction, any
alteration to the current SITE COMMENTS will completely replace that comment. Therefore, any change
will require that the entire field be re-entered. SITE COMMENTS (Line 2) is entered in the database
as a field separate from SITE COMMENTS (Line 1). It may be used as a continuation of the comment
begun in Line 1.
To DELETE existing SITE COMMENTS, fill columns 11-78 with asterisks on a MODIFY transaction.
(Be sure you fill all columns, or else the asterisks will be stored in the Site File as SITE COMMENTS.
If there are no SITE COMMENTS for a new site, do not submit this transaction.
Error Messages:
ERROR - ALL FIELDS BANK ON MODIFY
For a MODIFY transaction, SITE COMMENTS is a required field (since it is the only field),
and cannot be blank.
ERROR - SITE COMMENTS CANNOT BE BLANK
For an INSERT transaction, SITE COMMENTS is a required field and cannot be blank.
Transaction Type A7
4-68
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.0 Monitor Transactions (Fl through F5)
This set of five transactions is used to update monitor information in the Site File. Type Fl contains the
following fields:
MONITOR TYPE
DATE TYPE EFF
ANALYZ LAB
COLLECT LAB
REPORT ORG
RO EFFECTIVE DATE
DATE SAMPLING BEGAN
DATE SAMPLING ENDED
AUDIT DATE
PROJECT CLASS
ACTION TYPE
ACTION TYPE REASON
DOMINANT SOURCE
MEASUREMENT SCALE
MONITOR TYPE OBJECTIVE
NONATTA1NMENT AREA
URBAN AREA REPRESENTED
PAMS REQ SAMPLING FREQ
MONITOR OPEN PATH NUMBER
Type F2 contains the following fields:
MONITOR STREET NUMBER 1
DISTANCE FROM ROAD 1
MONITOR STREET NUMBER 2
DISTANCE FROM ROAD 2
MONITOR STREET NUMBER 3
DISTANCE FROM ROAD 3
REF METHOD USED
REF METHOD USED DATE
SITE CRITERIA MET
DATE SITE CRITERIA MET
QA PLAN
QA EFFECTIVE DATE
PROBE LOCATION CODE
PROBE HEIGHT
December 1993 5-1 Monitor Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
HORIZONTAL DISTANCE (FROM SUPPORT)
VERTICAL DISTANCE (FROM SUPPORT)
UNRESTRICTED AIR FLOW
OBSTRUCTION #1
TYPE OBSTRUCTION
DIRECTION FROM MONITOR
DISTANCE FROM INLET (IN METERS)
HEIGHT OF OBSTRUCTION (ABOVE PROBE)
OBSTRUCTION #2
TYPE OBSTRUCTION
DIRECTION FROM MONITOR
DISTANCE FROM INLET (IN METERS)
HEIGHT OF OBSTRUCTION (ABOVE PROBE)
OBSTRUCTION #3
TYPE OBSTRUCTION
DIRECTION FROM MONITOR
DISTANCE FROM INLET (IN METERS)
HEIGHT OF OBSTRUCTION (ABOVE PROBE)
Type F3 contains the following fields:
MONITORING AREA
WORST SITE
SURROGATE FLAG
NUM SCH SAMPLE MO
REQ SAMPLING FREQ
RSF EFFECTIVE DATE
SHORT TERM SCH SAT
SHORT TERM COMP DATE
FIRST EXCEED CORRECTION
Type F4 contains the following field:
MONITOR COMMENTS (LINE 1)
Type F5 contains the following field:
MONITOR COMMENTS (LINE 2)
Figure 5-1 shows the coding form for transaction types Fl through F5.
INSERT transactions are used to create a monitor that does not exist in the Site File. A type Fl
transaction is required to INSERT a monitor; the other four are optional. A type F3 transaction is
required to insert TSP or PM10 monitors for U.S. states or territories. A monitor is always associated
with a site. To INSERT a new monitor, either its parent site must already exist on the database, or the
parent site must be created at the same time with Site transactions in the same screening file.
Monitor Transactions
5-2
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
DELETE transactions are used to remove a monitor from the Site File. The DELETE action code is
allowed only for type Fl transactions.
MODIFY transactions are used to change information in the Site File for existing monitors. The values
coded on a MODIFY transaction replace the values of the corresponding fields in the monitor record of
the Site File. If no value existed previously, the value from the transaction is inserted into the monitor
record. Values may also be deleted from a monitor record of the Site File by coding asterisks (*) in
every position of the corresponding fields of a monitor transaction. Some fields are required, and cannot
be deleted. They are identified in the coding instructions that follow.
The following error messages pertain to the monitor transactions:
ERROR - ATTEMPT TO ADD MONITOR FOR NON-EXISTENT SITE
The site for which a monitor is being added is not in the Site File and does not have valid records
in the Screening File.
ERROR - ATTEMPT TO DELETE LAST MONITOR WITHOUT DELETING THE SITE
This is an attempt to delete the last monitor for a site without deleting the site. Either eliminate
this transaction, or include a type Al DELETE transaction to remove the site also.
ERROR - ATTEMPT TO DELETE MONITOR WITHOUT DELETING ALL RAW DATA
Raw data exists in the database for this monitor. The monitor cannot be deleted until all of its
data has been deleted.
ERROR - ATTEMPT TO DELETE MONITOR WITHOUT DELETING ALL SLAMS DATA
SLAMS data exists in the database for this monitor. The monitor cannot be deleted until all of
its data has been deleted.
ERROR - CANNOT ADD A SITE WITHOUT A VALID MONITOR
Valid Al through A4 and Fl transactions for the same site must be present in the Screening File
in order to insert a new site (and monitor) into the Site File. This really means that no valid Fl
transaction was found.
ERROR - CANNOT ADD DATA FOR MONITOR BEING DELETED
There is an Fl DELETE transaction for the same monitor-id as the current INSERT.
ERROR - CANNOT ADD PM DATA WITHOUT VALID MONITOR
An F3 INSERT transaction exists, and there is not a related Fl transaction.
December 1993 5-3 Monitor Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR - CANNOT MODIFY DATA BEFORE IT IS INSERTED
When a new monitor is being INSERTed, MODIFY transactions are permitted only following
an INSERT.
ERROR - CANNOT MODIFY DATA FOR MONITOR BEING DELETED
There is an Fl DELETE transaction for the same monitor-ID as the current MODIFY.
ERROR - DUPLICATE RECORDS
There are two or more transactions in the screening file with the same monitor-ID, transaction
type, and action code.
ERROR - MISSING REQUIRED MONITOR INFORMATION
The set of transactions for inserting a new monitor is incomplete because a type Fl transaction
is either absent or invalid. A valid Fl transaction is required in order to INSERT a new monitor.
ERROR - MONITOR INVALID DUE TO DUPLICATE "F3"
An Fl transaction for PARAMETER '11101' OR '81101' does not pass the required edits
because there are duplicate F3 transactions.
ERROR - NOT AUTHORIZED FOR THIS MONITOR
Each monitor-ID is associated with a group of screening files (those whose names are the same
except in the last two positions). The association, or "ownership", is established when the
monitor is inserted into the Site File or when an unassociated monitor is changed by Site or
Monitor transactions (Al through F5). Once the association is established, all transactions
involving the monitor must be in a screening file of the group that "owns" the monitor. This
error message means the screening file group does not have ownership of the monitor. Either
the wrong monitor-ID was coded, or a different screening file must be used for the transaction
in question.
ERROR - REQUIRED "F3" TRANSACTION INVALID
An Fl INSERT transaction for PARAMETER '11101' or '81102* does not pass the required
edits because of errors on the F3 transaction.
ERROR - REQUIRED "F3" TRANSACTION MISSING
An F3 transaction is required when there is an Fl transaction for U.S. states or territories and
the PARAMETER is '11101' or '81102'.
Monitor Transactions 5-4 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
£
a
tf
I
£
o
u
c
Q
E
O
1
IE
1*
I
iMIlhi
liiill
Figure 5-1. Coding Form for Transaction Types FI - F5
December 1993
5-5
Monitor Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.1 Common Fields
The fields common to transaction types Fl through F5 are PARAMETER, POC, and, in combination,
MONITOR ID.
5.1.1 PARAMETER
PARAMETER is a code assigned to the parameter measured by a monitor. Parameters may be pollutants
(e.g., sulfur dioxide in the atmosphere) or non-pollutants (e.g., wind speed).
Attributes:
Coding Instructions:
5 digit code
Required
Place a valid parameter code in columns 11-15. For transaction type F3, only parameter codes 11101
(TSP) and 81102 (PM-10) are valid. Otherwise, a code is valid if it exists in the AIRS GEO-COMMON
File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
Error Message:
ERROR - INVALID PARAMETER CODE
PARAMETER must be in the GEO-COMMON File.
Monitor Transactions
5-6
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.1.2 POC (Parameter Occurrence Code)
POC is a code used to distinguish between different monitors at one site that are measuring the parameter.
For example, the first monitor established to measure CO at a site would have POC = T. If an
additional monitor were established at the same site to measure CO, that monitor would have POC = '2'.
However, if a new instrument were installed to replace the original instrument used as the first monitor,
that would be the same monitor and it would have POC = T. For criteria pollutants, data from
different sampling methods should only be stored under the same POC if the sampling intervals are the
same and the methods are reference or equivalent. For sites where duplicate sampling is being conducted
by multiple agencies or one agency with multiple samplers, multiple POC's must be utilized to store all
samples. For non-criteria pollutants, data from multiple sampling methods can be stored under the same
POC if the sampling intervals are the same.
Attributes: 1 digit code
Required
Coding Instructions:
In column 16, enter a valid POC in the range 1 through 9.
Error Message:
ERROR - INVALID POC CODE
POC is a required field. It must be numeric in the range 1-9.
December 1993 5-7 Monitor Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.1.3 MONITOR-ID (Monitor Identification Code)
The MONITOR ID identifies the monitor to which a transaction applies. It is comprised of the STATE,
COUNTY, SITE, PARAMETER, and POC fields.
Attributes:
Coding Instructions:
IS digit code
Required
Place a valid MONITOR ID in columns 2-16. For MODIFY and DELETE transactions, a monitor-ID
is valid if it exists in the AQ Site File. For INSERT transactions, a monitor-ID is valid if it does not
exist in the Site File. You can obtain a list of monitor-IDs with several standard reports of the Air
Quality Retrieval Subsystem, described in Volume AQ4 of the AIRS User's Guide. When coding a new
monitor-ID for an INSERT transaction, ensure that columns 2-3 contain a valid STATE, 4-6 a valid
COUNTY, 7-10 a valid SITE, 11-15 a valid PARAMETER, and 16 a valid POC.
Error Messages:
ERROR • ATTEMPT TO ADD MONITOR DATA FOR AN EXISTING MONITOR
An INSERT transaction may not be used when the monitor already exists in the data base. If
fields are to be added to an existing monitor, use a MODIFY transaction.
ERROR - ATTEMPT TO CHANGE MONITOR DATA THAT DOES NOT EXIST
The MONITOR ID on a MODIFY transaction is not in the Site File. A monitor that does not
exist cannot be changed.
ERROR - ATTEMPT TO DELETE MONITOR DATA THAT DOES NOT EXIST
The MONITOR ID on a DELETE transaction is not in the Site File. A monitor that does not
exist cannot be changed.
Monitor Transactions
5-8
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.2 Transaction Type Fl - Monitor Data - Part 1
The fields described below are validated for INSERT (I) and MODIFY (M) transactions; no validation
is performed for DELETE (D) transactions.
For a MODIFY transaction, at least one of the following fields must be non-blank:
MONITOR TYPE
DATE TYPE EFF
ANALYZ LAB
COLLECT LAB
REPORT ORG
RO EFFECTIVE DATE
DATE SAMPLING BEGAN
DATE SAMPLING ENDED
AUDIT DATE
PROJECT CLASS
ACTION TYPE
ACTION TYPE REASON
DOMINANT SOURCE
MEASUREMENT SCALE
MONITOR TYPE OBJECTIVE
NONATTAINMENT AREA
URBAN AREA REPRESENTED
PAMS REQ SAMPLING FREQ
MONITOR OPEN PATH NUMBER
If this condition is not met, the following message is generated:
ERROR - ALL FIELDS BLANK ON MODIFY
To insert a new monitor, an Fl transaction with valid values for the following fields is required:
MONITOR TYPE
DATE TYPE EFF
ANALYZ LAB
COLLECT LAB
REPORT ORG
REPORT ORG EFFECTIVE DATE
DATE SAMPLING BEGAN
URBAN AREA REPRESENTED
If any of these fields is missing or invalid, the following message is generated:
ERROR - MISSING REQUIRED MONITOR INFORMATION
December 1993 5-9 Transaction Type Fl
-------
Air Quality Data Coding
ABRS User's Guide
Volume AQ2
5.2.1 MONITOR TYPE
MONITOR TYPE identifies the administrative classification of the monitor.
Attributes:
1 character code
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid code in column 17. A code is valid if it exists in the GEO-
COMMON File (except as noted below). Valid codes are listed in Volume GC2 of the AIRS User's
Guide.
Codes T (NAMS) and '6', '7', and '8' (PAMS) are valid codes only for the AIRS database
administrator, who has the sole authority to change monitor type to or from NAMS or PAMS. You may
not use code T, '6', '7', or '8' on an INSERT or a MODIFY transaction, and you may not change a
code T, '6', '7', or '8' in an existing monitor record of the Site File to any other value. To create a
new NAMS or PAMS monitor, you must INSERT it using a non-NAMS MON TYPE or non-PAMS
MON TYPE, then have the AIRS database administrator change the monitor type to NAMS or PAMS.
You must enter MONITOR TYPE when you enter a value for DATE TYPE EFF.
Error Messages:
ERROR - CANNOT CHANGE MONITOR-TYPE FROM A '9'
MONITOR TYPE may not be changed from '9' (secured) to any other monitor type. A new
monitor-ID must be assigned in order to use the same equipment as a non-secured monitor.
ERROR - CANNOT CHANGE MONITOR-TYPE TO A '9'
MONITOR TYPE may not be changed to '9' (secured) from any other monitor type. A new
monitor-ID must be assigned in order to use the same equipment as a secured monitor.
Transaction Type Fl
5-10
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - CANNOT CHANGE TO NAMS UNTIL ALL REQUIRED FIELDS ARE GIVEN
VALUES
If monitor type = T (NAMS) on a MODIFY, the following fields must be valued in the Site
File:
MEASUREMENT SCALE STREET NAME (1) '
DATE SITE CRITERIA MET YR OF TRAFFIC FLOW (1)'
DATE SAMPLING BEGAN PROBE LOCATION CODE
MONITOR* TYPE OBJECTIVE UNRESTRICTED AIR FLOW
ACTION TYPE HORIZONTAL DISTANCE
DISTANCE FROM ROAD (1)' VERTICAL DISTANCE
ERROR - CANNOT CHANGE TO PAMS UNTIL ALL REQUIRED FIELDS ARE GIVEN
VALUES
If monitor type = '6', '7', or '8' (PAMS) on a MODIFY, the following fields must be valued
in the Site File:
MEASUREMENT SCALE MSA REPRESENTED (1) *
DATE SITE CRITERIA MET CMS A REPRESENTED (1) *
DATE SAMPLING BEGAN STREET NAME (1) *
MONITOR TYPE OBJECTIVE YR OF TRAFFIC FLOW (1) "
ACTION TYPE PROBE LOCATION CODE
DISTANCE FROM ROAD (1) ' HORIZONTAL DISTANCE
SITE LOCATION TYPE (1) " VERTICAL DISTANCE
If monitor type = '6', '7', or '8' and if the parameter value is '43xxx' or '45xxx', the following
additional field must be valued:
PAMS REQ SAMPLING FREQ
* at least one occurrence
December 1993 5-11 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - CANNOT DELETE MONITOR-TYPE
MONITOR TYPE is a required field and cannot be deleted. Remove the asterisk from this field
of the MODIFY transaction.
ERROR - INVALID MONITOR-TYPE
For an INSERT transaction, MONITOR TYPE may not be blank or ' 1'. It must be in the GEO-
COMMON File. To create a new NAMS monitor with an INSERT transaction, code a
MONITOR TYPE other than T (NAMS), then have the AIRS database administrator change it
to NAMS after the monitor has been inserted into the Site File and approved as a NAMS
monitor.
ERROR - ONLY ADBA CAN CHANGE STATUS OF A MONITOR FROM NAMS
ERROR - ONLY ADBA CAN CHANGE STATUS OF A MONITOR TO NAMS
Only the AIRS database administrator (ADBA) can change monitor type to or from T (NAMS).
Contact the ADBA about this change and erase the code from the MONITOR TYPE field. If
MONITOR TYPE is the only field coded on the transaction (other than the common fields),
delete the transaction.
ERROR - ONLY ADBA CAN CHANGE STATUS OF A MONITOR FROM PAMS
ERROR - ONLY ADBA CAN CHANGE STATUS OF A MONITOR TO PAMS
Only the AIRS database administrator (ADBA) can change monitor type to or from '6', '7', or
'8'(PAMS). Contact the ADBA about this change and erase the code from the MONITOR TYPE
field. If MONITOR TYPE is the only field coded on the transaction (other than the common
fields), delete the transaction.
Transaction Type Fl
5-12
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.2.2 DATE TYPE EFF
DATE TYPE EFF is the date that the most recent monitor type became effective.
Attributes: 6 digit date
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid date in YYMMDD format in columns 18-23. A date is valid for
this field if it is:
1) on or after 1 January 1980, if MONITOR TYPE is ' 1' (NAMS) or *2' (SLAMS); on or
after 1 January 1957 otherwise
2) on or after DATE SAMPLING BEGAN, for a MODIFY, and on DATE SAMPLING
BEGAN, for an INSERT
3) on or before DATE SAMPLING ENDED
4) no later than a year after the date the edit is performed
You must enter DATE TYPE EFF when you enter a value for MONITOR TYPE.
Error Messages:
ERROR - CANNOT DELETE DATE-TYPE-EFF
DATE TYPE EFF is a required field and cannot be deleted. Remove the asterisks from this field
of the MODIFY transaction.
ERROR - CANNOT MOVE DATE-TYPE-EFF FORWARD UNLESS MONITOR-TYPE CHANGES
For a MODIFY transaction, DATE TYPE EFF cannot be moved forward in time without
changing the monitor type.
ERROR - DATA FOR THIS YEAR IS ARCHIVED
For a MODIFY transaction, raw data cannot be archived for the year indicated in DATE TYPE
EFF or for any year(s) following.
ERROR - DATE-TYPE-EFF CANNOT BE BLANK
If MONITOR TYPE has a value, DATE TYPE EFF cannot be blank.
December 1993 5-13 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - DATE-TYPE-EFF NOT = SAMP-BEGIN
For an INSERT transaction, DATE TYPE EFF must be equal to DATE SAMPLING BEGAN.
ERROR - INVALID DATE-TYPE-EFFECTIVE
For an INSERT transaction, DATE TYPE EFF cannot be blank. The date specified on an
INSERT or MODIFY transaction must meet the criteria given above in coding instructions and
must be a valid Gregorian date.
ERROR - ONLY ADBA CAN CHANGE DATE-TYPE-EFFECTIVE OF NAMS MONITOR
Only the AIRS database administrator (ADBA) can change the DATE TYPE EFF field on a
NAMS monitor if the date is earlier than the date in the database or the most recent date in the
Monitor History record for a NAMS monitor.
ERROR - ONLY ADBA CAN CHANGE DATE-TYPE-EFFECTIVE OF PAMS MONITOR
Only the AIRS database administrator (ADBA) can change the DATE TYPE EFF field on a
PAMS monitor if the date is earlier than the date in the database or the most recent date in the
Monitor History record for a PAMS monitor.
ERROR - SLAMS DATA EXISTS FOR OR AFTER DATE-TYPE-EFFECTIVE
On a MODIFY transaction, the MONITOR TYPE cannot be changed to a non-NAMS
or non-SLAMS value if SLAMS data exists for the year indicated in DATE TYPE EFF
or for later years.
Transaction Type Fl
5-14
December 1993
-------
o
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.2.3 ANALYZLAB
ANALYZ LAB identifies the laboratory responsible for the analysis of air quality measurement samples.
Attributes: 3 digit code
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 24-26. A code is valid if it exists in the AIRS
GEO-COMMON File in combination with STATE. Valid codes are listed in Volume GC2 of the AIRS
User's Guide.
Error Messages:
ERROR - CANNOT DELETE ANALYZE-LAB
ANALYZ LAB is a required field and cannot be deleted. Remove the asterisks from this field
of the MODIFY transaction.
ERROR - INVALID ANALYZE-LAB
For an INSERT transaction, ANALYZ LAB cannot be blank. The combination of STATE and
ANALYZ LAB must exist in the GEO-COMMON File.
WARNING - CANNOT VERIFY ANALYZE-LAB
ANALYZ LAB is checked in combination with STATE. If STATE is invalid, ANALYZ LAB
cannot be checked.
December 1993 5-15 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.2.4 COLLECT LAB (Collection Lab)
COLLECT LAB identifies the laboratory responsible for the collection of air quality measurement
samples.
Attributes:
3 digit code
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 27-29. A code is valid if it exists in the GEO-
COMMON File in combination with STATE. Valid codes are listed in Volume GC2 of the AIRS User's
Guide.
Error Messages:
ERROR - CANNOT DELETE COLLECT-LAB
COLLECT LAB is a required field and cannot be deleted. Remove the asterisks from this field
of the MODIFY transaction.
ERROR - INVALID COLLECT-LAB
For an INSERT transaction, COLLECT LAB cannot be blank. The combination of STATE and
COLLECT LAB must exist in the GEO-COMMON File.
WARNING - CANNOT VERIFY COLLECT-LAB
COLLECT LAB must be checked in combination with STATE. If STATE is invalid, COLLECT
LAB cannot be checked.
Transaction Type Fl
5-16
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.2.5 REPORT ORG
REPORT ORG identifies the agency reporting Precision and Accuracy data for a specific site. If there
is no Precision and Accuracy data, then the REPORT ORG identifies the agency reporting air quality
data.
Attributes: 3 digit code
Required for INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 30-32. A code is valid if it exists in the GEO-
COMMON File in combination with STATE. Valid codes are listed in Volume GC2 of the AIRS User's
Guide.
Error Messages:
ERROR - CANNOT DELETE REPORT-ORG
REPORT ORG is a required field and cannot be deleted. Remove the asterisks from this field
of the MODIFY transaction.
ERROR - INVALID REPORT-ORG
For an INSERT transaction, REPORT ORG cannot be blank if MONITOR TYPE = '!' or '2'.
The combination of STATE and REPORT ORG must exist in the GEO-COMMON File.
WARNING - CANNOT VERIFY REPORT-ORG
REPORT ORG must be checked in combination with STATE. If STATE is invalid, REPORT
ORG cannot be checked.
December 1993 5-17 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.2.6 RO EFFECTIVE DATE
RO EFFECTIVE DATE is the effective date of the reporting organization responsible for the collection
of Precision and Accuracy data. For all monitors, this is the date that the Precision and Accuracy data
applies for this monitor for the reporting organization.
Attributes:
6 digit date
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place the appropriate date in YYMMDD format in columns 33-38. A date
is valid for this field if it is:
1) on or after 1 January 1980, if MON TYPE is 'I1 (NAMS) or '2' (SLAMS); on or after
1 January 1957 otherwise
2) on or after DATE SAMPLING BEGAN
3) on or before DATE SAMPLING ENDED
4) no later than a year after the date the edit is performed
You must enter RO EFFECTIVE DATE when you enter a value for REPORT ORG.
Error Messages:
ERROR - CANNOT DELETE RO-EFF-DATE
RO EFFECTIVE DATE is a required field and cannot be deleted. Remove the asterisks from
this field of the MODIFY transaction.
ERROR - INVALID RO-EFF-DATE
For an INSERT transaction, RO EFFECTIVE DATE cannot be blank if MONITOR TYPE =
T or '2'. The date specified on an INSERT or MODIFY transaction must meet the criteria
given above in coding instructions and must be a valid Gregorian date.
ERROR - PA DATA EXISTS PRIOR TO THE RO-EFFECTIVE-DATE
For a MODIFY transaction, RO EFFECTIVE DATE cannot be moved to a date later than the
earliest precision or accuracy raw data.
Transaction Type Fl
5-18
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - ROEFF-DATE CANNOT BE BLANK
For a MODIFY transaction, if REPORT ORG is specified, RO EFFECTIVE DATE must be
specified.
WARNING - CANNOT VERIFY RO-EFF-DATE
RO EFFECTIVE DATE cannot be verified if MONITOR TYPE is blank and the MONITOR-ID
is invalid.
December 1993 5-19 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.2.7 DATE SAMPLING BEGAN
DATE SAMPLING BEGAN is the date on which air quality samples were first collected by the monitor.
Attributes:
6 digit date
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid date in YYMMDD format in columns 39-44. If this transaction
accompanies a type Al transaction for the site, then DATE SAMPLING BEGAN must be on or after
DATE SITE ESTABLISHED and on or before DATE SITE TERMINATED. Otherwise, DATE
SAMPLING BEGAN must be between January 1, 1957, and a year after the current date.
Error Messages:
ERROR - CANNOT DELETE DATE-SAMPLING-BEG
DATE SAMPLING BEGAN is a required field and cannot be deleted. Remove the asterisks
from this field of the MODIFY transaction.
ERROR • INVALID DATE-SAMPLING-BEGAN
For an INSERT transaction, DATE SAMPLING BEGAN cannot be blank. The date specified
on an INSERT or MODIFY transaction must meet the criteria given above in coding instructions
and must be a valid Gregorian date.
ERROR - RAW DATA EXISTS OUT OF THE SAMPLING DATE RANGE
DATE SAMPLING BEGAN on a MODIFY transaction must be equal to or earlier than the date
of the earliest raw data record for this monitor.
ERROR - SUMMARY DATA EXISTS OUT OF THE SAMPLING DATE RANGE
DATE SAMPLING BEGAN on a MODIFY transaction is equal to the year of the earliest
Summary record and the raw data is archived. DATE SAMPLING BEGAN cannot be later than
the earliest quarter for which there is data on the Summary record.
Transaction Type F1
5-20
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.2.8 DATE SAMPLING ENDED
DATE SAMPLING ENDED is the last date on which air quality samples were collected by the monitor.
Attributes: 6 digit date
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid date in YYMMDD format in columns 45-50. To be valid, a date
must be between January 1, 1957 and the current date. DATE SAMPLING ENDED must be on or after
DATE SAMPLING BEGAN. Also, if this transaction accompanies a type Al transaction with values
for DATE SITE TERM and/or DATE SITE ESTAB, then DATE SAMPLING ENDED must be on or
after DATE SITE ESTABLISHED and on or before DATE SITE TERMINATED.
To DELETE, place asterisks in columns 45-50 of a MODIFY transaction.
Error Messages:
ERROR - INVALID DATE-SAMPLING-ENDED
For an INSERT transaction, DATE SAMPLING ENDED may be blank or a valid Gregorian date
that meets the criteria given above.
For a MODIFY transaction, DATE SAMPLING ENDED may be blank, asterisks, or a valid
Gregorian date that meets the criteria given above.
For a MODIFY transaction, DATE SAMPLING ENDED must be greater than the REPORT
ORG EFFECTIVE DATE and the DATE TYPE EFF.
ERROR - RAW DATA EXISTS OUT OF THE SAMPLING DATE RANGE
DATE SAMPLING ENDED on a MODIFY transaction must be equal to or later than the date
of the latest Raw Data record for this monitor.
ERROR - SITE WAS TERMINATED - DATE-SAMPLING-ENDED CANNOT BE DELETED
On a MODIFY transaction, the DATE SAMPLING ENDED field cannot be deleted if the site
has been terminated.
ERROR - SITE WAS TERMINATED - DATE-SAMPLING-ENDED MUST BE VALUED
On a INSERT transaction, the DATE SAMPLING ENDED field must be valued if the
site has been terminated.
December 1993 5-21 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - SUMMARY DATA EXISTS OUT OF THE SAMPLING DATE RANGE
DATE SAMPLING ENDED on a MODIFY transaction is equal to the year of the latest
Summary record and ±6 raw data is archived. DATE SAMPLING ENDED cannot be prior to
the latest quarter for which there is data on the Summary record.
Transaction Type Fl
5-22
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5,2.9 AUDIT DATE
AUDIT DATE is the date of the last EPA quality assurance audit of the monitor.
Attributes: 6 digit date
Optional
Coding Instructions:
To INSERT or MODIFY/place a valid date in YYMMDD format in columns 51-56. A valid date is
between January 1, 1980 (when NAMS monitoring regulations were promulgated), and the current date.
Also, if this transaction accompanies a type Al transaction with values for either DATE SITE
TERMINATED or DATE SITE ESTABLISHED, or both, then DATE LAST EPA AUDIT must be on
or after DATE SITE ESTABLISHED and on or before DATE SITE TERMINATED.
To DELETE, place asterisks in columns 51-56 of a MODIFY transaction.
Error Message:
ERROR - INVALID AUDIT-DATE
For an INSERT transaction, DATE LAST EPA AUDIT may be blank or a valid Gregorian date
that meets the criteria given above in coding instructions.
For a MODIFY transaction, DATE LAST EPA AUDIT may be blank, asterisks, or a valid
Gregorian date that meets the criteria given above.
December 1993 5-23 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.2.10 PROJECT CLASS
PROJECT CLASS designates the type of sampling (population-oriented, source-oriented, background,
etc.) performed at a site.
Attributes:
Coding Instructions:
2 character code
Optional
To INSERT or MODIFY, place a valid code in columns 57-58. A valid code is one that exists in the
AIRS GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
To DELETE, place asterisks in columns 57-58 of a MODIFY transaction.
Error Message:
ERROR - INVALID PROJECT-CLASS
For an INSERT transaction, PROJECT CLASS may be blank or a valid code that is in the GEO-
COMMON File.
For a MODIFY transaction, PROJECT CLASS may be blank, asterisks, or a valid code that is
in the GEO-COMMON File.
Transaction Type Fl
5-24
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.2.11 ACTION TYPE
ACTION TYPE indicates the kind of administrative action taken by EPA headquarters in regard to a
NAMS monitor, such as approval or disapproval.
Attributes: 3 character alphanumeric
Optional
Cannot DELETE for NAMS monitor
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 59-61.
To DELETE, place asterisks in columns 59-61 of a MODIFY transaction. This field cannot be deleted
if MONITOR TYPE = 1, 6, 7, or 8.
This field must be blank or alphanumeric (no special characters). This field can by input only through
an ADBA Screening File.
Some typical values for this field are: 'APP' (approved), 'DIS' (disapproved), 'RDS' (redesignated), and
'REQ' (required).
Error Messages:
ERROR - CANNOT DELETE ACTION-TYPE
For a MODIFY transaction, ACTION TYPE cannot be asterisks if MONITOR TYPE = T, '6',
'7', or '8'.
ERROR - INVALID ACTION-TYPE
For an INSERT transaction, ACTION TYPE may be blank or alphanumeric.
For a MODIFY transaction, ACTION TYPE may be blank, alphanumeric, or asterisks.
ERROR - NON-ADBA SCREENING FILE
This field must be input through an ADBA Screening File.
December 1993 5-25 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.2.12 ACTION TYPE REASON
AT REASON is the reason for negative actions by EPA headquarters with regard to a monitor.
Attributes:
Coding Instructions:
2 digit numeric
Optional
To INSERT or MODIFY, place a numeric value in columns 62-63. This field can be input only through
an ADBA Screening File.
To DELETE, place asterisks in columns 62-63 of a MODIFY transaction.
At this time, there is no list of valid codes for this field.
Error Message:
ERROR - INVALID ACTION-TYPE-REASON
For an INSERT transaction, ACTION TYPE REASON may be blank or numeric.
For a MODIFY transaction, ACTION TYPE REASON may be blank, numeric, or asterisks.
ERROR - NON-ADBA SCREENING FILE
This field must be input through an ADBA Screening File.
Transaction Type Fl
5-26
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.2.13 DOMINANT SOURCE
DOMINANT SOURCE indicates the primary source of the pollutant being monitored.
Attributes: 1 digit code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid DOMINANT SOURCE code in column 64. Valid codes are
listed in Volume GC2 of the AIRS User's Guide.
To DELETE, place an asterisk in column 64 of a MODIFY transaction.
Error Message:
ERROR - INVALID DOMINANT-SOURCE
For an INSERT transaction, DOMINANT SOURCE may be blank or one of the valid codes
listed in Volume GC2 of the AIRS User's Guide.
For a MODIFY transaction, DOMINANT SOURCE may be blank, asterisk, or a valid code.
December 1993 5-27 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.2.14 MEASUREMENT SCALE
MEASUREMENT SCALE is a code that denotes the geographic rcope of the measurements of air quality
data made by this monitor. The implication is that the same measurement made elsewhere within the
measurement scale would produce an equivalent result obtained at the monitoring site.
Attributes:
Coding Instructions:
1 character code
Optional
To INSERT or MODIFY, place a valid code in column 65. A valid code is one that exists in the AIRS
GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
To DELETE, place an asterisk in column 65 of a MODIFY transaction.
Error Message:
ERROR - INVALID MEASUREMENT-SCALE
For an INSERT transaction, MEASUREMENT SCALE may be blank or a valid code.
For a MODIFY transaction, MEASUREMENT SCALE may be blank, asterisk, or a valid code.
Transaction Type Fl
5-28
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.2.15 MONITOR TYPE OBJECTIVE
MONITOR TYPE OBJECTIVE is the primary reason for measuring air quality data at this monitor.
Attributes: 1 character code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in column 66. A code is valid if it exists in the AIRS GEO-
COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
To DELETE, place an asterisk in column 66 of a MODIFY transaction.
Error Messages:
ERROR - INVALID MONITOR-TYPE-OBJECTIVE
For an INSERT transaction, MONITOR TYPE OBJECTIVE may be blank or a valid code.
For a MODIFY transaction, MONITOR TYPE OBJECTIVE may be blank, asterisk, or a valid
code.
December 1993 5-29 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.2.16 NONATTAINMENT AREA
NONATTAINMENT AREA is a code that identifies the nonattainment area in which the monitor is
located. The area must be in nonattainment status for the pollutant that the monitor measures.
Attributes:
Coding Instructions:
5 character code
Optional
To INSERT or MODIFY, NONATTAINMENT AREA, place a valid code in columns 67-71. A code
is valid if it is a valid STATUS-AREA code in the GEO-COMMON File. Valid codes are listed in
Volume GC2 of the AIRS User's Guide.
This field may be used only with parameters 42101, 44201, 12128, 42401, 42602, or 81102.
PARAMETER is translated into PROGRAM-SIP as follows:
42101 = CO
44201 = OZONE
12128 = PB
42401 = SO2
42602 = NO2
81102 = PM10
PROGRAM-SIP must match STATUS-AREA code. It also must be a valid combination of STATE,
COUNTY, and NONATTAINMENT AREA in the Status Area X-Ref record of the AIRS GEO-
COMMON File.
If STATE or COUNTY is not valid, this field cannot be verified.
To DELETE, place *'s in columns 67-71 of the MODIFY transaction.
Error Messages:
ERROR - INVALID NONATTAINMENT AREA
NONATTAINMENT AREA must be a valid STATUS-AREA code. The NONATTAINMENT
AREA code must match the PARAMETER and PROGRAM-SIP. There must be a valid
combination of STATE, COUNTY, and NONATTAINMENT AREA in the GEO-COMMON
File.
ERROR - NONATTAINMENT AREA MUST BE BLANK
If PARAMETER is not 42101, 44201, 12128, 42401, 42602, or 81102, this field must be blank.
Transaction Type Fl
5-30
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
WARNING - CANNOT VERIFY NONATTAJNMENT AREA
If STATE or COUNTY is invalid, this field cannot be verified.
C»ecember 1993 5-31 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.2.17 URBAN AREA REPRESENTED
URBAN AREA REPRESENTED indicates the urban area from which the concentrations originated, not
the location of the monitor. For example, the maximum ozone monitor is frequently outside the URBAN
AREA REPRESENTED, because ozone forms in the atmosphere during transport.
Attributes:
4 digit code
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid URBAN AREA code in columns 72-75. A code is valid if it is
a valid URBAN-AREA code in the GEO-COMMON File. Valid codes are listed in Volume GC2 of the
AIRS User's Guide.
If the SITE is not within an URBAN AREA, use code 0000 (zeros).
ERROR - CANNOT DELETE URBAN-AREA
URBAN AREA is a required field and cannot be deleted. Remove the asterisks from this field
of the MODIFY transaction.
ERROR - INVALID URBAN-AREA
URBAN AREA cannot be blank for an INSERT transaction. It must be in the GEO-COMMON
File.
Transaction Type Fl
5-32
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.2.18 PAMS REQ SAMPLING FREQ
PAMS REQ SAMPLING FREQUENCY is the sampling frequency for organic compounds required by
PAMS regulations.
Attributes: 1 character code
Optional
Coding Instructions:
PAMS REQ SAMPLING FREQUENCY pertains to non-PM-10 monitors only; therefore, if
PARAMETER = 81102 (PM-10), this field must be blank.
To INSERT or MODIFY, place a valid code in column 76. A value is valid if it is a valid REQ
SAMPLING FREQUENCY code in the GEO-COMMON File. Valid codes are listed in Volume GC2
of the AIRS User's Guide.
To DELETE, place an asterisk in column 76 of a MODIFY transaction.
Error Messages:
4fc ERROR - INVALID PAMS REQ SAMPLING FREQUENCY
PAMS REQ SAMPLING FREQ must be a valid REQ SAMPLING FREQUENCY code in the
GEO-COMMON File.
ERROR - PAMS REQ SAMP NOT ALLOWED
If PARAMETER is 81102, this field must be blank.
December 1993 5-33 Transaction Type Fl
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.2.19 MONITOR OPEN PATH NUMBER
MONITOR OPEN PATH NUMBER is the specific open path registered at the site that the monitoring
data and monitor represent. The number must be registered at the site before it can be defined by the
monitor.
Attributes:
1 digit code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in column 77. Valid codes are 1 through 9.
To DELETE, place an * in column 77 of a MODIFY transaction.
Error Messages:
ERROR - INVALID MONITOR-PATH-NUMBER
Valid values are 1 through 9.
ERROR - OPEN PATH NUMBER DOES NOT EXIST
The number must be defined for the site before the MONITOR OPEN PATH NUMBER is
designated.
Transaction Type Fl
5-34
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
5.3 Transaction Type F2 - Monitor Data - Part 2
The fields described below are validated for INSERT (I) and MODIFY (M) transactions.
For a MODIFY transaction, at least one of the following fields must be non-blank:
MONITOR STREET NUMBER 1
DISTANCE FROM ROAD 1
MONITOR STREET NUMBER 2
DISTANCE FROM ROAD 2
MONITOR STREET NUMBER 3
DISTANCE FROM ROAD 3
REF METHOD USED
REF METHOD USED DATE
SITE CRITERIA MET
DATE SITE CRITERIA MET
QA PLAN
QA EFFECTIVE DATE
PROBE LOCATION CODE
PROBE HEIGHT
HORIZONTAL DISTANCE (FROM SUPPORT)
VERTICAL DISTANCE (FROM SUPPORT)
UNRESTRICTED AIR FLOW
OBSTRUCTION #1
TYPE OBSTRUCTION
DIRECTION FROM MONITOR
DISTANCE FROM INLET (IN METERS)
HEIGHT OF OBSTRUCTION (ABOVE PROBE)
OBSTRUCTION #2
TYPE OBSTRUCTION
DIRECTION FROM MONITOR
DISTANCE FROM INLET (IN METERS)
HEIGHT OF OBSTRUCTION (ABOVE PROBE)
OBSTRUCTION #3
TYPE OBSTRUCTION
DIRECTION FROM MONITOR
DISTANCE FROM INLET (IN METERS)
HEIGHT OF OBSTRUCTION (ABOVE PROBE)
If this condition is not met, the following message is generated:
ERROR - ALL FIELDS BLANK ON MODIFY
December 1993 5-3S Transaction Type F2
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5.3.1 STREET INFORMATION
The monitor's relationship to up to three nearby streets may be described by using the three street
information groups on the F2 transaction. There is no requirement that any of the groups be valued.
Moreover, there is no requirement that the groups be filled in any particular order. It is important to
note, however, that once a particular group has been valued, it will always retain that position relative
to the other groups, even if the others are unvalued. For example, assume that when you INSERTed a
monitor, the only street group you placed values into was the third group (columns 27-31). If you later
need to modify the DISTANCE FROM ROAD figure, then you will have to use the third DISTANCE
FROM ROAD occurrence on the transaction (columns 28-31). So, since street information groups are
identified only by position, it is recommended that the groups be filled left to right; i.e., use the third
group only for the third of three valued groups, the second for the second of two or three, and the first
for the first of one, two, or three.
Within a particular group the only inter-field requirement is that if either MONITOR STREET NUMBER
or DISTANCE FROM ROAD is valued, the other must also be valued. Similarly, one may not be deleted
without also deleting the other.
Transaction Type F2
5-36
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.3.1.1 MONITOR STREET NUMBER
MONITOR STREET NUMBER refers back to the street number existing at the site level. The user may
enter a number for up to three different streets around the monitor.
Attributes:
Coding Instructions:
1 digit numeric
Optional
To INSERT or MODIFY, place an integer greater than zero in column 17 (group 1), column 22 (group
2), and/or column 27 (group 3). To enter a value for MONITOR STREET NUMBER within a group,
you must also provide a value for DISTANCE FROM ROAD within the same group.
To DELETE, place an asterisk in columns 17, 22, and/or 27 of a MODIFY transaction. If you delete
MONITOR STREET NUMBER within a group, you must also delete DISTANCE FROM ROAD within
the same group (columns 18-21, 23-26, and/or 28-31).
Refer to Section 5.3.1, STREET INFORMATION, for a discussion of the usage of the three street
description groups.
Error Messages:
ERROR - CANNOT DELETE MON-STREET-NUMBER
If MONITOR STREET NUMBER is deleted, then DISTANCE FROM ROAD of the same group
must also be deleted.
ERROR - INVALID MONITOR STREET NUMBER
For an INSERT transaction, MONITOR STREET NUMBER must be blank or numeric > 0.
For a MODIFY transaction, MONITOR STREET NUMBER must be blank, numeric, > 0, or
asterisks.
ERROR - STREET NUMBER DOES NOT EXIST
The street number must be defined for the site before the MONITOR STREET NUMBER is
designated.
December 1993
5-37
Transaction Type F2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.3.1.2 DISTANCE FROM ROAD
DISTANCE FROM ROAD is the distance in meters at the closest point between the sensing or air
sampling equipment at a monitoring site and the edge of the roadway specified by the monitor street
number.
Attributes: 4 digit numeric
Optional
Coding Instructions:
To INSERT or MODIFY, place an integer greater than zero in columns 18-21 (group 1), 23-26 (group
2), and/or 28-31 (group 3). If you enter a value for DISTANCE FROM ROAD within a group, you must
also provide a value for MONITOR STREET NUMBER within the same group.
To DELETE, place asterisks in columns 18-21, 23-26, and/or 28-31 of a MODIFY transaction. If you
delete DISTANCE FROM ROAD within a group, you must also delete MONITOR STREET NUMBER
within the same group (columns 17, 22, and/or 27).
Refer to Section 5.3.1, STREET INFORMATION, for a discussion of the usage of the three street
description groups.
Error Messages:
ERROR - CANNOT DELETE DIST-FROM-ROAD
If DISTANCE FROM ROAD is deleted, then MONITOR STREET NUMBER of the same group
must also be deleted.
ERROR - DIST-FROM-ROAD CANNOT BE BLANK
If MONITOR STREET NUMBER is valued, DISTANCE FROM ROAD may not be blank.
Enter a value for DISTANCE FROM ROAD or delete the value for MONITOR STREET
NUMBER.
ERROR - INVALID DIST-FROM-ROAD
For an INSERT transaction, DISTANCE FROM ROAD must be blank or numeric > 0.
For a MODIFY transaction, DISTANCE FROM ROAD must be blank, numeric > 0, or
asterisks.
Transaction Type F2 5-38 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.3.2 REF METHOD USED
REF METHOD USED is a code that indicates whether or not a reference method is used for sampling
and analysis of the PARAMETER measured by the monitor.
Attributes:
1 character code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in column 32. The valid codes are:
Y - Reference or equivalent instrument is being used, and REF METHOD USED DATE is
the date when utilization of reference or equivalent methods began.
N - Reference or equivalent instrument is not being used.
If you specify 'Y' on an INSERT or MODIFY, you must also provide REF METHOD USED DATE.
To DELETE, place an asterisk in column 32 of a MODIFY transaction. If REF METHOD USED is
deleted, then REF METHOD USED DATE must also be deleted.
Error Message:
ERROR - CANNOT DELETE REF-METHOD-USED
For a MODIFY transaction, unless REF METHOD USED DATE is deleted as well, REF
METHOD USED DATE cannot be deleted.
ERROR - INVALID REF-METHOD-USED
For an INSERT transaction, REF METHOD USED must be blank or one of the valid codes
given above.
For a MODIFY transaction, REF METHOD USED must be blank, asterisk, or one of the valid
codes given above.
December 1993
5-39
Transaction Type F2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.3.3 REF METHOD USED DATE
The meaning of this field depends on the value in the REF METHOD USED field. If REF METHOD
USED contains 'Y', then this is the date the use of a reference method began. If REF METHOD USED
contains 'N', then this field is not used.
Attributes: 4 digit date
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid Gregorian date in YYMM format into columns 33-36. The date
must be between January 1970 or the DATE SAMPLING BEGAN, whichever is later, and the current
date or the DATE SAMPLING ENDED, whichever is earlier.
To DELETE, place asterisks in columns 33-36 of a MODIFY transaction. If REF METHOD USED
DATE is deleted, then REF METHOD USED must also be deleted.
If a transaction contains a 'Y' for REF METHOD USED, REF METHOD USED DATE must be valued.
Error Messages:
ERROR - CANNOT DELETE REF-METHOD-DATE
For a MODIFY transaction, if REF METHOD USED is 'Y', REF METHOD USED DATE
cannot be deleted. Enter a valid date in REF METHOD USED DATE or change the 'Y' in REF
METHOD USED to an asterisk or another valid code.
ERROR - INVALID REF-METHOD-USED-DATE
If REF METHOD USED DATE is present, it must be a valid Gregorian date (YYMM only)
between January 1970 and the current date. Make sure the date is within that range and that
month has an appropriate value. The date must be between DATE SAMPLING BEGAN and
DATE SAMPLING ENDED.
ERROR - REF-METHOD-DATE CANNOT BE BLANK
If REF METHOD USED equals 'Y', REF METHOD USED DATE must be valued.
ERROR - REF-METHOD-DATE NOT ALLOWED
If REF METHOD USED does not equal 'Y', REF METHOD USED DATE must be blank or
asterisks.
Transaction Type F2 5-40 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.3.4 SITE CRITERIA MET
SITE CRITERIA MET indicates whether the monitor meets the siting criteria as prescribed in the EPA
monitoring regulations.
Attributes:
1 character code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in column 37. The valid codes are:
Y - Siting criteria were met
N - Siting criteria were not met
W - Siting criteria were not met, but a waiver was granted.
To DELETE, place an asterisk in column 37 of a MODIFY transaction.
If you specify 'Y' or 'W, you must also provide a value for DATE SITE CRITERIA MET.
Error Message:
ERROR - INVALID SITE-CRITERIA-MET
For an INSERT transaction, SITE CRITERIA MET must be blank or one of the valid codes
given above.
For a MODIFY transaction, SITE CRITERIA MET must be blank, an asterisk, or one of the
valid codes given above.
December 1993
5-41
Transaction Type F2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.3.5 DATE SITE CRITERIA MET
DATE SITE CRITERIA MET is the date the siting criteria were met (SITE CRITERIA MET = 'Y')
or when a waiver was granted (SITE CRITERIA MET = 'W').
Attributes: 4 digit date
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid date in YYMM format in columns 38-41. The date must be
between January 1957 and a year after the current date.
To DELETE, place asterisks in columns 38-41 of a MODIFY transaction. Although there is currently
no edit check to prevent it, you should not delete DATE SITE CRITERIA MET while the value of SITE
CRITERIA MET is 'Y' or *W* in the Site File (instead of on the transaction).
If SITE CRITERIA MET = 'N', you may not specify this date.
Error Messages:
ERROR - CANNOT DELETE SITE-CR-DATE
For a MODIFY transaction, if SITE CRITERIA MET = 'Y' or 'W, DATE SITE CRITERIA
MET cannot be deleted. Enter a valid date in DATE SITE CRITERIA MET or change the value
in SITE CRITERIA MET to asterisk of another valid date.
ERROR - INVALID DATE-SITE-CRITERIA-MET
If DATE SITE CRITERIA MET is valued, the date must be a valid Gregorian date between
January 1957 and a year after the current date. Make sure the date is within that range and that
month has an appropriate value.
If DATE SITE CRITERIA MET is valued, it must be between the monitor's DATE SAMPLING
BEGAN and DATE SAMPLING ENDED values.
ERROR - SITE-CR-DATE CANNOT BE BLANK
If SITE CRITERIA MET equals 'Y* or 'W, DATE SITE CRITERIA MET must be valued.
ERROR - SITE-CRITERIA-DATE NOT ALLOWED
If SITE CRITERIA MET does not equal 'Y' or 'W, DATE SITE CRITERIA MET must be
blank or asterisks.
Transaction Type F2 5-42 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.3.6 QAPLAN
QA PLAN indicates whether a quality assurance plan has been approved for the specific monitor.
Attributes: 1 character code
Conditionally required
Coding Instructions:
To INSERT or MODIFY, place a valid value in column 42. Valid values for QA PLAN are:
Y
N
C
a quality assurance plan has been approved for the monitor.
a quality assurance plan has not been approved for the monitor.
a quality assurance plan has been conditionally approved for the monitor.
To DELETE, place an asterisk in column 42 of a MODIFY transaction.
If QA PLAN is 'Y' or 'C', then QA EFFECTIVE DATE must be valued with a valid date.
To MODIFY, if QA PLAN is '*' or 'N' and a date exists for QA EFFECTIVE DATE, QA EFFECTIVE
DATE must also be valued with '*'.
Error Messages:
ERROR - INVALID QA-PLAN
For an INSERT transaction, QA PLAN must be blank or one of the valid codes given above.
For a MODIFY transaction, QA PLAN must be blank, an asterisk, or one of the valid codes
given above.
ERROR - QA-PLAN MUST BE DELETED
On a MODIFY transaction, if QA EFFECTIVE DATE is valued with all asterisks, QA PLAN
must be an asterisk.
ERROR - QA-PLAN MUST BE "Y" OR "C"
If QA EFFECTIVE DATE is valued with a date, QA PLAN must be 'Y' or 'C'.
December 1993
5^43
Transaction Type F2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.3.7 QA EFFECTIVE DATE
The meaning of this field depends on the value in the QA PLAN field. If QA PLAN is *Y', QA
EFFECTIVE DATE is the date the quality assurance plan became effective. If QA PLAN contains blank
or 'N', this field is not used. If QA PLAN is *C, QA EFFECTIVE DATE reflects the date of
conditional approval. If the QA EFFECTIVE DATE is prior to the DATE SAMPLING BEGAN, the
QA EFFECTIVE DATE should be entered with the same date as the DATE SAMPLING BEGAN.
Attributes: 4 digit date
Conditionally required
Coding Instructions:
To INSERT or MODIFY, place a valid Gregorian date in YYMM format into columns 43-46. The date
must be within the sampling dates for the monitor. The date must be between January 1957 and the
current date.
To DELETE, place an asterisks in columns 43-46 of a MODIFY transaction. When deleting QA
EFFECTIVE DATE, an asterisk or 'N' is required in the QA PLAN field.
If a transaction contains 'Y' or 'C' for QA PLAN, QA EFFECTIVE DATE must be valued.
Error Messages:
ERROR - INVALID QA-EFFECTIVE-DATE
If QA EFFECTIVE DATE is present, it must be a valid Gregorian date in YYMM format. The
date must be between January 1957 and the current date. Make sure that month has an
appropriate value. Please note that if the QA plan for the pollutant is in effect before the monitor
was active, the QA EFFECTIVE DATE * DATE SAMPLING BEGAN date.
If QA EFFECTIVE DATE is present, it must be a date between the monitor's DATE
SAMPLING BEGAN and DATE SAMPLING ENDED.
ERROR - QA-EFFECT-DATE MUST BE BLANK
On an INSERT transaction with QA PLAN = *N', QA EFFECTIVE DATE must not be valued.
ERROR - QA-EFFECTIVE-DATE MUST BE DELETED
If QA PLAN on a MODIFY transaction is either an asterisk or 'N', QA EFFECTIVE DATE also
must be valued with asterisks.
ERROR - QA-EFFECTIVE-DATE MUST BE NUMERIC
If QA PLAN is 'Y' or 'C', QA EFFECTIVE DATE must be numeric.
Transaction Type F2 5-44 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
WARNING - CANNOT VERIFY QA-EFFECT-DATE
If QA PLAN is invalid, QA EFFECTIVE DATE cannot be validated.
December 1993
5-45
Transaction Type F2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.3.8 PROBE LOCATION CODE
PROBE LOCATION CODE identifies the location of the sampling probe.
Attributes: 1 digit numeric
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid code in column 47. A code is valid if it is in the AIRS GEO-
COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
Error Messages:
ERROR - CANNOT DELETE PROBE-LOC-CODE
PROBE LOCATION CODE is a required field and cannot be deleted. Remove the asterisks from
this field of the MODIFY transaction.
ERROR - INVALID PROBE-LOC-CODE
PROBE LOCATION CODE must be in the GEO-COMMON File.
ERROR - PROBE-LOC-CODE CANNOT BE BLANK
PROBE LOCATION CODE cannot be blank on an INSERT transaction.
Transaction Type F2 5-46 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.3.9 PROBE HEIGHT
PROBE HEIGHT is the sampling probe height from the ground in meters.
Attributes: 3 digit numeric
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions: '
To INSERT or MODIFY, place an integer number greater than zero in columns 48-50.
Error Message:
ERROR - CANNOT DELETE PROBE-HEIGHT
PROBE HEIGHT is a required field and cannot be deleted. Remove the asterisks from this field
of the MODIFY transaction.
ERROR - INVALID PROBE-HEIGHT
For an INSERT transaction, PROBE HEIGHT must be numeric > 0.
For a MODIFY transaction, PROBE HEIGHT must be blank or numeric > 0.
ERROR - PROBE-HEIGHT CANNOT BE BLANK
PROBE HEIGHT cannot be blank on an INSERT transaction.
December 1993
5-47
Transaction Type F2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.3.10 HORIZONTAL DISTANCE
HORIZONTAL DISTANCE is the horizontal distance of the probe from its supports.
Attributes: 1 digit numeric
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place an integer in column 51.
Error Messages:
ERROR - CANNOT DELETE HORIZONTAL DIST
HORIZONTAL DISTANCE is a required field and cannot be deleted. Remove the asterisks
from this field of the MODIFY transaction.
ERROR - HORIZONTAL-DIST MUST BE NUMERIC
On an INSERT transaction, HORIZONTAL DISTANCE cannot be spaces.
ERROR - INVALID HORIZONTAL-DIST
If valued, HORIZONTAL DISTANCE must be numeric.
Transaction Type F2 5-48 December 1993
-------
AIRS User's Guide
Volume A Q2
Air Quality Data Coding
5.3.11 VERTICAL DISTANCE
VERTICAL DISTANCE is the vertical distance of the probe from its supports.
Attributes: 1 digit numeric
Required on INSERT
Optional on MODIFY
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place an integer in column 52.
Error Messages:
ERROR - CANNOT DELETE VERTICAL DIST
VERTICAL DISTANCE is a required field and cannot be deleted. Remove the asterisks from
this field of the MODIFY transaction.
ERROR - INVALID VERTICAL-DISTANCE
If valued, VERTICAL DISTANCE must be numeric.
ERROR - VERTICAL-DIST MUST BE NUMERIC
On an INSERT transaction, VERTICAL DISTANCE cannot be spaces.
December 1993
5-49
Transaction Type F2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.3.12 UNRESTRICTED AIR FLOW
UNRESTRICTED AIR FLOW indicates whether or not the flow of air to the monitor is restricted.
Attributes: 1 character code
Optional
Coding Instructions:
To INSERT or MODIFY, place a valid code in column 53.
Valid codes are: Y - Yes
N-No
W - Waiver
If UNRESTRICTED AIR FLOW is an asterisk on a MODIFY transaction, then columns 54-74 must also
contain asterisks. This will delete all three occurrences of TYPE OBSTRUCTION and its associated
fields (DIRECTION FROM MONITOR, DISTANCE FROM INLET, and HEIGHT OF
OBSTRUCTION).
Error Messages:
ERROR - INVALID UNRST-AIR-FLOW
On an INSERT transaction, UNRESTRICTED AIR FLOW must be Y, N, W, or blank. On a
MODIFY transaction, UNRESTRICTED AIR FLOW must be *, Y, N, W, or blank.
ERROR - MUST DELETE ALL OBSTRUCTION DATA
If UNRESTRICTED AIR FLOW is deleted, OBSTRUCTION DESCRIP must be deleted as well.
ERROR - OBSTRUCTION DATA CANNOT BE BLANK
If UNRESTRICTED AIR FLOW is N or W, OBSTRUCTION DESCRIP cannot be blank.
ERROR - UNRST-AIR-FLOW CANNOT BE BLANK
If OBSTRUCTION DESCRIP is not blank, UNRESTRICTED AIR FLOW cannot be blank.
Transaction Type F2 5-50 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.3.13 OBSTRUCTION DESCRIPTION
The type of obstruction for a monitor with restricted air flow is described by using the three TYPE
OBSTRUCTION groups on the F2 transaction. At least one of the groups must be valued if
UNRESTRICTED AIR FLOW is 'N* (No) or 'W (Waiver). If UNRESTRICTED AIR FLOW is 'Y'
(Yes), then all three groups must be blank.
There is no requirement that the groups be filled in any particular order. It is important to note,
however, that once a particular group has been valued, it will always retain that position relative to the
other groups, even if the others are unvalued. For example, assume that when you INSERTed a monitor,
the only TYPE OBSTRUCTION group you placed values in was the third group (columns 68-74). If you
later need to MODIFY the HEIGHT OF OBSTRUCTION figure, you will have to use the third HEIGHT
OF OBSTRUCTION occurrence on the transaction (columns 73-74). Since TYPE OBSTRUCTION
groups are identified only by position, it is recommended that the groups be filled left to right, i.e., use
the third group only for the third of three valued groups, the second for the second of two or three, and
the first for the first of one, two, or three.
Within a particular group, the only inter-field requirement is that if TYPE OBSTRUCTION is valued,
then DIRECTION FROM MONITOR, DISTANCE FROM INLET, and HEIGHT OF OBSTRUCTION
also must be valued. Similarly, if TYPE OBSTRUCTION is deleted, then the other fields within the
group also must be deleted.
December 1993
5-51
Transaction Type F2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.3.13.1 TYPE OBSTRUCTION
TYPE OBSTRUCTION describes the type of obstruction responsible for the restricted air flow of a
monitor.
Attributes: 1 digit numeric
Conditionally optional
Coding Instructions:
If UNRESTRICTED AIR FLOW = *Y' on an INSERT transaction, all occurrences of TYPE
OBSTRUCTION must be blank.
To INSERT or MODIFY, place a valid code in column 54 (group 1), column 61 (group 2), and/or
column 68 (group 3). Valid codes are listed in Volume GC2 of the AIRS User's Guide. If you enter
a value for TYPE OBSTRUCTION for a group, you must also provide a value for DIRECTION FROM
MONITOR, DISTANCE FROM INLET, and HEIGHT OF OBSTRUCTION within the same group.
To DELETE, place an asterisk in columns 54, 61, and/or 68 of a MODIFY transaction. If you delete
TYPE OBSTRUCTION within a group, you also must delete DIRECTION FROM MONITOR,
DISTANCE FROM INLET, and HEIGHT OF OBSTRUCTION within the same group (columns 55-60,
62-67, and/or 69-74).
Note: All three groups of TYPE OBSTRUCTION may not be deleted unless UNRESTRICTED
AIR FLOW = *Y* or '*'.
Refer to Section 5.3.13, OBSTRUCTION DESCRIPTION, for a discussion of the usage of the three
TYPE-OBSTRUCTION groups.
Error Messages:
ERROR - INVALID TYPE-OBSTRUCTION
TYPE OBSTRUCTION must be a valid TYPE OBSTRUCTION code in the AIRS GEO-
COMMON File. TYPE OBSTRUCTION may be asterisks only on a MODIFY transaction.
ERROR - OBSTRUCTION DATA CANNOT BE BLANK
On an INSERT transaction, if UNRESTRICTED AIR FLOW = 'N' or 'W, at least one
occurrence of TYPE OBSTRUCTION must be valued.
Transaction Type F2 5-52 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.3.13.2 DIRECTION FROM MONITOR
DIRECTION FROM MONITOR indicates in which direction from the monitor the obstruction is located.
Attributes:
Coding Instructions:
2 character code
Optional
To INSERT or MODIFY,'place a valid code in columns 55-56 (group 1), columns 62-63 (group 2),
and/or columns 69-70 (group 3). A code is valid if it is a valid COMPASS SECTOR code in the AIRS
GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide. If you enter
a value for DIRECTION FROM MONITOR for a group, you must also provide a value for TYPE OF
OBSTRUCTION, DISTANCE FROM INLET, and HEIGHT of OBSTRUCTION within the same group.
To DELETE, place asterisks in columns 55-56, 62-63, and/or 69-70 of a MODIFY transaction. You
may delete this field only if TYPE OBSTRUCTION, DISTANCE FROM INLET, and HEIGHT OF
OBSTRUCTION of the same group also are being deleted.
Refer to Section 5.3.13, OBSTRUCTION DESCRIPTION, for a discussion of the usage of the three
TYPE OBSTRUCTION groups.
Error Messages:
ERROR - CANNOT DELETE DIR-FROM-MONITOR
DIRECTION FROM MONITOR cannot be deleted unless TYPE OBSTRUCTION within the
same group is being deleted and UNRESTRICTED AIR FLOW = Y.
ERROR - DIR-FROM-MONITOR CANNOT BE BLANK
If TYPE OBSTRUCTION is valued and UNRESTRICTED AIR FLOW * Y, DIRECTION
FROM MONITOR within the same group must be valued.
ERROR - DIR-FROM-MONITOR MUST BE BLANK
If TYPE OBSTRUCTION is blank and UNRESTRICTED AIR' FLOW * Y, DIRECTION
FROM MONITOR within the same group must be blank.
ERROR - DIR-FROM-MONITOR MUST BE DELETED
If TYPE-OBSTRUCTION within the same group is asterisks and UNRESTRICTED AIR FLOW
* Y, DIRECTION FROM MONITOR must be asterisks.
December 1993
5-53
Transaction Type F2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR - INVALID DIR-FROM-MONITOR
DIRECTION FROM MONITOR must be a valid COMPASS SECTOR code in the AIRS GEO-
COMMON File.
Transaction Type F2 5-54 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.3.13.3 DISTANCE FROM INLET
DISTANCE FROM INLET describes the distance of the obstruction from the probe at the closest point.
Attributes:
Coding Instructions:
2 digit numeric
Optional
To INSERT or MODIFY, place a valid code in columns 57-58 (group 1), columns 64-65 (group 2),
and/or columns 71-72 (group 3). A code is valid if it is numeric greater than zero. If you enter a value
for DISTANCE FROM INLET for a group, you must also provide a value for TYPE OF
OBSTRUCTION, DIRECTION FROM MONITOR, HEIGHT OF OBSTRUCTION, and DISTANCE
FROM INLET within the same group.
To DELETE, place asterisks in columns 57-58, 64-65, and/or 71-72 of a MODIFY transaction. You
may delete this field only if TYPE OBSTRUCTION, DIRECTION FROM MONITOR, and HEIGHT
OF OBSTRUCTION of the same group also are being deleted.
Refer to Section 5.3.13, OBSTRUCTION DESCRIPTION, for a discussion of the usage of the three
TYPE OBSTRUCTION groups.
Error Messages:
ERROR - CANNOT DELETE DIST-FROM-INLET
DISTANCE FROM INLET cannot be deleted unless TYPE OBSTRUCTION within the same
group is being deleted and UNRESTRICTED AIR FLOW = Y.
ERROR - DIST-FROM-INLET CANNOT BE BLANK
If TYPE-OBSTRUCTION is valued and UNRESTRICTED AIR FLOW * Y, DISTANCE
FROM INLET within the same group must be valued.
ERROR - DIST-FROM-INLET MUST BE BLANK
If TYPE-OBSTRUCTION is blank and UNRESTRICTED AIR FLOW * Y, DISTANCE FROM
INLET within the same group must be blank.
ERROR - INVALID DIST-FROM-INLET
DISTANCE FROM INLET must be numeric greater than zero.
December 1993
5-55
Transaction Type F2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR - MUST DELETE DIST-FROM-INLET
If TYPE OBSTRUCTION within the same group is asterisks and UNRESTRICTED AIR FLOW
* Y, DISTANCE FROM INLET must be asterisks.
Transaction Type F2 5-56 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.3.13.4 HEIGHT OF OBSTRUCTION
HEIGHT OF OBSTRUCTION describes the height of the top of the obstruction above the probe.
Attributes:
Coding Instructions:
2 digit numeric
Optional
To INSERT or MODIFY, place a valid code in columns 59-60 (group 1), columns 66-67 (group 2),
and/or columns 73-74 (group 3). A code is valid if it is numeric greater than zero. If you enter a value
for HEIGHT OF OBSTRUCTION for a group, you must also provide a value for TYPE OF
OBSTRUCTION, DIRECTION FROM MONITOR, and DISTANCE FROM INLET within the same
group.
To DELETE, place asterisks in columns 59-60, 66-67, and/or 73-74 of a MODIFY transaction. You
may delete this field only if TYPE OBSTRUCTION, DIRECTION FROM MONITOR, and DISTANCE
FROM INLET of the same group also are being deleted.
Refer to Section 5.3.13, OBSTRUCTION DESCRIPTION, for a discussion of the usage of the three
TYPE OBSTRUCTION groups.
Error Messages:
ERROR - CANNOT DELETE HT-OF-OBSTRUCT
HEIGHT OF OBSTRUCTION cannot be deleted unless TYPE OBSTRUCTION within the same
group is being deleted, and UNRESTRICTED AIR FLOW = Y.
ERROR - HT-OF-OBSTRUCT CANNOT BE BLANK
If TYPE OBSTRUCTION is valued and UNRESTRICTED AIR FLOW
OBSTRUCTION within the same group must be valued.
ERROR - HT-OF-OBSTRUCT MUST BE BLANK
If TYPE OBSTRUCTION is blank and UNRESTRICTED AIR FLOW
OBSTRUCTION within the same group must be blank.
ERROR - INVALID HT-OF-OBSTRUCT
HEIGHT OF OBSTRUCTION must be numeric greater than zero.
Y, then HEIGHT OF
Y, then HEIGHT OF
December 1993
5-57
Transaction Type F2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR - MUST DELETE HT-OF-OBSTRUCT
If TYPE OBSTRUCTION within the same group is asterisks and UNRESTRICTED AIR FLOW
* Y, HEIGHT OF OBSTRUCTION must be asterisks.
Transaction Type F2 5-58 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.4 Transaction Type F3 - Monitor Data - Part 3
The fields described below are validated for INSERT (I) and MODIFY (M) transactions.
For a MODIFY transaction, at least one of the following fields must be non-blank:
MONITORING AREA
WORST SITE
SURROGATE FLAG
NUMSCH-SAMPLE MO
REQ SAMPLING FREQ
RSF EFFECTIVE DATE
SHORT TERM SCH SAT
SHORT TERM COMP DATE
FIRST EXCEED CORRECTION
If this condition is not met, the following message is generated:
ERROR - ALL FIELDS BLANK ON MODIFY
December 1993
5-59
Transaction Type F3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.4.1 MONITORING AREA
MONITORING AREA is a code that describes the geographic monitoring area for PM-10 (81102)
monitors.
Attributes: 4 digit code
Required for PM-10 INSERT
Optional for PM-10 MODIFY
Prohibited if not PM-10
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a valid code in columns 17-20. A valid code is one that exists in the
AIRS GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
This field may not be deleted.
Error Messages:
ERROR - CANNOT DELETE MONITORING AREA
MONITORING AREA may not be deleted.
ERROR - INVALID MONITORING AREA CODE
The MONITORING AREA code specified was not found in the AIRS GEO-COMMON File.
ERROR - MONITORING AREA CANNOT BE BLANK
MONITORING AREA is a required field on INSERT transactions.
ERROR - MONITORING AREA NOT ALLOWED
MONITORING AREA is allowed only for monitors whose associated parameter is PM-10
(81102).
WARNING - CANNOT VERIFY MONITORING AREA
If PARAMETER is not valid, it cannot be determined if this field is required or prohibited.
Transaction Type F3 5-60 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.4.2 WORST SITE
Within a particular monitoring area, those monitors with the highest PM-10 concentrations must have
their WORST SITE indicator set to T, and are expected to monitor at the recommended sampling
frequency. Other monitors may be classified as either: not worst site monitors, or monitoring on an
accelerated schedule, but not at the recommended sampling frequency.
Attributes:
1 digit code
Required for PM-10 INSERT
Optional for PM-10 MODIFY
Prohibited if not PM-10
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place one of the following codes in column 21:
1 Worst site
2 Not worst site
3 Monitoring on an accelerated schedule, but not at the recommended sampling frequency
Error Messages:
ERROR - CANNOT DELETE WORST-SITE
This field may not be deleted.
ERROR - INVALID WORST-SITE CODE
This field must be one of the above codes.
ERROR - WORST-SITE CANNOT BE BLANK
This field is required for PM-10 (81102) INSERT transactions.
ERROR - WORST-SITE NOT ALLOWED
This field is allowed only for PM-10 (81102) monitors.
WARNING - CANNOT VERIFY WORST-SITE
If PARAMETER is not valid, it cannot be determined if this field is required or prohibited.
December 1993
5-61
Transaction Type F3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.4.3 SURROGATE FLAG
Some TSP monitors may serve as surrogate monitors for PM-10. Such monitors are identified by setting
this field to 'Y'.
Attributes: 'Y' or 'N'
Required for TSP INSERT
Optional for TSP MODIFY
Prohibited if not TSP
May not be DELETEd
Coding Instructions:
To INSERT or MODIFY, place a 'Y' in column 22 if this TSP (11101) monitor is a surrogate for PM-10
(81102); otherwise, place an 'N' in column 22. Leave this field blank if the transaction applies to a PM-
10 monitor.
Error Messages:
ERROR - CANNOT DELETE SURROGATE-FLAG
This field may not be deleted.
ERROR - INVALID SURROGATE-FLAG
This field must be 'Y' or 'N1 or blank.
ERROR - SURROGATE-FLAG CANNOT BE BLANK
This field is required for TSP INSERT transactions.
ERROR - SURROGATE-FLAG NOT ALLOWED
This field is allowed only on TSP (11101) transactions.
WARNING - CANNOT VERIFY SURROGATE-FLAG
If PARAMETER is invalid, it cannot be determined if SURROGATE FLAG is required or
prohibited.
Transaction Type F3 5-62 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.4.4 HUM SCH SAMPLE MO
This field specifies the number of samples required within an indicated month for those monitors whose
sampling frequency (REQ SAMPLING FREQ) is '8' (Stratified Random), '9' (Random), or 'S*
(Seasonal). Twelve slots are available for specifying the sampling schedule of each month of the year.
Attributes:
2 digit numeric
Required on INSERT for RSF '8', '9', or'S'
Optional on INSERT for other sampling frequencies
Optional on MODIFY
May not be DELETEd for sampling frequencies '8', *9', or 'S'
May be DELETEd for other sampling frequencies
Coding Instructions:
For INSERT, a valid integer must be placed in each of the 12 two-digit fields in columns 23-46 when
the sampling frequency is *8', '9', or 'S'. For other sampling frequencies, blanks or a valid integer may
be placed in any of the 12 fields. An integer is valid if it is zero or positive and does not exceed the
number of days in the corresponding month (January in columns 23-24, February in 25-26, etc).
For MODIFY, a valid integer is also required for sampling frequencies '8', '9', and *S' in those
occurrences for which there is no corresponding value in that monitor's record in the Site File.
None of these occurrences may be deleted when sampling frequency is '8', '9', or 'S'. For other
sampling frequencies, a NUM SCH SAMPLES MO occurrence may be deleted by placing asterisks in
the appropriate columns.
Warning
It is recommended that these occurrences not be deleted if the required sampling frequency for any time
period will remain '8', '9', or 'S'. Deleting occurrences in this case will cause a loss of historical data.
Error Messages:
ERROR - CANNOT DELETE NUM-SCH-SAMP
For monitors whose sampling frequency is (or will be by virtue of a MODIFY) '8', '9', or 'S',
all 12 occurrences of this field must be valued.
ERROR - INVALID NUM-SCH-SAMP
This field must be an integer greater than or equal to zero and less than or equal to the number
of days in the corresponding month if the sampling frequency of this monitor is '8', '9', or 'S'.
For other sampling frequencies, blank is also allowed.
December 1993
5-63
Transaction Type F3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR - NUM-SCH-SAMP CANNOT BE BLANK
For monitors whose sampling frequency is (or will be by virtue of a MODIFY) '8', '9\ or 'S',
all 12 occurrences of this field must be valued.
ERROR - NUM-SCH-SAMP DOES NOT EXIST
Asterisks in a field specify deletion of a value that does not exist in the Site File. A MODIFY
transaction cannot have asterisks in this field if the corresponding field in the monitor's record
in the Site File is blank.
Transaction Type F3 5-64 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.4.5 REQ SAMPLING FREQ
REQ SAMPLING FREQ indicates how often 24-hour samples are taken, e.g., daily, every third day,
stratified random, etc. REQ SAMPLING FREQ pertains to PM-10 monitors only. If PARAMETER
— 81102, this field must be valued; otherwise, it must be blank. Required sampling frequency is linked
to RSF EFFECTIVE DATE (Required Sampling Frequency Effective Date). If one is specified, the other
must also be specified.
Attributes:
1 character code
Required on INSERT
Required on MODIFY if RSF EFFECTIVE DATE is valued
Prohibited on MODIFY if RSF EFFECTIVE DATE is blank
May not be DELETEd
Coding Instructions:
For INSERT, place a valid value in column 47. A value is valid if it appears in an AIRS-GEO-
COMMON File type E Description record with Item-Type = SF. Valid codes are listed in Volume GC2
of the AIRS User's Guide. Also make sure that you enter a value into field RSF EFFECTIVE DATE.
For MODIFY, you must either leave blank both this field and RSF EFFECTIVE DATE, or enter a value
for both fields.
Error Messages:
ERROR - CANNOT DELETE REQ-SAMPLING-FREQ
This field may not be deleted.
ERROR - INVALID REQ-SAMPLING-FREQ CODE
Sampling frequency must be one of the codes defined by the Item Type SF records of the GEO-
COMMON type E Description record.
ERROR - REQ-SAMPLING-FREQ CANNOT BE BLANK
You must enter a value for this field on an INSERT transaction or on a MODIFY transaction if
RSF EFFECTIVE DATE is valued.
ERROR - REQ-SAMPLING-FREQ MUST BE BLANK
If PARAMETER is not '81102*, this field must be blank.
December 1993
5-65
Transaction Type F3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.4.6 RSF EFFECTIVE DATE
The RSF EFFECTIVE DATE is the date on which the sampling frequency specified in REQ SAMPLING
FREQ became or will become effective. This field is linked to field REQ SAMPLING FREQ. If one
is specified, the other must also be specified.
Attributes: 6 digit date
Required on INSERT
Required on MODIFY if REQ SAMPLING FREQ valued
Prohibited on MODIFY if REQ SAMPLING FREQ blank
May not be DELETEd
Coding Instructions:
For INSERT, place a valid date in columns 48-53. A date is valid if it is a Gregorian date in the format
YYMMDD not falling before July 1, 1987 or the date the monitor began sampling, whichever is later,
and not falling after one year past the current date or the date the monitor ended sampling, whichever
is earlier.
For MODIFY, place a valid date in columns 48-53 only if field REQ SAMPLING FREQ is also present.
Error Messages:
ERROR - CANNOT DELETE RSF-EFF-DATE
This field may not be deleted.
ERROR - INVALID RSF-EFF-DATE
The date must be in the format YYMMDD and must be within the range specified above in
coding instructions.
ERROR - RSF-EFF-DATE CANNOT BE BLANK
This field must be present on INSERT transactions and on MODIFY transactions that also have
a value for REQ SAMPLING FREQ.
Transaction Type F3 5-66 December 2993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.4.7 SHORT TERM SCH SAT
This field indicates whether or not the monitor and monitoring area are part of the long term sampling
plan described in Part 58.13 of the monitoring regulation for 24-hour data. It applies only to PM-10
monitors. A value of 'N' indicates that the monitor and monitoring area have not yet satisfied the short-
term sampling schedule. This field is linked to SHORT TERM COMP DATE.
Attributes: 'Y' or 'N'
Required on INSERT for PM-10
Optional on MODIFY for PM-10
Prohibited for non-PM-10 monitors
May not be DELETEd
Coding Instructions:
To INSERT, place a 'Y' or *N' in column 54.
To MODIFY, place a 'Y' or 'N' in column 54, or leave column 54 blank to leave the field in the
database unchanged.
If you give this field the value 'Y', you must also give a value to field SHORT TERM COMP DATE.
Error Messages:
ERROR - CANNOT DELETE SHORT-TERM-SCH
This field may not be deleted.
ERROR - INVALID SHORT-TERM-SCH
Only'Y1 or'N* is allowed.
ERROR - SHORT-TERM-SCH CANNOT BE BLANK
This field is required for PM-10 INSERT transactions.
ERROR - SHORT-TERM-SCH NOT ALLOWED
This field is allowed only on PM-10 monitors.
WARNING - CANNOT VERIFY SHORT-TERM-SCH
If PARAMETER is not valid, it cannot be determined if this field is required or prohibited.
December 1993
5-«7
Transaction Type F3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.4.8 SHORT TERM COMP DATE
This field is used to specify the date when the PM-10 monitor and monitoring area satisfied the Part
58.13 short term sampling schedule. This field is linked to SHORT TERM SCH SAT.
Attributes: 6 digit date
Required if SHORT TERM SCH SAT = *Y*
Prohibited if SHORT TERM SCH SAT * 'Y
May not be DELETEd
''
Coding Instructions:
If SHORT TERM SCH SAT - 'Y*, place a valid date in columns 55-60. A date is valid if it is a
Gregorian date in the format YYMMDD that falls on or after July 1, 1987 or the date the monitor began
sampling, whichever is later, and not falling after one year past the current date or the date the monitor
ended sampling, whichever is earlier.
Error Messages:
ERROR - CANNOT DELETE SHORT-TERM-DATE
This field may not be deleted.
ERROR - INVALID SHORT-TERM-DATE
This date must be in the format YYMMDD and must be within the range specified above in
coding instructions.
ERROR - SHORT-TERM-DATE CANNOT BE BLANK
This field is required when SHORT TERM SCH SAT = 'Y'.
ERROR - SHORT-TERM-DATE NOT ALLOWED
This field is prohibited when SHORT TERM SCH SAT * 'Y'.
WARNING - CANNOT VERIFY SHORT-TERM-DATE
If SHORT TERM SCH SAT = 'Y' and PARAMETER is invalid, it cannot be determined if this
field is required or prohibited.
Transaction Type F3 S-6& December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.4.9 FIRST EXCEED CORRECTION
This field is used to indicate whether or not a correction is needed to the calculation of estimated
exceedances (see 40 CFR 50.6).
Attributes: *Y' or *N'
Required on INSERT for PM-10
Optional on MODIFY for PM-IO
Prohibited for non-PM-10
May not be DELETEd
Coding Instructions:
To INSERT, place a 'Y' or 'N' in column 61.
For MODIFY transactions, 'Y', 'N', and blank are allowed.
Error Messages:
ERROR - CANNOT DELETE F1RST-EXCEED-COR
This field may not be deleted.
ERROR - FIRST-EXCEED-COR CANNOT BE BLANK
This field is required on PM-10 INSERT transactions.
ERROR - FIRST-EXCEED-COR NOT ALLOWED
This field is allowed only on PM-10 transactions.
ERROR - INVALID FIRST-EXCEED-COR
Only 'Y' and 'N' are allowed on INSERT transactions, and only 'Y', 'N', and blank are allowed
on MODIFY transactions.
WARNING - CANNOT VERIFY FIRST-EXCEED-COR
If PARAMETER is not valid, it cannot be determined if this field is required or prohibited.
December 1993
5-69
Transaction Type F3
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
5.5 Transaction Type F4 - MONITOR COMMENTS (Line 1)
This transaction has just one field, and it is validated for INSERT and MODIFY transactions. (DELETE
is not a valid action for type F4 transactions.) If there are no MONITOR COMMENTS, do not submit
this transaction.
5.5.1 MONITOR COMMENTS
MONITOR COMMENTS is a free-format field that may be used in any way. It is normally used to
describe special features of the monitor.
*
Attributes: 62 character field
Optional
Coding Instructions:
To INSERT or MODIFY MONITOR COMMENTS, place the appropriate text in columns 17-78.
To DELETE existing MONITOR COMMENTS, fill columns 17-78 with asterisks on a MODIFY
transaction. (Be sure all columns are filled, or else the asterisks will be stored in the Site File as the
MONITOR COMMENTS.)
If there are no MONITOR COMMENTS, do not submit this transaction.
Error Messages:
ERROR - ALL FIELDS BLANK ON MODIFY
For a MODIFY transaction, MONITOR COMMENTS is a required field (since it is the only
field), and cannot be blank.
ERROR - MONITOR-COMMENT CANNOT BE BLANK
For an INSERT transaction, MONITOR COMMENTS cannot be blank.
Transaction Type F4 5-70 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
5.6 Transaction Type F5 - MONITOR COMMENTS (Line 2)
This transaction has just one field, and it is validated for INSERT and MODIFY transactions. (DELETE
is not a valid action for type F5 transactions.) If there are no MONITOR COMMENTS, do not submit
this transaction.
5.6.1 MONITOR COMMENTS
MONITOR COMMENTS As a free-format field that may be used in any way. It is normally used to
describe special features of the monitor.
Attributes:
62 character field
Optional
Coding Instructions:
To INSERT or MODIFY MONITOR COMMENTS, place the appropriate text in columns 17-78.
To DELETE existing MONITOR COMMENTS, fill columns 17-78 with asterisks on a MODIFY
transaction. (Be sure all columns are filled, or else the asterisks will be stored in the Site File as the
MONITOR COMMENTS.)
If there are no MONITOR COMMENTS, do not submit this transaction.
Error Messages:
ERROR - ALL FIELDS BLANK ON MODIFY
For a MODIFY transaction, MONITOR COMMENTS is a required field (since it is the only
field), and cannot be blank.
ERROR - MONITOR-COMMENT CANNOT BE BLANK
For an INSERT transaction, MONITOR COMMENTS cannot be blank.
December 1993
5-71
Transaction Type F5
-------
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.0 SLAMS Transactions (M, N, P, R, S, T, U, and V)
Air Quality monitoring sites that are part of the State and Local Air Monitoring System (SLAMS) are
required to submit each year a summary of their measurements of criteria pollutants. The summary
information is stored in the SLAMS File of the AIRS database, where each record holds the summary
data reported by a SLAMS monitor for a given year.
The "SLAMS transactions", AIRS transaction types M-P and R-V, are used to store and update the
information in the SLAMS File. Because different kinds of information must be reported for each criteria
pollutant, there is a different AIRS transaction type for each one. Another AIRS transaction type (V)
supplies information that is common to all but one of the criteria pollutants (lead). The N transaction
supplies information about exceedances of paniculate matter air quality standards. The following table
lists the transaction types used for each pollutant. No other AIRS transaction types update the SLAMS
File.
Transaction Type Parameter
Primary Secondary Code
M
P
R
S
T
U
N,V
V
V
V
V
(none)
11101/81102
42401
42101
42602
44201
12128
Pollutant Name
TSP or PM-10
Sulfur Dioxide
Carbon Monoxide (CO)
Nitrogen Dioxide
Ozone (03)
Lead
The pairs of SLAMS transactions, consisting of a primary (M, P, R, S, or T) transaction and secondary
(V) transaction for the same monitor-ID, year, and sampling interval, usually must be coded and validated
together. To load new SLAMS data or to change existing SLAMS data, both transactions of a pair must
be coded (except for lead). If there were any PM exceedances, one or more N transactions must be
coded with the M and V transactions. To change existing carbon monoxide SLAMS data, for example,
you must code a type R transaction and a type V transaction for the same monitor-ID, year, and sampling
interval. To change existing SLAMS data for a TSP monitor that had exceedances, you must code type
M, N, and V transactions. Even if you are changing just one field of an existing SLAMS record, you
must code all the required fields on all the transactions for that monitor-year. In effect, you cannot
change just one field; you must replace the entire record.
Pairs of INSERT transactions (action code = T) are used to load new data into the SLAMS File. The
values coded on a pair of INSERT transactions are used to create a new record in the SLAMS File.
December 1993
6-1
SLAMS Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
Pairs of MODIFY transactions (action code = *M') are used to change existing data in the SLAMS File.
The values coded on a pair of MODIFY transactions replace the corresponding values in a SLAMS
record. Since nearly all fields of the SLAMS transactions are required, it is generally not possible to
insert or delete individual fields of an existing SLAMS record with MODIFY transactions.
DELETE transactions (action code = 'D') are used to delete entire SLAMS records. Unlike the other
two action codes, a single primary transaction type is used to delete a SLAMS record. The N and V
transaction types are not used for deleting; action code 'D' is not allowed on N and V transactions.
SLAMS transactions have essentially no effect on other types of AIRS transactions in a screening file.
Altering a SLAMS transaction affects only the other SLAMS transaction with which it is paired. SLAMS
transactions can be affected by site transactions (types Al - A7) and monitor transactions (types Fl - F5)
that have the same site-ID or monitor-ID as the SLAMS transactions. In that case, altering a site or
monitor transaction may affect the edit level of the SLAMS transactions in the same screening file.
The type M transaction contains Total Suspended Paniculate (TSP) or PM-10 data in the following fields:
INT (interval)
UNITS
YEAR
DP (decimal position)
WEIGHTED ARITH MEAN (weighted arithmetic mean)
SUM GRIT (summary criteria)
SAMPLING DATA
The type N transaction contains Total Suspended Paniculate (TSP) or PM-10 data in the following fields:
INT (interval)
UNITS
YEAR
EX OCC (exceedance occurrence)
DP (decimal position)
EXCEEDANCE VALUE } 6 occurrences
EXCEEDANCE DATE } 6 occurrences
SLAMS Transactions 6-2 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
The type P transaction contains Sulfur Dioxide (SCy data in the following fields:
INT (interval)
UNITS
YEAR
OBS-1HR (observation 1 hour)
OBS-24HR (observation 24 hour)
DP (decimal position)
24-HOUR: FIRST MAX (first maximum value)
DATE (of FIRST MAX)
SEC MAX (second maximum value)
DATE (of SEC MAX)
3-HOUR: FIRST MAX ( first maximum value)
TIME (of FIRST MAX)
SEC MAX (second maximum value)
TIME (of SEC MAX)
3-HOUR EXCEEDANCE
24-HOUR EXCEEDANCE
ARITHMETIC MEAN
SUM CRTT (summary criteria flag)
The type R transaction, contains carbon monoxide (CO) data in the following fields:
INT (interval)
UNITS
YEAR
OBS-1HR (observation 1 hour)
DP (decimal position)
1-HOUR: FIRST MAX (first maximum value)
TIME (of FIRST MAX)
SEC MAX (second maximum value)
TIME (of SEC MAX)
8-HOUR: FIRST MAX (first maximum value)
TIME (of FIRST MAX)
SEC MAX (second maximum value)
TIME (of SEC MAX)
1-HOUR EXCEEDANCE
8-HOUR EXCEEDANCE
December 1993
6-3
SLAMS Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
The type S transaction contains nitrogen dioxide (NO;) data in the following fields:
INT (interval)
UNITS
YEAR
OBS-1HR (observation 1 hour)
OBS-24HR (observation 24 hour)
DP (decimal position)
1-HOUR: FIRST MAX (first maximum value)
TIME (of FIRST MAX)
SEC MAX (second maximum value)
TIME (of SEC MAX)
24-HOUR: FIRST MAX (first maximum value)
DATE (of FIRST MAX)
SEC MAX (second maximum value)
DATE (of SEC MAX)
ARITHMETIC MEAN
SUM CRTT (summary criteria flag)
The type T transaction contains ozone (O3) data in the following fields:
INT (interval)
UNITS
YEAR
OBS-1HR (observation 1 hour)
DP (decimal position)
1-HOUR: FIRST MAX (first maximum value)
TIME (of MAX value)
SEC MAX (second maximum value)
TIME
THIRD MAX (third maximum value)
TIME
FOURTH MAX (fourth maximum value)
TIME
1-HR EXCEEDANCE
The type U transaction contains lead (Pb) data in the following fields:
INT (interval)
UNITS
YEAR
METHOD (5 occurrences)
DP (decimal position)
NO. OF SAMPLES (number of samples) }
ARITH MEAN (arithmetic mean) } for each of four quarters
SUM CRIT (summary criteria flag) }
SLAMS Transactions 6-4 December 1993
-------
AIRS User's Quick
Volume AQ2
Air Quality Data Coding
The type V transaction contains additional SLAMS method and frequency data in the following fields:
INT (interval)
YEAR
METHOD (5 occurrences)
FREQUENCY (9 occurrences)
EXC FLAG (exceptional events flag)
The following error messages pertain to the SLAMS transactions:
ERROR - ACTION CODES DO NOT MATCH ON SLAMS RECORDS
The action code of an N or V transaction and its corresponding M, P, R, S, or T transaction
must agree.
ERROR - ALL SLAMS INVALID DUE TO DUPLICATE "V"
The first SLAMS transaction of a pair is valid, but there are duplicate type V transactions.
ERROR - ALL SLAMS RECORDS NOT VALID
The first SLAMS transaction of a pair is valid, but the second transaction, type V, is invalid.
ERROR - ATTEMPT TO ADD SLAMS DATA FOR AN EXISTING SLAMS
Data already exists in the SLAMS File for the monitor-ID and year specified on an INSERT
transaction. To add values to an existing SLAMS record, it may be possible to use a MODIFY
transaction; however, very few SLAMS fields can be added and most fields are required even
on a MODIFY transaction. Verify that the monitor-ID and year are correct.
ERROR - ATTEMPT TO CHANGE SLAMS DATA THAT DOES NOT EXIST
The data identified by monitor-ID and year on a MODIFY transaction does not exist in the
SLAMS File. Verify that the monitor-ID and year are correct.
ERROR - ATTEMPT TO DELETE SLAMS DATA THAT DOES NO*T EXIST
The data identified by monitor-ID and year on a DELETE transaction does not exist in the
SLAMS File. Verify that the monitor-ID and year are correct.
ERROR - CANNOT ADD DATA FOR MONITOR BEING DELETED
There is an Fl DELETE transaction for the same monitor-id as the current INSERT.
December 1993
6-5
SLAMS Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR - CANNOT MODIFY DATA FOR MONITOR BEING DELETED
There is an Fl DELETE transaction for the same monitor-id as the current MODIFY.
ERROR - DUPLICATE RECORDS
There are two or more transactions with the same monitor, year, and transaction type.
ERROR - MONITOR WAS NOT NAMS OR SLAMS FOR THIS YEAR
The monitor was not a NAMS or SLAMS monitor for the year indicated on this
transaction.
ERROR - NOT AUTHORIZED FOR THIS MONITOR
Each monitor-ID is associated with a group of screening files (those whose names are the
same except in the last two positions). The association, or "ownership", is established
when the monitor is inserted into the Site File or when an unassociated monitor is
changed by Site or Monitor transactions (types Al - F5). Once the association is
established, all transactions involving the monitor must be in a screening file of the group
that "owns" the monitor. This error message means that the screening file group does
not have ownership of the monitor-ID on the SLAMS transaction. Either the wrong
monitor-ID was coded, or a different screening file must be used for the transaction in
question.
ERROR - PREVIOUS SLAMS CARD MISSING OR INVALID
The V transaction of a pair of SLAMS transactions is present and valid, but the
corresponding M, N, P, R, S, or T transaction is missing or is invalid.
ERROR - REQUIRED "V" TRANSACTION MISSING
The first SLAMS transaction of a pair is valid, but the corresponding V transaction is
missing.
SLAMS Transactions 6-6 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.1 Common Fields
The fields described in this section are present on all the types of SLAMS transaction. Also, see Chapter
3, which describes fields that are common to all transaction types.
6.1.1 PARAMETER
PARAMETER is a five-digit code that identifies the pollutant being measured and/or analyzed by the
monitor.
Attributes:
5 digit code
Required
Coding Instructions:
In columns 11-15, enter a valid PARAMETER code from the following list:
Transaction Type Parameter
M
N
P
R
S
T
U
V
11101 (TSP) or 81102 (PM-10)
11101 (TSP) or 81102 (PM-10)
42401 (S02)
42101 (CO)
42602 (NOj)
44201 (O3)
12128 (Pb)
11101,42101,42401,
42602, 44201, or 81102
Error Message:
ERROR - INVALID PARAMETER CODE
PARAMETER must be in the list above.
December 1993
6-7
SLAMS Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.1.2 POC (Parameter Occurrence Code)
POC is a code used to distinguish between different monitors at one site that are measuring the same
parameter. For example, the first monitor established to measure CO at a site would have POC = T.
If an additional monitor were established at the same site to measure CO, that monitor would have POC
= '2'. However, if a new instrument were installed to replace the original instrument used as the first
monitor, that would be the same monitor and it would have POC = T, even if there were a change in
sampling method or interval.
Attributes: 1 digit code
Required
Coding Instructions:
In column 16, enter a valid POC in the range 1 through 9.
Error Message:
ERROR - INVALID POC CODE
POC is a required field. It must be numeric in the range 1-9.
SLAMS Transactions 6-8 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.1.3 Monitor Identification Code (Monitor-ID)
The monitor-ID identifies the monitor to which a transaction applies. It is comprised of the STATE,
COUNTY, SITE, PARAMETER, and POC fields.
Attributes:
Coding Instructions:
15 digit code
Required
Place a valid monitor-ID in columns 2-16. A monitor-ID is valid if it is in the AQ Site File. You can
obtain a list of monitor-IDs with several standard batch retrieval reports of the Air Quality Subsystem,
described in Volume AQ4 of the User's Guide. When coding a monitor-ID ensure that columns 2-3
contain a valid STATE, 4-6 a valid COUNTY, 7-10 a valid SITE, 11-15 a valid PARAMETER, and 16
a valid POC.
Error Messages:
ERROR - INVALID MONITOR-ID
The monitor-ID is not in the Site File.
December 1993
6-9
SLAMS Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.2 Transaction Type M - SLAMS Paniculate Information
This transaction applies only to PM-10 (81102) or TSP (11101) monitors.
The coding form for the M transaction is shown in Figure 6-1.
The fields listed below are validated for INSERT (I) and MODIFY (M) transactions and each field must
have a non-blank value.
INT (interval)
UNITS
YEAR
DP (decimal position)
WEIGHTED ARTTH MEAN (weighted arithmetic mean)
SUM CRTT (summary criteria flag)
SAMPLING DATA (first occurrence required)
Individual fields may not be deleted.
None of these fields is validated on DELETE transactions.
Error Messages:
ERROR - ALL DATA FIELDS ARE BLANK
An INSERT or MODIFY transaction has no value for any of these fields.
Transaction Type M 6-10 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
o
»sr
, a i£_
4-H-
£
a
3 »
§ I
51 1
MiSPP:
s!l
-s
sn
I!
Hi
2
S
%
!!
i!
f!3
arn*
I!
iS a. Si
ill
S!
a
3
Figure 6-1. Coding Form for Transaction Type M - SLAMS TSP/PM-10 Data
December 1993
6-11
Transaction Type M
-------
1
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.2.1 INT (Interval)
INT indicates the sampling interval used for the monitoring activities.
Attributes: 1 character code
Required
Coding Instructions:
For TSP monitors (11101), the only allowed interval is '7* (24-hour). For PM-10 monitors (81102), the
only allowed intervals are '7' (24-hour) or T (1-hour). Place the appropriate code in column 17.
Error Messages:
ERROR - INVALID INTERVAL
TSP monitors may have only interval '7'. PM-10 monitors may have only interval '7' or T.
WARNING - CANNOT VERIFY INTERVAL
The validity of interval code T cannot be determined if PARAMETER is not valid.
Transaction Type M 6-12 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.2.2 UNITS
UNITS indicates the dimensional system in which a parameter concentration is expressed.
Attributes: 3 character code
Requited
Coding Instructions:
Place '001' in columns 18-20. Units code '001' (micrograms/cu. m.) is the only value allowed on M
transactions.
Error Messages:
ERROR - INVALID UNITS
Only code '001' is allowed.
December 1993
6-13
Transaction Type M
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.2.3 YEAR
YEAR contains the last two digits of the year for which PM-10 data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 21-22, enter a valid year between 1981 and the current year.
Error Message:
ERROR - INVALID YEAR
YEAR is not in the range 81 through the current year.
Transaction Type M 6-14 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.2.4 DP (Decimal Position)
DP is the decimal place indicator for Paniculate Matter M transactions. It indicates the number of digits
to the right of the implied decimal point in fields containing concentration observations.
Attributes:
1 digit numeric
Required
Coding Instructions:
Place a '0* or T in column 23.
Error Messages:
ERROR - INVALID DECIMAL-POSITION
The only allowed decimal position indicators on M transactions are '0' and T.
December 1993
6-15
Transaction Type M
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.2.5 WEIGHTED ARTTH MEAN (Weighted Arithmetic Mean)
WEIGHTED ARTTH MEAN is the ?rithmetic mean of the observed paniculate concentrations for the
year (including exceptional events). One half of the minimum detectable is substituted for observations
below the minimum detectable when computing the mean.
Attributes: 4 digit numeric
Required
Coding Instructions:
Place the arithmetic mean (adjusted for decimal position DP) in columns 24-27. The mean must be
greater than zero.
Error Messages:
ERROR - INVALID ARITH-MEAN
The mean must be numeric and greater than zero.
Transaction Type M 6-16 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.2.6 SUM CRIT (Summary Criteria Flag)
This field indicates whether or not enough observations were made during the year to satisfy the AIRS
summary criteria. Exceptional events data are included.
Quarterly PM-10 data is valid if:
1) at least 75% of the scheduled observations are present
2) the minimum sampling frequency code is not *0'
3) the minimum sampling frequency is not greater than the required sampling frequency
If the sampling frequency for the entire quarter is random or stratified random, the following conditions
apply:
1) at least 75% of the scheduled observations are present
2) the number of scheduled observations is greater than the number that would be generated
by the required systematic sampling schedule
Yearly data is valid if each quarter's data is valid.
Attributes: 1 digit code
Required
Coding Instructions:
If the data is valid, place a T in column 28; otherwise, place a '0' in column 28.
Error Messages:
ERROR - INVALID SUM-CRITERIA
Only the values *0' and T are allowed.
December 1993
6-17
Transaction Type M
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.2.7 SAMPLING DATA
These fields are used to provide information about the various sampling frequencies that were used during
the year. As many as four sampling frequencies may be recorded for the year. Each occurrence has the
fields:
SF (sampling frequency)
OBS-24HR (observation 24 hour)
ADD SAMP DAYS (additional sampling days)
DATE SF BEGAN (date sampling frequency began)
The first occurrence must be valued, and subsequent occurrences must be filled consecutively and
chronologically (i.e., occurrence "i" must be filled before occurrence "i+1" and the date in occurrence
"i" must fall before the date in occurrence "i+l").
If the first occurrence has the value 'M' for SF, then the remaining three occurrences must be blank.
Use the code 'M' if sampling frequency changed more than four times during the year.
Error Messages:
ERROR - SAMPLING-DATA CANNOT BE BLANK
The first occurrence of these fields must be valued, and there cannot be any blank gaps between
valued occurrences.
ERROR - SAMPLING-DATA NOT ALLOWED
The last three occurrences must be blank if the first sampling frequency is 'M'.
Transaction Type M 6-18 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.2.7.1 SF (Sampling Frequency)
Each occurrence specifies the sampling frequency that was in effect for a portion of the year.
Attributes: 1 character code
First occurrence required
Subsequent occurrences optional
Coding Instructions:
Place a valid code in the appropriate occurrence (column 29, 40, 51, and/or 62). A code is valid if it
appears in an AIRS GEO-COMMON File type E Description record with Item Type = SF. Valid codes
are listed in Volume GC2 of the AIRS User's Guide. There are two exceptions:
1) Although 'S' appears in the GEO-COMMON File, it is not allowed here.
2) The code 'M' is valid in the first occurrence, although it does not appear in the GEO-
COMMON File.
Error Messages:
ERROR - INVALID SAMPLING-FREQ CODE
A valid code is either 'M' in the first occurrence or a code other than 'S' that appears in a GEO-
COMMON File type E Description record with Item Type = SF.
ERROR - SAMPLING-FREQ CANNOT BE BLANK
The first occurrence must be valued. Other occurrences must be valued if any other field in an
occurrence of the group is valued.
December 1993
6-19
Transaction Type M
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.2.7.2 OBS-24HR (Observation 24 Hour)
This field gives the number of observations recorded by the monitor under a given sampling frequency.
Attributes: 3 digit numeric
First occurrence required
Last three occurrences optional
Coding Instructions:
Place the number of observations associated with the corresponding sampling frequency in columns 30-
32, 41-43, 52-54, and/or 63-65. The first occurrence is required. The last three occurrences are
required only if associated fields are valued.
A number of observations is valid if it is a positive integer less than or equal to the number of days the
associated sampling frequency was in effect. The number of days a sampling frequency was in effect is
based on the current and next occurrences of DATE SF BEGAN. If there is no next occurrence of
DATE SF BEGAN, the end of the period is assumed to be 31 December.
Error Messages:
ERROR - INVALID OBSER-24HR
This field must be a positive integer less than or equal to the number of days the associated
sampling frequency was in effect.
ERROR - OBSER-24HR CANNOT BE BLANK
The first occurrence is required. Subsequent occurrences are required if other fields in the same
occurrence of the group are valued.
WARNING - CANNOT VERIFY OBSER-24HR
If the current or next occurrence of DATE SF BEGAN is invalid, the maximum allowed value
of OBS-24HR cannot be determined.
Transaction Type M 6-20 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.2.7.3 ADD SAMP DAYS (Additional Sampling Days)
This field indicates the number of extra samples taken beyond those indicated by the associated sampling
frequency.
Attributes: 3 digit numeric
First occurrence required
Last three occurrences optional
Coding Instructions:
Place a valid integer in columns 33-35, 44-46, 55-57, and/or 66-68. An integer is valid if it is zero or
a positive integer less than or equal to OBS-24HR. The first occurrence is required. The last three
occurrences are required only if associated fields are valued.
Error Messages:
ERROR - ADD-SAMP-DAYS CANNOT BE BLANK
The first occurrence must be valued. Subsequent occurrences are required if other fields in the
occurrence of the group are valued.
ERROR - INVALID ADD-SAMP-DAYS
This field must be an integer less than or equal to OBS-24HR.
WARNING - CANNOT VERIFY ADD-SAMP-DAYS
If OBS-24HR is invalid, the maximum value of this field cannot be determined.
December 1993
6-21
Transaction Type M
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.2.7.4 DATE SF BEGAN (Date Sampling Frequency Began)
This field gives the date the associated sampling frequency became active. The end of the active period
for this sampling frequency is either the day before the date in the next occurrence of this field or 31
December, if there is no next occurrence.
Attributes: 4 digit numeric
First occurrence required
Last three occurrences optional
Coding Instructions:
Place a valid month and day value with the form MMDD in columns 36-39, 47-50, 58-61, and/or 69-72.
Month must be in the range 01-12. Day must be from 01 to the number of days in the month.
Combined with YEAR, the indicated date may not be earlier than the date the monitor began sampling
or January 1, 1981, whichever came last. Similarly, the date may not be later than the date the monitor
ceased operating or the current date, whichever came first.
If there is more than one occurrence of this group, the dates associated with each of the groups must be
unique and in chronological order.
Error Messages:
ERROR - DATE-SAMP-FREQ CANNOT BE BLANK
The first occurrence must be valued. Subsequent occurrences are required if their associated
fields in that group occurrence are valued.
ERROR - DATE-SAMP-FREQ OUT OF ORDER
The various valued occurrences must be in chronological order.
ERROR - DUPLICATE DATE-SAMP-FREQ
Sampling frequency start dates may not be duplicated.
ERROR - INVALID DATE-SAMP-FREQ
When combined with YEAR, this date must fall within the narrowest range defined by January
1, 1981 or the monitor start date and the monitor end date or the current date.
WARNING - CANNOT VERIFY DATE-SAMP-FREQ
If YEAR is invalid, no date range check can be made.
Transaction Type M 6-22 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.3 Transaction Type N - SLAMS Paniculate Exceedances
This transaction applies only to PM-10 (81102) or TSP (11101) monitors.
The coding form for the N transaction is shown in Figure 6-2.
Type N transactions are used to provide up to ten TSP exceedances or up to 60 PM-10 exceedances for
a given monitor year. Field EX OCC (exceedance occurrence) is used to differentiate among the various
occurrences of the transaction for one monitor year.
The fields listed below are validated for INSERT (I) and MODIFY (M) transactions and each field must
have a non-blank value.
INT (interval^
UNITS
YEAR
EX OCC (exceedance occurrence)
DP (decimal position)
EXCEEDANCE DATA - 6 occurrences of:
EXCEEDANCE VALUE
EXCEEDANCE DATE
Individual fields may not be deleted using asterisks on a MODIFY transaction, and the DELETE (D)
action code is not allowed for the N transaction.
If more than one transaction is required for a given set of exceedances, then the exceedances should be
densely packed into the transactions. No single transaction should have a valued occurrence of
EXCEEDANCE DATA to the right of an unvalued occurrence. Similarly, if there are "k" transactions,
the first "k-1" transactions must have values for all six occurrences of EXCEEDANCE DATA on each
transaction.
Error Messages:
ERROR - ALL DATA FIELDS ARE BLANK
An INSERT or MODIFY transaction has no value for any of the fields listed above.
December 1993
6-23
Transaction Type N
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
5 I
«h D
8« =
S
l!
S
«
u
»l
*
f
u
k
u
tf
s
\
I
u
t
*
Ui
^
u
\
4
it
u
£
Ui
«•)
B
\
I
Ul
u
M
f.
Ul
u
<
s
Ul
x
Ul
v
Ul
U
$
H
S3
x
Ul
I
»
^ %
A
!
j V{
' ?
1 *
t
i ?
! *^
4
ft!
A
«3
5
1H
ft
HI
3
5
JS
a
s
B
a
S
4
*
riO
i
••
>•«
$
»
1
> i
s 5
Mil
ill
I1'
Z
ii
£J
ZJ
2T
Cl
fl
»
1
*
«
i
i
i
i
i
»
<
i
.
1
1
1
i
•
i
i
i
•
t
f
x \
•
t
i
1
i
•
2
t
.
i
J
1
1
1
1
1
1
1
1
i
I
1
1
I
|
1
1
1
,
I
•
'
I
'
i
J
^
I
r
!
li
£8suS-5
> a. o i <
i °-
z
•o
3
Figure 6-2. Coding Form for Transaction Type N - SLAMS TSP/PM-10 Exceedances
Transaction Type N
6-24
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.3.1 INT (Interval)
INT indicates the sampling interval used for the monitoring activities.
Attributes: 1 character code
Required
Coding Instructions:
For TSP monitors (11101), the only allowed interval is '7* (24-hour). For PM-10 monitors (81102), the
only allowed intervals are '7' (24-hour) or T (1-hour). Place the appropriate code in column 17.
Error Messages:
ERROR - INVALID INTERVAL
TSP monitors may have only interval '7'. PM-10 monitors may have only intervals '7' or T,
WARNING - CANNOT VERIFY INTERVAL
The validity of interval code T cannot be determined if PARAMETER is not valid.
December 1993
6-25
Transaction Type N
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.3.2 UNITS
UNITS indicates the dimensional system in which a parameter concentration is expressed.
Attributes: 3 digit code
Required
Coding Instructions:
PJace '001' in columns 18-20. Units code '001' (micrograms/cu. m.) is the only value allowed on N
transactions.
Error Messages:
ERROR - INVALID UNITS
Only code '001' is allowed.
Transaction Type N 6-26 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.3.3 YEAR
YEAR contains the last two digits of the year for which PM-10 data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 21-22, enter a valid year between 1981 and the current year.
Error Message:
ERROR - INVALID YEAH
YEAR is not in the range 81 through the current year.
December 1993
6-27
Transaction Type N
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.3.4 EX OCC (Exceedance Occurrence)
Since more exceedances may be reported than can fit on one card, this field is used to differentiate among
the various occurrences of the transaction. It is simply an integer that indicates whether a particular
transaction is the first, second, third, etc., for a particular monitor year.
Attributes: 2 digit numeric
Required
Coding Instructions:
Place the appropriate transaction occurrence number in columns 23 and 24, right justified and zero filled.
Since TSP is limited to ten exceedances, the only allowed values for this field are '01' and "02'.
Since PM-10 monitors may report up to 60 exceedances, the allowed values are *01* through '10'.
Numbers should be used in order, i.e., 01, 02, 03, etc.
Error Messages:
ERROR - INVALID EXCEED-OCCUR
Valid values for TSP are '01' and '02'. Valid values for PM-10 are '01' through '30'. Numbers
must be used in sequence.
WARNING - CANNOT VERIFY EXCEED-OCCUR
If PARAMETER is not valid, the allowed range for this field cannot be determined.
Transaction Type N 6-28 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
o
6.3.5 DP (Decimal Position)
DP is the decimal place indicator for Paniculate Matter N transactions. It indicates the number of digits
to the right of the implied decimal point in fields containing exceedances.
Attributes: 1 digit numeric
Required
Coding Instructions:
Place a *0' or T in column 25.
Error Messages:
ERROR - INVALID DECIMAL-POSITION
The only allowed decimal position indicators on N transactions are *0' and T.
December 1993
6-29
Transaction Type N
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.3.6 EXCEEDANCE DATA
This group of fields is used to provide the values of exceedances and their dates of occurrence for a
monitor year. Each N transaction has space for six occurrences of the group. Within one transaction,
no valued occurrence of this group may appear to the right of an unvalued occurrence, and only the last
N transaction for a monitor year may have unvalued occurrences of the group.
At least one occurrence (the first) is required.
Error Messages:
ERROR - EXCEED-DATA CANNOT BE BLANK
No single N transaction may have a valued occurrence of EXCEEDANCE DATA after a blank
occurrence, and only the last N transaction for a monitor year may have blank occurrences of
EXCEEDANCE DATA.
ERROR - EXCEED-DATA NOT ALLOWED
For TSP, a maximum of ten exceedances are reported. Therefore, the last two occurrences of
EXCEEDANCE DATA cannot be valued on a transaction having PARAMETER = '11101' and
EXCEED OCCUR = '0/2*.
WARNING - CANNOT VERIFY EXCEED-DATA
If PARAMETER is not valid and EXCEED OCCUR - '0/2', it cannot be determined whether
non-blank values are allowed or prohibited in the last two occurrences of EXCEEDANCE
DATA.
Transaction Type N 6-30 December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
6.3.6.1 EXCEEDANCE VALUE
This field is used to provide a single exceedance value.
Attributes: 4 digit numeric
First occurrence required
Subsequent occurrences optional
Coding Instructions:
Place a valid exceedance, scaled to DP, as an integer (right justified and zero filled) in columns 26-29,
34-37, 42-45, 50-53, 58-61, and/or 66-69.
The actual value is represented by the expression:
EXCEED-VALUE / (10 ** DP)
and must exceed the national 24-hour primary or secondary standard for the parameter. These standards
are obtained from the appropriate GEO-COMMON File type J Standards record.
Error Messages:
ERROR - EXCEED-VALUE CANNOT BE BLANK
If the associated EXCEEDANCE DATE is valued, EXCEEDANCE VALUE must be valued.
ERROR - INVALID EXCEED-VALUE
An exceedance must be greater than either the primary or secondary standard for the parameter.
If parameter is invalid, the lesser of the standards for TSP and PM-10 is used for this test.
WARNING - CANNOT VERIFY EXCEED-VALUE
If DP is invalid, the comparison with the primary or secondary value cannot be done.
December 1993 6-31 Transaction Type N
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.3.6.2 EXCEEDANCE DATE
This field provides the date of the associated exceedance value.
Attributes: 4 digit date
First occurrence required
Subsequent occurrences optional
Coding Instructions:
Place a date in the format MMDD in columns 30-33, 38-41, 46-49, 54-57, 62-65, and/or 70-73. When
combined with YEAR, it must specify a valid Gregorian date that occurs no earlier than January 1, 1981
or the date the monitor began sampling, whichever came later. Similarly, the date may not be later than
the current date or the date the monitor stopped sampling, whichever is earlier.
Error Messages:
ERROR - EXCEED-DATE CANNOT BE BLANK
If the associated EXCEEDANCE VALUE is present, EXCEEDANCE DATE must also be
present.
ERROR - INVALID EXCEED-DATE
The date must fall between the sampling start and end dates for the monitor, but can be no earlier
than January 1, 1981 and no later than the current date.
WARNING - CANNOT VERIFY EXCEED-DATE
If YEAR is not valid, this field cannot be validated.
Transaction Type N 6-32 December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
6.4 Transaction Type P - SLAMS S02 Data
The P transaction is used to insert, modify, and delete sulfur dioxide data in the AQ SLAMS File. When
inserting or modifying data, the P transaction must be accompanied by a V transaction.
The coding form for the P transaction is shown in Figure 6-3.
All the fields of the P transaction are required for INSERT and MODIFY actions. For a DELETE
action, only the YEAR field is required (plus the common fields, monitor-ID, transaction type, and action
code).
Error Messages:
ERROR - ALL FIELDS BLANK ON MODIFY
This message occurs if all the P transaction fields are blank on a MODIFY transaction. Although
this condition is just as invalid for an INSERT, this message only occurs for a MODIFY (for
consistency with other transaction types).
December 1993 6-33 Transaction Type P
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
i &
§ 2
! !
i £
'•JS e
:S S
§15
£;»
»y<
zSfc
IIs
£y
i
l'
i8
i>
!!
i!i
!
' 'D t!
Sff
£
Figure 6-3. Coding Form for Transaction Type P - SLAMS SO, Data
Transaction Type P
6-34
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
6.4.1 INT (Interval)
INT indicates the sampling interval used for the monitoring activities.
Attributes: 1 character code
Required
Coding Instructions:
For 1-hour observations, enter T in column 17. For 24-hour observations, enter '7* in column 17. No
other intervals are permitted.
Error Messages:
ERROR - INTERVAL CODES DO NOT MATCH ON SLAMS RECORDS
The interval code (INT) on this transaction is different from the corresponding V transaction.
They must agree.
ERROR - INVALID INTERVAL
INT must be T or T.
December 1993 6-35 Transaction Type P
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
6.4.2 UNITS
UNITS indicates the dimensional system in which a pollutant concentration is expressed.
Attributes: 3 digit code
Required
Coding Instructions:
In columns 18-20, enter '007' (parts per million). No other units code is permitted.
Error Message:
ERROR - INVALID UNITS
The only valid value for UNITS is '007'.
Transaction Type P
6-36
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
6,4.3 YEAR
YEAR contains the last two digits of the year for which SO2 data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 21-22, enter a valid year between 1981 and the current year.
Error Message:
ERROR - INVALID YEAR
YEAR is not in the range 81 through the current year.
December 1993 6-37 Transaction Type P
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
6.4.4 OBS-1 HR (Observation 1 Hour)
OBS-1 HR represents the number of 1-hour SO2 observations made during the year.
Attributes: 4 digit numeric
Required for INT = 1
Prohibited for INT = 7
Coding Instructions:
If INT = 1, enter the number of 1-hour observations in columns 23-26.
If INT - 7, leave this field blank.
Error Messages:
ERROR - INVALID OBSER-1HR
If INT = I, OBS-1 HR must be numeric > 0.
If INT = 1 and YEAR represents a "leap" year, OBS-I HR must be numeric, > 0, and <, 8784.
If INT = 1 and YEAR represents a "non-leap" year, OBS-1HR must be numeric, > 0, and <_
8760.
ERROR - OBSER-1HR NOT ALLOWED
If INT = 7, OBS-1 HR must be blank.
WARNING - CANNOT VERIFY OBSER-1HR
If INT = 1, YEAR is invalid, and OBS-1 HR > 8760, this field cannot be checked.
Transaction Type P
6-38
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
6.4.5 OBS-24 HR (Observation 24 Hour)
OBS-24 HR represents the number of 24-hour observations made during the year.
Attributes: 3 digit numeric
Required for INT = 7
Prohibited for INT = 1
Coding Instructions:
If INT = 7, enter the number of 24-hour observations right justified in columns 27-29. The number
must be an integer > 0 and .<. 366.
If INT = 1, leave this field blank.
Error Messages:
ERROR - INVALID OBSER-24HR
For INT = 7, OBS-24 HR must be numeric > 0 and <. 366.
ERROR - OBSER-24HR NOT ALLOWED
For INT = 1, OBS-24 HR must be blank.
December 1993 6-39 Transaction Type P
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
6.4.6 DP (Decimal Position)
DP is the decimal position indicator for S02 values. It indicates the number of digits to the right of the
implied decimal point in each field containing a value of SO; concentration.
Attributes: 1 digit numeric
Required
Coding Instructions:
In column 30, enter a decimal position indicator of *2* or '3'. This allows for SO2 observations of 0.001
through 99.99. Use the DP value appropriate for the precision of the measurements. For example, if
the analytical procedure yields results that are valid to two decimal places, use DP = '2'.
Error Message:
ERROR - INVALID DECIMAI^POSITION
DP must be *2' or '3'.
Transaction Type P
6-40
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.4.7 24-HOUR FIRST MAX (24-Hour First Maximum)
24-HOUR FIRST MAX is the highest 24-hour value of S02 concentration for the year. If INT = 7 (24-
hour), then this is simply the highest value observed. If INT = 1 (1-hour) this is the highest 24-hour
midnight-to-midnight average of the hourly observations from those days with at least 18 observations.
In either case, exceptional events data are included in the calculations.
Attributes:
4 digit numeric
Required
Coding Instructions:
Enter the highest value for the year right justified in columns 31-34. Remember to allow for the implied
decimal point indicated by DP. The value must be greater than zero.
Error Message:
ERROR - INVALID MAX1-24HR
24-HOUR FIRST MAX must be numeric > 0.
December 1993
6-41
Transaction Type P
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.4.8 24-HOUR FIRST MAX DATE (24-Hour First Maximum Date)
24-HOUR FIRST MAX DATE is the month and day when the 24-HOUR FIRST MAX occurred.
Attributes: 4 digit date
Required
Coding Instructions:
In columns 35-38, enter the month and day of the 24-HOUR FIRST MAX in MMDD format. Remember
code two digits each for both month and day. Use a leading zero for each, as needed.
If the 24-HOUR FIRST MAX value occurred on more than one day in the year, enter the date of the first
occurrence in this field.
Error Message:
ERROR - INVALID DATE-MAX1-24HR
Month (MM) must be *OT through '12' and day (DD) must be two digits and valid for the given
month.
Transaction Type P 6-42 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.4.9 24-HOUR SEC MAX (24-Hour Second Maximum)
24-HOUR SEC MAX is the second highest 24-hour value of SO2 concentration for the year. It is derived
in a manner similar to 24-HOUR FIRST MAX.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the second highest 24-hour S02 value for the year right justified in columns 39^2. Remember to
allow for the implied decimal point indicated by DP.
If the highest 24-hour value for the year occurred on more than one day, enter that same value for 24-
HOUR SEC MAX.
Error Messages:
ERROR - INVALID MAX2-24HR
24-HOUR SEC MAX must be numeric > 0.
ERROR - MAX2-24HR > MAX1-24HR
24-HOUR SEC MAX must be < 24-HOUR FIRST MAX.
December 1993
6-43
Transaction Type P
-------
AffiS User's Guide
Air Quality Data Coding Volume AQ2
6.4.10 24-HOUR SEC MAX DATE (24-Hour Second Maximum Date)
24-HOUR SEC MAX DATE is the month and day when the 24-HOUR SEC MAX occurred.
Attributes: 4 digit date
Coding Instructions:
In columns 43-46, enter the month and day of the 24-HOUR SEC MAX in MMDD format. Remember
to code two digits each for month and day. Use a leading zero for each, as needed.
If the same value is coded for FIRST MAX and SEC MAX, enter the date of the second occurrence in
this field.
Error Message:
ERROR - INVALID DATE-MAX2-24HR
Month (MM) must be *01' through '12* and day (DD) must be two digits and valid for the given
month.
Transaction Type P 6-44 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.4.11 3-HOUR FIRST MAX (3-Hour First Maximum)
3-HOUR FIRST MAX is the highest 3-hour average value of SO2 concentration for the year. Eight 3-
hour averages are computed for each day using the 1-hour observations for hours 00-02, 03-05, 06-08,
and so on. All three 1-hour observations must be present to compute a 3-hour average. Exceptional
events data are included.
Attributes: 4 digit numeric
Required for INT = 1
Prohibited for INT = 7
Coding Instructions:
If INT = 1, enter the highest 3-hour SO; value for the year right justified in columns 47-50. The value
must be numeric > 0. Remember to allow for the implied decimal point indicated by DP.
For INT = 7, leave this field blank.
Error Messages:
ERROR - INVALID MAX1-3HR
For INT = 1, 3-HOUR FIRST MAX must be numeric > 0.
ERROR - MAX1-3HR NOT ALLOWED
For INT = 7, 3-HOUR FIRST MAX must be blank.
December 1993
6-45
Transaction Type P
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.4.12 3-HOUR FIRST MAX TIME (3-Hour First Maximum Time)
3-HOUR FIRST MAX TIME is the month, day, and third hour of the 3-hour time interval from which
3-HOUR FIRST MAX was derived.
Attributes: 6 digit date
Required for INT = 1
Prohibited for INT = 7
Coding Instructions:
If INT = 1, enter in columns 51-56 the month, day, and, hour of the 3-HOUR FIRST MAX in
MMDDHH format. For example, if hours 6, 7, and 8 on 5 January yielded the maximum 3-hour
average, 3-HOUR FIRST MAX TIME would be coded as '010508'.
If the 3-HOUR FIRST MAX value occurred more than once during the year, enter the date and time of
the first occurrence in this field.
If INT = 7, leave this field blank.
Error Messages:
ERROR - INVALID TIME-MAX1-3HR
For INT = 1, month (MM) must be '01' through '12', day (DD) must be valid for the given
month, and hour (HH) must be '00' through '23'.
ERROR - TIME-MAX1-3HR NOT ALLOWED
For INT ~ 7, this field must be blank.
Transaction Type P 6-46 December 1993
I
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.4.13 3-HOUR SEC MAX (3-Hour Second Maximum)
3-HOUR SEC MAX is the second highest 3-hour average value of SOj for the year. It is computed in
a manner similar to 3-HOUR FIRST MAX.
Attributes: 4 digit numeric
Required for INT = 1
Prohibited for INT = 7
Coding Instructions:
If INT = 1, enter the second highest 3-hour SOj value for the year right justified in columns 57-60.
Remember to allow for the implied decimal point indicated by DP. If the highest 3-hour value occurred
more than once during the year, enter the same value for this field as for 3-HOUR FIRST MAX.
If INT = 7, leave this field blank.
Error Messages:
ERROR - INVALID MAX2-3HR
For INT = 1, 3-HOUR SEC MAX must be numeric > 0.
ERROR - MAX2-3HR > MAX1-3HR
SEC MAX must be <. FIRST MAX.
ERROR - MAX2-3HR NOT ALLOWED
For INT = 7, 3-HOUR SEC MAX must be blank.
December 1993
6-47
Transaction Type P
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.4.14 3-HOUR SEC MAX TIME (3-Hour Second Maximum Time)
3-HOUR SEC MAX TIME is the month, day, and third hour of the three-hour time interval from which
3-HOUR SEC MAX was derived.
Attributes: 6 digit date
Required for INT = 1
Prohibited for INT - 7
Coding Instructions:
If INT = 1, enter in columns 61-66, the month, day, and hour of the 3-HOUR SEC MAX in MMDDHH
format. For example, if hours 9, 10, and 11 on 19 July yielded the second highest 3-hour average, 3-
HOUR SEC MAX TIME would be coded as '071911*. If the highest 3-hour value occurred more than
once during the year, enter the date and time of the second occurrence in this field.
If INT = 7, leave this field blank.
Error Messages:
ERROR - INVALID TIME-MAX2-3HR
For INT = 1, month (MM) must be *01' through '12', day (DD) must be valid for the given
month, and hour (HH) must be '00' through '23'.
ERROR - TIME-MAX2-3HR NOT ALLOWED
For INT = 7, 3-HOUR TIME must be blank.
Transaction Type P 6-48 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.4.15 3-HOUR EXCEEDANCE I
3-HOUR EXCEEDANCE is the number'of 3-hour average values that exceeded the SO2 secondary
standard during the year. Exceptional evepts data are included.
Attributes: 4 digit numeric '
Required for INT = 1
Prohibited for INT = 7 '
Coding Instructions:
If INT - 1, enter an integer value <_ 2920 right justified in columns 67-70. Enter zeros if there were
no exceedances.
If INT = 7, leave this field blank.
i
Error Messages: :
ERROR - EXCEED-3HR NOT ALLOWED
For INT = 7, 3-HOUR EXCEEbANCE must be blank.
ERROR - INVALID EXCEED-3HR
!
For INT = 1, 3-HOUR EXCEEDANCE must be numeric _<. 2920.
December 1993
6-49
Transaction Type P
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.4.16 24-HOUR EXCEEDANCE
24-HOUR EXCEEDANCE is the number of 24-hour values that exceeded the S02 primary standard
during the year. For INT = 1, the count is based on midnight-to-midnight averages. For INT = 7, the
count is based on the observed values. Exceptional events data are included.
Attributes: 3 digit numeric
Required
Coding Instructions:
In columns 71-73, enter a numeric value <. the value in OBS-24 HR for INT = 7. Enter a numeric
value <. 366 for INT = 1. Enter zero if there were no exceedances.
Error Message:
ERROR - INVALID EXCEED-24HR
This field must contain a valid numeric value, which may be zero. For INT = 7, 24-HOUR
EXCEEDANCE must be jC the value in OBS-24 HR. For INT = 1,24-HOUR EXCEEDANCE
must be < 366.
Transaction Type P 6-50 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.4.17 ARITHMETIC MEAN
ARITHMETIC MEAN is average of observed S02 values for the year. Exceptional events data are
included. One half of the minimum detectable value is substituted for those observations less than the
minimum detectable when computing the mean.
Attributes: 4 digit numeric
Required
Coding Instructions:
In columns 74-77, enter the arithmetic mean for SQ,. Do not forget to allow for the implied decimal
point indicated by DP.
Error Message:
ERROR - INVALID ARTTH-MEAN
ARITHMETIC MEAN must be numeric > 0.
December 1993
6-51
Transaction Type P
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.4.18 SUM CRTT (Summary Criteria Flag)
This field indicates whether or not enough observations were made during the year to satisfy the AIRS
summary criteria. Exceptional events data are included.
Attributes: 1 digit code
Required
Coding Instructions:
If INT = 1 and at least 75% of the possible observations were made in the year, place a T in column
78.
If INT = 7 and each quarter has at least 12 observations, place a T in column 78.
If neither of these conditions is true, place a '0* in column 78.
Error Messages:
ERROR - INVALID SUM-CRITERIA
SUM CRTT must be '0' or T.
Transaction Type P 6-52 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.5 Transaction Type R - SLAMS CO Data
The R transaction is used to insert, modify, and delete carbon monoxide (CO) data in the AQ SLAMS
File. When inserting or modifying data, a V transaction must accompany the R transaction.
The coding form for the R transaction is shown in Figure 6-4.
AH the fields of an R transaction are required for INSERT and MODIFY actions. For a DELETE action,
only the YEAR field is required (plus the common fields, monitor-ID, transaction type, and action code).
Error Message:
ERROR - ALL FIELDS BLANK ON MODIFY
This message occurs if all the R transaction fields are blank on a MODIFY transaction. Although
this condition is just as invalid for an INSERT, this message only occurs for a MODIFY (for
consistency with other transaction types).
December 1993
6-53
Transaction Type R
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
S
a
y
i -
§ &
o
o
«
tV. '
ill
il-
i!
•t—r
±3
li
!!
i
S
S
*- Q. S O O
di O •- It 0.
fl- rt Z T Q
S
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.5.1 INT (Interval)
INT indicates the sampling interval used for monitoring activities.
Attributes: 1 character code
Required
Coding Instructions:
In column 17, enter T (1 hour). This is the only valid interval code for R transactions.
Error Messages:
ERROR - INTERVAL CODES DO NOT MATCH ON SLAMS RECORDS
The interval code (INT) on this, transaction is different from the corresponding V transaction.
They must agree.
ERROR - INVALID INTERVAL
INT must be T.
December 1993
6-55
Transaction Type R
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.5.2 UNITS
UNITS indicates the dimensional system in which a pollutant concentration is expressed.
Attributes: 3 digit code
Required
Coding Instructions:
In columns 18-20, enter '007* (parts per million). This is the only valid units code for R transactions.
Error Message:
ERROR - INVALID UNITS
The only valid value for UNITS is '007'.
Transaction Type R 6-56 December 1993
-------
o
AIRS User's Guide
Volume A Q2
Air Quality Data Coding
6.5.3 YEAR
YEAR contains the last two digits of the year for which CO data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 21-22, enter a valid year between 1981 and the current year.
Error Message:
ERROR - INVALID YEAR
YEAR is not in the range of 81 through the current year.
December 1993
<5-57
Transaction Type R
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.5.4 OBS-1 HR (Observation 1 Hour)
OBS-1 HR represents the number of 1-hour CO observations made during the year.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the number of 1-hour observations right justified in columns 23-26.
Error Messages:
ERROR - INVALID OBSER-1HR
OBS-1 HR must be numeric > 0.
If YEAR represents a "leap" year, OBS-1HR must be numeric, > 0, and <. 8784.
If year represents a "non-leap" year, OBS-1HR must be numeric, > 0, and .<. 8760.
WARNING • CANNOT VERIFY OBSER-1HR
If YEAR is invalid and OBS-1 HR > 8760, this field cannot be checked.
Transaction Type R 6-58 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.5.5 DP (Decimal Position)
DP is the decimal position indicator for CO values. It indicates the number of digits to the right of the
decimal point in each field containing a value of CO concentration.
Attributes:
1 digit numeric
Required
Coding Instructions:
In column 27, enter a decimal position indicator ('0* or T). This allows values of 0.1 through 9999.
Use the DP value appropriate for the precision of the measurement. For example, if the analytical
procedure yields results that are valid to one decimal place, use DP = T.
Error Message:
ERROR - INVALID DECIMAL-POSITION
DP must contain '0* or T.
December 1993
6-59
Transaction Type R
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.5.6 1-HOUR FIRST MAX (1-Hour First Maximum)
1-HOUR FIRST MAX is the highest 1-hour observation of CO for the year. Exceptional events data are
included.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the highest 1-hour CO observation for the year right justified in columns 28-31. Do not forget to
allow for the implied decimal point indicated by DP.
Error Message:
ERROR - INVALID MAX1-1HR
1-HOUR FIRST MAX must be numeric > 0.
Transaction Type R 6-60 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.5.7 1-HOUR FIRST MAX TIME (1-Hour First Maximum Time)
1-HOUR FIRST MAX TIME is the month, day, and hour when the 1-HOUR FIRST MAX occurred.
Attributes: 6 digit date
Required
Coding Instructions:
In columns 32-37, enter the month, day, and hour of the FIRST MAX in MMDDHH format. Use a
leading zero for month, day, and hour as needed.
If the 1-HOUR FIRST MAX value occurred at more than one time in the year, enter the date and hour
of the first occurrence.
Error Message:
ERROR - INVALID TIME-MAX1-1HR
Month (MM) must be '01' through '12', day (DD) must be valid for the given month, and hour
(HH) must be W through '23'.
December 1993
(-61
Transaction Type R
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.5.8 1-HOUR SEC MAX (1-Hour Second Maximum)
1-HOUR SEC MAX is the second highest 1-hour observation of CO for the year. Exceptional events
data are included.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the second highest 1-hour CO value for the year right justified in columns 38-41. Do not forget
to allow for the implied decimal point indicated by DP.
If the highest 1-hour CO value occurred more than one time in the year, enter that same value for 1-
HOUR SEC MAX.
Error Messages:
ERROR - INVALID MAX2-1HR
1-HOUR SEC MAX must be numeric > 0.
ERROR - MAX2-1HR > MAX 1-1HR
1-HOUR SEC MAX must be .<. 1-HOUR FIRST MAX.
Transaction Type R " 6-62 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.5.9 1-HOUR SEC MAX TIME (1-Hour Second Maximum Time)
1-HOUR SEC MAX TIME is the month, day, and hour when 1-HOUR SEC MAX occurred.
Attributes: 6 digit date
Required
Coding Instructions:
Enter the month, day, and hour of the SEC MAX in MMDDHH format in columns 42-47. Use a leading
zero for month, day, or hour, as needed.
If the same value is entered for FIRST MAX and SEC MAX, enter the date and hour of the second
occurrence in this field.
Error Message:
ERROR - INVALID TIME-MAX2-1HR
Month (MM) must be '01' through '12', day (DD) must be valid for the given month, and hour
(HH) must be '00' through '23'.
December 1993
ti-63
Transaction Type R
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.5.10 8-HOUR FIRST MAX (8-Hour First Maximum)
8-HOUR FIRST MAX is the highest 8-hour miming average of CO for the year. The 8-hour running
average for hour k is the average of the observations for hours k through k-7. There must be at least six
observations in an eight-hour block for an average to be computed. Exceptional events data are included.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the highest 8-hour running average value right justified in columns 48-51. Remember to allow for
the implied decimal point indicated by DP.
Error Message:
ERROR - INVALID MAX1-8HR
8-HOUR FIRST MAX must be numeric > 0.
Transaction Type R 6-64 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.5.1 i 8-HOUR FIRST MAX TIME (8-Hour First Maximum Time)
8-HOUR FIRST MAX TIME is the month, day, and hour of the last hour in the 8- hour averaging period
that generated 8-HOUR FIRST MAX.
Attributes: 6 digit date
Required
Coding Instructions:
In columns 52-57, enter the month, day, and hour of the 8-HOUR FIRST MAX in MMDDHH format.
Use a leading zero for month, day, or hour, as needed.
If the 8-HOUR FIRST MAX value occurred more than once in the year, enter the date and hour of the
first occurrence.
Error Message:
ERROR - INVALID TIME-MAX1-8HR
Month (MM) must be *01' through M2', day (DD) must be valid for the given month, and hour
(HH) must be '00' through '23'.
December 1993
6-6S
Transaction Type R
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.5.12 8-HOUR SEC MAX (8-Hour Second Maximum)
8-HOUR SEC MAX is the highest 8-hour running average CO value that is less than or equal to the 8-
HOUR FIRST MAX value and is least influenced by the original observations that yielded the first
maximum. After computing the first maximum, list it and the eight next highest 8-hour averages ordered
by decreasing magnitude. If two values have the same magnitude, order them chronologically. The
second maximum is the first value in the list that occurred at least eight hours before or after any value
higher in the list. The reason for this method is to avoid the influence of spikes in the original raw data
that cause plateaus in the running averages.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the CO second maximum 8-hour running average value for the year right justified in columns 58-
61. Remember to allow for the implied decimal point indicated by DP.
Error Messages:
ERROR - INVALID MAX2-8HR
8-HOUR SEC MAX must be numeric > 0.
ERROR - MAX2-8HR > MAX1-8HR
8-HOUR SEC MAX must be .<_ FIRST MAX.
Transaction Type R 6-66 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.5.13 8-HOUR SEC MAX TIME (8-Hour Second Maximum Time)
8-HOUR SEC MAX TIME is the month, day, and hour of the last hour in the 8-hour averaging period
that generated 8-HOUR SEC MAX.
Attributes: 6 digit numeric
Required
Coding Instructions:
In columns 62-67, enter the month, day, and hour of the SEC MAX in MMDDHH format. Use a
leading zero for month, day, or hour, as needed.
Error Message:
ERROR - INVALID TIME-MAX2-8HR
Month (MM) must be '01' through '12', day (DD) must be valid for the given month, and hour
(HH) must be '00' through '23*.
December 1993
6-67
Transaction Type R
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.5.14 1-HOUR EXCEEDANCE
1-HOUR EXCEEDANCE is the number of 1-hour observations during the year that exceeded the CO
1-hour ambient air quality standard. Exceptional events data are included.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter an integer number of exceedances right justified in columns 68-71. The number must be _<. the
value in OBS-1HR. Enter zero if there were no exceedances.
Error Message:
ERROR - INVALID EXCEED-IHR
EXCEEDANCE must be numeric <_ the value in OBS-1HR.
Transaction Type R 6-68 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.5.15 8-HOUR EXCEEDANCE
8-HOUR EXCEEDANCE is the number of non-overlapping 8-hour running averages during the year that
exceeded the CO 8-hour ambient air quality standard. Exceptional events data are included.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter an integer number of exceedances right justified in columns 72-75. The number must be £_ 1095.
Enter zero if there were no exceedances.
Error Message:
ERROR - INVALID EXCEED-8HR
EXCEEDANCE must be numeric <. 1095 (the number of consecutive 8-hour periods in one
year).
December 1993
6-69
Transaction Type R
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.6 Transaction Type S - SLAMS NO2 Data
The S transaction is used to insert, modify, and delete nitrogen dioxide (NOj) data in the AQ SLAMS
File. When inserting or modifying data, a V transaction must accompany the S transaction.
The coding form for the S transaction is shown in Figure 6-5.
All the fields of an S transaction are required for INSERT and MODIFY actions. For a DELETE action,
only the YEAR field is required (plus the common fields, monitor-ID, transaction type, and action code).
Error Message:
ERROR - ALL FIELDS BLANK ON MODIFY
This message occurs if all the S transaction fields are blank on a MODIFY transaction. Although
this condition is just as invalid for an INSERT, this message only occurs for a MODIFY (for
consistency with other transaction types).
Transaction Type S 6-70 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
si
o»:
«
^i
i
s
Tueft*
,
!1
1
:
is
•a
,
1 -,
5 i.
ill
I
3,
S!
~7
w •
1 _
*
1
I
J5
••
24
H
*•
E
!
I *
* !
1 :
i
i;
MI 2
•»« :
p
• -
i "
1 J
:
2
-
- •
Jl
« •
S ™
1st-
it
I*!
FT
zt
Zi
• i
r^
s:
S,
Si
4!
5
4
J
2
i
3
0
1
i
V
>
i
!
i
t
1
I ,
i
j
i
r i
E
i
i
i
1
7
i
.
<
i
1
|
i
|
i.
|
I
i
]
|
|
i
I
i
t
i
i
|
I
!
j
i
i
i
,
1
T
i
1
1
1
\
i
f
I
I
>
i
i
i
J
i
i
i
i
|
i
I
t
•
1
i
[
1
i
j
1
i
J
i
"T
5 I
• ••
II i
o
$
I
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.6.1 INT (Interval)
INT indicates the sampling interval used for monitoring activities.
Attributes: 1 character code
Required
Coding Instructions:
For 1-hour observations, enter T in column 17. For 24-hour observations, enter '7* in column 17. No
other intervals are permitted.
Error Messages:
ERROR - INTERVAL CODES DO NOT MATCH ON SLAMS RECORDS
The interval code (INT) on this transaction is different from the corresponding V transaction.
They must agree.
ERROR - INVALID INTERVAL
INT must be Tor 'T.
Transaction Type S 6-72 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.6.2 UNITS
UNITS indicates the dimensional system in which a pollutant concentration is expressed.
Attributes: 3 digit code
Required
Coding Instructions:
In columns 18-20, enter '007' (parts per million). This is the only units code permitted for S
transactions.
Error Message:
ERROR - INVALID UNITS
The only valid value for UNITS is '007'.
December 1993
6-73
Transaction Type S
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.6.3 YEAR
YEAR contains the last two digits of the year for which NO2 data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 21-22, enter a valid year between 1981 and the current year.
Error Message:
ERROR - INVALID YEAR
YEAR must be in the range 81 through the current year.
Transaction Type S 6-74 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.6.4 OBS-1 HR (Observation 1 Hour)
OBS-1 HR represents the number of 1-hour NO2 observations made during the year.
Attributes: 4 digit numeric
Required for INT = 1
Prohibited for INT = 7
Coding Instructions:
If INT = 1, enter the number of 1-hour observations in columns 23-26.
If INT = 7, leave this field blank.
Error Messages:
ERROR - INVALID OBSER-1HR
If INT = 1, OBS-1HR must be numeric > 0.
If INT = 1 and YEAR represents a "leap" year, OBS-IHR must be numeric, > 0, and <_ 8784.
If INT = 1 and YEAR represents a "non-leap" year, OBS-IHR must be numeric, > 0, and <_
8760.
ERROR - OBSER-1HR NOT ALLOWED
If INT = 7, OBS-IHR must be blank.
WARNING - CANNOT VERIFY OBSER-1HR
If INT = 1, YEAR is invalid, and OBS-IHR > 8760, this field cannot be checked.
o
December 1993
6-75
Transaction Type S
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.6.5 OBS-24 HR (Observation 24 Hour)
OBS-24 HR represents the number of 24-hour observations made during the year for NO2.
Attributes: 3 digit numeric
Required for INT = 7
Prohibited for INT = 1
Coding Instructions:
If INT = 7, enter the number of 24-hour observations right justified in columns 27-29. The number
must be an integer > 0 and <_ 366.
If INT = 1, leave this field blank.
Error Messages:
ERROR - INVALID OBSER-24HR
For INT = 7, OBS-24 HR must be numeric > 0 and <_ 366.
ERROR - OBSER-24HR NOT ALLOWED
For INT - 1, OBS-24 HR must be blank.
Transaction Type S 6-76 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.6.6 DP (Decimal Position)
DP is the decimal position indicator for N02 values. It indicates the number of digits to the right of the
implied decimal point in each field containing a value of N02 concentration.
Attributes: 1 digit numeric
Required
Coding Instructions:
In column 30, enter a valid decimal position indicator of '2' or '3'. This allows observations of 0.001
through 99.99. Use a DP value that is appropriate for the precision of the collection and analysis
methods. If results are valid to three decimal places, use DP = '3'; otherwise use DP = '2'.
Error Message:
ERROR - INVALID DECIMAL-POSITION
DP must be '2* or '3'.
December 1993
6-77
Transaction Type S
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.6.7 1-HOUR FIRST MAX (1-Hour First Maximum)
1-HOUR FIRST MAX is the highest 1-hour N02 observation for the year. Exceptional events data are
included.
Attributes: 4 digit numeric
Required for INT = 1
Prohibited for INT = 7
Coding Instructions:
If INT - 1, enter the highest 1-hour NOj value for the year right justified in columns 31-34. Remember
to allow for the implied decimal point indicated by DP. The value must be greater than zero.
If INT = 7, leave this field blank.
Error Messages:
ERROR - INVALID MAX1-1HR
For INT = 1, 1-HOUR FIRST MAX must be numeric > 0.
ERROR - MAX1-1HR NOT ALLOWED
For INT = 7, 1-HOUR FIRST MAX must be blank.
Transaction Type S 6-78 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.6.8 1-HOUR FIRST MAX TIME (1-Hour First Maximum Time)
1-HOUR FIRST MAX TIME is the month, day, and hour when I-HOUR FIRST MAX occurred.
Attributes: 6 digit date
Required for INT = 1
Prohibited for INT = 7
Coding Instructions:
If INT = 1, enter in columns 35-40 the month and day of the 1-HOUR FIRST MAX in MMDDHH
format. Use a leading zero for month, day, or hour, as needed.
If the 1-HOUR FIRST MAX value occurred more than once during the year, enter the date and hour of
the first occurrence in this field.
If INT = 7, leave this field blank.
Error Messages:
ERROR - INVALID TIME-MAXMHR
For INT = 1, month (MM) must be '01' through '12', day (DD) must be valid for the given
month, and hour (HH) must be '00' through '23'.
ERROR - TIME-MAX1-1HR NOT ALLOWED
For INT = 7, 1-HOUR FIRST MAX TIME must be blank.
December 1993
6-79
Transaction Type S
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.6.9 1-HOUR SEC MAX (1-Hour Second Maximum)
1-HOUR SEC MAX is the second highest 1-hour observation of NO2 for the year. Exceptional events
data are included.
Attributes: 4 digit numeric
Required for INT = 1
Prohibited for INT = 7
Coding Instructions:
If INT - 1, enter in columns 41-44 the second highest 1-hour NQ observation for the year. Remember
to allow for the implied decimal point indicated by DP. The value must be greater than zero. If the
highest 1-hour value occurred more than once during the year, enter that same value for this field.
If INT = 7, leave this field blank.
Error Messages:
ERROR - INVALID MAX2-1HR
For INT = 1, 1-HOUR SEC MAX must be numeric > 0.
ERROR - MAX2-1HR NOT ALLOWED
For INT = 7, 1-HOUR SEC MAX must be blank.
ERROR - MAX2-1HR > MAX1-1HR
1-HOUR SEC MAX must be <. 1-HOUR FIRST MAX
Transaction Type S 6-80 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.6.10 1-HOUR SEC MAX TIME (1-Hour Second Maximum Time)
1-HOUR SEC MAX TIME is the month, day, and hour when 1-HOUR SEC MAX occurred.
Attributes: 6 digit date
Required for INT = 1
Prohibited for INT = 7
Coding Instructions:
If INT = 1, enter in columns 45 - 50, the month, day, and hour of the 1-HOUR SEC MAX in
MMDDHH format. Use a leading zero for month, day, or hour, as needed. If the highest 1-hour value
occurred more than once during the year, enter the date and time of the second occurrence in this field.
If INT = 7, leave this field blank.
Error Messages:
ERROR - INVALID TIME-MAX2-1HR
For INT = 1, month (MM) must be '01' through '12', day (DD) must be valid for the given
month, and hour (HH) must be '00' through '23'.
ERROR - TIME-MAX2-1HR NOT ALLOWED
For INT = 7, 1-HOUR SEC MAX TIME must be blank.
December 1993
6-81
Transaction Type S
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.6.11 24-HOUR FIRST MAX (24-Hour First Maximum)
24-HOUR FIRST MAX is the highest 24-hour observation of N02for the year.
Attributes: 4 digit numeric
Required for INT = 7
Prohibited for INT = 1
Coding Instructions:
If INT = 7, enter the highest 24-hour NOj observation for the year right justified in columns 51-54. The
number must be greater than zero. Remember to allow for the implied decimal point indicated by DP.
If INT = 1, leave this field blank.
Error Messages:
ERROR - INVALID MAX1-24HR
For INT = 7, 24-HOUR FIRST MAX must be numeric > 0.
ERROR - MAX1-24HR NOT ALLOWED
For INT = 1, 24-HOUR FIRST MAX must be blank.
Transaction Type S 6-82 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.6.12 24-HOUR FIRST MAX DATE (24-Hour First Maximum Date)
24-HOUR FIRST MAX DATE is the month and day when the 24-HOUR FIRST MAX occurred.
Attributes: 4 digit date
Required for INT = 7
Prohibited for INT = 1
Coding Instructions:
If INT = 7, enter in columns 55-58 the month and day of the 24-HOUR FIRST MAX in MMDD format.
Use a leading zero for month or day, as needed.
If the 24-HOUR FIRST MAX value occurred more than once in the year, enter the date of the first
occurrence in this field.
If INT = 1, leave this field blank.
Error Messages:
ERROR - DATE-MAX1-24HR NOT ALLOWED
For INT = 1, 24-HOUR FIRST MAX DATE must be blank.
ERROR - INVALID DATE-MAXI-24HR
For INT = 7, month (MM) must be '01' through '12' and day (DD) must be valid for the given
month.
December 1993
6-83
Transaction Type S
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.6.13 24-HOUR SEC MAX (24-Hour First Maximum Date)
24-HOUR SEC MAX is the second highest 24-hour observation of NO, for the year.
Attributes: 4 digit numeric
Required for INT = 7
Prohibited for INT = 1
Coding Instructions:
If INT = 7, enter the second highest 24-hour NQj observation for the year right justified in columns 59-
62. The number must be greater than zero. Remember to allow for the implied decimal point indicated
by DP. If the highest 24-hour value for the year occurred more than once, enter that same value in this
field.
If INT = 1, leave this field blank.
Error Messages:
ERROR - INVALID MAX2-24HR
For INT = 7, 24-HOUR SEC MAX must be numeric > 0.
ERROR - MAX2-24HR NOT ALLOWED
For INT = 1, 24-HOUR SEC MAX must be blank.
ERROR - MAX2-24HK > MAX1-24HR
24-HOUR SEC MAX must be < 24-HOUR FIRST MAX.
Transaction Type S 6-84 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.6.14 24-HOUR SEC MAX DATE (24-Hour Second Maximum Date)
24-HOUR SEC MAX DATE is the month and day when 24-HOUR SEC MAX occurred.
Attributes: 4 digit date
Required for INT = 7
Prohibited for INT = 1
Coding Instructions:
If INT = 7, enter in columns 63-66 the month and day of the 24-HOUR SEC MAX in MMDD format.
Use a leading zero for month and day as needed. If the same value is coded for 24-HOUR FIRST MAX
and SEC MAX, enter the date of the second occurrence in this field.
If INT = 1, leave this field blank.
Error Messages:
ERROR - DATE-MAX2-24HR NOT ALLOWED
For INT = 1, 24-HOUR SEC MAX DATE must be blank.
ERROR - INVALID DATE-MAX2-24HR
For INT = 7, Month (MM) must be '01' through ' 12' and day (DD) must be valid for the given
month.
December 1993
6-85
Transaction Type S
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.6.15 ARITHMETIC MEAN
ARITHMETIC MEAN is the average of all observed values for the year. Exceptional events data are
included. One half of the minimum detectable is used in place of observations less than the minimum
detectable when computing the mean.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the arithmetic mean for N0: right justified in columns 67-70 Remember to allow for the implied
decimal point indicated by DP. The value must be greater than zero.
Error Message:
ERROR - INVALID ARTTH-MEAN
ARITHMETIC MEAN must be numeric > 0.
Transaction Type S 6-86 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.6.16 SUM CRTT (Summary Criteria Flag)
SUM CRJT indicates whether or not enough observations were made during the year to satisfy the AIRS
summary criteria.
Attributes: 1 digit code
Required
Coding Instructions:
If INT = 1 and at least 75% of the possible observations were made in the year, place a T in column
71.
If INT = 7 and each quarter has at least 12 observations, place a T in column 71.
If neither of these two conditions is true, place a '0* in column 71.
Error Message:
ERROR - INVALID SUM-CRITERIA
SUM CRTT must be '0' or T.
December 1993
6-87
Transaction Type S
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.7 Transaction Type T - SLAMS 03 Data
The T transaction is used to insert, modify, and delete ozone (O,) data in the AQ SLAMS File. When
inserting or modifying data, a V transaction must accompany the T transaction.
The coding form for the T transaction is shown in Figure 6-6.
AH the fields of the T transactions are required for INSERT and MODIFY actions. For a DELETE
action, only the YEAR field is required (plus the common fields, monitor-ID, transaction type, and action
code).
Error Message:
ERROR - ALL FIELDS BLANK ON MODIFY
This message occurs if all the T transaction fields are blank on a MODIFY transaction. Although
this condition is just as invalid for an INSERT, this message only occurs for a MODIFY (for
consistency with other transaction types).
Transaction Type T 6-88 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
S
o
1
s«= s
t
•f,
£
<%
5|*
B|l
OB
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.7.1 INT (Interval)
INT indicates the sampling interval used for monitoring activities.
Attributes: 1 character code
Required
Coding Instructions:
In column 17, enter T (1 hour). This is the only valid interval code for T transactions.
Error Messages:
ERROR - INTERVAL CODES DO NOT MATCH ON SLAMS RECORDS
The interval code (INT) on this transaction is different from the corresponding V transaction.
They must agree.
ERROR - INVALID INTERVAL
INT must be T.
Transaction Type T 6-90 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.7.2 UNITS
UNITS indicates the dimensional system in which a pollutant concentration is expressed.
Attributes: 3 digit code
Required
Coding Instructions:
In columns 18-20, enter '007' (parts per million). This is the only valid units code for T transactions.
Error Message:
ERROR - INVALID UNITS
The only valid value for UNITS is '007'.
December 1993
6-91
Transaction Type T
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.7.3 YEAR
YEAR contains the last two digits of the year for which 03 data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 21-22, enter a valid year between 1981 and the current year.
Error Message:
ERROR - INVALID YEAR
YEAR is not in the range 81 through the current year.
Transaction Type T 6-92 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Date Coding
6.7.4 OBS-1 HR (Observation 1 Hour)
OBS-1 HR represents the number of 1-hour 03 observations made during the year.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the number of 1-hour observations right justified in columns 23-26. The number must be an
integer > 0 and <.. 8760.
Error Message:
ERROR - INVALID OBSER-1HR
OBS-1 HR must be numeric > 0 and <_ 8760.
December 1993
6-93
Transaction Type T
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.7.5 DP (Decimal Position)
DP is the decimal point indicator for O3 values. It indicates the number of digits to the right of the
implied decimal point in each field containing a value of Q, concentration.
Attributes: 1 digit numeric
Required
Coding Instructions:
In column 27, enter a valid decimal position indicator ('2' or '3'). These are the only decimal indicators
allowed on T transactions. They allow values of 0.001 through 99.99. Use a DP value that is
appropriate for the collection and analysis methods employed. For example, if results are valid only to
two decimal places, use DP = '2' rather than '3'.
Error Message:
ERROR - INVALID DECIMAL-POSITION
DP must contain '2* or '3'.
Transaction Type T 6-94 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.7.6 Ozone Maximum Values
The four ozone maximum values of the T transaction, 1-HOUR FIRST MAX, 1-HOUR SEC MAX, 1-
HOUR THIRD MAX, and 1-HOUR FOURTH MAX, all are derived from valid daily maximum ozone
values. An ozone daily maximum value is valid if one of the following criteria is met:
1) There are at least nine 1-hour observations between 9:00 a.m. and 8:59 p.m. (sampling start
hours 09 through 20). The daily maximum does not have to occur within that time span, but the
requisite number of observations must have been made.
2) One or more of the 1-hour observations for the day exceeds the ozone 1-hour ambient air quality
primary standard.
If neither of those criteria is met on a given day, a valid daily maximum value cannot be derived, and
none of the observations for that day is considered in determining the ozone maximum values.
To obtain the four maximum values for the T transaction, derive all the valid daily maxima for the year.
Include exceptional events data if they occurred. Next, arrange the valid daily maxima in order of
magnitude, with the highest value first in the list. If the same value occurs more than once, arrange the
occurrences in chronological order with the earliest occurrence first. The first four values in the ordered
list are the maximum values for the T transaction.
December 1993
6-95
Transaction Type T
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.7.7 1-HOUR FIRST MAX (I-Hour First Maximum)
1-HOUR FIRST MAX is the highest daily maximum value of ozone for the year. Exceptional data are
included.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the highest valid daily maximum ozone value for the year right justified in columns 28-31. See
Section 6.6.6 for the method of deriving the maximum value. Remember to allow for the implied
decimal position indicated by DP.
Error Message:
ERROR - INVALID MAX1-1HR
1-HOUR FIRST MAX must be numeric > 0.
Transaction Type T 6-96 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.7.8 1-HOUR FIRST MAX TIME (1-Hour First Maximum Time)
1-HOUR FIRST MAX TIME is the month, day, and hour when 1-HOUR FIRST MAX occurred.
Attributes:
6 digit date
Required
Coding Instructions:
In columns 32-37, enter the month, day, and hour of the 1-HOUR FIRST MAX in MMDDHH format.
Use a leading zero for month, day, or hour, as needed. Use the procedure given in Section 6.6.6 to
determine the FIRST MAX value and time.
Error Message:
ERROR - INVALID TIME-MAXMHR
Month (MM) must be '01' through '12', day (DD) must be valid for the given month, and hour
(HH) must be '00' through '23'.
December 1993
6-97
Transaction Type T
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.7.9 1-HOUR SEC MAX (1-Hour Second Maximum)
1-HOUR SEC MAX is the second highest valid daily maximum value of ozone for the year. Exceptional
events data are included.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the second highest valid daily maximum ozone value for the year right justified in columns 38-41.
See Section 6.6.6 for the method of deriving the maximum value. Remember to allow for the implied
decimal position indicated by DP.
Error Messages:
ERROR * INVALID MAX2-1HR
1-HOUR SEC MAX must be numeric > 0.
ERROR - MAX2-1HR > MAX1-1HR
1-HOUR SEC MAX must be <_ FIRST MAX.
Transaction Type T 6-98 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.7.10 1-HOUR SEC MAX TIME (1-Hour Second Maximum Time)
1-HOUR SEC MAX TIME is the month, day, and hour when 1-HOUR SEC MAX occurred.
Attributes:
6 digit date
Required
Coding Instructions:
In columns 42-47, enter the month, day, and hour of the 1-HOUR SEC MAX in MMDDHH format.
Use a leading zero for month, day, or hour, as needed. See Section 6.6.6 for the method of deriving
SEC MAX value and time.
Error Message:
ERROR - INVALID TIME-MAX2-1HR
Month (MM) must be '01' through '12', day (DD) must be valid for the given month, and hour
(HH) must be '00' through '23'.
December 1993
6-99
Transaction Type T
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.7.11 1-HOUR THIRD MAX (1-Hour Third Maximum)
1-HOUR THIRD MAX is the third highest valid daily maximum value of ozone for the year.
Exceptional events data are included.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the third highest valid daily maximum ozone value for the year right justified in columns 48-51.
See Section 6.6.6 for the method of deriving the maximum value. Remember to allow for the implied
decimal position indicated by DP.
Error Messages:
ERROR - INVALID MAX3-1HR
1-HOUR THIRD MAX must be numeric > 0.
ERROR - MAX3-1HR > MAX2-1HR
1-HOUR THIRD MAX must be <. SEC MAX.
Transaction Type T 6-100 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.7.12 1-HOUR THIRD MAX TIME (1-Hour Third Maximum Time)
1-HOUR THIRD MAX TIME is the month, day, and hour when 1-HOUR THIRD MAX occurred.
Attributes:
6 digit date
Required
Coding Instructions:
In columns 52-57, enter the month, day, and hour of the 1-HOUR THIRD MAX in MMDDHH format.
Use a leading zero for month, day, or hour, as needed. See Section 6.6.6 for the method of deriving
THIRD MAX value and time.
Error Message:
ERROR - INVALID TIME-MAX3-1HR
Month (MM) must be '01' through '12', day (DD) must be valid for the given month, and hour
(HH) must be '00' through '23'.
December 1993
6-101
Transaction Type T
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.7.13 1-HOUR FOURTH MAX (1-Hour Fourth Maximum)
1-HOUR FOURTH MAX is the fourth highest valid daily maximum value of ozone for the year.
Exceptional events data are included.
Attributes: 4 digit numeric
Required
Coding Instructions:
Enter the fourth highest valid daily maximum ozone value for the year right justified in columns 58-61.
See Section 6.6.6 for the method of deriving the maximum value. Remember to allow for the implied
decimal position indicated by DP.
Error Messages:
ERROR - INVALID MAX4-1HR
1-HOUR FOURTH MAX must be numeric > 0.
ERROR - MAX4-1HR > MAX3-1HR
1-HOUR FOURTH MAX must be <. THIRD MAX.
Transaction Type T 6-102 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.7.14 1-HOUR FOURTH MAX TIME (1-Hour Fourth Maximum Time)
1-HOUR FOURTH MAX TIME is the month, day, and hour when 1-HOUR FOURTH MAX occurred.
Attributes:
6 digit date
Required
Coding Instructions:
In columns 62-67, enter the month, day, and hour of the 1-HOUR FOURTH MAX in MMDDHH
format. Use a leading zero for month, day, or hour, as needed. See Section 6.6.6 for the method of
deriving FOURTH MAX value and time.
Error Message:
ERROR - INVALID TIME-MAX4-1HR
Month (MM) must be '01' through '12', day (DD) must be valid for the given month, and hour
(HH) must be '00' through '23'.
December 1993
6-103
Transaction Type T
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.7.15 1-HR EXCEEDANCE
1-HOUR EXCEEDANCE is the number of valid ozone daily maximum values that exceeded the ozone
1-hour ambient air quality primary standard. See Section 6.6.6 for a discussion of ozone daily maximum
values.
Attributes: 3 digit numeric
Required
Coding Instructions:
Enter an integer number of exceedances right justified in columns 68-70. The number must not exceed
366. Enter '0' if there were no exceedances.
Error Message:
ERROR - INVALID EXCEED-1HR
EXCEEDANCE must be numeric £_ 366.
Transaction Type T 6-104 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.8 Transaction Type U - SLAMS Pb Data
The U transaction is used to insert, modify, and delete lead (Pb) data in the AQ SLAMS File. A V
transaction is not used for lead data.
The coding form for the U transaction is shown in Figure 6-7.
For INSERT and MODIFY transactions, all of the following fields of the U transaction must be valued:
INT (interval)
UNITS
METHOD (at least one of the five occurrences)
DP (decimal position)
QUARTERS (at least one of four occurrences):
NO. OF SAMPLES (number of samples)
ARTTH MEAN (arithmetic mean)
SUM CRTT (summary criteria flag)
For a DELETE transaction, you need only specify YEAR.
Error Message:
ERROR - ALL FIELDS BLANK ON MODIFY
This message occurs if all the U transaction fields are blank on a MODIFY transaction.
Although this condition is just as invalid for an INSERT, this message only occurs for a
MODIFY (for consistency with other transaction types).
December 1993
(-105
Transaction Type U
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
I
IP
fp
^*i
>1
" 1?.
T
• t
9
&
3
!j
£
c
&
%
3
5
• mil KIIII
51!
II
5 IIMII J
$__•«•(
I ^1
1 'i
i i
0 1?
i ,,— n
I *
! i!
1 -^
9 •«.
s \
S 1 1
2 I
I mum
" * ••pt
^••1
1
ifit
1
l =
1 ;
S
i— t
>•• i
s?
K
r»
g
"EC
*"«T
K
. -
1:1
w *
i :_
lib-
I
I
i
i
L.*_
1
a a
1 ~"
1
L
3199 i i
l
111
S
S!
i
Figure 6-7. Coding Form for Transaction Type U - SLAMS Pb Data
Transaction Type U
6-106
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.8.1 INT (Interval)
INT indicates the sampling interval used for monitoring activities.
Attributes: 1 character code
Required
Coding Instructions:
In column 17, enter '7* (24 hours) or 'C (composite). No other interval codes are valid for U
transactions.
Error Message:
ERROR - INVALID INTERVAL
INT must be '7' or 'C.
December 1993
(-107
Transaction Type U
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.8.2 UNITS
UNITS indicates the dimensional system in which a pollutant concentration is expressed.
Attributes: 3 digit code
Required
Coding Instructions:
In columns 18-20, enter '001' (micrograms per cubic meter at 25 degrees C). This is the only valid units
code for U transactions.
Error Message:
ERROR - INVALID UNITS
The only valid value for UNITS is '001'.
Transaction Type U 6-108 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.8.3 YEAR
YEAR contains the last two digits of the year for which Pb data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 21-22, enter a valid year between 1981 and the current year.
Error Message:
ERROR - INVALID YEAR
YEAR must be in the range 81 through the current year.
December 1993
6-109
Transaction Type U
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.8.4 METHOD
METHOD identifies a particular method for collecting and analyzing lead samples.
Attributes: 3 digit code
Required
Coding Instructions:
Since it is possible for multiple methods to be used for the analysis of lead throughout the year, five fields
are available on U transactions for lead methods. Fields should be filled consecutively from left to right;
i.e., fill columns 23-25 first, then 26-28, then 29-31, then 32-34, then 35-37. For each field used, enter
a valid method code. The method must be valid in combination with the interval (INT) and UNITS of
the lead data. Some methods are valid only in certain states. Valid pollutant, method, interval, units,
and state combinations are listed in Volume GC2 of the AIRS User's Guide.
If a method you used is not valid or if you used more than five methods, contact the AIRS database
administrator.
Error Messages:
ERROR - ALL METHODS CANNOT BE BLANK
At least one of the five possible occurrences of METHOD must be present for INSERT
transactions.
ERROR - INVALID METHOD
If an occurrence of METHOD is non-blank, it must be a valid code.
If PARAMETER, INTERVAL, and UNITS are valid, then the combination of those three and
the METHOD must exist in the GEO-COMMON File.
ERROR - INVALID METHOD FOR STATE
If PARAMETER, METHOD, INTERVAL, and UNITS are in the GEO-COMMON File, then
the METH-VAL-FLAG must be checked. If METH-VAL-FLAG = N, then METHOD is
invalid, except for states listed in the STATE fields. Refer to the listing of codes in Volume GC2
of the User's Guide.
ERROR - METHODS MUST BE CONSECUTIVE
Multiple METHOD codes must be entered in consecutive fields starting from the first occurrence.
Transaction Type U 6-110 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
WARNING - CANNOT VERIFY METHOD
If PARAMETER or INTERVAL or UNITS is invalid and METHOD is numeric, METHOD
cannot be verified further.
December 1993
£-111
Transaction Type U
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.8.5 DP (Decimal Position)
DP indicates the number of digits to the right of the implied decimal point in the quarterly ARTTH
MEAN fields of the U transaction.
Attributes: 1 digit numeric
Required
Coding Instructions:
In column 38, enter a valid decimal position indicator (T, '2', or '3'). These allow observations of
0.001 through 999.9 and are the only decimal indicators allowed for U transactions. Use a value for DP
that is appropriate for the precision of the analysis method(s) employed. For example, if the results are
valid to just one decimal place, use DP = T.
Error Message:
ERROR - INVALID DECIMAL-POSITION
DP must contain T, '2', or '3'.
Transaction Type U 6-112 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.8.6 Lead Quarterly Statistics
Lead summary statistics (number of samples, arithmetic mean, and summary criteria flag) are reported
for a year by quarter using the FIRST QUARTER, SECOND QUARTER, THIRD QUARTER, and
FOURTH QUARTER entries of the U transaction. For an INSERT transaction, there must be lead
statistics for at least one quarter. A MODIFY transaction may be used to add, change, or delete quarterly
statistics, but only by replacement of the values for all four quarters. In other words, a MODIFY
transaction must provide a complete replacement for all the values of an existing SLAMS record rather
than just the values to be changed. Do not use asterisks to delete the existing values for a quarter; just
leave blank the fields for that quarter.
Suppose, for example, that you provided statistics only for the first three quarters of a year when you
created the SLAMS record with an INSERT transaction, and that you want to add the statistics for the
fourth quarter. To do so, you would use a MODIFY action and code the new statistics for the fourth
quarter and, in addition, you would have to code the existing statistics for the first three quarters. If you
coded only the fourth quarter statistics, the statistics for the first three quarters would be deleted from
the SLAMS file.
As another example, suppose you need to change just the number of samples in quarter two because the
wrong number was coded when the record was originally created. In addition to coding the correct
number of samples in quarter two on the MODIFY transaction, you must also code all the other statistics
for the second quarter and for the other three quarters.
Error Message:
ERROR - ALL 4 QUARTERS CANNOT BE BLANK
On an INSERT transaction, values for at least one occurrence of quarterly statistics must be
entered.
December 1993
6-113
Transaction Type U
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.8.6.1 NO. OF SAMPLES (Number of Samples)
NO. OF SAMPLES indicates the number of samples taken in the quarter.
Attributes: 2 digit numeric
Required
Coding Instructions:
Place a valid integer right justified in columns 39-40 (quarter 1), 46-47 (quarter 2), 53-54 (quarter 3),
and/or 60-61 (quarter 4). Valid sample counts can be no more than 91 samples in each of the first two
quarters, and no more than 92 samples in each of the last two quarters.
If there were no samples taken in a quarter, do not code zero; rather, leave all fields for that quarter
blank.
Error Message:
ERROR - INVALID NUM-PB-SAMP-QTR
For the first and second occurrences of this field, this field can be blank or numeric > 0 and <_
91.
For the third and fourth occurrences of this field, this field can be blank or numeric > 0 and <,
92.
Transaction Type U 6-114 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.8.6.2 ARTTH MEAN (Arithmetic Mean)
ARTTH MEAN is the arithmetic mean of lead concentrations observed during the quarter. Exceptional
events data are included.
Attributes:
4 digit numeric
Required
Coding Instructions:
Place the arithmetic mean in columns 41-44 (quarter 1), 48-51 (quarter 2), 55-58 (quarter 3), and/or 62-
65 (quarter 4). Remember to allow for the implied decimal point indicated by DP.
Error Message:
ERROR - INVALID ARITH-MEAN-PB-QTR
ARTTH MEAN may be blank or numeric > 0.
December 1993
6-115
Transaction Type U
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.8.6.3 SUM CRTT (Summary Criteria Flag)
SUM CRIT indicates whether or not enough observations were taken to satisfy the AIRS summary criteria
for the quarter.
Attributes: 1 character code
Required
Coding Instructions:
For INT = 7, place a T in columns 45, 52,59, and/or 66 if at least 12 observations were made during
the quarters.
For INT — C, the minimum number of observations required to set SUM CRIT to T depends on the
composite type of the original raw data being summarized by this transaction/quarter. If the composite
type of the original raw data is T or '2* (quarterly or seasonal), the minimum number of observations
required is T. If the composite type is '3' (monthly), the minimum number of observations is '2\ If
the composite type is '4' (weekly), the minimum number of observations is '9'. If the minimum number
of observations are present in the quarter, place a T in columns 45, 52, 59, and/or 66.
If none of these conditions is met, place a 'O1 in columns 45, 52, 59, and/or 66.
Error Message:
ERROR - INVALID SUM-CRITERIA
SUM CRIT must be '0' or T.
Transaction Type U 6-116 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.9 Transaction Type V - SLAMS Method and Frequency Data
The V transaction is used with M, P, R, S, and T transactions to insert and modify information in the
AQ SLAMS File about the methods used for collecting and analyzing pollutant data and how frequently
certain pollutant concentrations were observed. The V transaction is never used for deleting SLAMS
data.
The coding form for the V transaction is shown in Figure 6-8.
For an INSERT or MODIFY transaction, values must be present for each of these fields:
INT (interval)
METHOD (at least one occurrence)
FREQUENCY (except for daily N0:)
EXC FLAG (exceptional events flag)
Error Message:
ERROR - ALL FIELDS BLANK ON MODIFY
This message occurs if all the V transaction fields are blank on a MODIFY transaction.
Although this condition is just as invalid for an INSERT, this message only occurs for a
MODIFY (for consistency with other transaction types).
December 1993
6-117
Transaction Type V
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
t 1
wrulHS '
t
*
!
'.
1 »
• S 1
S .i [ I
£ * i
1. * *
o S '
8 • »
i e i ! I
S s _ I
£ o s :
I
"I E
i S
j I
£ £
;
V S •
U^1 i
5£ .! ;
2 ^ «z ^ ?
^ > « ' r *
§B u o : F
"z2 i s;
O ttl O »' L —
FSS « I -
* S * z 5 -
1 2 ^ s \ '
wZ 5 2 "I E ~
S 4? * o '
Z K S *• it
O tj j^ S 5^^
E 3
z= ! ;
l •
I :
i ;
t r
1
!
i
3
t
Uf
*M
i
I
t
s
IftLJJ—
1 — 1*1*1
— *•
• JS
I e ...
1 a S
8-1 1 *
^| w f
Jl ^ g 5 *
S ? TB * ^ ~
P § C S" O »
iS Ssu5<=.
lu O >- O *-
££55<
po- i*
2 0
$ S
>
•g
0
CO
S
0
z
Figure 6-8. Coding Form for Transaction Type V - SLAMS Methods and Frequencies
Transaction Type V
6-118
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.9.1 INT (Interval)
INT indicates the sampling interval used for monitoring activities.
Attributes: 1 character code
Required
Coding Instructions:
Place the appropriate interval code in column 17. The interval code must be the same as the one from
the corresponding M, P, R, S, or T transaction.
Error Messages:
ERROR - INTERVAL CODES DO NOT MATCH ON SLAMS RECORDS
The interval code (INT) on this transaction is different from the corresponding M, P, R, S, or
T transaction. They must agree.
ERROR - INVALID INTERVAL
The interval code (INT) on this transaction is not valid for the corresponding M, P, R, S, or T
transaction.
December 1993
6-119
Transaction Type V
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
6.9.2 YEAR
YEAR contains the last two digits of the year for which data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 18-19, enter a valid year between 1981 and the current year.
Error Message:
ERROR - INVALID YEAR
YEAR is not in the range 81 through the current year.
Transaction Type V 6-120 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6.9.3 METHOD
METHOD indicates the method used to sample and analyze pollutant concentrations.
Attributes: 3 digit code
Required
Coding Instructions:
Up to five methods may be reported for the year. The five fields on the transaction must be filled from
left to right with no intervening blank fields; i.e., use columns 20-22 first, then 23-25, then 26-28, then
29-31, then 32-34.
Only certain combinations of PARAMETER, METHOD, INT (interval) and UNITS are valid, and some
methods are valid only in certain states. Valid combinations are listed in Volume GC2 of the AIRS
User's Guide.
If a method you used is not valid or if you used more than five methods, contact the AIRS database
administrator.
Error Messages:
ERROR - ALL METHODS CANNOT BE BLANK
At least one of the five possible occurrences of METHOD must be valued.
ERROR - INVALID METHOD
If an occurrence is non-blank, it must be a valid code.
If PARAMETER, INTERVAL, and UNITS are valid, then the combination of those three and
the METHOD must exist in the GEO-COMMON File.
ERROR - INVALID METHOD FOR STATE
If PARAMETER, METHOD, INTERVAL, and UNITS are in the GEO-COMMON File, then
the METH-VAL-FLAG must be checked. If METH-VAL-FLAG = N, then METHOD is
invalid, except for states listed in the STATE fields. '
ERROR - METHODS MUST BE CONSECUTIVE
Multiple METHOD codes must appear in consecutive fields starting from the first occurrence.
WARNING - CANNOT VERIFY METHOD
If PARAMETER or INTERVAL or UNITS is invalid and METHOD is numeric, METHOD
cannot be verified further.
December 1993
6-121
Transaction Type V
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
6.9.4 FREQUENCY
FREQUENCY indicates the number of observations of pollutant concentration that fall within a particular
range of values. Exceptional events data are included. The following table lists the value ranges for each
pollutant:
Parameter:
Pollutant:
Interval:
Units:
Field/Col.
1/35-38
2/39^2
3/43-46
4/47-50
5/51-54
6/55-58
7/59-62
8/63-66
9/67-70
42401
SO2
24-hour
ppm
.00-.04
.05-.08
.09-. 12
.13-.16
.17-.20
.21-.24
.25-.2S
> .28
n/a
11101
TSP
24-hour
ug/m3
0-50
51-100
101-150
151-200
201-250
251-300
301^00
> 400
n/a
42101
CO
8-hr avg
ppm
0-4
5-8
09-12
13-16
17-20
21-24
25-28
> 28
n/a
42602
NO2
1-hour
ppm
.00-.04
.05-.08
.09-. 12
.13-.I6
.17-.20
.21-. 24
.25-.2S
> .28
n/a
44201
03
Daily max
ppm
.00-.04
.05-.08
.09-. 12
.13-.16
.I7-.20
.21-.24
.2S-.28
> .28
n/a
81102
PM-10
24-hour
ug/m3
0-25
26-50
51-75
76-100
101-125
126-150
151-175
176-200
> 200
Attributes: 4 digit numeric
Required for all SLAMS parameters except interval 7 NO,
Prohibited for interval 7 NO2
Coding Instructions:
The V transaction has slots for nine frequencies. In each slot, enter the number of values that are within
the value range for the slot. The number must be right justified in the field. Enter zero if there are no
values within the particular range. To determine which range a value is within, round the value to the
number of decimal places shown in the table above and use the range limits shown there.
Except for PM-10, the ninth occurrence should be left blank.
Transaction Type V
6-122
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
In most cases, frequencies are based on the same values reported on the primary transaction (M, P, R,
S, or T) for means, maximum values, etc. The value to be counted depends on the pollutant and
sampling interval, as follows:
Trans
IffiS
M
M
M
P
P
R
S
S
T
Pollutant
TSP
PM-10
PM-10
SO2
S02
CO
NO,
NO,
03
Parameter
11101
81102
81102
42401
42401
42101
42602
42602
44201
7
1
7
1
7
1
1
7
1
Value Counted for Frequencies
observed 24-hour value
24-hour average (midnight-to-midnight of
1 -hour observations
observed 24-hour value
24-hour average (midnight-to-midnight) of
observations
observed 24-hour value
1-hour
8-hour running average of 1-hour observations
observed 1-hour value
(none - frequencies not reported)
valid daily maximum of 1-hour observations
In those cases when frequencies are based directly on the observed values, the total number of values
counted in all the frequency ranges must not exceed the number of observations reported on the
corresponding M, P, or S transaction.
Error Messages:
ERROR - ALL FREQUENCIES ARE BLANK
Except when PARAMETER = 42602 and INT = 7 (24-hour NO2), values must be present in the
FREQUENCY fields.
ERROR - ALL FREQUENCIES ARE ZERO
All eight (or nine) occurrences of FREQUENCY cannot be zero.
ERROR - FREQUENCIES NOT ALLOWED
When PARAMETER = 42602 and INT = 7 (24-hour NO,), all the FREQUENCY fields must be
blank.
December 1993
6-123
Transaction Type V
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR • FREQUENCY**) CANNOT BE BLANK
AH eight (or nine) FREQUENCY fields must have values. Enter zero if there were no
observations in a particular range.
ERROR - FREQUENCY^ IS INVALID
Zero and positive integers, right justified and zero filled, are valid values.
ERROR - FREQUENCY(9) NOT ALLOWED
Except when PARAMETER = 81102 (PM-10), the ninth FREQUENCY field must be blank.
ERROR - INVALID TOTAL FREQUENCIES ON SLAMS RECORDS
The total of all eight (or nine) FREQUENCY fields must be less than or equal to the number of
observations reported on the corresponding M, P, or S transaction.
WARNING - CANNOT VERIFY FREQUENCIES
If PARAMETER is invalid, or if PARAMETER = 42602 (NO;,) and INT is invalid, it cannot be
determined if FREQUENCY values are required or prohibited.
Transaction Type V 6-124 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
6,9.5 EXC FLAG (Exceptional Events Flag)
EXC FLAG is used to indicate whether or not exceptional event data are included in this transaction and
the corresponding M, R, S, or T transaction.
Attributes: 1 digit code
Required
Coding Instructions:
In column 79, enter '0' if no exceptional event data are included, or enter '2' if exceptional event data
are included.
Error Message:
ERROR - INVALID EXCEPT-DATA-FLAG
EXC FLAG must be '0' or '2'.
December 1993
6-125
Transaction Type V
-------
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
7.0 Raw Data Transactions (1, 2, and 3)
The three transactions in this group are used to insert, modify, and delete the individual observations of
parameter values in the AIRS database. Most of the parameter values are, of course, the concentrations
of air pollutants measured with various methods and at various time intervals. Some non-pollutant
observations are also reported, such as wind speed and other meteorological values. These observations
of parameter values are collectively called "raw data" because they are the actual, unprocessed values
reported by the monitoring sites. This is contrasted with the summaries of the observations reported as
SLAMS data or derived by AIRS software and stored in the Air Quality Summary File.
The AIRS database has three main files in which the raw data are stored; the Hourly, Daily, and
Composite files. There are three other analogous files for storing "secured" data, which is private data
that can be altered or retrieved only by the organization responsible for submitting it.
The Hourly File contains the reported observations of parameters monitored at sampling intervals less
than 24 hours. Each record holds approximately one-fourth of the values a monitor reports in one month:
days 1-8, days 9-16, days 17-24, or day 25 through the end of the month.
The Daily File contains the reported observations of parameters monitored at sampling intervals of 24
hours or more. Each record holds six months of observations from a monitor.
The Composite File contains composite observations, in which several samples obtained at different times
are combined and analyzed as one. Most pollutants reported this way have sampling intervals of 24
hours. Each record of the Composite File holds a monitor's composite observations for an entire year.
The fact that there are three types of files for storing raw data values is really of little consequence to
you, the person storing data. Which file is used depends on which type of transaction you use.
Transaction type 1 is for the Hourly File, type 2 for the Daily File, and type 3 for the Composite File.
Furthermore, you do not have to be concerned about which record of a file a raw data value is stored in.
The AIRS software automatically takes care of creating or deleting records as needed when you insert
or delete values. This is in contrast to the transactions and files discussed in earlier sections of this
volume. When you deal with the Site File or the SLAMS file, you must be aware of what records are
in the file, for the AIRS transactions apply to records rather than values. For the Site and SLAMS files,
an INSERT action creates a record, a DELETE action deletes a record and all the values in it. Those
considerations do not apply to the raw data files. You simply specify enough information to identify the
monitor and the date/time of a value, and the AIRS software automatically determines which record of
a file contains it. The establishment of different ways of updating the two kinds of files was a deliberate
decision. NADB believes it is more natural to act on the record as a unit in the Site and SLAMS files,
while an individual value is the natural unit of action in the raw data files.
December 1993 7-1 Raw Data Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
In the raw data files, there are three Melds for each possible observation: sample value, which is the
measured value of a parameter, stored as an integer; decimal position indicator, which gives the position
of the implied decimal point in the sample value field; and validity flag. The contents of these three
fields determine how an "observation" is interpreted. If decimal position is blank and sample value is
zero, there is no observation; a parameter value was not reported. If decimal position is blank and
sample value is non-zero, the sample value field is interpreted as a code (a "null value") that explains why
an observation was not reported (equipment malfunction, for example). A numeric value for decimal
position signals the presence of a "real" observation, which gives the measured value of a parameter.
The decimal position field scales the sample value field by indicating how many digits of the value (stored
as an integer) are to the right of the decimal point. In other words, the observed value is (sample value
field)/{10**(decimal position field)}, where the "**" means exponentiation, or "raised to the power of.
This same scheme is used for both the raw data files and the raw data transactions. In fact, the values
in the files are simply copied from the transactions.
The validity flag field is used only with "real" observations, when an observed parameter value is present.
A non-blank validity flag indicates the observed value is exceptional in some way, usually higher than
normal by a substantial amount. The value of the validity flag indicates the cause of the exceptional
observation (a forest fire, for example). If no specific cause can be attributed for the exceptional
observation, "V is coded for the validity flag (to indicate that the value is valid). A non-blank validity
flag exempts the associated observation from certain level-3 edit checks which it would not otherwise
pass. Without the exemption provided by the validity flag, neither the exceptional data nor any "normal"
data for the same day or month would pass level-3 edit checks. If the data failed to pass the edit checks,
it could not be loaded into the AIRS database.
Most values do not have validity flags, since they are associated with rare (exceptional) events or
circumstances. Furthermore, the use of validity flags is important only for criteria pollutants. Every
episode of validity flag usage (except code "V") must be approved by state and EPA officials and must
conform with the procedures and requirements set forth in "Guideline on the Identification and Use of
Air Quality Data Affected by Exceptional Events", publication number EPA-450/4-86-007, July, 1986.
Action codes are interpreted the same way for all three types of raw data transactions. INSERT actions
are used to enter raw data values where none previously existed. The monitor reporting the raw data
values must already exist in the AIRS Site File or else there must be valid transactions in the same
screening file to create the monitor. DELETE actions are used to remove one or more existing raw data
values from the AIRS database. MODIFY actions are used to change existing raw data values or to
delete them.
Raw Data Transactions 7-2 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
The three types of raw data transactions have several fields in common. They are:
MONITOR-ID, consisting of
STATE
COUNTY
SITE
PARAMETER
PARAMETER OCCURRENCE CODE (POC)
INT (interval)
UNITS
METHOD
YEAR
December 1993
7-3
Raw Data Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
Transaction type 1 contains hourly data in the following fields:
MOUTH
DAY
ST HR (stan hour)
DP (decimal position)
SAMPLE VALUE (eight occurrences)
VF (validity flag - eight occurrences)
Transaction type 2 contains daily data in the following fields:
MONTH
DAY
START HOUR
SF (sampling frequency)
DP (decimal position)
SAMPLE VALUE
VF (validity flag)
Transaction type 3 contains composite data in the following fields:
PERIOD CODE
NO. OF SAMPLES
COMP TYPE (composite type)
DP (decimal position)
SAMPLE VALUE
VF (validity flag)
Detailed coding instructions and explanations of error messages for the common fields and for the three
raw data transactions are given in following sections of this section.
The EDIT error messages listed below pertain to a raw data transaction as a whole, rather than to a
specific field. Most of the messages pertain to all three types of raw data transactions.
Error Messages:
ERROR - ATTEMPT TO ADD DATA PRIOR TO OLDEST MONITOR DATE
There is no monitor of any type that was active for the monitor-ID and date/time specified on an
INSERT or MODIFY transaction. For all three transaction types, check the monitor-ID and
date.
Raw Data Transactions 7-4 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
ERROR - ATTEMPT TO ADD DATA THAT EXISTS IN THE DATABASE
A value already exists in the raw data file for the monitor-ID and date/time specified on an
INSERT transaction. The value in the database will also be displayed on the error report. For
a type 1 transaction, verify that the value is in the correct sample value slot and that the start
hour is correct. For all three transaction types, verify that the date and monitor-ID are correct.
ERROR - ATTEMFF TO CHANGE DATA THAT DOES NOT EXIST
There is no value in the raw data file for the monitor-ID and date/time specified on a MODIFY
transaction. For a type 1 transaction, verify that the proper sample value slot is used and that
the start hour is correct. For all three transaction types, check the monitor-ID and date.
ERROR - ATTEMPT TO DELETE DATA THAT DOES NOT EXIST
There is no value in the raw data file for the monitor-ID and date/time specified on a DELETE
transaction. For a type 1 transaction, verify that the proper sample value slot is used and that
the stan hour is correct. For all three transaction types, check the monitor-ID and date.
ERROR - CANNOT ADD DATA FOR MONITOR BEING DELETED
There is an F DELETE transaction for the same monitor-id as the current INSERT.
ERROR - CANNOT MODIFY DATA FOR MONITOR BEING DELETED
There is an F DELETE transaction for the same monitor-id as the current MODIFY.
ERROR - DATA FOR THIS YEAR IS ARCHIVED
The raw data files of the AIRS database normally contain only the last five years' data. Data for
prior years is removed from the database and stored on tape. This process is called "archiving".
The opposite process, reloading the data on tape to the database, is called "de-archiving".
This message occurs when the date coded on a raw data transaction applies to a year that has
been archived. If the transaction has the correct year coded, contact the AIRS database
administrator to have the data for that year de-archived so the transaction can be applied. The
transaction will not pass edit checks until the raw data has been de-archived.
December 1993
7-5
Raw Data Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR - NOT AUTHORIZED FOR THIS MONITOR
Each monitor-ID is associated with a group of screening files (those whose names are the same
except in the last two positions). The association, or "ownership", is established when the
monitor is inserted into the Site File or when an unassociated monitor is changed by Site or
Monitor transactions (types A1-A7 or F1-F5). Once the association is established, all transactions
involving that monitor must be in the screening file of the group that "owns" the monitor. This
error message means that the screening file group does not have ownership of the monitor-ID on
the raw data transaction. Either the wrong monitor-ID was coded, or a different screening file
must be used for the transaction in question.
Raw Data Transactions 7-6 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
7.1 Common Fields
7.1.1 PARAMETER
PARAMETER is a code assigned to a specific parameter being measured and/or analyzed. It may be a
pollutant, such as ozone, or a non-pollutant, such as wind direction.
Attributes:
5 digit code
Required
Coding Instructions:
Place a valid PARAMETER code in columns 11-15. A code is valid if it exists in the AIRS GEO-
COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
Error Message:
ERROR - INVALID PARAMETER CODE
PARAMETER must be in the GEO-COMMON File.
December 1993
7-7
Raw Data Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
7.1.2 PARAMETER OCCURRENCE CODE
PARAMETER OCCURRENCE CODE (POC) is a code used to distinguish between different monitors
at the same site that are measuring the same parameter. For example, the first monitor established to
monitor CO at a site would have POC — 1. If an additional monitor were established at the same site
to measure CO, that monitor would have POC = 2. However, if a new instrument were installed to
replace the original instrument used as the first monitor, that would be the same monitor and it would
have POC = 1, even if there were a change in sampling method or interval. (Interval can change only
at the end of a year.)
Attributes: 1 digit code
Required
Coding Instructions:
In column 16, enter a valid POC in the range 1 through 9.
Error Message:
ERROR - INVALID POC CODE
POC is a required field. It must be numeric in the range 1-9.
Raw Data Transactions 7-8 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
7.1.3 Monitor Identification Code (Monitor-ID)
The Monitor-ID identifies the monitor to which a transaction applies. It is comprised of the STATE,
COUNTY, SITE, PARAMETER, and PARAMETER OCCURRENCE CODE (POC) fields.
Attributes:
Coding Instructions:
15 digit code
Required
Place a valid monitor-ID in columns 2-16. A monitor-ID is valid if it is in the AQ Site File. You can
obtain a list of monitor-IDs with several standard reports of the Air Quality Retrieval Subsystem,
described in Volume AQ4 of this User's Guide. When coding a monitor-ID ensure that columns 2-3
contain a valid STATE, 4-6 a valid COUNTY, 7-10 a valid SITE, 11-15 a valid PARAMETER, and 16
a valid POC.
Note that you cannot change the monitor-ID of raw data in the database using a MODIFY transaction.
To change monitor-ID you must delete the data from the database and then insert it with the new monitor-
ID code.
Error Messages:
ERROR - INVALID MONITOR-ID
The monitor-ID is not in the Site File. Tnis message occurs only if all the constituent parts of
monitor-ID are valid.
December 1993
7-9
Raw Data Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
7.1.4 INT
INT indicates the sampling interval used for monitoring activities.
Attributes: 1 character code
Required
Coding Instructions:
Enter a valid interval code in column 17. To be valid, an interval code must exist in the AIRS GEO-
COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
For transaction type 1, INT must represent a non-composite sampling interval of less than 24 hours.
For transaction type 2, INT must represent a non-composite sampling interval of 24 hours or greater.
For transaction type 3, INT must be C (composite).
Note that you cannot change the INT of raw data in the database using a MODIFY transaction. To
change INT, you must delete the data from the database and then insert it with the new INT code.
Error Messages:
ERROR - INTERVAL CANNOT CHANGE WITHIN A CALENDAR YEAR
Data in the raw data file for this monitor and year has a different interval than the transaction.
An interval change for a monitor can only occur at a year boundary. If sampling interval
changes within a year, a new monitor (with a different parameter occurrence code) must be
created.
ERROR - INVALID INTERVAL
INT is not in the GEO-COMMON File or it is not valid for the transaction type.
Raw Data Transactions 7-10 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
7.1.5 UNITS
UNITS indicates the dimensional system in which a parameter measurement is expressed.
Attributes:
Coding Instructions:
3 digit code
Required
Place a valid units code in columns 18-20. A code is valid if it exists in combination with
PARAMETER, INTERVAL, and METHOD in the AIRS GEO-COMMON File. Valid codes are listed
in Volume GC2 of the AIRS User's Guide.
Note that you cannot change the UNITS of raw data in the database using a MODIFY transaction. To
change UNITS, you must delete the data from the database and then insert it with the new UNITS code.
Error Messages:
ERROR - INVALID POLL-INT-METH-UNITS
If PARAMETER, INTERVAL, and METHOD are valid, then the combination of these three and
UNITS code must exist in the GEO-COMMON File.
ERROR - INVALID UNITS
The UNITS code must be in the GEO-COMMON File.
ERROR - UNITS CANNOT CHANGE WITHIN A CALENDAR MONTH
The UNITS code of an INSERT transaction is different from the UNITS of data already in the
database for the same month. Units code changes can occur only at month boundaries.
ERROR - UNITS MUST MATCH UNITS ON DATABASE
The UNITS code of a MODIFY transaction is different from the UNITS of the data in the
database to which the transaction applies.
WARNING - CANNOT VERIFY UNITS
If PARAMETER or INTERVAL or METHOD is invalid and UNITS is in the GEO-COMMON
File, then UNITS cannot be verified further.
December 1993
7-11
Raw Data Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
7.1.6 METHOD
METHOD indicates the method used to sample and analyze parameter values.
Attributes: 3 digit code
Required
Coding Instructions:
Place a valid method code in columns 21-23. A method code is valid if it exists in combination with
parameter, interval, and units in the AIRS GEO-COMMON File. Valid codes are listed in Volume GC2
of the AIRS User's Guide.
Note that if you change or delete the METHOD of raw data in the database, a warning message will be
issued if the input METHOD does not match the METHOD in the database.
Error Messages:
ERROR - INVALID METHOD
METHOD must be numeric.
ERROR - INVALID METHOD FOR STATE
If PARAMETER, METHOD, INTERVAL, and UNITS exist in the GEO-COMMON File, then
the METH-VAL-FLAG must be checked. If METH-VAL-FLAG = N, then METHOD is
invalid, except for states listed in the STATE fields of the GEO-COMMON record.
ERROR - INVALID POLL-INT-METH-UNITS
If PARAMETER, INTERVAL, and UNITS are valid, then the combination of these with
METHOD must exist in the GEO-COMMON File.
WARNING - CANNOT VERIFY METHOD
If PARAMETER or INTERVAL or UNITS is invalid and METHOD is numeric, it cannot be
verified further.
WARNING - METHOD DOES NOT MATCH METHOD ON DATABASE
The METHOD code of a MODIFY or DELETE transaction is different from the METHOD of
the data in the database to which the transaction applies.
Raw Data Transactions 7-12 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
7.1.7 YEAR
YEAR contains the last two digits of the year for which raw data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 24-25, enter a valid year between 1957 and the current year.
Note that you cannot change the YEAR of raw data in the database using a MODIFY transaction. To
change YEAR you must delete the data from the database and then insert it with the new YEAR value.
Error Messages:
ERROR - INVALID YEAR
Year is not in the range 57 through current year.
ERROR - MONITOR INACTIVE FOR THIS DATE
The combination of YEAR with MONTH and DAY or with PERIOD CODE specifies a date
before this monitor began sampling or after sampling ended. The dates when sampling began
and ended are stored in the Site File. (See fields DATE SAMPLING BEGAN and DATE
SAMPLING ENDED of the Fl transaction in Section 5 of this voiume.)
December 1993
7-13
Raw Data Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
7.2 Transaction Type 1 - Hourly Data
The type 1 transaction is used for parameter observations with sampling intennJs less than 24 hours.
Type 1 transactions insert, modify, or delete raw data values in the Hourly File of the AIRS database.
The coding form for the type 1 transaction is shown in Figure 7-1. Each line across the body of the form
represents one transaction, which can hold as many as eight observations, or "sample values".
AH the sample values entered on a particular type 1 transaction apply to the same day. The hour of a
sample value is determined by its position on the transaction (which "slot" it occupies). The first slot is
for the hour specified in the stan hour (ST HR) field of the transaction. The second slot is for the start
hour plus the sampling interval, the third slot is for the start hour plus twice the sampling interval, and
so on. In general, hour of a slot = (start hour) + [(slot number - 1) * (hours in sampling interval)].
Because there can be as many as eight sample values per transaction, the temporal scope of a given type
1 transaction varies considerably depending on the sampling interval. With some intervals, a single
transaction holds all the sample values for a day, while multiple transactions are needed with other
intervals. For example, only four slots of one transaction are used to report the 6-hour observations for
a day, while all eight slots of three transactions are needed to report the 1-hour observations for a day.
Recognizing the temporal scope of a transaction is most important with DELETE actions, described
below.
An INSERT transaction is used to insert observations or missing value reason codes into the database
where neither currently exists. A sample value slot on the transaction is ignored if it is blank, and has
no effect on the database.
A MODIFY transaction is used to change or delete existing observations or missing value reason codes.
A sample value slot on the transaction is ignored if it is blank, and has no effect on the database. A
MODIFY transaction may not be used to insert a value where none currently exists; an INSERT
transaction must be used for that purpose. Furthermore, a MODIFY transaction may not be used to
change the interval, method, units, or date/time of an observation. The existing data must be deleted and
inserted with the desired new value to change any of those fields.
A DELETE transaction is used to remove all the existing observations and missing value reason codes
within the temporal scope of the transaction. The sample value slots are not used and are ignored. An
observation or code does not have to exist for every hour within the scope of the transaction; those that
do exist are deleted.
Transaction Type 1 7-14 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
Transaction Type 1 Error Messages:
ERROR - ALL FIELDS BLANK ON MODIFY
All the fields (INT through VF #8) of a MODIFY transaction are blank.
ERROR - DUPLICATE HOURLY VALUES ON THESE RECORDS
There are two or more transactions with the same action code that have a SAMPLE VALUE for
the same monitor, date, and hour. There is no limit on the number of transactions for a given
monitor and date, just so no two of them have the same action code for the same hour. As many
as three transactions may pertain to the SAMPLE VALUE for a given hour if they all have
different action codes. If multiple actions for one hour are present, they are applied to the
database in the order DELETE, INSERT, MODIFY.
December 1993
7-15
Transaction Type 1
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
i.-
i i 1 1
1 I
!
i
i :
• i
s r
$ j:
si
55
Hill
1
.55
i:
S S
I I I
. ! ;l M I I I I I ! I I I ! I ! I
a- - I «' I ! I I : i : t 1 i ' i . ' I ! I i I ! i ! i I ' I
i i
5 *
i i i i i
i I
I ' i
Figure 7-1. Coding Form for Transaction Type 1
Transaction Type 1
7-16
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
7.2.1 MONTH
MONTH identifies the month for which hourly data is being reported.
Attributes:
2 digit date
Required
Coding Instructions:
In columns 26-27, enter a valid month designation (01-12). Use a leading zero as needed.
Error Messages:
ERROR - INVALID MONTH
Valid values are 01 through 12. The combination of YEAR, MONTH, and DAY must be a valid
Gregorian date within the range January 1, 1957, through the current date.
ERROR - MONITOR INACTIVE FOR THIS DATE
The combination of YEAR, MONTH, and DAY must fall within the bounds of the dates
sampling began and ended at this monitor. The sampling dates used for the comparison may be
present on the F transaction being submitted for this monitor or, if not, are stored in the Site
File. (See fields DATE SAMPLING BEGAN and DATE SAMPLING ENDED of the type Fl
transaction in Section 5 of this volume.)
December 1993
7-17
Transaction Type I
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
7.2.2 DAY
DAY is the day of the month for which hourly data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 28-29, enter a valid day designation (01-31, depending on MONTH). Use a leading zero as
needed.
Error Messages:
ERROR - INVALID DAY
DAY must be valid for the given MONTH. The combination of YEAR, MONTH, and DAY
must be a valid Gregorian date within the range January 1, 1957, through the current date.
ERROR - MONITOR INACTIVE FOR THIS DATE
The combination of YEAR, MONTH, and DAY must fall within the bounds of the dates
sampling began and ended at this monitor. The sampling dates used for the comparison may be
present on the F transaction being submitted for this monitor or, if not, are stored in the Site
File. (See fields DATE SAMPLING BEGAN and DATE SAMPLING ENDED of the type Fl
transaction in Section 5 of this volume.)
Transaction Type 1 7-18 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
7.2.3 ST HR (Start Hour)
ST HR is the beginning hour of the sampling period for the first SAMPLE VALUE "slot" on the
transaction, given in standard time at the location of the monitoring site The first hour of a day, 00,
begins at midnight, and the last hour, 23, begins at 11:00 p.m.
Attributes:
Coding Instructions:
2 digit code
Required
In columns 30-31, enter a valid start hour based on the interval. The table below gives the permissible
ST HRs for the various intervals allowed for a type 1 transaction:
Sampling Interval INT Code
Start Hours (ST HR)
1 hour
2 hours
3 hours
4 hours
6 hours
8 hours
12 hours
1
2
B
3
4
5
6
00, 08, 16
00, 01, 16, 17
00 through 02
00 through 03
00 through 05
00 through 07
00 through 1 1
Error Messages:
ERROR - INVALID START-HOUR
Valid values depend upon INT. ST HR must be one of the values listed above for the relevant
interval.
ERROR - NOT ALLOWED 2 CARDS WITH THESE START HOURS
There cannot be two interval 2 (2-hour) transactions with the same action code for the same day
whose stan hours are 00 and 01 or 16 and 17. The first card should be either 00 or 01 and the
second card should be either 16 or 17.
ERROR - NOT ALLOWED TWO START HOURS FOR THIS INTERVAL
For intervals B, 3, 4, 5, and 6 (3, 4, 6, 8, and 12 hours), there cannot be two transactions with
the same action code for the same day whose start hours are different.
December 1993
7-19
Transaction Type 1
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
WARNING - CANNOT VERIFY START-HOUR
If INTERVAL is invalid, ST HR cannot be checked.
Transaction Type 1 7-20 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
7.2.4 DP
DP indicates the number of digits to the right of the decimal point in the SAMPLE VALUE fields.
Attributes:
Coding Instructions:
1 digit code
Conditionally required
Enter a valid DP value in column 32. Valid values are blank and the digits 0-5. The same DP value
applies to all SAMPLE VALUE fields on the transaction. If the sample values require different DPs,
use multiple transactions to code the compatible DP and SAMPLE VALUEs.
With INSERT and MODIFY transactions, DP may be either numeric or blank. A numeric value for DP
implies that true observations are coded in the SAMPLE VALUE fields, and that they are to be scaled
by the power of ten indicated by DP. A blank value for DP implies that missing value reason codes
("null values") are coded in the SAMPLE VALUE fields rather than true observed values. This means
that you cannot code both true observations and missing value reason codes on the same transaction
because their DP requirements are incompatible. You can, however, code two transactions for the same
time period, one for the true observations and the other for the missing value reason codes.
Although you can place an asterisk in this field on a DELETE transaction, doing so is meaningless. A
DELETE on a type 1 transaction says to delete all values in the time range covered by the transaction.
Error Messages:
ERROR - INVALID DECIMAL-POSITION
Valid values are 0 through 5 and blank.
December 1993
7-21
Transaction Type 1
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
7.2.5 SAMPLE VALUE (8 occurrences)
The eight SAMPLE VALUE fields contain the actual numeric values of the hourly data.
Attributes: 4 digit numeric
Required for INSERT and MODIFY (one occurrence)
Coding Instructions:
A type 1 transaction has slots for eight observations. These slots are in columns 33-36, 38-41, 43-46,
48-51, 53-56, 58-61, 63-66, and 68-71. The slot into which an observation is placed depends upon the
hour associated with the observation, the sampling interval (INT in column 17), and the start hour (ST
HR in columns 30-31) for the day's observations, according to the relationship:
SLOT* = 1 + (HR - SH) / NH
where HR is the hour associated with the observation,
SH is the start hour of the observations for that day, and
NH is the number of hours between observations.
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date and hour corresponding to the slot you use. Place in SAMPLE
VALUE a true observation of a parameter value or a code for why a true observation is not being
reported (a missing value reason code, or "null value"). Leave blank any occurrence of SAMPLE
VALUE for an hour when you do not wish to report a true observation or a missing value reason code.
You must enter a numeric value in at least one of the SAMPLE VALUE slots.
Use a MODIFY transaction to alter or delete a value that already exists in the database. A value must
exist in the database for the date and hour corresponding to each slot you use. Fill the SAMPLE VALUE
field with asterisks to delete an existing value. To alter an existing SAMPLE VALUE, code a true
observation or a missing value reason code as described above for the INSERT action. Leave blank each
occurrence of SAMPLE VALUE for an hour when you do not wish to alter or delete an existing value.
You must enter a numeric value or asterisks in at least one of the SAMPLE VALUE slots.
Use a DELETE transaction to delete from the database all the values corresponding to the available slots
on the transaction. For example, if the DELETE transaction is for 4-hour data (INT=3) and the start
hour (ST HR) is 01, then the values for hours 01, 05, 09, 13, 17, and 21 would be deleted. (The last
two slots of the transaction would have no effect because they are not used for the specified interval.)
You need not enter asterisks or any other value in the SAMPLE VALUE slots (or the DP field); they are
ignored.
Numeric values that represent true observations must be entered right justified in the SAMPLE VALUE
fields. Leading zeros are optional. For some PARAMETERS you may enter negative values. To enter
a negative value, place a minus sign in the first position of the SAMPLE VALUE field and three digits
in the remaining positions. For example, you would code the negative value -3 as -003 on the
transaction. Remember to allow for the implied decimal point indicated by the DP field.
Transaction Type 1 7-22 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
For some PARAMETERS, upper limits have been established for observations, and the numeric value
you enter cannot exceed that maximum (unless you also enter a validity flag with the value). The
relevant maximum values and PARAMETERS are listed below:
Maximum Value
75 ppm
2620 ug/m3
1 ppm
1 ppm
1.5 ppm
100 ppm
10 ppm
0.5 ppm
0.5 ppm
360 degrees
360 degrees
360 degrees
360 degrees
360 degrees
PARAMETER
42101 (carbon monoxide)
42401 (sulfur dioxide)
42601 (nitric oxide)
42602 (nitrogen dioxide)
42603 (oxides of nitrogen)
43101 (total hydrocarbon)
43102 (non-methane hydrocarbon)
44101 (total oxidants)
44201 (ozone)
61102 (horizontal wind direction)
61104 (resultant 1-hour horizontal wind direction)
61106 (std. deviation of horizontal wind direction)
61107 (std. deviation of vertical wind direction)
61112 (vertical wind direction)
Missing value reason codes, or "null values", are 4-digit codes. Valid codes are in the GEO-COMMON
File, and you can find a listing of them in Volume GC2 of the AIRS User's Guide. Note that DP must
be blank in order for SAMPLE VALUE to be interpreted as a missing value reason code. You cannot
put missing value reason codes and true observations on the same transaction.
Error Messages:
ERROR - ALL SAMP-VALUES CANNOT BE BLANK
For an insert transaction, all eight SAMPLE VALUE fields cannot be blank.
ERROR - HIGH SAMPLE-VALUE
The value given exceeds the maximum value allowed for the PARAMETER.
December 1993
7-23
Transaction Type 1
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR - INVALID NULL SAMPLE-VALUE
When DP field is blank on an INSERT or MODIFY transaction, the SAMPLE VALUE fields
are interpreted as missing value reason codes ("null value"). The SAMPLE VALUE field
associated with this message does not contain a valid "null value" code. Valid codes are in the
GEO-COMMON File, and they are listed in Volume GC2 of the AIRS User's Guide. If a
missing value reason code should not be entered, place an appropriate numeric value in the DP
field.
ERROR - INVALID SAMPLE-VALUE
For an INSERT transaction, SAMPLE VALUE may be blank, a 4-digit missing value reason
code, an unsigned numeric value right justified in the field, or a signed numeric value of the form
-nnn. A signed numeric value is allowed only for certain PARAMETERS (61109, 61202,62101,
62103, 62106, 63305, or 81102).
For a MODIFY transaction, this field may be asterisks or one of the values allowed for an
INSERT transaction.
ERROR - TOO MANY REPORTED VALUES FOR THIS INTERVAL
More sample values than can exist for one day have been entered. The maximum number of
values is based on interval according to:
Maximum Number
Sampling Interval INT Code Of Values
1 hour 1 24
2 hours 2 12
3 hours B 8
4 hours 3 6
6 hours 4 4
8 hours 5 3
12 hours 6 2
Transaction Type 1 7-24 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
7.2.6 VF (8 occurrences)
VF (Validity-Flag) is used to give the reason for an abnormal observation. The presence of VF with an
observation indicates that the observation is due to an "exceptional event" or its abnormal value has been
checked and found to be valid. State or EPA regional personnel must approve of the use of validity
flags. Refer to "Guideline on the Identification and Use of Air Quality Data Affected by Exceptional
Events", publication #EPA-450/4-86-007, July, 1986.
Attributes:
Coding Instructions:
1 character code
Optional
If an observation results from an exceptional event (e.g., volcano, forest fire, disaster clean-up, etc.),
place a valid validity flag in column 37, 42, 47, 52, 57, 62, 67, and/or 72. A valid validity flag is one
that exists in the AIRS GEO-COMMON File for this parameter. Valid codes are listed in Volume GC2
of the AIRS User's Guide. The code "V", which stands for "validated", is also used for VF when there
is no specific cause attributable for an abnormal value.
VF may not be inserted or modified by itself. If VF is valued, the corresponding SAMPLE VALUE
must also appear. About the only time this wiil matter is when you need to attach a validity flag to an
already entered value. In such a case, you must re-enter the value with the validity flag using a MODIFY
transaction.
To delete a validity flag from the database, code an asterisk for VF and code the observation value in the
associated SAMPLE VALUE field.
Error Messages:
ERROR - BAD VALIDITY-FLAG FOR PARAMETER
For an insert transaction, the VF can be V, blank, or an exceptional event flag that is in the
GEO-COMMON File for the PARAMETER.
For a modify transaction, the VF can be asterisk or one of the values allowed for an INSERT
transaction.
/
ERROR - INVALID VALIDITY-FLAG
On a MODIFY transaction, if VF is not V, blank, asterisk, or one of the valid codes in the GEO-
COMMON File, it is an error.
December 1993
7-25
Transaction Type 1
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR - VALIDITY-FLAG NOT ALLOWED
The VF can only be entered if its corresponding SAMPLE-VALUE is valued.
On a modify transaction, VF cannot be an asterisk if the SAMPLE-VALUE field is blank.
If DP is blank, then VF must be blank.
WARNING - CANNOT VERIFY VALIDITY-FLAG
The combination of PARAMETER and VF cannot be validated because PARAMETER is invalid.
Transaction Type 1 7-26 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
7.2.7 Statistical Tests
The Pattern and Gap tests performed on hourly data (INT = 1) are described briefly below. See the EPA
document "Screening Procedures for Ambient Air Quality" for more detailed information (publication
# EPA-450/2-78-037, July 1978). All the values for a month must pass the statistical tests. If any value
in the month fails any test, the entire month fails.
7.2.7.1 Pattern Tests
Pattern Tests are performed on hourly data for pollutants 44201 (O3), 42101 (CO), 42401 (SOj), and
42602 (NOj). Exceptional event data are excluded from the tests. The tests are run on a month of hourly
data. Essentially, each test scans the month's values and compares them against empirically derived
thresholds to determine if they are questionable. If so, the value is flagged as failing that particular test.
The raw data values are converted to the appropriate units before the tests are applied. The factors used
to convert from reporting units to the units of the tests are given in Table 7-1. The threshold values for
each pollutant and each test are listed in Table 7-2. As that table shows, different threshold values pertain
depending on the season of the year and the time of day.
The Dixon test (not applied to CO) scans each day's values and determines the highest, second highest,
and lowest values in that day. It then computes the Dixon ratio, defined as (max - secmax) / (max -low).
If this value is greater than 0.55, the day fails the Dixon test and all hours are marked as failing.
The Max Hour test compares each value in the month to a constant to determine if the value is too high.
If so, it is marked as failing.
The High Difference test compares the value at each hour in the month to the previous hour and the
subsequent hour. If the difference between any two hours is greater than allowable, then the hour under
inspection is marked as failing.
The Spike test works much like the High Difference test, except that both differences must be greater than
allowable for the test to fail. Also, the percentage difference between the hour in question and both its
adjacent hours must be greater than allowable for the test to fail. If either the difference or the
percentage comparison fails, the value is rejected.
The High Consecutive Values test looks at each hour and the subsequent three hours. If all four values
are greater than allowable, then all four hours are marked as failing the test.
December 1993
7-27
Transaction Type I
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
If a value fails a test, the following message will be received in the EDIT error report:
WARNING - HOURLY VALUE FAILS PATTERN TEST
Additional information about values that failed pattern tests is presented in the EDIT "patterns and gap
failure" report (see Figure 7-2 below). Since the various pattern tests are used to detect abnormal values,
look for a value that is much higher or lower than its neighbors. If alt values are indeed correct, some
of them should be marked as exceptional events or as validated values.
Table 7-1. Conversion Factors for the Pattern and Gap Tests
Pollutant
42101 (CO)
Units for Gap and
Pattern Tests
ppm
42401
pphm*
42602
pphm*
44201 (Oj)
pphm"
Reported Units
005 (mg/m3 25°)
006 (mg/m3 0°)
007 (ppm)
008 (ppb)
001 (ug/m3 25°)
002 (ug/m3 0°)
007 (ppm)
008 (ppb)
001 (ug/m3 25°)
002 (ug/m3 0°)
007 (ppm)
008 (ppb)
001 (ug/m3 25°)
002 (ug/m3 0°)
007 (ppm)
008 (ppb)
Conversion
Factors
0.86957
0.79653
1.0
0.001
0.03817
0.03496
100.0
0.1
0.05319
0.04872
100.0
0.1
0.05102
0.04673
100.0
0.1
*pphm = parts per hundred million
Transaction Type 1
7-28
December 1993
-------
AIRS User's Guide
Volume AQ2
Pollutant
Ozone
(pphm)
Carbon
Monoxide
(ppm)
Sulfur
Dioxide
(pphm)
Nitrogen
Dioxide
(pphm)
Table 7-2.
Data
Stratification
Summer-Day
Months: 05-10
Hours: 10-17
Summer-Night
Months: 05-10
Hours: 18-09
Winter-Day
Months: 11-04
Hours: 10-17
Winter-Night
Months: 11-04
Hours: 18-09
Rush Traffic
Hours: 06-10,
16-20
Non-Rush Traffic
Hours: 11-15,
21-05
Zone 1
Regions: 1,5,6,7
Zone 2
Regions: 2,3,4
Zone 3
Regions: 8,9,10
None
Air Quality Data Coding
Threshold Values for the Pattern Tests.
Max. High Consecutive
Hour Diff. Spike Values Min.
Test Test Test Test Value*
50 15 10(300%) 26 5
38 10 5(300%) 26 5
26 13 10(300%) 26 5
15 10 5 (300%) 26 5
65 22 17(500%) 35 17
44 22 17 (500%) 35 17
99 19 8 (500%) 38 25
50 11 8(500%) 38 25
30 8 8 (500%) 38 25
64 27 11(300%) 53 12
*Values below the minimum are excluded from the High Difference and Spike tests.
December 1993
7-29
Transaction Type 1
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
7.2.7.2 Gap Test
The Gap Test is performed on data for pollutants 44201 (0-,), 42101 (CO), 42401 (SO;), and 42602
(NOj). Exceptional events data are excluded. The Gap test is so named because it looks for gaps in
the frequency distribution table for a month's values. The test is run on a month of hourly data (INT
= 1). For each pollutant, the program builds a frequency distribution table and computes constants
associated with the frequency distribution. If there is not enough data to compute the constants, a
warning is issued. Having determined the constants, a largest reasonable gap is estimated Then the
largest actual gap in the data is determined and compared to the largest estimated gap to determine
whether the month passes or fails the Gap test.
Error Messages:
WARNING - HOURLY VALUES FAIL GAP TEST
If erroneous values are found, correct them and run EDIT again. If all values are correct,
mark the values that caused the failure as either exceptional events or validated values (after
obtaining the necessary approval).
WARNING - INSUFFICIENT HOURLY VALUES TO PERFORM GAP TEST
At least two values are required to perform the Gap test.
WARNING - SOURCE ORIENTED SO2 FAILED GAP TEST
SO2 data with a project class of '2' failed the Gap test.
Transaction Type 1 7-30 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
7.2.7.3 Patterns and Gap Failure Report
Figure 7-2 shows a sample of the Patterns and Gap Failure Report produced by the EDIT program.
The report identifies the day in which a pattern test failed or the month in which the gap test failed,
and it shows the first and last "keys" of the transactions involved in the failed test. Under the
beading "hourly values failing test(s) / test(s) failed", the report gives addition information to help
identify the values that failed the test.
For pattern test failures, the report shows all the values for each day in which a value failed a test. If
database values are being changed with modify transactions, some of the values listed may be from
the database and some from the transactions in the screening file. One-letter codes under the values
indicate which of the pattern tests a value failed. If a particular value failed more than one test,
multiple codes are listed. The codes are:
D Dixon test
M Max hour test
H High difference test
S Spike test
C High consecutive values test
The codes are also listed on each page of the reports as part of the page heading.
Determining which values are involved in a failure of the gap test is a bit more difficult. The gap test
identifies a gap in the frequency distribution of a month's values. Often, but not always, the gap is
due to an "outlier", a value unusually higher or lower than the bulk of the data for the month. The
Patterns and Gap Failure Report does not identify the date and hour of the value(s) failing the gap
test, but it does give information that may allow manual identification of the values(s). "Gap size" is
the difference in magnitude between the two values on either side of the gap in the frequency
distribution, expressed in the units used for the gap test (ppm or pphm). "Num above gap" is the
number of values above the gap. If the number of values is large, the gap is in the smallest values
for the month. Finally, "slot below gap" is the value on the low end of the gap, expressed in the
units of the test (ppm or pphm).
To identify a gap manually, it may be necessary to list values both in the database and in the
screening file. Refer to Volume AQ4 of the AIRS User's Guide for instruction for generating listings
of the raw data values in the AIRS database or in a screening file. (See report numbers AMP350 and
AMP950.)
December 1993
7-31
Transaction Type 1
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
09/30/93
AMP050
AEROMETRtC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
EDIT PATTERNS AND GAP FAILURE REPORT
FOR SCREENING FILE ANAOBA10
PAGE:
TEST H - MAX HOUR TEST H - HI DIFF TEST 0 - DIXON RATIO TEST S - SPIKE TEST C - HI-CONS-4-HR
RECORD KEY TYMMOO HOURS HOJRLY VALUES FAILING TEST{S) / TEST(S) FAILED
FAILED GAP TEST
37067D0014240118610601001
THRU
37067000142401U610621161
86060$ 00-07
06-15
16-23
640. 650. 685. 660. 665. 90.
M
3706700014240118610601001
THRU
3706700014740118610621161
3706700014240118610601001
THRU
3706700014240118610621161
860614 00-07
08-15
16-Z3
860615 00-07
08-H
16-23
680.
650.
685.
680.
H
650.
685.
50.
600.
650.
650.
600.
650.
1685.
HNS
690.
655.
N
685.
690.
655.
90.
695.
1660.
HN C
690.
645.
630.
665.
H
600.
1665.
M C
665.
600.
en.
660.
69S.
1690.
M C
660.
695.
690.
655.
692.
1673.
MH C
643.
690.
685.
650.
670.
I960.
NHSC
650.
670.
680.
3706700014Z401186106Q1QOI
THRU
3706700014240118610621161
8606
860601
860602
860604
GAP SIZE: U WJM ABOVE GAP: 224 SLOT BELOK GAP:
FAILED GAP
00-07
08-15
16-23
00-07
08-15
16-23
00-07
08-15
16-23
680.
650.
680.
685.
.0680
.0685
650.
605.
650.
610.
650.
.1650
.0650
685.
69D.
685.
65S.
.1685
.0655
690.
60S.
690.
695.
660.
.5660
.0660
665.
632.
611.
603.
605.
.0665
.0665
660.
599.
660.
635.
690.
.0690
.0690
605.
690.
615.
678.
.0685
.0688
609.
670.
611.
670.
680.
.0680
.0620
Figure 7-2. Sample Patterns and Gap Failure Report
Transaction Type 1
7-32
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
7.3 Transaction Type 2 - Daily Data
Type 2 transactions are used to provide data about parameters with non-composite sampling intervals
of 24 hours or greater.
Figure 7-3 shows the coding form for transaction type 2. Each line across the body of the form
corresponds to a transaction.
An INSERT transaction is used to insert observations or missing value reason codes where none
already exists in the database.
A MODIFY transaction is used to change or delete existing fields within daily records in the
database. A value is deleted by filling the SAMPLE VALUE (and, optionally, the VF field) with
asterisks.
A DELETE transaction is used to remove a value or missing value reason code from the database. A
DELETE transaction is equivalent to a MODIFY transaction with asterisks.
Error Messages:
ERROR - ALL FIELDS BLANK ON MODIFY
All the fields (INT through VF) of a modify transaction are blank. INT, UNITS, METHOD,
and at least one of START HOUR, SF, DF, SAMPLE VALUE, or VF must be specified.
December 1993
7-33
Transaction Type 2
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
~l
>s
o«;
OSS
Ssgl
ut K < O £
\-t° U
zs<
IP
s S s
I '
: 6 =
- S -!
ir
T
0.
•c
*~
_ .£ U. O •
s: o er"- Z
e .E .E « j.
E -5.-Q. E =
5 E E o 1
ec
O
a.
O
Z
- .
O >
Figure 7-3. Coding Form for Transaction Type 2
Transaction Type 2
7-34
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
7.3.1 MONTH
MONTH is the month for which daily data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 26-27, enter a valid month designation (01-12). Use a leading zero as needed.
Error Messages:
ERROR - INVALID MONTH
Valid values are 01 through 12. The combination of YEAR, MONTH, and DAY must be a
valid Gregorian date within the range January 1, 1957 through the current date.
ERROR - MONITOR INACTIVE FOR THIS DATE
The combination of YEAR, MONTH, and DAY must fall within the bounds of the dates
sampling began and ended at this monitor. The sampling dates used for the comparison may be
present on the Fl transaction being submitted for this monitor or, if not, are stored in the Site
File. (See fields DATE SAMPLING BEGAN and DATE SAMPLING ENDED of the type Fl
transaction in Section 5 of this volume.)
December 1993 7-35 Transaction Type 2
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
7.3.2 DAY
DAY indicates the day of the month for which daily data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 28-29 enter a valid day designation (01-31, depending on MONTH). Use a leading zero
as needed.
Error Messages:
ERROR - INVALID DAY
DAY must be valid for the given MONTH. The combination of YEAR, MONTH, and DAY
must be a valid Gregorian date within the range January 1, 1957 through the current date.
ERROR - MONITOR INACTIVE FOR THIS DATE
The combination of YEAR, MONTH, and DAY must fall within the bounds of the dates
sampling began and ended at this monitor. The sampling dates used for the comparison my be
present on the Fi transaction being submitted for this monitor, or it not, are stored in the Site
File. (See fields DATE SAMPLING BEGAN and DATE SAMPLING ENDED of the type Fl
transaction in Section 5 of this volume.)
Transaction Type 2 7-36 December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
7.3.3 START HOUR
START HOUR is the beginning hour for the sampling period in standard time at the location of the
monitoring site. The first hour of a day, 00, begins at midnight, and the last hour 23, begins at
11:00 p.m.
Attributes: 2 digit numeric
Required if DP is non-blank
Prohibited if DP is blank
Coding Instructions:
On an INSERT or MODIFY transaction, START-HOUR must be blank if the DP field is blank, and
START HOUR must be numeric (00-23) if the DP field is non-blank. This means you cannot insert
or change START HOUR by itself or when a missing value reason code is entered in SAMPLE
VALUE. It also means you can delete START HOUR only if you use a DELETE transaction. In
order to change an existing START HOUR in the database, you must also code the DP and SAMPLE
VALUE fields on a MODIFY transaction.
On a DELETE transaction, START HOUR can have any value; it is ignored.
Error Messages:
ERROR - INVALID START-HOUR
Valid values are 00 through 23 when DP is numeric.
ERROR - START-HOUR NOT ALLOWED
START HOUR must be blank if DP is blank, meaning a missing value reason code is being
entered.
December 1993 7-37 Transaction Type 2
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
7.3.4 SF (Sampling Frequency)
SF indicates how much time elapses between observations. It is expressed in terms compatible with
the associated INTERVAL. For example, an SF of *3' for weekly data (INT = A) indicates that
samples are taken every three weeks.
Attributes:
1 character code
Required for TSP and PM-10
Optional otherwise
Coding Instructions:
To INSERT or MODIFY, enter a valid code in column 32.
A code is valid if it appears in a GEO-COMMON type E Description record with Item Type = SF
(except code 'S')-
To DELETE, place an asterisk in column 72 of a MODIFY transaction.
Error Messages:
ERROR - INVALID SAMPLE-FREQUENCY
For an insert transaction,this field may be blank or numeric > 0.
For a modify transaction, this field may be blank, asterisks, or numeric > 0.
Transaction Type 2
7-38
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
7.3.5 DP (Decimal Position)
DP indicates the number of digits to the right of the decimal point in the SAMPLE VALUE field.
Attributes: 1 digit numeric
Required for actual observations
Prohibited for missing reason codes and deletion
Coding Instructions:
When inserting or modifying an actual observation (coded in SAMPLE VALUE), place an integer
value, 0-5, in column 33. In all other circumstances, leave the DP field blank. This includes
inserting or modifying a missing value reason code, and deleting an existing value from the database
by coding asterisks for SAMPLE VALUE on a MODIFY transaction.
Error Messages:
ERROR - INVALID DECIMAL-POSITION
Valid values for DP ar 0-5 and blank.
E»ecember 1993 7-39 Transaction Type 2
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
7.3.6 SAMPLE VALUE
SAMPLE VALUE is the observation being reported, or a missing reason code.
Attributes: 4 digit numeric
Required
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not
be a value in the database for the date of the transaction. Place in SAMPLE VALUE a true
observation of a parameter value or a code for why a true observation is not being reported (a
missing value reason code, or "null value").
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in
the database for the date of the transaction. To alter an existing SAMPLE VALUE, code a true
observation or a missing value reason code as described above for the INSERT action. You may also
fill the SAMPLE VALUE field with asterisks to delete an existing value, but it is easier (and better)
to use a DELETE transaction. You must enter a numeric value or asterisks in the SAMPLE VALUE
field.
Use a DELETE transaction to delete a value from the database. A value must exist in the database
for the date of the transaction. You need not enter asterisks or any other value in the SAMPLE
VALUE field; they are ignored. A DELETE transaction removes the value and the associated start
hour and sampling frequency fields from the database. Using a MODIFY transaction with asterisks to
delete SAMPLE VALUE leaves those two associated fields in the database. For that reason, you
should use a DELETE transaction instead of MODIFY to delete values from the database.
Numeric values that represent true observations must be entered right justified in the SAMPLE
VALUE field (column 34-37). Leading zero are optional. For some PARAMETERS you may enter
negative values. To enter a negative value, place a minus sign in the first position of the SAMPLE
VALUE field and three digits in the remaining positions. For example, you would code the negative
value -13 as -013 on the transaction. Remember to allow for the implied decimal point indicated by
the DP field.
For some PARAMETERS, upper limits have been established for observations, and the numeric value
you enter cannot exceed that maximum (unless you also enter a validity flag with the value). The
relevant maximum values and PARAMETERS are listed below:
Transaction Type 2
7-40
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
Maximum Value PARAMETER
1000 ug/m3 11101 (total suspended paniculate)
100 ug/m3 12128 (lead)
2620 ug/m3 42401 (sulfur dioxide)
1 ppm 42602 (nitrogen dioxide)
360 degrees 61104 (resultant 24-hour horizontal wind direction)
1000 ug/m3 81102 (paniculate matter)
Missing value reason codes, or "null values", are 4-digit codes. Valid codes are in the GEO-
COMMON File, and are listed in Volume GC2 of the AIRS User's Guide. Note that DP must be
blank in order for SAMPLE VALUE to be interpreted as a missing value reason code.
Error Messages:
ERROR - HIGH SAMPLE-VALUE
The value given exceeds the maximum value allowed for the PARAMETER.
ERROR - INVALID NULL SAMPLE-VALUE
For an INSERT or MODIFY transaction, if DP is blank, then the SAMPLE VALUE must be
one of the missing value reason codes in the GEO-COMMON File.
ERROR - INVALID SAMPLE-VALUE
For an INSERT transaction, SAMPLE VALUE may be blank, a 4-digit missing value reason
code, an unsigned numeric value right-justified in the field, or a signed numeric value of the
form - nnn. A signed numeric value is allowed only for PARAMETERS 62104 and 62105.
For a MODIFY transaction, SAMPLE VALUE may be asterisks or one of the values allowed
for INSERT transactions.
December 1993 7-41 Transaction Type 2
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
7.3.7 VF
VF (Validity Flag) is used to give the reason for an abnormal observation. The presence of VF with
an observation indicates that the observation is due to an "exceptional event" or its abnormal value
has been checked and found to be valid. State or EPA regional personnel must approve of the use of
validity flags. Refer to "Guideline on the Identification and Use of Air Quality Data Affected by
Exceptional Events", publication IEPA-450/4-86-007, July, 1986.
Attributes:
1 character code
Optional
Coding Instructions:
To INSERT or MODIFY, place a validity flag code in column 38. Valid codes are listed in Volume
GC2 of the AIRS User's Guide. The code "V", which stands for "validated", is used when there is
no specific cause attributable for an abnormal value.
To DELETE, place an asterisk in column 38 of a MODIFY transaction along with the associated
value in columns 34-37 (even if the value is unchanged, its presence is required).
Error Messages:
ERROR - BAD VALIDITY-FLAG FOR PARAMETER
For an insert transaction, VF can be V (validated value), blank, or one of the exceptional event
flags in the GEO-COMMON File for the PARAMETER.
For a modify transaction, VF can be V, blank, asterisk, or one of the exceptional event flags in
the GEO-COMMON File for the PARAMETER.
ERROR - INVALID VALIDITY-FLAG
If VF is not V, blank, or asterisk on a modify and it is not in the GEO-COMMON File, it is an
error.
ERROR - VALIDITY-FLAG NOT ALLOWED
The VF can only be entered if its corresponding SAMPLE-VALUE is valued.
On a modify transaction, VF cannot be asterisk if the SAMPLE-VALUE field is blank.
If DP is blank, then VF must be blank.
WARNING - CANNOT VERIFY VALIDITY-FLAG
The combination of PARAMETER and VF cannot be validated because PARAMETER is
invalid.
Transaction Type 2
7-42
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
7.3,8 Statistical Tests
The Shewhart test which is performed on Interval 7 (daily) data is described briefly herein. See the
EPA Document "Screening Procedures for Ambient Air Quality" for more detailed information
(publication # EPA-450/2-78-037, July 1987).
The Shewhart test is performed on daily data (INT = 7, 24-hour) for pollutants 12128 (Pb), 42401
(SOj), 42602 (NOj), and 81102 (PM-10). Exceptional events data are excluded. The test is run on a
month of daily data. The program counts the number of valid samples for the current month and
each of the three previous months. If there is insufficient data to perform the test, a warning message
is issued. Given sufficient data for at least two of the three previous months, the program computes
the mean and range for the current month. It then computes the historical mean and range, from the
mean and range of the data for the three historical months. The mean and range for the current
month are compared against the historical values to determine whether the current month passes or
fails the Shewhart test.
The following messages appear in the EDIT error report:
WARNING - DAILY VALUES FAIL SHEWHART TEST
Examine the data for the month that failed. If all values are correct, at least one of these
should be marked as either an "exceptional event" or as a "validated value".
WARNING - NOT ENOUGH DAILY HISTORICAL VALUES TO RUN SHEWHART TEST
At least four historical values are needed for the Shewhart test.
Figure 7-4 contains a sample of the EDIT Shewhart Failure Report that provides additional
information. The report lists the values that failed the test so they may be reviewed.
IJecember 1993 7-43 Transaction Type 2
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
03/30/87
ANPOSO
AEROHETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
EDIT SHEKHAST FAILURE REPORT
FOR SCREENING FILE OCSCSF02
PAGE:
..j.—+.—2-
RECORD KEY
rrwt
DAYS
-DAILY VALUES FAILING SHEUHART TEST-
37067002*424011*421111 M
THRU
370670026424011*421114 H
4 RECORDS WARNING - NOT ENOUGH DAILY HISTORICAL VALUES TO RUN SHEUHART TEST
370670028424011853050? M
THRU
3706700284240118520502 H
1 RECORDS WARNING - NOT ENOUGH DAILY HISTORICAL VALUES TO RUN SHEHKART TEST
370670028424011*521215 M
THRU
370670028424011*521231 N
*S12
01-08
09-16
17-24
25-31
9999.
8.989
7479.
1212.
90.90
8080.
232.3
1313.
9191.
34.34
2424.
1234.
5555.
4.545
.30V
234.5
666.6
.5656
.30
34.56
7777. 888.8
.0676 .7878
.30V 6868.
Figure 7-4. Shewhart Failure Report
Transaction Type 2
7-44
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
7.4 Transaction Type 3 - Composite Data
Transaction type 3 is used for composite observations, interval code C. Type 3 transactions insert,
modify, and delete raw data values in the Composite File of the AIRS database.
Figure 7-5 shows the coding form transaction type 3. Each line across the body of the form
corresponds to a transaction.
An INSERT transaction is used to insert a new observation into the database where none already
exists.
A MODIFY transaction is used to change or delete an existing observation in the database.
A DELETE transaction is used to delete an observation and its associated fields from the database.
Missing value reason codes ("null values") are not used on type 3 transactions.
Error Messages:
ERROR - ALL FIELDS BLANK ON MODIFY
All the fields (INT through VF) of a modify transaction are blank. INT, UNITS, METHOD,
and at least one of NO. OF SAMPLES. COMP TYPE, DP, SAMPLE VALUE, or VF must be
specified.
December 1993 7-45 Transaction Type 3
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
£«_
O w £
< Jl-
gjoi >
-if Q >
gz£S
a. ~
O
z
Figure 7-5. Coding Form for Transaction Type 3
Transaction Type 3
7-46
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
7.4.1 PERIOD CODE
PERIOD CODE indicates the time period within YEAR to which an observation applies. It is
expressed in units that may be inferred from COMP TYPE. It is used in a manner similar to the date
and times associated with hourly and daily data.
Attributes: 2 digit code
Required
Coding Instructions:
Enter a valid period code in columns 26-27. Valid period codes depend on COMP TYPE as follows:
COMP TYPE Valid PERIOD CODE
1 (Quarterly) 01-04
2 (Seasonal) 01-04
3 (Monthly) 01-12
4 (Weekly) 01-53
5 (Annually) 01
Error Messages:
ERROR - INVALID PERIOD-CODE
PERIOD CODE must be one of the values listed above.
ERROR - MONITOR INACTIVE FOR THIS DATE
PERIOD CODE (with YEAR) must fall within the year-period bounds of the dates sampling
began and ended at this monitor. The sampling dates used for the comparison may be present
on the Fl transaction being submitted for this monitor or, if not, are stored in the Site File.
(See fields DATE SAMPLING BEGAN and DATE SAMPLING ENDED of the type Fl
transaction in Section 5 of this volume.)
WARNING - CANNOT VERIFY PERIOD-CODE
If COMP TYPE is invalid, this field cannot be checked.
December 1993 7-47 Transaction Type 3
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
7.4.2 NO. OF SAMPLES
This field contains the number of samples that were combined to yield this composite value.
Attributes: 2 digit numeric
Required
Coding Instructions:
To INSERT or MODIFY, place the number of samples composited into columns 28-29.
Error Messages:
ERROR - INVALID CNT-SAMPLES
If COMP TYPE = 1 or 2, this field must be numeric <. 92.
If COMP TYPE = 3, this field must be numeric <_ 31.
If COMP TYPE = 4, this field must be numeric <_ 7.
If COMP TYPE = 5, this field must be numeric <. 99.
WARNING - CANNOT VERIFY CNT-SAMPLES
If COMP-TYPE is invalid, this field cannot be checked.
Transaction Type 3
7-48
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
7.4.3 COMPTYPE
COMP TYPE indicates the time period over which samples are composited, or the frequency of
submitting composite samples.
Attributes: 1 digit code
Required
Coding Instructions:
In column 30, enter a valid COMP TYPE from the following:
1 Quarterly
2 Seasonal
3 Monthly
4 Weekly
5 Annual
Error Messages:
ERROR - COMP-TYPE CANNOT CHANGE WITHIN A CALENDAR YEAR
The Composite Type of a monitor may be changed only at a year boundary.
ERROR - INVALID COMP-TYPE
Valid values are 1 through 5.
E'ecember 1993 7-49 Transaction Type 3
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
7.4.4 DP
DP indicates the number of digits to the right of the decimal point in the SAMPLE VALUE field.
Attributes:
1 digit numeric
Optional
Coding Instructions:
When inserting or modifying SAMPLE VALUE or DP, DP must be entered as numeric 0-5 in
column 31.
When deleting an observation, or when modifying some other field on the transaction, DP may be
blank.
Error Message:
ERROR - INVALID DECIMAL-POSITION
Valid values for DP are 0-5 and blank.
Transaction Type 3
7-50
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
7.4.5 SAMPLE VALUE
SAMPLE VALUE contains the value of a composite observation.
Attributes: 4 digit numeric
Optional
Coding Instructions:
To INSERT or MODIFY an observation, place the observation in columns 32-35. Remember to
allow for the implied decimal point indicated by DP.
To DELETE an observation, submit a DELETE transaction with columns 1-27 filled.
Error Message:
ERROR - INVALID SAMPLE-VALUE
For an insert transaction, this field must be numeric.
For a modify transaction, this field may be blank, asterisks, or numeric.
December 1993 7-51 Transaction Type 3
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
7.4.6 VF (Validity Flag)
VF (Validity Flag) is used :o give the reason for an abnormal observation. The presence of VF with
an observation indicates that the observation is due to an "exceptional event" or it's abnormal value
has been checked and found to be valid. State or EPA regional personnel must approve of the use of
validity flags. Refer to "Guideline on the Identification and Use of Air Quality Data Affected by
Exceptional Events", publication #EPA-450/4-86-007, July, 1986.
Attributes:
1 character code
Optional
Coding Instructions:
If an observation results from an exceptional event (e.g., volcano, forest fire, disaster clean-up, etc.),
place a valid validity flag in column 36. A valid validity flag is one that exists in the AIRS GEO-
COMMON File for this parameter. Valid codes are listed in Volume GC2 of the AIRS User's
Guide. The code "V", which stands for "validated", is also used for VF when there is no specific
cause attributable for an abnormal value.
VF may not be inserted, modified, or deleted by itself. If VF is valued, the corresponding SAMPLE
VALUE must also appear. About the only time this will matter is when you need to attach a validity
flag to an already entered value. In such a case, you must re-enter the value with the validity flag
using a MODIFY transaction.
To DELETE, place an asterisk in column 36 and code the associated SAMPLE VALUE in columns
32-35 (even if the sample is unchanged).
Error Messages:
ERROR - BAD VALIDITY-FLAG FOR PARAMETER
For an insert transaction, the VF can be V, blank, or one of the exceptional event flags in the
GEO-COMMON File for the PARAMETER.
For a modify transaction, the VF can be V, blank, asterisk, or one of the exceptional event
flags in the GEO-COMMON File for the PARAMETER.
ERROR - INVALID VALIDITY-FLAG
If VF is not V, blank, or asterisk on a modify and is not in the GEO-COMMON File, it is an
error.
Transaction Type 3
7-52
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - VALIDITY-FLAG NOT ALLOWED
The VF can only be entered if its corresponding SAMPLE-VALUE is valued.
On a modify transaction, VF cannot be an asterisk if the SAMPLE-VALUE field is blank.
If DP is blank, then VF must be blank.
WARNING - CANNOT VERIFY VALIDITY-FLAG
If PARAMETER is invalid and VF is in the GEO-COMMON File, no further checks can be
made.
December 1993 7-53 Transaction Type 3
-------
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
8.0 Special Transactions (Z and 4)
The two transactions in this group are used to insert, modify, and delete special values in the raw data
files of the AIRS database. The type Z transaction deals with the minimum detectable value of a
parameter. The type 4 transaction deals with missing value reason codes, or "null values". Both
transactions can apply to a date range rather than a single date.
The only way to load a minimum detectable value into the AIRS database is to use a Z transaction.
The value loaded from the transaction overrides the default (national) minimum detectable value for a
particular monitor.
The type 4 transaction is an alternative to the raw data transactions (types 1 and 2) for putting missing
value reason codes into the AIRS database. These are codes that explain why a real observation of a
parameter value was not reported by a monitor for a particular date and time. Transaction type 4
provides convenience of use, since only one transaction is needed to supply a missing value reason
code for all the possible observations within a date range, rather than multiple type 1 or type 2
transactions which would be needed to cover the same date range.
The following error message pertains to transaction types Z and 4:
ERROR - CANNOT ADD DATA FOR MONITOR BEING DELETED
There is an F DELETE transaction for the same monitor-id as the current INSERT.
ERROR - CANNOT MODIFY DATA FOR MONITOR BEING DELETED
There is an F DELETE transaction for the same monitor-id as the current MODIFY.
ERROR - DUPLICATE RECORDS
Two or more transactions have the same monitor-ID, year, time period, transaction type, and
action code.
December 1993 8-1 Special Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - NOT AUTHORIZED FOR THIS MONITOR
Each monitor-ID is associated with a group of screening files (those whose names are the same
except in the last two positions). The association, or "ownership", is established when the
monitor is inserted into the Site File or when an unassociated monitor is changed by Site or
Monitor transactions (types A1-A7 or F1-F5). Once the association is established, all
transactions involving that monitor must be in the screening file of the group that "owns" the
monitor. This error message means that the screening file group does not have ownership of
the monitor-ID on the special transaction. Either the wrong monitor-ID was coded, or a
different screening file must be used for the transaction in question.
Special Transactions
8-2
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
8.1 Common Fields
Transaction types Z and 4 have the following common fields:
PARAMETER
PARAMETER OCCURRENCE CODE (POC)
MONITOR-ID
INT (interval)
UNITS
METHOD
BEGIN YEAR
BEGIN MON (month)
Transaction type Z contains minimum detectable data in the following additional fields:
END YEAR
END MON (month)
DP
MIN DET VALUE
Transaction type 4 contains null data in the following additional fields:
BEGIN DAY
END YEAR
END MON (month)
END DAY
REASON CODE
December 1993
8-3
Special Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
8.1.1 PARAMETER
PARAMETER is a code assigned to a specific parameter being measured and/or analyzed. It may be
a pollutant, such as ozone, or a non-pollutant, such as wind direction.
Attributes: 5 digit code
Required
Coding Instructions:
Place a valid parameter code in columns 11-15. A code is valid if it exists in the AIRS GEO-
COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
Error Message:
ERROR - INVALID PARAMETER CODE
PARAMETER must be in the GEO-COMMON File.
Special Transactions 8-4 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
8.1.2 PARAMETER OCCURRENCE CODE
PARAMETER OCCURRENCE CODE (POC) is a code used to distinguish between different
monitors at the same site that are measuring the same parameter. For example, the first monitor
established to monitor CO at a site would have POC = 1. If an additional monitor were established
at the same site to measure CO, that monitor would have POC - 2, However, if a new instrument
were installed to replace the original instrument used as the first monitor, that would be the same
monitor and it would have POC = 1, even if there were a change in sampling method or interval.
Interval can change only at the end of the year.
Attributes:
1 digit code
Required
Coding Instructions:
In column 16, enter a valid POC in the range 1 through 9.
Error Message:
ERROR - INVALID POC CODE
POC is a required field. It must be numeric in the range 1-9.
December 1993
8-5
Special Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
8.1.3 Monitor Identification Code (Monitor-ID)
The Monitor-ID identifies the monitor to which a transaction applies. It is comprised of the STATE,
COUNTY, SITE, PARAMETER, and PARAMETER OCCURRENCE CODE (POC) fields.
Attributes: 15 digit code
Required
Coding Instructions:
Place a valid monitor-ID in columns 2-16. A monitor-ID is valid if it is in the AQ Site File. You
can obtain a list of monitor-IDs with several standard reports of the Air Quality Retrieval Subsystem,
described in Volume AQ4 of the User's Guide. When coding a monitor-ID ensure that columns 2-3
contain a valid STATE, 4-6 a valid COUNTY, 7-10 a valid SITE, 11-15 a valid PARAMETER, and
16 a valid POC.
Error Messages:
ERROR - INVALID MONITOR-ID
The monitor-ID is not in the Site File. This message occurs only if all the constituent parts of
monitor-ID are valid.
Special Transactions 8-6 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
8.1.4 INT
INT indicates the sampling interval used for monitoring activities.
Attributes:
1 character code
Required
Coding Instructions:
Place a valid interval code in column 17. A code is valid if it exists in combination with
PARAMETER in the AIRS GEO-COMMON File, except that interval code C, composite, is not
allowed for transaction type 4. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
Error Message:
ERROR - INVALID INTERVAL
INT must be in the GEO-COMMON File. Interval C is not valid.
December 1993
8-7
Special Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
8.1.5 UNITS
UNITS indicates the dimensional system and in which a parameter measurement is expressed.
Attributes: 3 digit code
Required
Coding Instructions:
Place a valid units code in columns 18-20. A code is valid if it exists in combination with
PARAMETER, INTERVAL, and METHOD in the AIRS GEO-COMMON File. Valid codes are
listed in Volume GC2 of the AIRS User's Guide.
Error Messages:
ERROR - INVALID POLL-INT-METH-UNITS
If PARAMETER, INTERVAL, and METHOD are valid, then the combination of these three
and UNITS must exist in the GEO-COMMON File.
ERROR - INVALID UNITS
The UNITS code must be in the GEO-COMMON File.
WARNING - CANNOT VERIFY UNITS
If PARAMETER or INTERVAL or METHOD is invalid and UNITS is in the GEO-COMMON
File, then UNITS cannot be verified further.
Special Transactions 8-8 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
8.1.6 METHOD
METHOD is the method used to collect and analyze parameter values.
Attributes: 3 digit code
Required
Coding Instructions:
Place a valid method code in columns 2!-23. A code is valid if it exists in combination with
parameter, interval, and units in the AIRS GEO-COMMON File. Valid codes are listed in Volume
GC2 of the AIRS User's Guide.
Error Messages:
ERROR - INVALID METHOD
METHOD must be numeric.
ERROR - INVALID POLL-INT-METH-UN1TS
If PARAMETER, INTERVAL, and UNITS are valid, then the combination of these with
METHOD must exist in the GEO-COMMON File.
ERROR - INVALID METHOD FOR STATE
If PARAMETER, METHOD, INTERVAL, and UNITS exist in the GEO-COMMON File, then
the METH-VAL-FLAG must be checked. If METH-VAL-FLAG = N, then METHOD is
invalid, except for states listed in the STATE fields of the GEO-COMMON record.
WARNING - CANNOT VERIFY METHOD
If PARAMETER or INTERVAL or UNITS is invalid and METHOD is numeric, it cannot be
verified further.
December 1993
8-9
Special Transactions
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
8.2 Transaction Type Z - Minimum Detectable Value
A type Z transaction is used to specify a special minimum detectable value for a given monitor for a
given time period, which may be as short as one month or as long as several years. This special
minimum detectable overrides the default minimum detectable defined in the GEO-COMMON File
for the parameter.
Figure 8-1 shows the coding form for transaction type Z.
An INSERT transaction is used to specify the minimum detectable where none is currently specified
(other than the default in GEO-COMMON). There must be at least one observation present in the
database for the date range of the Z transaction.
A MODIFY transaction is used to change the special minimum detectable for a monitor for a
specified time period. There must be at least one observation present in the database for the date
range of the Z transaction.
A DELETE transaction is used to remove the special minimum detectable for a monitor for a given
time period. The minimum detectable for that period then reverts to the default value in GEO-
COMMON.
Error Messages:
ERROR - ALL FIELDS BLANK ON MODIFY
DP or MIN DET VALUE must be specified for a type Z transaction.
ERROR - ATTEMPT TO ADD DATA THAT EXISTS IN THE DATABASE
A minimum detectable value already exists for this time period. Do not use an INSERT
transaction.
ERROR - ATTEMPT TO CHANGE DATA THAT DOES NOT EXIST
There must be at least one observation with a special minimum detectable value already in the
database within the period specified.
ERROR - ATTEMPT TO DELETE DATA THAT DOES NOT EXIST
There must be at least one observation with a special minimum detectable value already in the
database within the period specified.
ERPOR - DATA FOR THIS YEAR IS ARCHIVED
No part of the specified time period may be archived. Contact the AIRS database administrator
to have the data in question de-archived.
Transaction Type Z 8-10 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
WARNING - METHOD DOES NOT MATCH METHOD ON DATABASE
The method code of a MODIFY or DELETE transaction is different from the METHOD of the
data in the database to which the transaction applies.
December 1993
8-11
Transaction Type Z
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
l<
2 *
f
5 i
f =
I a|
H;
s!s
~> s
J I -
O O
IS *
SEJ^
° s
I *
I ! I
i >
_u
i I I
I !
z£
lw<
I I
I i i ! ! I I
i 1 I
I M I
! ! I
Mill
I 1 ! ! I i i I i ! ! i
-I I i
St -
gz -
*
o
5 E u
a. v> o
u •— o.
O 2 O
CL ~
CO
UJ
O
Z
Figure 8-1. Coding Form for Transaction Type Z
Transaction Type 7.
8-12
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
8.2.1 BEGIN YEAR/BEGIN MON
BEGIN YEAR and BEGIN MON define the beginning year and month for which the minimum
detectable value is in effect.
Attributes:
4 digit date
Required
Coding Instructions:
Place a valid year/month combination in YYMM format in columns 26-27. A valid year/month is
within the range January 1957 through the current month. The year/month must also be within the
dates when sampling began and ended at the monitor.
Error Messages:
ERROR - BEGIN-DATE > CURRENT DATE
BEGIN DATE must be £ the current date.
ERROR - INVALID BEGIN-DATE
BEGIN DATE must be a valid date in YYMM format.
ERROR - INVALID BEGIN-MONTH
BEGIN MON must be in the range 01-12.
ERROR - INVALID BEGIN-YEAR
BEGIN YEAR must be £ 57 and < the current year.
ERROR - MONITOR INACTIVE FOR THIS DATE
BEGIN DATE must be within the time span when sampling began and ended at this monitor.
The sampling dates used for the comparison may be present on the F transaction being
submitted for this monitor or, if not, are stored in the Site File.
December 1993
8-13
Transaction Type Z
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
8.2.2 END YEAR/END MON
END YEAR and END MON define the ending year and month for which the minimum detectable
value is in effect.
Attributes: 4 digit date
Required
Coding Instructions:
To INSERT or MODIFY, place a valid year/month combination in YYMM format in columns 28-31.
A valid year/month is within the range January 1957 through the current month. The year/month
must also be within the dates when sampling began and ended at the monitor.
Error Messages:
ERROR - END-DATE < BEGIN-DATE
END DATE must be £ BEGIN DATE.
ERROR - END-DATE > CURRENT DATE
END DATE must be £ the current year and month.
ERROR - INVALID END-DATE
END DATE must be a valid year/month.
ERROR - INVALID END-MONTH
END MON must be in the range 01-12.
ERROR - INVALID END-YEAR
END YEAR must be a 57 and £ the current year.
ERROR - MONITOR INACTIVE FOR THIS DATE
END DATE must be within the time span when sampling began and ended at this monitor.
The sampling dates used for the comparison may be present on the F transaction being
submitted for this monitor or, if not, are stored in the Site File.
Transaction Type Z 8-14 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
o
8.2.3 DP
DP indicates the number of digits to the right of the decimal point in MIN DET VALUE.
Attributes:
1 digit numeric
Required
Coding Instructions:
To INSERT or MODIFY, place a decimal indicator of 0-5 in column 32.
DP may be blank on a DELETE transaction when deleting the minimum detectable for a particular
date range.
Error Message:
ERROR - INVALID DECIMAL-POSITION
DP must contain a value in the range 1 through 5 on INSERT or MODIFY transactions.
December 1993
8-15
Transaction Type Z
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
8.2.4 MINDET VALUE
MIN DET VALUE defines the minimum value, i.e., the lowest concentration that can be detected by
a sampling instrument.
Attributes: 4 digit numeric
Required
Coding Instructions:
To INSERT or MODIFY, place the minimum detectable in columns 33-36. Remember to allow for
the implied decimal point indicated by DP. If the minimum detectable is negative, place the minus
sign in column 33, right justify the value in columns 34-36, then fill any blanks in those columns with
zeros.
\
To DELETE, submit a DELETE transaction with columns 1-31 filled. The content of the DP and
MIN DET VALUE fields does not matter; they are ignored.
Error Message:
ERROR - INVALID MIN-DETECTABLE-VALUE
MIN DET VALUE must be numeric and in the form -nnn or nnnn, as described above.
Negative values are allowed only for certain PARAMETERS.
Transaction Type Z 8-16 December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
8.3 Transaction Type 4 - Missing Data Reason (Null Data)
A type 4 transaction is used to deal with missing value reason codes ("null values") over a given time
period, which may be as short as one day or as long as several years. The use of missing value
codes is not encouraged for data missing for a year or more. Missing value reason codes may be
entered for hourly and daily data. They may not be used for composite data.
Figure 8-2 shows the coding form for missing value reason codes.
An INSERT transaction is used to insert the given missing value reason code into each possible
observation slot for the specified monitor, interval, units, method, and time period where no
observation or missing value reason code exists. A MODIFY transaction is used to change existing
missing value reason codes for a given time period to the indicated code. There may be actual
observations as well in the time period; they are not affected. A DELETE transaction is used to
remove all missing value reason codes for the indicated time period. Any actual observations in the
time period are not affected.
Error Messages:
ERROR - ALL FIELDS BLANK ON MODIFY
The REASON CODE may not be blank on a MODIFY transaction. It must contain a code that
is in the GEO-COMMON File.
ERROR - ATTEMPT TO ADD DATA THAT EXISTS IN THE DATABASE
There must be at feast one missing observation in the specified time period for the
monitor/interval/units/method.
ERROR - ATTEMPT TO CHANGE DATA THAT DOES NOT EXIST
There must be at least one existing missing value reason code in the specified time period.
ERROR - ATTEMPT TO DELETE DATA THAT DOES NOT EXIST
There must be at least one existing missing value reason code in the specified time period.
ERROR - DATA FOR THIS YEAR IS ARCHIVED
Some portion of the data in the indicated time period has been archived. Contact the AIRS
database administrator to have the data in question de-archived.
December 1993 8-17 Transaction Type 4
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
si:
85s
111 *" 1
s s
1|-
^ «J P-
ii^
SE^'S
si2£
ilii
'r«J
S s
s .
I I I I
I I I
I I
li
!
II
« O
EU
O 5
o.
to
UJ
^
O
Figure 8-2. Coding Form for Transaction Type 4
Transaction Type 4
8-18
December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
8.3.1 BEGIN DATE
BEGIN YEAR, BEGIN MON, and BEGIN DAY specify the beginning date for the application of this
transaction.
Attributes:
6 digit code
Required
Coding Instructions:
Place a valid date in YYMMDD format in columns 24-29. To be valid, the date must be within the
range January 1, 1957, through the current date, and within the dates that sampling began and ended
at the monitor.
Error Messages:
ERROR - BEGIN-DATE > CURRENT DATE
BEGIN-DATE must be «£ current date.
ERROR - INVALID BEGIN-DATE
BEGIN-DATE must be a valid Gregorian date as described above.
ERROR - INVALID BEG1N-DAY
BEGIN DAY must be numeric > 0 and appropriate for the month.
ERROR - INVALID BEGIN-MONTH
BEGIN MON must be numeric, 00-12.
ERROR - INVALID BEGIN-YEAR
BEGIN YEAR must be £ 57 and S current year.
ERROR - MONITOR INACTIVE FOR BEGIN-DATE
BEGIN-DATE must be within the time span when sampling began and ended at the monitor,
which are stored in the Site File.
December 1993
8*19
Transaction Type 4
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR - MONITOR INACTIVE FOR THIS DATE
BEGIN-DATE must be within the time span when sampling began and ended at the monitor.
The sampling dates used for the comparison may be present on the F transaction being
submitted for this monitor or, if not, are stored in the Site File.
Transaction Type 4 8-20 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
8.3.2 END DATE
END YEAR, END MON, and END DAY specify the last day to which this transaction applies.
Attributes:
6 digit date
Required
Coding Instructions:
Place a valid date in YYMMDD format in columns 30-35. To be valid, the date must be in the range
January 1, 1957, through the current date, and within the dates that sampling began and ended at the
monitor.
Error Messages:
ERROR - END-DATE < BEGIN-DATE
END-DATE must be £ BEGIN-DATE.
ERROR - END-DATE > CURRENT DATE
END-DATE must be & current date.
ERROR - INVALID END-DATE
END-DATE must be a valid Gregorian date as described above.
ERROR - INVALID END-DAY
END DAY must be numeric > 0 and appropriate for the month.
ERROR - INVALID END-MONTH
END MON must be numeric, 00-12.
ERROR - INVALID END-YEAR
END YEAR must be ^ 57 and < current year.
ERROR - MONITOR INACTIVE FOR END-DATE
END DATE must be within the time span when sampling began and ended at the monitor,
which are stored in the Site File.
December 1993
8-21
Transaction Type 4
-------
AIRS User's Guide
Air Quality Data Coding Volume AQ2
ERROR - MONITOR INACTIVE FOR THIS DATE
BEGIN-DATE must be within the time span when sampling began and ended at the monitor.
The sampling dates used for the comparison may be present on the F transaction being
submitted for mis monitor or, if not, are stored in the Site File.
Transaction Type 4 8-22 December 1993
-------
AIRS User's Guide
Volume AQ2
Air Quality Data Coding
8.3.3 REASON CODE
REASON CODE is the missing value reason code that will be applied to the indicated date range.
The code gives the reason why an actual observation is not available, such as a natural disaster or an
equipment malfunction.
Attributes:
4 digit code
Required
Coding Instructions:
To INSERT or MODIFY, place a valid missing value reason code in columns 36-39. To be valid,
the code must exist in the AIRS GEO-COMMON File. The valid codes are listed in Volume GC2 of
the AIRS User's Guide.
To DELETE, submit a DELETE transaction with columns 1-36 filled. The content of REASON
CODE does not matter; it is ignored.
For INSERTs, there may be no actual observations (DP non-blank) in the raw data for the date range
indicated on the type 4 transaction.
For MODIFYs, the missing reason code will be applied to all "missing" observations (those for which
DP is blank) in the indicated range, regardless of the presence of missing value reason codes.
For DELETE, all missing reason codes within the indicated date range will be removed.
Error Message:
ERROR - INVALID REASON-CODE
The REASON CODE may not be blank. It must contain a code that is in the GEO-COMMON
File.
December 1993
8-23
Transaction Type 4
-------
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.0 Precision/Accuracy Transactions (8 and 9)
The two transactions in this group are used to insert, modify, and delete the individual observations of
parameter values in the AIRS database. The parameter values are the known and observed concentrations
of air pollutants measured with the various methods and at various time intervals. These observations
of parameter values are collectively called "raw precision/accuracy data" because they are the actual,
unprocessed values reported by the monitoring sites. This is contrasted with the summaries of the
observations derived by AIRS software and stored in the Air Quality monitor and reporting organization
summary files. The precision and accuracy raw data is stored in a single file in the AIRS database, the
Monitor Data File. This file contains the reported observations of parameters tested at various sampling
intervals. Each record holds a month of observations for a monitor.
In the precision/accuracy raw data file, there are three sets of fields for each possible observation: actual
value, which is the known concentration of a parameter, stored as an integer; indicated value, which is
the observed concentration of a parameter as measured by the monitor, stored as an integer; and decimal
position indicator, which gives the position of the implied decimal point in the actual and indicated fields.
The contents of these three fields determine how an "observation" is interpreted. If decimal position is
blank, there is no observation; a parameter value is not reported. A numeric value for decimal position
signals the presence of a "real" observation, which gives the known and observed value of a parameter.
The decimal position field scales the actual and indicated value field by indicating how many digits of
the value (stored as an integer) are to the right of the decimal point. In other words, the measured value
is (value/field)/! 10 ** (decimal position field)}, where "**" means exponentiation, or "raised to the
power of. This same scheme is used for both the precision/accuracy raw data file and the
precision/accuracy raw data transactions. In fact, the values in the files are simply copied from the
transactions.
Action codes are interpreted the same way for both types of precision/accuracy raw data transactions.
INSERT actions are used to enter precision/accuracy raw data values where none previously existed. The
monitor reporting the precision/accuracy raw data values must already exist in the AIRS Site File.
DELETE actions are used to remove one or more existing precision/accuracy raw data values from the
AIRS database. MODIFY actions are used to change existing precision/accuracy raw data values or to
delete them.
December 1993 9-1 Precision/Accuracy Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
The two types of precision/accuracy raw data transactions have several fields in common. They are:
MONITOR-ID, consisting of
STATE
COUNTY
SITE
PARAMETER
PARAMETER OCCURRENCE CODE (POC)
INT (interval)
UNITS
METHOD
YEAR
MONTH
DAY
Transaction type 8 contains precision data in the following fields:
DP (decimal position)
ACTUAL DESIGNATED
INDICATED COLLOCATED MON1
INDICATED COLLOCATED MON2
INDICATED COLLOCATED MON3
INDICATED COLLOCATED MON4
INDICATED COLLOCATED MON5
Transaction type 9 contains accuracy data in the following fields:
TYPE AUDIT
LOCAL PRIMARY STANDARD
AUDIT CLASSIFICATION
DP (decimal position)
ACTUAL LEVEL-1
INDICATED LEVEL-1
ACTUAL LEVEL-2
INDICATED LEVEL-2
ACTUAL LEVEL-3
INDICATED LEVEL-3
ACTUAL LEVEL-4
INDICATED LEVEL-4
ACTUAL LEVEL-5
INDICATED LEVEL-5
ZERO SPAN
Detailed coding instructions and explanations of error messages for the common fields and for the two
precision/accuracy transactions are given below.
Precision/Accuracy Transactions
9-2
December 1993
-------
AIRS User's Guide A. n ,. ^
Volume AQ2 Air Qual'ty Data Coding
The EDIT error messages listed below pertain to a precision/accuracy raw data transaction as a whole,
rather than to a specific field. These messages pertain to both types of precision/accuracy transactions.
December 1993 9-3 Precision/Accuracy Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
Error Messages:
ERROR - ATTEMPT TO ADD DATA PRIOR TO OLDEST MONITOR DATE
There is no monitor of any type that was active for the monitor-ID and date specified on an
INSERT or MODIFY transaction. For both transaction types, check the monitor-ID and date.
ERROR - ATTEMPT TO ADD DATA PRIOR TO OLDEST RO-EFFECTIVE-DATE
There is no reporting organization that was active for the monitor-ID and date specified on an
INSERT or MODIFY transaction. For both transaction types, check the monitor-ID and date.
ERROR - ATTEMPT TO ADD DATA THAT EXISTS IN THE DATABASE
A value already exists in the precision/accuracy raw data file for the monitor-ID and date
specified on an INSERT transaction. For both transaction types, verify that the value is in the
correct sample value slot. For both transaction types, verify that the date and monitor-ID are
correct. The value in the database will also be displayed on the error report.
ERROR - ATTEMPT TO CHANGE DATA THAT DOES NOT EXIST
There is no value in the precision/accuracy raw data file for the monitor-ID and date specified
on a MODIFY transaction. For both transaction types, verify that the proper sample value slot
is used. For both transaction types, check the monitor-ID and date.
ERROR - ATTEMPT TO DELETE DATA THAT DOES NOT EXIST
There is no value in the precision/accuracy raw data file for the monitor-ID and date specified
on a DELETE transaction. For both transaction types, verify that the proper sample value slot
is used. For both transaction types, check the monitor-ID and date.
ERROR - CANNOT ADD DATA FOR MONITOR BEING DELETED
There is an F DELETE transaction for the same monitor-ID as the current INSERT.
ERROR - CANNOT MODIFY DATA FOR MONITOR BEING DELETED
There is an F DELETE transaction for the same monitor-ID as the current MODIFY.
Precision/Accuracy Transactions
9-4
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - NOT AUTHORIZED FOR THIS MONITOR
Each monitor-ID is associated with a group of screening files (those whose names are the same
except in the last two positions). The association, or "ownership", is established when the
monitor is inserted into the Site File or when an unassociated monitor is changed by Site or
Monitor transactions (types A1-A7 or F1-F5). Once the association is established, all transactions
involving that monitor must be in the screening file of the group that "owns" the monitor. This
error message means that the screening file group does not have ownership of the monitor-ID on
the precision/accuracy raw data transaction. Either the wrong monitor-ID was coded, or a
different screening file must be used for the transaction in question.
ERROR - RO-EFFECTTVE-DATE NOT VALUED FOR THIS MONITOR
The reporting organization effective date on the monitor record was blank, or the old history date
on the history record was blank.
WARNING - ALL PA DATA MUST BE SUBMITTED FOR DATA BEFORE 1987
Precision or accuracy data submitted for years prior to 1987 wilt cause recalculation of the
precision/accuracy monitor summary and reporting organization summary. If all raw data does
not exist or is not submitted, the recalculation could result in the loss of summary information.
December 1993 9-5 Precision/Accuracy Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
s
9
^•^H
?
•MMM
- i
5j = '
i3 i
ijlj"
»|5-t
tii i
I i
\l\ I
if
a _
«
* i
•HWHW
i
8
•••••
I
it
IE
~t
H
•M
J
-
—
—
-
-
W~
»"
n
-
—
»"•
•••
i
r
t
,
§ •
.
I S»
r §S»
' n
a :
. |i
* ii
. *
a g
* if
. "
Is S
•SI
~\\
t ;
. *8
• «1
•
• M
- *i
,i»J
- »
5
A
_
t
i
I
i
*
3
i
SJ i
ih
;
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.1 Common Fields
9.1.1 PARAMETER
PARAMETER is a code assigned to a specific parameter being measured and/or analyzed. It must be
a pollutant, such as ozone.
Attributes: 5 digit code
Required
Coding Instructions:
Place a valid PARAMETER code in columns 11-15. A code is valid if it exists in the AIRS GEO-
COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
Error Message:
ERROR - INVALID PARAMETER CODE
PARAMETER must be in the AIRS GEO-COMMON File.
December 1993 9-7 Precision/Accuracy Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.1.2 PARAMETER OCCURRENCE CODE
PARAMETER OCCURRENCE CODE (POC) is a code used to distinguish between different monitors
at the same site that are measuring the same parameter. For example, the first monitor established to
monitor CO at a site would have POC =1. If an additional monitor were established at the same site
to measure CO, that monitor would have POC = 2. However, if a new instrument were installed to
replace the original instrument used as the first monitor, that would be the same monitor and it would
have POC = 1, even if there were a change in sampling method or interval. (Interval can change only
at the end of a year.)
Attributes:
1 digit code
Required
Coding Instructions:
In column 16, enter a valid POC in the range 1 through 9.
Error Message:
ERROR - INVALID POC CODE
POC is a required field. It must be numeric in the range 1-9.
Precision/Accuracy Transactions
9-8
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.1.3 Monitor Identification Code (Monitor-ID)
The Monitor-ID identifies the monitor to which a transaction applies. It is comprised of the STATE,
COUNTY, SITE, PARAMETER, and PARAMETER OCCURRENCE CODE (POC) fields.
Attributes: 15 digit code
Required
Coding Instructions:
Place a valid monitor-ID in columns 2-16. A monitor-ID is valid if it is in the AQ Site File. You can
obtain a list of monitor-IDs with several standard reports of the Air Quality Retrieval Subsystem,
described in Volume AQ4 of this User's Guide. When coding a monitor-ID ensure that columns 2-3
contain a valid STATE, 4-6 a valid COUNTY, 7-10 a valid SITE, 11-15 a valid PARAMETER, and 16
a valid POC.
Note that you cannot change the monitor-ID of raw data in the database using a MODIFY transaction.
To change monitor-ID you must delete the data from the database and then insert it with the new monitor-
ID code.
Error Message:
ERROR - INVALID MONITOR-ID
The monitor-ID is not in the Site File. This message occurs only if all the constituent pans of
monitor-ID are valid.
December 1993 9-9 Precision/Accuracy Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.1.4 INT
INT indicates the sampling interval used for monitoring activities.
Attributes:
Coding Instructions:
1 character code
Required
Enter a valid interval code in column 17. To be valid, an interval code must exist in the AIRS GEO-
COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
Note that you cannot change the INT of raw data in the database using a MODIFY transaction. To
change INT, you must delete the data from the database and then insert it with the new INT code.
Error Messages:
ERROR - INTERVAL CANNOT CHANGE WITHIN A CALENDAR YEAR
Data in the raw data file for this monitor and year has a different interval than the transaction.
An interval change for a monitor can only occur at a year boundary. If sampling interval
changes within a year, a new monitor (with a different parameter occurrence code) must be
created.
ERROR - INVALID INTERVAL
INT is not in the AIRS GEO-COMMON File or it is not valid for the transaction type.
Precision/Accuracy Transactions
9-10
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.1.5 UNITS
UNITS indicates the dimensional system in which a parameter measurement is expressed.
Attributes: 3 digit code
Required
Coding Instructions:
Place a valid units code in columns 18-20. A code is valid if it exists in combination with parameter,
interval, and method in the AIRS GEOCOMMON File. Valid codes are listed in Volume GC2 of the
AIRS User's Guide.
Note that you cannot change the UNITS of raw data in the database using a MODIFY transaction. To
change UNITS, you must delete the data from the database and then insert it with the new UNITS code.
Error Messages:
ERROR - INVALID POLL-INT-METH-UNITS
If PARAMETER, INTERVAL, and METHOD are valid, then the combination of these three and
UNITS code must exist in the AIRS GEO-COMMON File.
ERROR - INVALID UNITS
The UNITS code must be in the AIRS GEO-COMMON File.
ERROR - UNITS CANNOT CHANGE WITHIN A CALENDAR MONTH
The UNITS code of an INSERT transaction is different from the UNITS of data already in the
database for the same month. Units code changes can occur only at month boundaries.
ERROR - UNITS MUST MATCH UNITS ON DATABASE
The UNITS code of a MODIFY transaction is different from the UNITS of the data in the
database to which the transaction applies.
/
WARNING - CANNOT VERIFY UNITS
If PARAMETER or INTERVAL or METHOD is invalid and UNITS is in the AIRS GEO-
COMMON File, then UNITS cannot be verified further.
December 1993 9-11 Precision/Accuracy Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.1.6 METHOD
METHOD indicates the method used to sample and analyze parameter values.
Attributes:
Coding Instructions:
3 digit code
Required
Place a valid method code in columns 21-23. A method code is valid if it exists in combination with
parameter, interval, and units in the AIRS GEO-COMMON File. Valid codes are listed in Volume GC2
of the AIRS User's Guide.
Note that you cannot change the METHOD of raw data in the database using a MODIFY transaction.
To change METHOD, you must delete the data from the database and then insert it with the new
METHOD code.
Error Messages:
ERROR - INVALID METHOD
METHOD must be numeric.
ERROR - INVALID METHOD FOR STATE
If PARAMETER, METHOD, INTERVAL, and UNITS exist in the AIRS GEO-COMMON File,
then the METH-VAL-FLAG must be checked. If METH-VAL-FLAG = N, then METHOD is
invalid, except for states listed in the STATE fields of the AIRS GEO-COMMON record.
ERROR - INVALID POLL-INT-METH-UNITS
If PARAMETER, INTERVAL, and UNITS are valid, then the combination of these with
METHOD must exist in the AIRS GEO-COMMON File.
WARNING - CANNOT VERIFY METHOD
If PARAMETER or INTERVAL or UNITS is invalid and METHOD is numeric, it cannot be
verified further.
WARNING - METHOD DOES NOT MATCH METHOD ON DATABASE
The METHOD code of a MODIFY or DELETE transaction is different from the METHOD of
the data in the database to which the transaction applies.
Precision/Accuracy Transactions
9-12
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.1.7 YEAR
YEAR contains the last two digits of the year for which raw data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 24-25, enter a valid year between 1980 and the current year.
Note that you cannot change the YEAR of raw data in the database using a MODIFY transaction. To
change YEAR you must delete the data from the database and then insert it with the new YEAR value.
Error Messages:
ERROR - INVALID YEAR
Year is not in the range 80 through current year.
ERROR - MONITOR INACTIVE FOR THIS DATE
The combination of YEAR with MONTH and DAY specifies a date before this monitor began
sampling or after sampling ended. The dates when sampling began and ended are stored in the
Site File. (See fields DATE SAMPLING BEGAN and DATE SAMPLING ENDED of the Fl
transaction in Section 5 of this volume.)
December 1993 9-13 Precision/Accuracy Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.1.8 MONTH
MONTH identifies the month for which data is being reported.
Attributes:
2 digit date
Required
Coding Instructions:
In columns 26-27, enter a valid month designation (01-12). Use a leading zero as needed.
Error Messages:
ERROR - INVALID MONTH
Valid values are 01 through 12. The combination of YEAR, MONTH, and DAY must be a valid
Gregorian date within the range January 1, 1980, through the current date.
ERROR - MONITOR INACTIVE FOR THIS DATE
The combination of YEAR, MONTH, and DAY must fall within the bounds of the dates
sampling began and ended at this monitor. The sampling dates used for the comparison may be
present on the F transaction being submitted for this monitor or, if not, are stored in the Site
File. (See fields DATE SAMPLING BEGAN and DATE SAMPLING ENDED of the type Fl
transaction in Section 5 of this volume.)
Precision/Accuracy Transactions
9-14
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.1.9 DAY
DAY is the day of the month for which data is being reported.
Attributes: 2 digit date
Required
Coding Instructions:
In columns 28-29, enter a valid day designation (01-31, depending on MONTH). Use a leading zero as
needed.
Error Messages:
ERROR - INVALID DAY
DAY must be valid for the given MONTH. The combination of YEAR, MONTH, and DAY
must be a valid Gregorian date within the range January 1, 1980, through the current date.
ERROR - MONITOR INACTIVE FOR THIS DATE
The combination of YEAR, MONTH, and DAY must fall within the bounds of the dates
sampling began and ended at this monitor. The sampling dates used for the comparison may be
present on the F transaction being submitted for this monitor or, if not, are stored in the Site
File. (See fields DATE SAMPLING BEGAN and DATE SAMPLING ENDED of the type Fl
transaction in Section 5 of this volume.)
December 1993 9-15 Precision/Accuracy Transactions
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.2 Transaction Type 8 - Precision Data
The type 8 transaction is used for parameter observations at various intervals to insert, modify, or delete
precision raw data values in the Monitor Raw Data File of the AIRS database.
The coding form for the type 8 transaction is shown in Figure 9-1. Each line across the body of the form
represents one transaction, which holds a single actual concentration and at least one indicated
concentration value.
All the values entered on a type 8 transaction apply to the same day. For intermittent monitors,
ACTUAL DESIGNATED is the observation from the designated monitor of the collocated samplers.
For continuous monitors, ACTUAL DESIGNATED is the known concentration of gas mixture used to
challenge the monitor. For intermittent monitors, INDICATED COLLOCATED MON1 is the
observation from the collocated monitor of the collocated pair. For continuous monitors, INDICATED
COLLOCATED MON1 is the observed concentration of gas indicated when the monitor was challenged
with a known concentration of gas mixture. For PM10 sampling sites with more than one collocated
monitor, record the observed concentrations in the first through fifth indicated slots.
An INSERT transaction is used to insert an observation into the database where it does not currently
exist. An indicated value slot on the transaction is ignored if it is blank, and has no effect on the
database.
A MODIFY transaction is used to change or delete existing observations. An indicated value slot on the
transaction is ignored if it is blank, and has no effect on the database. A MODIFY transaction may not
be used to insert a value where none currently exists; an INSERT transaction must be used for that
purpose. Furthermore, a MODIFY transaction may not be used to change the interval, method, units,
or date of an observation. The existing data must be deleted and inserted with the desired new value to
change any of those fields. To delete individual indicated values for PM10 sampling sites with more than
one collocated monitor, use all asterisks in the individual fields. If all indicated values are being deleted,
the actual value must also be deleted. In this case, it is better to use a DELETE transaction.
A DELETE transaction is used to remove all the existing observations within the temporal scope of the
transaction. The decimal position and the actual and indicated slots are not used and are ignored. An
observation does not have to exist for every indicated slot within the scope of the transaction; those that
do exist are deleted.
Error Message:
ERROR - ALL FIELDS BLANK ON MODIFY
All the fields (INT through INDICATED COLLOCATED MON5) of a MODIFY transaction are
blank.
Transaction Type 8
9-16
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - DUPLICATE RECORDS
There are two or more transactions with the same action code that have an
ACTUAL/INDICATED pair for the same monitor and date.
December 1993 9-17 Transaction Type 8
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.2.1 DP
DP indicates the number of digits to the right of the decimal point in the ACTUAL and INDICATED
fields.
Attributes:
Coding Instructions:
I digit code
Conditionally required
Enter a valid DP value in column 30. Valid values are blank and the digits 0-5. The same DP value
applies to all ACTUAL and INDICATED fields on the transaction.
With INSERT and MODIFY transactions, DP must be numeric. A numeric value for DP implies that
true observations are coded in the ACTUAL and INDICATED fields.
Although you can place an asterisk in this field on a DELETE transaction, doing so is meaningless. A
DELETE transaction says to delete all values in the time range covered by the transaction.
Error Messages:
ERROR - INVALID DECIMAL-POSITION
Valid values are 0 through 5 and blank.
Transaction Type 8
9-18
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.2.2 ACTUAL DESIGNATED
ACTUAL DESIGNATED is the observation being reported.
Attributes: 4 digit numeric
Required
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in ACTUAL DESIGNATED a true
observation of a parameter value.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing ACTUAL DESIGNATED, code a true
observation, as described above for the INSERT action. You may also fill the ACTUAL DESIGNATED
field with asterisks to delete an existing value, but it is easier (and better) to use a DELETE transaction.
You must enter a numeric value or asterisks in the ACTUAL DESIGNATED field.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the ACTUAL
DESIGNATED field; they are ignored. A DELETE transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the ACTUAL
DESIGNATED field (columns 31-34). Leading zeros are optional. Remember to allow for the implied
decimal point indicated by the DP field. If a filter for an intermittent monitor is lost or damaged, enter
all zeroes for the observation. The DP field must have a numeric value.
For some PARAMETERS, upper limits have been established for observations, and the numeric value
you enter cannot exceed that maximum. The relevant maximum values and PARAMETERS are listed
below:
Maximum Value PARAMETER
2000 ug/m3 11101 (total suspended paniculate)
80ug/m} 12128 (lead)
20 ppm 42101 (carbon monoxide)
.2 ppm 42401 (sulfur dioxide)
.2 ppm 42602 (nitrogen dioxide)
.2 ppm 44201 (ozone)
2000 ug/m3 81102 (paniculate matter)
December 1993 9-19 Transaction Type 8
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
For some PARAMETERS, percent differences are utilized to reject data that could be in error as a result
of transcription errors. The maximum percent differences and PARAMETERS are listed below:
Maximum Percent
Difference
± 160%
±16096
± 90%
± 90%
± 90%
± 90%
± 160%
11101
12128
42101
42401
42602
44201
81102
PARAMETER
For 'lliOl', M2128', and '81102', the percent difference is calculated using the following formula:
2 (indicated-actual)
(indicated* actual)
x 100
For '42101', '42401', '42602', and '44201', the percent difference is calculated using the following
formula:
(indicated- actual)
actual
x 100
Error Messages:
ERROR - ACTUAL-DESIG MUST BE NUMERIC
For an INSERT transaction, ACTUAL DESIGNATED must be an unsigned numeric value right-
justified in the field.
ERROR - HIGH PERCENT DIFFERENCE
For an INSERT or MODIFY transaction, the values given for ACTUAL DESIGNATED and
INDICATED COLLOCATED MONi exceed the maximum percent difference allowed for the
PARAMETER.
ERROR - HIGH SAMPLE VALUE
The value given exceeds the maximum value allowed for the PARAMETER.
Transaction Type 8
9-20
December 1993
-------
o
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - INVALID ACTUAL-DESIGNATED
For a MODIFY transaction, ACTUAL DESIGNATED may be asterisks or one of the values
allowed for INSERT transactions.
ERROR - MUST DELETE OR MODIFY DATA PAIR
On a MODIFY transaction, if INDICATED COLLOCATED MON1 is numeric, ACTUAL
DESIGNATED must be numeric. If INDICATED COLLOCATED MON1 is asterisks,
ACTUAL DESIGNATED must be asterisks.
WARNING - CANNOT VERIFY SAMPLE VALUE
If PARAMETER or UNITS is invalid, ACTUAL DESIGNATED cannot be checked.
December 1993 9-21 Transaction Type 8
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.2.3 INDICATED COLLOCATED MON1
INDICATED COLLOCATED MON1 is the observation being reported.
Attributes:
Coding Instructions:
4 digit numeric
Required
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in INDICATED COLLOCATED MON1
a true observation of a parameter value.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing INDICATED COLLOCATED MON1, code
a true observation, as described above for the INSERT action. You may also fill the INDICATED
COLLOCATED MON1 field with asterisks to delete an existing value, but it is easier (and better) to use
a DELETE transaction. You must enter a numeric value or asterisks in the INDICATED
COLLOCATED MON1 field.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the INDICATED
COLLOCATED MON1 field; they are ignored. A DELETE transaction removes the value from the
database.
Numeric values that represent true observations must be entered right justified in the INDICATED
COLLOCATED MON1 field (columns 35-38). Leading zeros are optional. Remember to allow for the
implied decimal point indicated by the DP field. If a filter for an intermittent monitor is lost or damaged,
enter all zeroes for the observation. The DP field must have a numeric value.
For some PARAMETERS, upper limits have been established for observations, and the numeric value
you enter cannot exceed that maximum. The relevant maximum values and PARAMETERS are listed
below:
Maximum Value
2000 ug/m3
80 ug/m3
20ppm
.2 ppm
.2 ppm
.2 ppm
2000 ug/mj
PARAMETER
11101 (total suspended paniculate)
12128 Gead)
42101 (carbon monoxide)
42401 (sulfur dioxide)
42602 (nitrogen dioxide)
44201 (ozone)
81102 (paniculate matter)
Transaction Type 8
9-22
December 1993
-------
o
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
For some PARAMETERS, percent differences are utilized to reject data that could be in error as a result
of transcription errors. The maximum percent differences and PARAMETERS are listed below:
Maximum Percent
Difference PARAMETER
±160%
±160%
± 90%
± 90%
± 90%
± 90%
±160%
11101
12128
42101
42401
42602
44201
81102
For MllOr, '12128', and '81102', the percent difference is calculated using the following formula:
f 2 (indicated- actual)
(indicated* actual)
x 100
For '42101', '42401', '42602', and '44201', the percent difference is calculated using the following
formula:
(indicated- actual)^) x
actual
Error Messages:
ERROR - HIGH PERCENT DIFFERENCE
For an INSERT or MODIFY transaction, the values given for ACTUAL DESIGNATED and
INDICATED COLLOCATED MONi exceed the maximum percent difference allowed for the
PARAMETER.
ERROR - HIGH SAMPLE VALUE
The value given exceeds the maximum value allowed for the PARAMETER.
ERROR - INDICATED-COL-MON1 MUST BE NUMERIC
For an INSERT transaction, INDICATED COLLOCATED MONI must be an unsigned numeric
value right-justified in the field.
December 1993 9-23 Transaction Type 8
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - INVALID INDICATED-COLLOCATED-MONl
For a MODIFY transaction, INDICATED COLLOCATED MON1 may be asterisks or one of
the values allowed for INSERT transactions.
ERROR - MUST DELETE OR MODIFY DATA PAIR
On a MODIFY transaction, if ACTUAL DESIGNATED is numeric, INDICATED
COLLOCATED MON1 must be numeric. If ACTUAL DESIGNATED is asterisks,
INDICATED COLLOCATED MON1 must be asterisks.
WARNING - CANNOT VERIFY SAMPLE VALUE
If PARAMETER or UNITS is invalid, INDICATED COLLOCATED MON1 cannot be checked.
Transaction Type 8
9-24
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.2.4 INDICATED COLLOCATED MON2
INDICATED COLLOCATED MON2 is the observation being reported for the second collocated monitor
at a PM)0 site.
Attributes: 4 digit numeric
Optional
Coding Instructions:
This field may be valued only if PARAMETER = '81102'.
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in INDICATED COLLOCATED MON2
a true observation of a parameter value.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing INDICATED COLLOCATED MON2, code
a true observation, as described above for the INSERT action. You may also fill the INDICATED
COLLOCATED MON2 field with asterisks to delete an existing value, but it is easier (and better) to use
a DELETE transaction. You must enter a numeric value or asterisks in the INDICATED
COLLOCATED MON2 field.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the INDICATED
COLLOCATED MON2 field; they are ignored. A DELETE transaction removes the value from the
database.
Numeric values that represent true observations must be entered right justified in the INDICATED
COLLOCATED MON2 field (columns 39-42). Leading zeros are optional. Remember to allow for the
implied decimal point indicated by the DP field. If a filter for an intermittent monitor is lost or damaged,
enter all zeroes for the observation. The DP field must have a numeric value.
Upper limits have been established for observations, and the numeric value you enter cannot exceed that
maximum. The relevant maximum value and PARAMETER are listed below:
Maximum Value PARAMETER
2000 ug/m3 81102 (paniculate matter)
Percent differences are utilized to reject data that could be in error as a result of transcription errors.
The maximum percent difference and PARAMETER are listed below:
Maximum Percent
Difference PARAMETER
±160% 81102
December 1993 9-25 Transaction Type 8
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
The percent difference is calculated using the following formula:
2 (indicated-actual)
(2 (ind.
\ (indi
x 100
(indicated* actual)
Error Messages:
ERROR - HIGH PERCENT DIFFERENCE
For an INSERT or MODIFY transaction, the values given for ACTUAL DESIGNATED and
INDICATED COLLOCATED MONi exceed the maximum percent difference allowed for the
PARAMETER.
ERROR - HIGH SAMPLE VALUE
The value given exceeds the maximum value allowed for the PARAMETER.
ERROR - INDICATED-COL-MON2 MUST BE BLANK
This field can be valued only if the PARAMETER is '81102'.
ERROR - INVALID INDICATED-COLLOCATED-MON2
For an INSERT transaction, INDICATED COLLOCATED MON2 must be an unsigned numeric
value right-justified in the field or blank.
For a MODIFY transaction, INDICATED COLLOCATED MON2 may be asterisks or one of
the values allowed for INSERT transactions.
WARNING - CANNOT VERIFY SAMPLE VALUE
If PARAMETER or UNITS is invalid, INDICATED COLLOCATED MON2 cannot be checked.
Transaction Type 8
9-26
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.2.5 INDICATED COLLOCATED MON3
INDICATED COLLOCATED MON3 is the observation being reported for the third collocated monitor
at a PM10 site.
Attributes: 4 digit numeric
Optional
Coding Instructions:
r
This field may be valued only if PARAMETER = '81102'.
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in INDICATED COLLOCATED MON3
a true observation of a parameter value.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing INDICATED COLLOCATED MON3, code
a true observation, as described above for the INSERT action. You may also fill the INDICATED
COLLOCATED MON3 field with asterisks to delete an existing value, but it is easier (and better) to use
a DELETE transaction. You must enter a numeric value or asterisks in the INDICATED
COLLOCATED MON3 field.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the INDICATED
COLLOCATED MON3 field; they are ignored. A DELETE transaction removes the value from the
database.
Numeric values that represent true observations must be entered right justified in the INDICATED
COLLOCATED MON3 field (columns 43-46). Leading zeros are optional. Remember to allow for the
implied decimal point indicated by the DP field. If a filter for an intermittent monitor is lost or damaged,
enter all zeroes for the observation. The DP field must have a numeric value.
Upper limits have been established for observations, and the numeric value you enter cannot exceed that
maximum. The relevant maximum value and PARAMETER are listed below:
Maximum Value PARAMETER
2000 ug/m3 81102 (paniculate matter)
Percent differences are utilized to reject data that could be in error as a result of transcription errors.
The maximum percent difference and PARAMETER are listed below:
Maximum Percent
Difference PARAMETER
+ 160% 81102
December 1993 9-27 Transaction Type 8
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
The percent difference is calculated using the following formula:
2 (indicated-actual)
12 (ind.
\ (indi
x 100
(indicated* actual)
Error Messages:
ERROR - HIGH PERCENT DIFFERENCE
For an INSERT or MODIFY transaction, the values given for ACTUAL DESIGNATED and
INDICATED COLLOCATED MONi exceed the maximum percent difference allowed for the
PARAMETER.
ERROR - HIGH SAMPLE VALUE
The value given exceeds the maximum value allowed for the PARAMETER.
ERROR - INDICATED-COMMONS MUST BE BLANK
This field can be valued only if the PARAMETER is '81102'.
ERROR - INVALID INDICATED-COLLOCATED-MON3
For an INSERT transaction, INDICATED COLLOCATED MON3 must be an unsigned numeric
value right-justified in the field or blank.
For a MODIFY transaction, INDICATED COLLOCATED MON3 may be asterisks or one of
the values allowed for INSERT transactions.
WARNING - CANNOT VERIFY SAMPLE VALUE
If PARAMETER or UNITS is invalid, INDICATED COLLOCATED MON3 cannot be checked.
Transaction Type 8
9-28
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.2.6 INDICATED COLLOCATED MON4
INDICATED COLLOCATED MON4 is the observation being reported for the fourth collocated monitor
at a PM10 site.
Attributes: 4 digit numeric
Optional
Coding Instructions:
This field may be valued only if PARAMETER = '81102'.
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in INDICATED COLLOCATED MON4
a true observation of a parameter value.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing INDICATED COLLOCATED MON4, code
a true observation, as described above for the INSERT action. You may also fill the INDICATED
COLLOCATED MON4 field with asterisks to delete an existing value, but it is easier (and better) to use
a DELETE transaction. You must enter a numeric value or asterisks in the INDICATED
COLLOCATED MON4 field.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the INDICATED
COLLOCATED MON4 field; they are ignored. A DELETE transaction removes the value from the
database.
Numeric values that represent true observations must be entered right justified in the INDICATED
COLLOCATED MON4 field (columns 47-50). Leading zeros are optional. Remember to allow for the
implied decimal point indicated by the DP field. If a filter for an intermittent monitor is lost or damaged,
enter all zeroes for the observation. The DP field must have a numeric value.
Upper limits have been established for observations, and the numeric value you enter cannot exceed that
maximum. The relevant maximum value and PARAMETER are listed below:
Maximum Value PARAMETER
2000 ug/m3 81102 (paniculate matter)
Percent differences are utilized to reject data that could be in error as a result of transcription errors.
The maximum percent difference and PARAMETER are listed below:
Maximum Percent
Difference PARAMETER
+ 160% 81102
December 1993 9-29 Transaction Type 8
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
The percent difference is calculated using the following formula:
x 100
2 (indicated- actual)
(indicated* actual)
Error Messages:
ERROR - HIGH PERCENT DIFFERENCE
For an INSERT or MODIFY transaction, the values given for ACTUAL DESIGNATED and
INDICATED COLLOCATED MONi exceed the maximum percent difference allowed for the
PARAMETER.
ERROR - HIGH SAMPLE VALUE
The value given exceeds the maximum value allowed for the PARAMETER.
ERROR - INDICATED-COL-MON4 MUST BE BLANK
This field can be valued only if the PARAMETER is '81102'.
ERROR - INVALID INDICATED-COLLOCATED-MON4
For an INSERT transaction, INDICATED COLLOCATED MON4 must be an unsigned numeric
value right-justified in the field or blank.
For a MODIFY transaction, INDICATED COLLOCATED MON4 may be asterisks or one of
the values allowed for INSERT transactions.
WARNING - CANNOT VERIFY SAMPLE VALUE
If PARAMETER or UNITS is invalid, INDICATED COLLOCATED MON4 cannot be checked.
Transaction Type 8
9-30
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.2.7 INDICATED COLLOCATED MON5
INDICATED COLLOCATED MON5 is the observation being reported for the fifth collocated monitor
at a PMJO site.
Attributes: 4 digit numeric
Optional
Coding Instructions:
This field may be valued only if PARAMETER = '81102'.
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in INDICATED COLLOCATED MON5
a true observation of a parameter value.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing INDICATED COLLOCATED MON5, code
a true observation, as described above for the INSERT action. You may also fill the INDICATED
COLLOCATED MON5 field with asterisks to delete an existing value, but it is easier (and better) to use
a DELETE transaction. You must enter a numeric value or asterisks in the INDICATED
COLLOCATED MON5 field.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the INDICATED
COLLOCATED MON5 field; they are ignored. A DELETE transaction removes the value from the
database.
Numeric values that represent true observations must be entered right justified in the INDICATED
COLLOCATED MON5 field (columns 51-54). Leading zeros are optional. Remember to allow for the
implied decimal point indicated by the DP field. If a filter for an intermittent monitor is lost or damaged,
enter all zeroes for the observation. The DP field must have a numeric value.
Upper limits have been established for observations, and the numeric value you enter cannot exceed that
maximum. The relevant maximum value and PARAMETER are listed below:
Maximum Value PARAMETER
2000 ug/m3 81102 (paniculate matter)
Percent differences are utilized to reject data that could be in error as a result of transcription errors.
The maximum percent difference and PARAMETER are listed below:
Maximum Percent
Difference PARAMETER
+ 160% 81102
December 1993 9-31 Transaction Type 8
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
The percent difference is calculated using the following formula:
2 (indicated-actual)
( 2 (ind.
\ (indi
x 100
(indicated* actual)
Error Messages:
ERROR - HIGH PERCENT DIFFERENCE
For an INSERT or MODIFY transaction, the values given for ACTUAL DESIGNATED and
INDICATED COLLOCATED MONi exceed the maximum percent difference allowed for the
PARAMETER.
ERROR - HIGH SAMPLE VALUE
The value given exceeds the maximum value allowed for the PARAMETER.
ERROR - INDICATED-COL-MON5 MUST BE BLANK
This field can be valued only if the PARAMETER is '81102'.
ERROR - INVALID INDICATED-COLLOCATED-MON5
For an INSERT transaction, INDICATED COLLOCATED MON5 must be an unsigned numeric
value right-justified in the field or blank.
For a MODIFY transaction, INDICATED COLLOCATED MON5 may be asterisks or one of
the values allowed for INSERT transactions.
WARNING - CANNOT VERIFY SAMPLE VALUE
If PARAMETER or UNITS is invalid, INDICATED COLLOCATED MON5 cannot be checked.
Transaction Type 8
9-32
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.3 Transaction Type 9 - Accuracy Data
The type 9 transaction is used for parameter observations at various intervals to insert, modify, or delete
accuracy raw data values in the Monitor Raw Data File of the AIRS database.
The coding form for the type 9 transaction is shown in Figure 9-1. Each line across the body of the form
represents one transaction, which holds values for at least one level, and up to five levels, of accuracy
data pairs.
AH the values entered on a type 9 transaction apply to the same day. For intermittent monitors, the
actual value is the known value from the audit device. For continuous monitors, the actual value is the
known concentration of gas mixture used to challenge the monitor. For intermittent monitors, the
indicated value is the observation recorded by the audit device. For continuous monitors, the indicated
value is the observed concentration of gas indicated when the monitor was challenged with a known
concentration of gas mixture.
An INSERT transaction is used to insert observations into the database where it does not currently exist.
An actual/indicated pair on the transaction is ignored if it is blank, and has no effect on the database.
A MODIFY transaction is used to change or delete existing observation. An actual/indicated pair on the
transaction is ignored if it is blank, and has no effect on the database. A MODIFY transaction may not
be used to insert a value where none currently exists; an INSERT transaction must be used for that
purpose. Furthermore, a MODIFY transaction may not be used to change the interval, method, units,
or date of an observation. The existing data must be deleted and inserted with the desired new value to
change any of those fields. To delete actual/indicated data pairs, enter ail asterisks for the actual value
and for the indicated value. Asterisks delete the values specified, but do not affect values at other levels
for the same day.
A DELETE transaction is used to remove all the existing observations within the temporal scope of the
transaction. The decimal position and the actual/indicated pairs are not used and are ignored. An
observation does not have to exist for every actual/indicated pair within the scope of the transaction; those
that do exist are deleted.
Error Messages:
ERROR - ALL FIELDS BLANK ON MODIFY
All the fields (INT through ZERO SPAN) of a MODIFY transaction are blank.
December 1993 9-33 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - DUPLICATE ACCURACY VALUES ON THESE RECORDS
There are two or more transactions with the same action code that have an actual /indicated pair
for the same monitor, date, and level, or there are two or more transactions with the same action
code that have a zero span for the same monitor and date. There is no limit on the number of
transactions for a given monitor and date, just so no two of them have the same action code for
the same level. As many as three transactions may pertain to the actual/indicated pair for a given
level if they all have different action codes. If multiple actions for one level are present, they
are applied to the database in the order DELETE, INSERT, MODIFY.
Transaction Type 9
9-34
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
^ 9.3.1 TYPE AUDIT
TYPE AUDIT (TA) is a code assigned to the type of audit conducted on the monitor.
Attributes: 1 digit code
Conditionally required
Coding Instructions:
Enter a valid TYPE AUDIT in column 30. Valid values are blank and the digits 1 - 3.
With INSERT transactions, TYPE AUDIT must be numeric. The valid values and their meanings are:
1 = audit conducted by reporting organization; audit standard certified by reporting organization
2 = audit conducted by reporting organization; audit standard certified by another organization
3 = audit conducted by other than reporting organization
For DELETE and MODIFY transactions, the TYPE AUDIT may be left blank.
Error Messages:
ERROR - INVALID TYPE-AUDIT
Valid values are 1 through 3 and blank.
ERROR - TYPE-AUDIT CANNOT BE BLANK
On an INSERT transaction, TYPE AUDIT must be I, 2, or 3.
ERROR - TYPE-AUDIT CANNOT BE DELETED
On a MODIFY transaction, TYPE AUDIT cannot be an asterisk.
December 1993 9-35 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3.2 LOCAL PRIMARY STANDARD
LOCAL PRIMARY STANDARD (LPS) is code indicating the source of the local primary standard.
Attributes:
Coding Instructions:
1 character code
Conditionally required
Enter a valid LOCAL PRIMARY STANDARD in column 31. Valid values are blank or a value from
the AIRS GEO-COMMON File. Valid codes are listed in Volume GC2 of the AIRS User's Guide.
For INSERT transactions, LOCAL PRIMARY STANDARD must be one of the codes from the AIRS
GEO-COMMON File.
For DELETE and MODIFY transactions, the LOCAL PRIMARY STANDARD may be left blank.
Error Messages:
ERROR - CANNOT DELETE LOCAL-STD-SOURCE
On a MODIFY transaction, LOCAL PRIMARY STANDARD cannot be an asterisk.
ERROR - INVALID LOCAL-STD-SOURCE
Valid values are blank or codes specified in the AIRS GEO-COMMON File.
ERROR - LOCAL-STD-SOURCE CANNOT BE BLANK
On an INSERT transaction, LOCAL PRIMARY STANDARD must be one of the codes from the
AIRS GEO-COMMON File.
Transaction Type 9
9-36
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.3.3 AUDIT CLASSIFICATION
AUDIT CLASSIFICATION (AC) is a code indicating the class of the audit taken at the monitor.
Attributes: 1 character code
Required
Coding Instructions:
Enter a valid AUDIT CLASSIFICATION in column 32. Valid values are:
A as analytical
F — flow
S = span
AUDIT CLASSIFICATION is specific to the PARAMETER-INTERVAL-UNITS as indicated in the
following table:
PARAMETER INTERVAL UNITS AUDIT CLASS
11101 7 072, 083 F
12128 7,8,C 072, 083 F
81102 7 072, 073, 083 F
12128 7,8,C 077 A
42401 7 064 A
42602 7 064 A
42101 1 005, 007 A or S
42401 1 001, 007, 008 A or S
42602 1 001, 007, 008 A or S
44201 1 001, 007, 008 A or S
Error Messages:
ERROR - AUDIT-CLASS CANNOT BE BLANK
AUDIT CLASSIFICATION must be valued for all transaction types.
ERROR - CANNOT DELETE AUDIT-CLASS
AUDIT CLASSIFICATION cannot be an asterisk on a MODIFY transaction.
ERROR - INVALID AUDIT-CLASS
Valid values are A, F or S; the value used must be valid for the PARAMETER-INTERVAL-
UNITS.
December 1993 9-37 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
WARNING - CANNOT VERIFY AUDIT-CLASS
If PARAMETER, INTERVAL, or UNITS is invalid, AUDIT CLASSIFICATION cannot be
checked.
Transaction Type 9
9-38
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
9.3.4 DP
DP indicates the number of digits to the right of the decimal point in the ACTUAL and INDICATED
fields.
Attributes: 1 digit code
Conditionally required
Coding Instructions:
r
Enter a valid DP value in column 33. Valid values are blank and the digits 0-5. The same DP value
applies to all ACTUAL and INDICATED fields on the transaction.
With INSERT and MODIFY transactions, DP must be numeric. A numeric value for DP implies that
true observations are coded in the ACTUAL and INDICATED fields.
Although you can place an asterisk in this field on a DELETE transaction, doing so is meaningless. A
DELETE transaction says to delete all values in the time range covered by the transaction.
Error Messages:
ERROR - INVALID DECIMAL-POSITION
Valid values are 0 through 5 and blank.
December 1993 9-39 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3.5 ACTUAL LEVEL-i
ACTUAL LEVEL-1 is the observation being reported.
Attributes:
4 digit numeric
Conditionally required
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in ACTUAL LEVEL-1 a true observation
of a parameter value. When a numeric value is entered for ACTUAL LEVEL-1, a numeric value must
also be entered for INDICATED LEVEL-1.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing ACTUAL LEVEL-1, code a true
observation, as described above for the INSERT action. When a numeric value is entered for ACTUAL
LEVEL-1, a numeric value must also be entered for INDICATED LEVEL-1. You may also fill the
ACTUAL LEVEL-1 field with asterisks to delete an existing value, but it is easier (and better) to use a
DELETE transaction. When asterisks are entered for ACTUAL LEVEL-1, asterisks must also be entered
for INDICATED LEVEL-1.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the ACTUAL LEVEL-1
field; they are ignored. A DELETE transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the ACTUAL LEVEL-1
field (columns 34-37). Leading zeros are optional. Remember to allow for the implied decimal point
indicated by the DP field.
For some PARAMETERS, a range of expected values has been established for observations.
Concentrations reported outside the range may be data for another level. The relevant ranges and
PARAMETERS are listed below:
Concentration Ranee PARAMETER
2.70-8.80 ppm
.027-.088 ppm
.027-.088 ppm
.027-.088 ppm
42101 (carbon monoxide)
42401 (sulfur dioxide)
42602 (nitrogen dioxide)
44201 (ozone)
For some PARAMETERS, percent differences are utilized to reject data that could be in error as a result
of transcription errors. The maximum percent differences and PARAMETERS are listed below:
Transaction Type 9
9-40
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
Maximum Percent
Difference PARAMETER
± 90%
± 90%
± 90%
± 90%
± 90%
12128
42101
42401
42602
44201
The percent difference is calculated using the following formula:
\ (indicated-actual)
actual
x 100
Error Messages:
ERROR - BOTH FIELDS MUST BE VALUED
On an INSERT or MODIFY transaction, if INDICATED LEVEL-1 is valued, ACTUAL LEVEL-1
must be valued.
ERROR - HIGH PERCENT DIFFERENCE
The percent difference between ACTUAL LEVEL-1 and INDICATED LEVEL-1 exceeds the
maximum permitted.
ERROR - INVALID ACTUAL-LEVEL-1
For an INSERT transaction, ACTUAL LEVEL-1 may be blank or an unsigned numeric value right-
justified in the field.
For a MODIFY transaction, ACTUAL LEVEL-1 may be asterisks or one of the values allowed
for INSERT transactions.
ERROR - MUST DELETE OR MODIFY DATA PAIR
f
On a MODIFY transaction, if INDICATED LEVEL-1 is asterisks, then ACTUAL LEVEL-1 must
be asterisks. If INDICATED LEVEL-1 is numeric, then ACTUAL LEVEL-1 must be numeric.
ERROR - SAMPLE VALUE MUST BE BLANK
If PARAMETER is '11101* or '81102', ACTUAL LEVEL-1 must be blank.
WARNING - CONCENTRATION OUT OF RANGE
The value given is outside of the range expected for the PARAMETER.
December 1993 9-41 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3.6 INDICATED LEVEL-1
INDICATED LEVEL-1 is the observation being reported.
Attributes:
4 digit numeric
Conditionally required
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in INDICATED LEVEL-1 a true
observation of a parameter value. When a numeric value is entered for INDICATED LEVEL-1, a
numeric value must also be entered for ACTUAL LEVEL-1.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing INDICATED LEVEL-1, code a true
observation, as described above for the INSERT action. When a numeric value is entered for
INDICATED LEVEL-1, a numeric value must also be entered for ACTUAL LEVEL-1. You may also
fill the INDICATED LEVEL-1 field with asterisks to delete an existing value, but it is easier (and better)
to use a DELETE transaction. When Asterisks are entered for INDICATED LEVEL-1, asterisks must
also be entered for ACTUAL LEVEL-1.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the INDICATED LEVEL-
1 field; they are ignored. A DELETE transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the INDICATED
LEVEL-1 field (columns 38-41). Leading zeros are optional. Remember to allow for the implied
decimal point indicated by the DP field.
For some PARAMETERS, a range of expected values has been established for observations.
Concentrations reported outside the range may be data for another level. The relevant ranges and
PARAMETERS are listed below:
Concentration Ranee PARAMETER
2.70-8.80 ppm
.027-.088 ppm
.027-.088 ppm
.027-. 088 ppm
42101 (carbon monoxide)
42401 (sulfur dioxide)
42602 (nitrogen dioxide)
44201 (ozone)
For some PARAMETERS, percent differences are utilized to reject data that could be in error as a result
of transcription errors. The maximum percent differences and PARAMETERS are listed below:
Transaction Type 9
9-42
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
41
Maximum Percent
Difference PARAMETER
± 90%
± 90%
± 90%
+ 90%
+ 90%
12128
42101
42401
42602
44201
The percent difference is calculated using the following formula:
f (indicated-actual)
actual
x 100
Error Messages:
ERROR - BOTH FIELDS MUST BE VALUED
On an INSERT or MODIFY transaction, if ACTUAL LEVEL-1 is valued, INDICATED LEVEL-1
must be valued.
ERROR - HIGH PERCENT DIFFERENCE
The percent difference between ACTUAL LEVEL-1 and INDICATED LEVEL-1 exceeds the
maximum permitted.
ERROR - INVALID INDICATED-LEVEL-1
For an INSERT transaction, INDICATED LEVEL-1 may be blank or an unsigned numeric value
right-justified in the field.
For a MODIFY transaction, INDICATED LEVEL-1 may be asterisks or one of the values allowed
for INSERT transactions.
ERROR - MUST DELETE OR MODIFY DATA PAIR
On a MODIFY transaction, if ACTUAL LEVEL-1 is asterisks, then INDICATED LEVEL-1 must
be asterisks. If ACTUAL LEVEL-1 is numeric, then INDICATED LEVEL-1 must be numeric.
ERROR - SAMPLE VALUE MUST BE BLANK
If PARAMETER is '11101' or '81102', INDICATED LEVEL-1 must be blank.
WARNING - CONCENTRATION OUT OF RANGE
The value given is outside of the range expected for the PARAMETER.
December 1993 9-43 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3.7 ACTUAL LEVEL-2
ACTUAL LEVEL-2 is the observation being reported.
Attributes:
4 digit numeric
Conditionally required
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in ACTUAL LEVEL-2 a true observation
of a parameter value. When a numeric value is entered for ACTUAL LEVEL-2, a numeric value must
also be entered for INDICATED LEVEL-2.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing ACTUAL LEVEL-2, code a true
observation, as described above for the INSERT action. When a numeric value is entered for ACTUAL
LEVEL-2, a numeric value must also be entered for INDICATED LEVEL-2. You may also fill the
ACTUAL LEVEL-2 field with asterisks to delete an existing value, but it is easier (and better) to use a
DELETE transaction. When asterisks are entered for ACTUAL LEVEL-2, asterisks must also be entered
for INDICATED LEVEL-2.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the ACTUAL LEVEL-2
field; they are ignored. A DELETE transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the ACTUAL LEVEL-2
field (columns 42-45). Leading zeros are optional. Remember to allow for the implied decimal point
indicated by the DP field.
For some PARAMETERS, a range of expected values has been established for observations.
Concentrations reported outside the range may be data for another level. The relevant ranges and
PARAMETERS are listed below:
Concentration Ranee PARAMETER
13.5-22.0 ppm
.135-.220ppm
.135-.220ppm
.135-.220ppm
42101 (carbon monoxide)
42401 (sulfur dioxide)
42602 (nitrogen dioxide)
44201 (ozone)
For some PARAMETERS, percent differences are utilized to reject data that could be in error as a result
of transcription errors. The maximum percent differences and PARAMETERS are listed below:
Transaction Type 9
9-44
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
Maximum Percent
Difference PARAMETER
± 90%
± 90%
± 90%
± 90%
±. 90%
± 90%
± 90%
11101
12128
42101
42401
42602
44201
81102
The percent difference is calculated using the following formula:
(indicated- actual)
actual \
Error Messages:
ERROR - BOTH FIELDS MUST BE VALUED
On an INSERT or MODIFY transaction, if INDICATED LEVEL-2 is valued, ACTUAL LEVEL-2
must be valued.
ERROR - HIGH PERCENT DIFFERENCE
The percent difference between ACTUAL LEVEL-2 and INDICATED LEVEL-2 exceeds the
maximum permitted.
ERROR - INVALID ACTUAL-LEVEL-2
For an INSERT transaction, ACTUAL LEVEL-2 may be blank or an unsigned numeric value right-
justified in the field.
For a MODIFY transaction, ACTUAL LEVEL-2 may be asterisks or one of the values allowed
for INSERT transactions.
ERROR - MUST DELETE OR MODIFY DATA PAIR
On a MODIFY transaction, if INDICATED LEVEL-2 is asterisks, then ACTUAL LEVEL-2 must
be asterisks. If INDICATED LEVEL-2 is numeric, then ACTUAL LEVEL-2 must be numeric.
WARNING - CONCENTRATION OUT OF RANGE
The value given is outside of the range expected for the PARAMETER.
December 1993 MS Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3,8 INDICATED LEVEL-2
INDICATED LEVEL-2 is the observation being reported.
Attributes:
4 digit numeric
Conditionally required
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in INDICATED LEVEL-2 a true
observation of a parameter value. When a numeric value is entered for INDICATED LEVEL-2, a
numeric value must also be entered for ACTUAL LEVEL-2.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing INDICATED LEVEL-2, code a true
observation, as described above for the INSERT action. When a numeric value is entered for
INDICATED LEVEL-2, a numeric value must also be entered for ACTUAL LEVEL-2. You may also
fill the INDICATED LEVEL-2 field with asterisks to delete an existing value, but it is easier (and better)
to use a DELETE transaction. When asterisks are entered for INDICATED LEVEL-2, asterisks must
also be entered for ACTUAL LEVEL-2.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the INDICATED LEVEL-
2 field; they are ignored. A DELETE transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the INDICATED
LEVEL-2 field (columns 46-49). Leading zeros are optional. Remember to allow for the implied
decimal point indicated by the DP field.
For some PARAMETERS, a range of expected values has been established for observations.
Concentrations reported outside the range may be data for another level. The relevant ranges and
PARAMETERS are listed below:
Concentration Ranee PARAMETER
13.5-22.0 ppm
.135-.220ppm
.135-.220ppm
.135-.220ppm
42101 (carbon monoxide)
42401 (sulfur dioxide)
42602 (nitrogen dioxide)
44201 (ozone)
For some PARAMETERS, percent differences are utilized to reject data that could be in error as a result
of transcription errors. The maximum percent differences and PARAMETERS are listed below:
Transaction Type 9
9-46
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
Maximum Percent
Difference PARAMETER
+ 9096
± 90%
-1- 90%
+ 90%
-1- 90%
± 90%
± 90%
11101
12128
42101
42401
42602
44201
81102
The percent difference is calculated using the following formula:
( 2 (indicated- actual) } x 10Q
\ actual /
Error Messages:
ERROR - BOTH FIELDS MUST BE VALUED
On an INSERT or MODIFY transaction, if ACTUAL LEVEL-2 is valued, INDICATED LEVEL-2
must be valued.
ERROR - HIGH PERCENT DIFFERENCE
The percent difference between ACTUAL LEVEL-2 and INDICATED LEVEL-2 exceeds the
maximum permitted.
ERROR - INVALID INDICATED-LEVEL-2
For an INSERT transaction, INDICATED LEVEL-2 may be blank or an unsigned numeric value
right-justified in the field.
For a MODIFY transaction, INDICATED LEVEL-2 may be asterisks or one of the values allowed
for INSERT transactions.
ERROR - MUST DELETE OR MODIFY DATA PAIR
On a MODIFY transaction, if ACTUAL LEVEL-2 is asterisks, then INDICATED LEVEL-2 must
be asterisks. If ACTUAL LEVEL-2 is numeric, then INDICATED LEVEL-2 must be numeric.
WARNING - CONCENTRATION OUT OF RANGE
The value given is outside of the range expected for the PARAMETER.
December 1993 9-47 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3.9 ACTUAL LEVEL-3
ACTUAL LEVEL-3 is the observation being reported.
Attributes:
4 digit numeric
Conditionally required
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in ACTUAL LEVEL-3 a true observation
of a parameter value. When a numeric value is entered for ACTUAL LEVEL-3, a numeric value must
also be entered for INDICATED LEVEL-3.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction To alter an existing ACTUAL LEVEL-3, code a true
observation, as described above for the INSERT action. When a numeric value is entered for ACTUAL
LEVEL-3, a numeric value must also be entered for INDICATED LEVEL-3. You may also fill the
ACTUAL LEVEL-3 field with asterisks to delete an existing value, but it is easier (and better) to use a
DELETE transaction. When asterisks ai i entered for ACTUAL LEVEL-3, asterisks must also be entered
for INDICATED LEVEL-3.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the ACTUAL LEVEL-3
field; they are ignored. A DELETE transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the ACTUAL LEVEL-3
field (columns 50-53). Leading zeros are optional. Remember to allow for the implied decimal point
indicated by the DP field.
For some PARAMETERS, a range of expected values has been established for observations.
Concentrations reported outside the range may be data for another level. The relevant ranges and
PARAMETERS are listed below:
Concentration Ranee PARAMETER
31.5-49.5 ppm
.3I5-.495 ppm
.315-.495 ppm
.315-.495ppm
42101 (carbon monoxide)
42401 (sulfur dioxide)
42602 (nitrogen dioxide)
44201 (ozone)
For some PARAMETERS, percent differences are utilized to reject data that could be in error as a result
of transcription errors. The maximum percent differences and PARAMETERS are listed below:
Transaction Type 9
9-48
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
Maximum Percent
Difference PARAMETER
± 90% 42101
± 90* 42401
± 90% 42602
± 90% 44201
The percent difference is calculated using the following formula:
I 2 (indicated- actual) \ x 10Q
| actual j
Error Messages:
ERROR - BOTH FIELDS MUST BE VALUED
On an INSERT or MODIFY transaction, if INDICATED LEVEL-3 is valued, ACTUAL LEVEL-3
must be valued.
ERROR - HIGH PERCENT DIFFERENCE
The percent difference between ACTUAL LEVEL-3 and INDICATED LEVEL-3 exceeds the
maximum permitted.
ERROR - INVALID ACTUAJL-LEVEL-3
For an INSERT transaction, ACTUAL LEVEL-3 may be blank or an unsigned numeric value right-
justified in the field.
For a MODIFY transaction, ACTUAL LEVEL-3 may be asterisks or one of the values allowed
for INSERT transactions.
ERROR - MUST DELETE OR MODIFY DATA PAIR
On a MODIFY transaction, if INDICATED LEVEL-3 is asterisks, then ACTUAL LEVEL-3 must
be asterisks. If INDICATED LEVEL-3 is numeric, then ACTUAL LEVEL-2 must be numeric.
ERROR - SAMPLE VALUE MUST BE BLANK
If PARAMETER is '11101', '12128', or '81102', ACTUAL LEVEL-3 must be blank.
WARNING - CONCENTRATION OUT OF RANGE
^^ The value given is outside of the range expected for the PARAMETER.
December 1993 9-49 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3.10 INDICATED LEVEL-3
INDICATED LEVEL-3 is the observation being reported.
Attributes:
4 digit numeric
Conditionally required
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in INDICATED LEVEL-3 a true
observation of a parameter value. When a numeric value is entered for INDICATED LEVEL-3, a
numeric value must also be entered for ACTUAL LEVEL-3.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing INDICATED LEVEL-3, code a true
observation, as described above for the INSERT action. When a numeric value is entered for
INDICATED LEVEL-3, a numeric value must also be entered for ACTUAL LEVEL-3. You may also
fill the INDICATED LEVEL-3 field with asterisks to delete an existing value, but it is easier (and better)
to use a DELETE transaction. When asterisks are entered for INDICATED LEVEL-3, asterisks must
also be entered for ACTUAL LEVEL-3.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the INDICATED LEVEL-
3 field; they are ignored. A DELETE transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the INDICATED
LEVEL-3 field (columns 54-57). Leading zeros are optional. Remember to allow for the implied
decimal point indicated by the DP field.
For some PARAMETERS, a range of expected values has been established for observations.
Concentrations reported outside the range may be data for another level. The relevant ranges and
PARAMETERS are listed below:
Concentration Ranee PARAMETER
31.5-49.5 ppm
.315-.495ppm
.315-.495 ppm
.315-.495 ppm
42101 (carbon monoxide)
42401 (sulfur dioxide)
42602 (nitrogen dioxide)
44201 (ozone)
For some PARAMETERS, percent differences are utilized to reject data that could be in error as a result
of transcription errors. The maximum percent differences and PARAMETERS are listed below:
Transaction Type 9
9-50
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
Maximum Percent
Difference PARAMETER
± 90% 42101
± 90% 42401
± 90% 42602
± 90% 44201
The percent difference is calculated using the following formula:
r
(indicated- actual) \ >
actual J
Error Messages:
ERROR - BOTH FIELDS MUST BE VALUED
On an INSERT or MODIFY transaction, if ACTUAL LEVEL-3 is valued, INDICATED LEVEL-3
must be valued.
ERROR - HIGH PERCENT DIFFERENCE
The percent difference between ACTUAL LEVEL-3 and INDICATED LEVEL-3 exceeds the
maximum permitted.
ERROR - INVALID INDICATED-LEVEL-3
For an INSERT transaction, INDICATED LEVEL-3 may be blank or an unsigned numeric value
right-justified in the field.
For a MODIFY transaction, INDICATED LEVEL-3 may be asterisks or one of the values allowed
for INSERT transactions.
ERROR - MUST DELETE OR MODIFY DATA PAIR
On a MODIFY transaction, if ACTUAL LEVEL-3 is asterisks, then INDICATED LEVEL-3 must
be asterisks. If ACTUAL LEVEL-3 is numeric, then INDICATED LEVEL-3 must be numeric.
ERROR - SAMPLE VALUE MUST BE BLANK
If PARAMETER is '11101', '12128*, or '81102', INDICATED LEVEL-3 must be blank.
WARNING - CONCENTRATION OUT OF RANGE
The value given is outside of the range expected for the PARAMETER.
December 1993 9-51 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3.11 ACTUAL LEVEL-4
ACTUAL LEVEL-4 is the observation being reported.
Attributes:
4 digit numeric
Conditionally required
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in ACTUAL LEVEL-4 a true observation
of a parameter value. When a numeric value is entered for ACTUAL LEVEL-4, a numeric value must
also be entered for INDICATED LEVEL-4.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing ACTUAL LEVEL-4, code a true
observation, as described above for the INSERT action. When a numeric value is entered for ACTUAL
LEVEL-4, a numeric value must also be entered for INDICATED LEVEL-4. You may also fill the
ACTUAL LEVEL-4 field with asterisks to delete an existing value, but it is easier (and better) to use a
DELETE transaction. When asterisks are entered for ACTUAL LEVEL-4, asterisks must also be entered
for INDICATED LEVELS.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the ACTUAL LEVEL-4
field; they are ignored. A DELETE transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the ACTUAL LEVEL-4
field (columns 58-61). Leading zeros are optional. Remember to allow for the implied decimal point
indicated by the DP field.
For some PARAMETERS, a range of expected values has been established for observations.
Concentrations reported outside the range may be data for another level. The relevant ranges and
PARAMETERS are listed below:
Concentration Ranee PARAMETER
72.0-99.0 ppm
.720-.990 ppm
.720-.990 ppm
.720-.990 ppm
42101 (carbon monoxide)
42401 (sulfur dioxide)
42602 (nitrogen dioxide)
44201 (ozone)
For some PARAMETERS, percent differences are utilized to reject data that could be in error as a result
of transcription errors. The maximum percent differences and PARAMETERS are listed below:
Transaction Type 9
9-52
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
Maximum Percent
Difference PARAMETER
± 90% 42101
± 90% 42401
± 90% 42602
± 90% 44201
The percent difference is calculated using the following formula:
f (indicated-actual)
actual
x 100
Error Messages:
ERROR - BOTH FIELDS MUST BE VALUED
On an INSERT or MODIFY transaction, if INDICATED LEVELS is valued, ACTUAL LEVELS
must be valued.
ERROR - HIGH PERCENT DIFFERENCE
The percent difference between ACTUAL LEVEL-4 and INDICATED LEVEL-4 exceeds the
maximum permitted.
ERROR - INVALID ACTUAL-LEVEL-4
For an INSERT transaction, ACTUAL LEVEL-4 may be blank or an unsigned numeric value right-
justified in the field.
For a MODIFY transaction, ACTUAL LEVEL-4 may be asterisks or one of the values allowed
for INSERT transactions.
ERROR - MUST DELETE OR MODIFY DATA PAIR
On a MODIFY transaction, if INDICATED LEVEL-4 is asterisks, then ACTUAL LEVEL-4 must
be asterisks. If INDICATED LEVEL-4 is numeric, then ACTUAL LEVEL-4 must be numeric.
ERROR - SAMPLE VALUE MUST BE BLANK
If PARAMETER is '11101', 12128', or '81102', or if PARAMETER is '42401' or '42602* and
INTERVAL is '?', ACTUAL LEVEL-4 must be blank.
WARNING - CONCENTRATION OUT OF RANGE
The value given is outside of the range expected for the PARAMETER.
December 1993 9-53 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3.12 INDICATED LEVEL-4
INDICATED LEVEL-4 is the observation being reported.
Attributes:
4 digit numeric
Conditionally required
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in INDICATED LEVEL-4 a true
observation of a parameter value. When a numeric value is entered for INDICATED LEVEL-4, a
numeric value must also be entered for ACTUAL LEVEL-4.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing INDICATED LEVEL-4, code a true
observation, as described above for the INSERT action. When a numeric value is entered for
INDICATED LEVEL-4, a numeric valu;; must also be entered for ACTUAL LEVEL-4. You may also
fill the INDICATED LEVEL-4 field with asterisks to delete an existing value, but it is easier (and better)
to use a DELETE transaction. When asterisks are entered for INDICATED LEVEL-4, asterisks must
also be entered for ACTUAL LEVEL-4.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the INDICATED LEVEL-
4 field; they are ignored. A DELE1E transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the INDICATED
LEVEL-4 field (columns 62-65). Leading zeros are optional. Remember to allow for the implied
decimal point indicated by the DP field.
For some PARAMETERS, a range of expected values has been established for observations.
Concentrations reported outside the range may be data for another level. The relevant ranges and
PARAMETERS are listed below:
Concentration Ranee PARAMETER
72.0-99.0 ppm
.720-.990 ppm
.720-.990 ppm
.720-.990 ppm
42101 (carbon monoxide)
42401 (sulfur dioxide)
42602 (nitrogen dioxide)
44201 (ozone)
For some PARAMETERS, percent differences are utilized to reject data that could be in error as a result
of transcription errors. The maximum percent differences and PARAMETERS are listed below:
Transaction Type 9
9-54
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
Maximum Percent
Difference PARAMETER
± 90% 42101
± 90% 42401
± 90% 42602
± 90% 44201
The percent difference is calculated using the following formula:
I (indicated-actual)
actual
x 100
Error Messages:
ERROR - BOTH FIELDS MUST BE VALUED
On an INSERT or MODIFY transaction, if ACTUAL LEVEL-* is valued, INDICATED LEVEL4
must be valued.
ERROR - HIGH PERCENT DIFFERENCE
The percent difference between ACTUAL LEVEL-4 and INDICATED LEVEL-4 exceeds the
maximum permitted.
ERROR - INVALID INDICATED-LEVEL-4
For an INSERT transaction, INDICATED LEVEL-4 may be blank or an unsigned numeric value
right-justified in the field.
For a MODIFY transaction, INDICATED LEVELS may be asterisks or one of the values allowed
for INSERT transactions.
ERROR - MUST DELETE OR MODIFY DATA PAIR
On a MODIFY transaction, if ACTUAL LEVEL-4 is asterisks, then INDICATED LEVEL-4 must
be asterisks. If ACTUAL LEVEL-* is numeric, then INDICATED LEVEL-4 must be numeric.
ERROR - SAMPLE VALUE MUST BE BLANK
If PARAMETER is '11101', '12128', or '81102', or if PARAMETER is '42401' or '42602* and
INTERVAL is '7', INDICATED LEVEL-4 must be blank.
WARNING - CONCENTRATION OUT OF RANGE
The value given is outside of the range expected for the PARAMETER.
December 1993 9-55 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3.13 ACTUAL LEVEL-5
ACTUAL LEVEL-5 is the observation being reported.
Attributes:
Coding Instructions:
4 digit numeric
Conditionally required
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in ACTUAL LEVEL-S a true observation
of a parameter value. When a numeric value is entered for ACTUAL LEVEL-S, a numeric value must
also be entered for INDICATED LEVEL-5.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing ACTUAL LEVEL-5, code a true
observation, as described above for the INSERT action. When a numeric value is entered for ACTUAL
LEVEL-5, a numeric value must also be entered for INDICATED LEVEL-5. You may also fill the
ACTUAL LEVEL-5 field with asterisks to delete an existing value, but it is easier (and better) to use a
DELETE transaction. When asterisks are entered for ACTUAL LEVEL-5, asterisks must also be entered
for INDICATED LEVEL-5.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the ACTUAL LEVEL-5
field; they are ignored. A DELETE transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the ACTUAL LEVEL-5
field (columns 66-69). Leading zeros are optional. Remember to allow for the implied decimal point
indicated by the DP field.
Error Messages:
ERROR - BOTH FIELDS MUST BE VALUED
On an INSERT or MODIFY transaction, if INDICATED LEVEL-5 is valued, ACTUAL LEVEL-5
must be valued.
ERROR - INVALID ACTUAL-LEVEL-5
For an INSERT transaction, ACTUAL LEVEL-5 may be blank or an unsigned numeric value right-
justified in the field.
For a MODIFY transaction, ACTUAL LEVEL-5 may be asterisks or one of the values allowed
for INSERT transactions.
Transaction Type 9
9-56
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - MUST DELETE OR MODIFY DATA PAIR
On a MODIFY transaction, if INDICATED LEVEL-5 is asterisks, then ACTUAL LEVEL-5 must
be asterisks. If INDICATED LEVEL-5 is numeric, then ACTUAL LEVEL-5 must be numeric.
December 1993 9-57 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3.14 INDICATED LEVEL-5
INDICATED LEVEL-5 is the observation being reported.
Attributes:
4 digit numeric
Conditionally required
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in INDICATED LEVEL-5 a true
observation of a parameter value. When a numeric value is entered for INDICATED LEVEL-5, a
numeric value must also be entered for ACTUAL LEVEL-5.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing INDICATED LEVEL-5, code a true
observation, as described above for the INSERT action. When a numeric value is entered for
INDICATED LEVEL-5, a numeric value must also be entered for ACTUAL LEVEL-5. You may also
fill the INDICATED LEVEL-5 field with asterisks to delete an existing value, but it is easier (and better)
to use a DELETE transaction. When asterisks are entered for INDICATED LEVEL-5, asterisks must
also be entered for ACTUAL LEVEL-5.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need not enter asterisks or any other value in the INDICATED LEVEL-
5 field; they are ignored. A DELETE transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the INDICATED
LEVEL-5 field (columns 70-73). Leading zeros are optional. Remember to allow for the implied
decimal point indicated by the DP field.
Error Messages:
ERROR - BOTH FIELDS MUST BE VALUED
On an INSERT or MODIFY transaction, if ACTUAL LEVEL-5 is valued, INDICATED LEVEL-5
must be valued.
ERROR - INVALID INDICATED-LEVEL-5
For an INSERT transaction, INDICATED LEVEL-5 may be blank or an unsigned numeric value
right-justified in the field.
For a MODIFY transaction, INDICATED LEVEL-5 may be asterisks or one of the values allowed
for INSERT transactions.
Transaction Type 9
9-58
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - MUST DELETE OR MODIFY DATA PAIR
On a MODIFY transaction, if ACTUAL LEVEL-5 is asterisks, then INDICATED LEVEL-5 must
be asterisks. If INDICATED LEVEL-5 is numeric, then ACTUAL LEVEL-5 must be numeric.
December 1993 9-59 Transaction Type 9
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
9.3.15 ZERO SPAN
ZERO SPAN is the observation being reported. ZERO SPAN is the observed value read from the
instrument when the concentration of the specific parameter used to test the monitor was zero.
Attributes:
5 digit signed numeric
Optional
Coding Instructions:
Use an INSERT transaction to insert a value that has not been reported previously. There must not be
a value in the database for the date of the transaction. Place in ZERO SPAN a true observation of a
parameter value.
Use a MODIFY transaction to alter a value that already exists in the database. A value must exist in the
database for the date of the transaction. To alter an existing ZERO SPAN, code a true observation as
described above for the INSERT action. You may also fill the ZERO SPAN field with asterisks to delete
an existing value, but it is easier (and better) to use a DELETE transaction.
Use a DELETE transaction to delete a value from the database. A value must exist in the database for
the date of the transaction. You need lot enter asterisks or any other value in the ZERO SPAN field;
they are ignored. A DELETE transaction removes the value from the database.
Numeric values that represent true observations must be entered right justified in the ZERO SPAN field
(columns 74-78). Leading zeros are required. You may enter negative values. To enter a negative
value, place a minus sign in the first position of the ZERO SPAN field and four digits in the remaining
positions. For example, you would code the negative value -13 as -0013 on the transaction. Remember
to allow for the implied decimal point indicated by the DP field.
Error Message:
ERROR - INVALID ZERO-SPAN
For an INSERT transaction, ZERO SPAN may be blank or a signed numeric value of the form -
nnnn.
For a MODIFY transaction, ZERO SPAN may be asterisks or one of the values allowed for
INSERT transactions.
Transaction Type 9
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
Appendix A. Alphabetical List of Error Messages
ERROR - ACTION CODES DO NOT MATCH ON SLAMS RECORDS
Transaction types M - V 6-5
ERROR - ACTUAL-DESIG MUST BE NUMERIC
Transaction type 8 9-20
ERROR - ADD-SAMP-DAYS CANNOT BE BLANK
Transaction type M 6-21
ERROR - AIR-BASIN ONLY FOR STATE 06
Transaction type A2 4-17
ERROR - ALL 4 QUARTERS CANNOT BE BLANK
Transaction type U 6-113
ERROR - ALL DATA FIELDS ARE BLANK
Transaction type M 6-10
Transaction type N 6-23
ERROR - ALL FIELDS BLANK ON MODIFY
Transaction type 1 7-15
Transaction type 2 7-33
Transaction type 3 7-45
Transaction type 4 8-17
Transaction type 8 9-16
Transaction type 9 9-33
Transaction type Al 4-6
Transaction type A2 4-13
Transaction type A3 4-29
Transaction type A4 4-51
Transaction type A5 4-66
Transaction type A6 4-67
Transaction type A7 4-68
Transaction type Fl 5-9
Transaction type F2 5-35
Transaction type F3 5-59
Transaction type F4 5-70
Transaction type F5 5-71
Transaction type P 6-33
Transaction type R 6-53
Transaction type S 6-70
Transaction type T 6-88
Transaction type U 6-105
Transaction type V 6-117
Transaction type 2 8-10
ERROR - ALL FREQUENCIES ARE BLANK
Transaction type V 6-123
December 1993 A-l Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - ALL FREQUENCIES ARE ZERO
Transaction type V 6-123
ERROR - ALL METHODS CANNOT BE BLANK
Transaction type U 6-110
Transaction type V 6-121
ERROR - ALL MONITORS NOT TERMINATED
Transaction type Al 4-10
ERROR - ALL SAMP-VALUES CANNOT BE BLANK
Transaction type 1 7-23
ERROR - ALL SLAMS INVALID DUE TO DUPLICATE "V"
Transaction types M-V 6-5
ERROR - ALL SLAMS RECORDS NOT VALID
Transaction types M-V 6-5
ERROR - ATTEMPT TO ADD DATA PRIOR TO OLDEST MONITOR DATE
Transaction types 1-3 7-4
Transaction types 8 and 9 9-4
ERROR - ATTEMPT TO ADD DATA PRIOR TO OLDEST RO-EFFECTIVE-DATE
Transaction types 8 and 9 9-4
ERROR - ATTEMPT TO ADD DATA THAT EXISTS IN THE DATABASE
Transaction type 4 8-17
Transaction type Z 8-10
Transaction types 1-3 7-5
Transaction types 8 and 9 9-4
ERROR - ATTEMPT TO ADD MONITOR DATA FOR AN EXISTING MONITOR
Transaction types Fl - F5 5-8
ERROR - ATTEMPT TO ADD MONITOR FOR NON-EXISTENT SITE
Transaction types Fl - F5 5-3
ERROR - ATTEMPT TO ADD SITE DATA FOR AN EXISTING SITE
Transaction types Al - A7 4-3
ERROR - ATTEMPT TO ADD SITE WITHOUT ADDING MONITOR
Transaction types Al - A7 4-3
ERROR - ATTEMPT TO ADD SLAMS DATA FOR AN EXISTING SLAMS
Transaction types M-V 6-5
ERROR - ATTEMPT TO CHANGE DATA THAT DOES NOT EXIST
Transaction type 4 8-17
Transaction type Z 8-10
Transaction types 1-3 7-5
Transaction types 8 and 9 9-4
ERROR - ATTEMPT TO CHANGE MONITOR DATA THAT DOES NOT EXIST
Transaction types Fl - F5 5-8
Error Messages
A-2
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - ATTEMPT TO CHANGE SITE DATA THAT DOES NOT EXIST
Transaction types Al - A7 4-3
ERROR - ATTEMPT TO CHANGE SLAMS DATA THAT DOES NOT EXIST
Transaction types M - V 6-5
ERROR - ATTEMPT TO DELETE DATA THAT DOES NOT EXIST
Transaction type 4 8-17
Transaction type Z 8-10
Transaction types 1-3 7-5
Transaction types 8 and 9 9-4
ERROR - ATTEMPT TO DELETE LAST MONITOR WITHOUT DELETING THE SITE
Transaction types Fl - F5 5-3
ERROR - ATTEMPT TO DELETE MONITOR DATA THAT DOES NOT EXIST
Transaction types Fl - F5 5-8
ERROR - ATTEMPT TO DELETE MONITOR WITHOUT DELETING ALL RAW DATA
Transaction types Fl - F5 5-3
ERROR - ATTEMPT TO DELETE MONITOR WITHOUT DELETING ALL SLAMS DATA
Transaction types Fl - F5 5-3
ERROR - ATTEMPT TO DELETE SITE DATA THAT DOES NOT EXIST
Transaction types Al - A7 4-3
ERROR - ATTEMPT TO DELETE SITE WITHOUT DELETING ALL MONITORS
Transaction types Al - A7 4-3
ERROR - ATTEMPT TO DELETE SLAMS DATA THAT DOES NOT EXIST
Transaction types M-V 6-5
ERROR - AUDIT-CLASS CANNOT BE BLANK
Transaction type 9 9-37
ERROR - BAD VALIDITY-FLAG FOR PARAMETER
Transaction type 1 7-25
Transaction type 2 7-42
Transaction type 3 7-52
ERROR - BEAM-LENGTH CANNOT BE BLANK
Transaction type A3 4-45
ERROR - BEAM-LENGTH MUST BE BLANK
Transaction type A3 4-45
ERROR - BEGIN-DATE > CURRENT DATE
Transaction type 4 8-19
Transaction type Z 8-13
ERROR - BOTH FIELDS MUST BE VALUED
Transaction type 9 9^1, 9^3, 9-45, 9-47, 9-49, 9-51, 9-53, 9-55, 9-56, 9-58
ERROR - CANNOT ADD A SITE WITHOUT A VALID MONITOR
Transaction types Fl - F5 5-3
ERROR - CANNOT ADD DATA FOR MONITOR BEING DELETED
Transaction type 8 and 9 9-4
Transaction types 1-3 7-5
Transaction types Fl - F5 5-3
Transaction types M-V 6-5
Transaction types Z and 4 8-1
December 1993 A-3 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - CANNOT ADD PM DATA WITHOUT VALID MONITOR
Transaction types Fl - F5 5-3
ERROR - CANNOT ADD SITE WITHOUT STREET INFORMATION
Transaction type A3 4-30
ERROR - CANNOT CHANGE DATE-SITE-TERMINATED TO EARLIER THAN DATE-
SAMPLING-ENDED
Transaction type Al 4-10
ERROR - CANNOT CHANGE MONITOR-TYPE FROM A '9'
Transaction type Fl 5-10
ERROR - CANNOT CHANGE MONITOR-TYPE TO A '9*
Transaction type Fl 5-10
ERROR - CANNOT CHANGE TO NAMS UNTIL ALL REQUIRED FIELDS ARE GIVEN
VALUES
Transaction type Fl 5-11
ERROR - CANNOT CHANGE TO PAMS UNTIL ALL REQUIRED FIELDS ARE GIVEN
VALUES
Transaction type Fl 5-11
ERROR - CANNOT DELETE ACTION-TYPE
Transaction type Fl 5-25
ERROR - CANNOT DELETE ANALYZE-LAB
Transaction type Fl 5-15
ERROR - CANNOT DELETE AQCR
Transaction type A2 4-15
ERROR - CANNOT DELETE AUDIT-CLASS
Transaction type 9 9-37
ERROR - CANNOT DELETE CITY
Transaction type A2 4-14
ERROR - CANNOT DELETE COLLECT-LAB
Transaction type Fl 5-16
ERROR - CANNOT DELETE DATE-SAMPLING-BEG
Transaction type Fl 5-20
ERROR - CANNOT DELETE DATE-SITE-ESTAB
Transaction Al 4-9
ERROR - CANNOT DELETE DATE-TYPE-EFF
Transaction type Fl 5-13
ERROR - CANNOT DELETE DATUM
Transaction type A4 4-63
ERROR - CANNOT DELETE DIR-FROM-MONITOR
Transaction type F2 5-53
Error Messages
A-4
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - CANNOT DELETE DIRECTION-SITE
Transaction type A2 4-27
ERROR - CANNOT DELETE DIST-FROM-INLET
Transaction type F2 5-55
ERROR - CANNOT DELETE DIST-FROM-ROAD
Transaction type F2 5-38
ERROR - CANNOT DELETE DISTANCE-SITE
Transaction type A2 4-26
ERROR - CANNOT DELETE EST-OF-ACCURACY
Transaction type A4 4-65
ERROR - CANNOT DELETE FIRST-EXCEED-COR
Transaction type F3 5-69
ERROR - CANNOT DELETE HT-OF-OBSTRUCT
Transaction type F2 5-57
ERROR - CANNOT DELETE HORIZONTAL DISTANCE
Transaction type F2 5^8
ERROR - CANNOT DELETE LAND-USE
Transaction type A2 4-22
ERROR - CANNOT DELETE LAST STREET INFORMATION
Transaction type A3 4-30
ERROR - CANNOT DELETE LATITUDE
Transaction type A4 4-58
ERROR - CANNOT DELETE LOCAL-STD-SOURCE
Transaction type 9 9-36
ERROR - CANNOT DELETE LOCATION-SETTING
Transaction type A2 4-21
ERROR - CANNOT DELETE LONGITUDE
Transaction type A4 4-60
ERROR - CANNOT DELETE MET-SITE-ID
Transaction type A2 4-25
ERROR - CANNOT'DELETE METH-OF-DETERM
Transaction type A4 4-62
ERROR - CANNOT DELETE MON-STREET-NUMBER
Transaction type F2 5-37
ERROR - CANNOT DELETE MONITOR-TYPE
Transaction type Fl 5-12
ERROR - CANNOT DELETE MONITORING AREA
Transaction type F3 5-60
ERROR - CANNOT DELETE MSA
Transaction type A2 4-16
ERROR - CANNOT DELETE NUM-SCH-SAMP
Transaction type F3 5-63
ERROR - CANNOT DELETE PROBE-HEIGHT
Transaction type F2 5-47
ERROR - CANNOT DELETE PROBE-LOC-CODE
Transaction type F2 5-46
December 1993 A-S Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - CANNOT DELETE REF-METHOD-DATE
Transaction type F2 5-40
ERROR - CANNOT DELETE REF-METHOD-USED
Transaction type F2 5-39
ERROR - CANNOT DELETE REPORT-ORG
Transaction type Fl . . . 5-17
ERROR - CANNOT DELETE REQ-SAMPLING-FREQ
Transaction type F3 5-65
ERROR - CANNOT DELETE RO-EFF-DATE
Transaction type Fl 5-18
ERROR - CANNOT DELETE RSF-EFF-DATE
Transaction type F3 5-66
ERROR - CANNOT DELETE SCALE
Transaction type A4 4-64
ERROR - CANNOT DELETE SEQUENCE-NUMBER
Transaction type A3 4-31
ERROR - CANNOT DELETE SHORT-TERM-DATE
Transaction type F3 5-68
ERROR - CANNOT DELETE SHORT-TERM-SCH
Transaction type F3 5-67
ERROR - CANNOT DELETE SITE-CR-DATE
Transaction type F2 5-42
ERROR - CANNOT DELETE STREET-ADDRESS
Transaction type Al .... 4-8
ERROR - CANNOT DELETE STREET-NUMBER
Transaction type A3 4-32
ERROR - CANNOT DELETE SUPPORT-AGENCY
Transaction type Al 4-7
ERROR - CANNOT DELETE SURROGATE-FLAG
Transaction type F3 5-62
ERROR - CANNOT DELETE URBAN-AREA
Transaction type Fl 5-32
ERROR - CANNOT DELETE UTM-EASTING
Transaction type A4 4-54
ERROR - CANNOT DELETE UTM-NORTHING
Transaction type A4 , 4-56
ERROR - CANNOT DELETE UTM-ZONE
Transaction type A4 4-52
ERROR - CANNOT DELETE VERTICAL DIST
Transaction type F2 5-49
Error Messages
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - CANNOT DELETE WORST-SITE
Transaction type F3 5-61
ERROR - CANNOT MODIFY DATA BEFORE IT IS INSERTED
Transaction types Fl - F5 5-4
ERROR - CANNOT MODIFY DATA FOR MONITOR BEING DELETED
Transaction 8 and 9 9-4
Transaction types 1-3 7-5
Transaction types Fl - F5 5-4
Transaction types M-V 6-6
Transaction types Z and 4 8-1
ERROR - CANNOT MOVE DATE-TYPE-EFF FORWARD UNLESS MONITOR-TYPE
CHANGES
Transaction type Fl 5-13
ERROR - CMSA-REPRESENTED MUST BE BLANK
Transaction type A3 4-41
ERROR - COMP-TYPE CANNOT CHANGE WITHIN A CALENDAR YEAR
Transaction type 3 7-49
ERROR - DATA FOR THIS YEAR IS ARCHIVED
Transaction type 4 8-17
Transaction type Fl 5-13
Transaction type Z 8-10
Transaction types 1-3 7-5
ERROR - DATE-MAX 1-24HR NOT ALLOWED
Transaction type S 6-83
ERROR - DATE-MAX2-24HR NOT ALLOWED
Transaction type S 6-85
ERROR - DATE-SAMP-FREQ CANNOT BE BLANK
Transaction type M 6-22
ERROR - DATE-SAMP-FREQ OUT OF ORDER
Transaction type M 6-22
ERROR - DATE-SITE-ESTAB CANNOT BE BLANK
Transaction type Al 4-9
ERROR - DATE-TYPE-EFF CANNOT BE BLANK
Transaction type Fl 5-13
ERROR - DATE-TYPE-EFF NOT = SAMP-BEGIN
Transaction type Fl 5-14
ERROR - DATUM CANNOT BE BLANK
Transaction type A4 4-63
ERROR - DIR-FROM-MONITOR CANNOT BE BLANK
Transaction type F2 5-53
ERROR - DIR-FROM-MONTTOR MUST BE BLANK
Transaction type F2 5-53
ERROR - DIR-FROM-MONTTOR MUST BE DELETED
Transaction type F2 5-53
ERROR - DIR-TO-TRANSMTT CANNOT BE BLANK
Transaction type A3 4-44
December 1993 A-7 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - DIR-TO-TRANSMTT MUST BE BLANK
Transaction type A3 4-44
ERROR - DIRECTION-SITE CANNOT BE BLANK
Transaction type A3 4-27
ERROR - DIRECTION-SITE MUST BE BLANK
Transaction type A2 4-27
ERROR - DIRECTION-TO-STREET CANNOT BE BLANK
Transaction type A3 4-38
ERROR - DIRECTION-TO-STREET MUST BE BLANK
Transaction type A3 4-38
ERROR - DIST-FROM-INLET CANNOT BE BLANK
Transaction type F2 5-55
ERROR - DIST-FROM-INLET MUST BE BLANK
Transaction type F2 5-55
ERROR - DIST-FROM-ROAD CANNOT BE BLANK
Transaction type F2 5-38
ERROR - DISTANCE-SITE CANNOT BE BLANK
Transaction type A2 4-26
ERROR - DISTANCE-SFTE MUST BE BLANK
Transaction type A2 4-26
ERROR - DUPLICATE ACCURACY VALUES ON THESE RECORDS
Transaction type 9 9-34
ERROR - DUPLICATE DATE-SAMP-FREQ
Transaction type M 6-22
ERROR - DUPLICATE HOURLY VALUES ON THESE RECORDS
Transaction type 1 7-15
ERROR - DUPLICATE OPEN PATH INFORMATION
Transaction type A3 4-42
ERROR - DUPLICATE RECORDS
Transaction type 8 9-17
Transaction types Al - A7 4-3
Transaction types Fl - F5 5-4
Transaction types M-V 6-6
Transaction types Z and 4 8-1
ERROR - DUPLICATE STREET INFORMATION
Transaction type A3 4-32
ERROR - END-DATE < BEGIN-DATE
Transaction type 4 8-21
Transaction type Z 8-14
ERROR - END-DATE > CURRENT DATE
Transaction type 4 8-21
Transaction type Z 8-14
ERROR - EST-OF-ACCURACY CANNOT BE BLANK
Transaction type A4 4-65
Error Messages
A-8
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - EXCEED-3HR NOT ALLOWED
Transaction type P 6-49
ERROR - EXCEED-DATE CANNOT BE BLANK
Transaction type N 6-32
ERROR - EXCEED-DATA CANNOT BE BLANK
Transaction type N 6-30
ERROR - EXCEED-DATA NOT ALLOWED
Transaction type N 6-30
ERROR - EXCEED-DATE CANNOT BE BLANK
Transaction type NT 6-32
ERROR - EXCEED-VALUE CANNOT BE BLANK
Transaction type N 6-31
ERROR - FIRST-EXCEED-COR CANNOT BE BLANK
Transaction type F3 5-69
ERROR - FIRST-EXCEED-COR NOT ALLOWED
Transaction type F3 5-69
ERROR - FREQUENCIES NOT ALLOWED
Transaction type V 6-123
ERROR - FREQUENCY(#) CANNOT BE BLANK
Transaction type V 6-124
ERROR - FREQUENCY(#) IS INVALID
Transaction type V 6-124
ERROR - FREQUENCY(9) NOT ALLOWED
Transaction type V 6-124
ERROR - HIGH PERCENT DIFFERENCE
Transaction type 8 9-20, 9-23, 9,26, 9-28, 9-30, 9-32
Transaction type 9 9^1, 9-43, 9-45, 9-47, 9^9, 9-51, 9-53, 9-55
ERROR - HIGH SAMPLE-VALUE
Transaction type 1 7-23
Transaction type 2 7-41
Transaction type 8 9-20, 9-23, 9-26, 9-28, 9-30, 9-32
ERROR - HORIZONTAL-DIST MUST BE NUMERIC
Transaction type F2 5-48
ERROR - HT-OF-OBSTRUCT CANNOT BE BLANK
Transaction type F2 5-57
ERROR - HT-OF-OBSTRUCT MUST BE BLANK
Transaction type F2 5-57
ERROR - INDICATED-COL-MON1 MUST BE NUMERIC
Transaction type 8 9-23
ERROR - INDICATED-COL-MON2 MUST BE BLANK
Transaction type 8 9-26
ERROR - INDICATED-COL-MON3 MUST BE BLANK
Transaction type 8 9-28
ERROR - INDICATED-COL-MON4 MUST BE BLANK
Transaction type 8 9-30
December 1993 A-9 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - INDICATED-COL-MON5 MUST BE BLANK
Transaction type 8 9-32
ERROR - INTERVAL CANNOT CHANGE WITHIN A CALENDAR YEAR
Transaction types 1-3 7-10
Transaction types 8 and 9 9-10
ERROR - INTERVAL CODES DO NOT MATCH ON SLAMS RECORDS
Transaction type P 6-35
Transaction type R 6-55
Transaction type S 6-72
Transaction type T 6-90
Transaction type V 6-119
ERROR - INVALID ACTION CODE
All transaction types 3-6
ERROR - INVALID ACTION-TYPE
Transaction type Fl 5-25
ERROR - INVALID ACTION-TYPE-REASON
Transaction type Fl 5-26
ERROR - INVALID ACTUAL-DESIGNATED
Transaction type 8 9-21
ERROR - INVALID ACTUAL-LEVEL-1
Transaction type 9 9-41
ERROR - INVALID ACTUAL-LEVEL-2
Transaction type 9 9-45
ERROR - INVALID ACTUAL-LEVEL-3
Transaction type 9 9-49
ERROR - INVALID ACTUAL-LEVELS
Transaction type 9 9-53
ERROR - INVALID ACTUAL-LEVEL-5
Transaction type 9 9-56
ERROR - INVALID ADD-SAMP-DAYS
Transaction type M 6-21
ERROR - INVALID AIR-BASIN
Transaction type A2 4-17
ERROR - INVALID ANALYZE-LAB
Transaction type Fl 5-15
ERROR - INVALID AQCR
Transaction type A2 4-15
ERROR - INVALID ARTTH-MEAN
Transaction type M 6-16
Transaction type P 6-51
Transaction type S 6-86
ERROR - INVALID ARTTH-MEAN-PB-QTR
Transaction type U 6-115
Error Messages
A-10
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - INVALID AUDIT-CLASS
Transaction type 9 9-37
ERROR - INVALID AUDIT-DATE
Transaction type Fl 5-23
ERROR - INVALID BEAM-LENGTH
Transaction type A3 4-45
ERROR - INVALID BEGIN-DATE
Transaction type 4 8-19
Transaction type Z 8-13
ERROR - INVALID BEGIN-DAY
Transaction type 4 8-19
ERROR - INVALID BEGIN-MONTH
Transaction type 4 8-19
Transaction type Z 8-13
ERROR - INVALID BEGIN-YEAR
Transaction type 4 8-19
Transaction type Z 8-13
ERROR - INVALID CITY
Transaction type A2 4-14
ERROR - INVALID CMSA
Transaction type A3 4-41
ERROR - INVALID CNT-SAMPLES
Transaction type 3 7-48
ERROR - INVALID COLLECT-LAB
Transaction type Fi 5-16
ERROR - INVALID COMP-TYPE
Transaction type 3 7-49
ERROR - INVALID COMPASS-SECTOR
Transaction type A2 4-19
ERROR - INVALID COUNTY CODE
All transaction types 3-8
ERROR - INVALID DATE-MAX 1-24HR
Transaction type P 6-42
Transaction type S 6-83
ERROR - INVALID DATE-MAX2-24HR
Transaction type P 6-44
Transaction type S .' 6-85
ERROR - INVALID DATE-SAMP-FREQ
Transaction type M 6-22
ERROR - INVALID DATE-SAMPLING-BEGAN
Transaction type Fl 5-20
ERROR - INVALID DATE-SAMPLING-ENDED
Transaction type Fl 5-21
ERROR - INVALID DATE-SITE-CRITERIA-MET
Transaction type F2 5-42
December 1993 A-ll Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - INVALID DATE-SITE-ESTAB
Transaction type Al 4-9
ERROR - INVALID DATE-SITE-TERM
Transaction type Al 4-10
ERROR - INVALID DATE-TYPE-EFFECTTVE
Transaction type Fl 5-14
ERROR - INVALID DATUM
Transaction type A4 4-63
ERROR - INVALID DAY
Transaction type 1 7-18
Transaction type 2 7-36
Transaction types 8 and 9 9-15
ERROR - INVALID DECIMAL-POSITION
Transaction type 1 7-21
Transaction type 2 7-39
Transaction type 3 7-50
Transaction type 8 9-18
Transaction type 9 9-39
Transaction type M 6-15
Transaction type N 6-29
Transaction type P 6-40
Transaction type R 6-59
Transaction type S 6-77
Transaction type T 6-94
Transaction type U 6-112
Transaction type Z 8-15
ERROR - INVALID DIFFERENCE-GMT
Transaction type A2 4-23
ERROR - INVALID DIR-FROM-MONITOR
Transaction type F2 5-54
ERROR - INVALID DIR-TO-TRANSMIT
Transaction type A3 4-44
ERROR - INVALID DIRECTION-SITE
Transaction type A2 4-27
ERROR - INVALID DIRECTION-TO-STREET
Transaction type A3 4-38
ERROR - INVALID DIST-FROM-INLET
Transaction type F2 5-55
ERROR - INVALID DIST-FROM-ROAD
Transaction type F2 5-38
ERROR - INVALID DISTANCE-CITY
Transaction type A2 4-20
ERROR - INVALID DISTANCE-SITE
Transaction type A2 4-26
Error Messages
A-12
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - INVALID DOMINANT-SOURCE
Transaction type Fl 5-27
ERROR - INVALID ELEVATJON-MSL
Transaction type A2 4-18
ERROR - INVALID END-DATE
Transaction type 4 8-21
Transaction type Z 8-14
ERROR - INVALID END-DAY
Transaction type 4 8-21
ERROR - INVALID END-MONTH
Transaction type 4 8-21
Transaction type Z 8-14
ERROR - INVALID END-YEAR
Transaction type 4 8-21
Transaction type Z 8-14
ERROR - INVALID EST-OF-ACCURACY
Transaction type A4 4-65
ERROR - INVALID EXCEED-1HR
Transaction type R 6-68
Transaction type T 6-104
ERROR - INVALID EXCEED-24HR
Transaction type P 6-50
ERROR - INVALID EXCEED-3HR
Transaction type P 6-49
ERROR - INVALID EXCEED-8HR
Transaction type R 6-69
ERROR - INVALID EXCEED-DATE
Transaction type N 6-32
ERROR - INVALID EXCEED-OCCUR
Transaction type N 6-28
ERROR - INVALID EXCEED-VALUE
Transaction type N 6-31
ERROR - INVALID EXCEPT-DATA-FLAG
Transaction type V 6-125
ERROR - INVALID FIRST-EXCEED-COR
Transaction type F3 5-69
ERROR - INVALID HORIZONTAL-DIST
Transaction type F2 5-48
ERROR - INVALID HQ-EVAL-DATE
Transaction type Al 4-11
ERROR - INVALID HT-OF-OBSTRUCT
Transaction type F2 5-57
ERROR - INVALID INDICATED-COLLOCATED-MON1
Transaction type 8 9-24
ERROR - INVALID'INDICATED-COLLOCATED-MON2
Transaction type 8 9-26
December 1993 A-13 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - INVALID INDICATED-COLLOCATED-MON3
Transaction type 8 9-28
ERROR - INVALID INDICATED-COLLOCATED-MON4
Transaction type 8 9-30
ERROR - INVALID INDICATED-COLLOCATED-MON5
Transaction type 8 9-32
ERROR - INVALID INDICATED-LEVEL-1
Transaction type 9 9-43
ERROR - INVALID INDICATED-LEVEL-2
Transaction type 9 9-47
ERROR - INVALID INDICATED-LEVEL-3
Transaction type 9 9-51
ERROR - INVALID INDICATED-LEVEL-4
Transaction type 9 9-55
ERROR - INVALID INDICATED-LEVEL-5
Transaction type 9 9-58
ERROR - INVALID INTERVAL
Transaction type M 6-12
Transaction type N 6-25
Transaction type P 6-35
Transaction type R 6-55
Transaction type S 6-72
Transaction type T 6-90
Transaction type U 6-107
Transaction type V 6-119
Transaction types 1-3 7-10
Transaction types 8 and 9 9-10
Transaction types Z and 4 8-7
ERROR - INVALID LAND-USE
Transaction type A2 4-22
ERROR - INVALID LAND-USE-PATH
Transaction type A3 4-50
ERROR - INVALID LATITUDE
Transaction type A4 4-59
ERROR - INVALID LOCAL-STD-SOURCE
Transaction type 9 9-36
ERROR - INVALID LOCATION-SETTING
Transaction type A2 4-21
ERROR - INVALID LONGITUDE
Transaction type A4 4-61
ERROR - INVALID MAX-BEAM-HEIGHT
Transaction type A3 4-49
Error Messages
A-14
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - INVALID MAX1-1HR
Transaction type R 6-60
Transaction type S 6-78
Transaction type T 6-96
ERROR - INVALID MAX1-24HR
Transaction type P 6-41
Transaction type S 6-82
ERROR - INVALID MAX1-3HR
Transaction type P 6-45
ERROR - INVALID MAX*1-8HR
Transaction type R 6-64
ERROR - INVALID MAX2-1HR
Transaction type R 6-62
Transaction type S 6-80
Transaction type T 6-98
ERROR - INVALID MAX2-3HR
Transaction type P 6-47
ERROR - INVALID MAX2-8HR
Transaction type R 6-66
ERROR - INVALID MAX2-24HR
Transaction type P 6-43
Transaction type S 6-84
ERROR - INVALID MAX3-1HR
Transaction type T 6-100
ERROR - INVALID MAX4-1HR
Transaction type T 6-102
ERROR - INVALID MEASUREMENT-SCALE
Transaction type Fl 5-28
ERROR - INVALID MET-SITE-ID
Transaction type A2 . 4-25
ERROR - INVALID METHOD
Transaction type U 6-110
Transaction type V 6-121
Transaction types 1-3 7-12
Transaction types 8 and 9 9-12
Transaction types Z and 4 8-9
ERROR - INVALID METHOD FOR STATE
Transaction type U 6-110
Transaction type V 6-121
Transaction types 1-3 7-12
Transaction types 8 and 9 9-12
Transaction types Z and 4 8-9
ERROR - INVALID METHOD-OF-DETERM
Transaction type A4 4-62
December 1993 A-15 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - INVALID MIN-BEAM-HEIGHT
Transaction type A3 4-48
ERROR - INVALID MIN-DETECTABLE-VALUE
Transaction type Z 8-16
ERROR - INVALID MONITOR STREET NUMBER
Transaction type F2 5-37
ERROR - INVALID MONITOR-ID
Transaction types 1-3 7-9
Transaction types 8 and 9 9-9
Transaction types M - V 6-9
Transaction types Z and 4 8-6
ERROR - INVALID MONITOR-PATH-NUMBER
Transaction type Fl 5-34
ERROR - INVALID MONITOR-TYPE
Transaction type Fl 5-12
ERROR - INVALID MONITOR-TYPE-OBJECTIVE
Transaction type Fl 5-29
ERROR - INVALID MONITORING AREA CODE
Transaction type F3 5-60
ERROR - INVALID MONTH
Transaction type 1 7-17
Transaction type 2 7-35
Transaction types 8 and 9 9-14
ERROR - INVALID MSA
Transaction type A2 4-16
ERROR - INVALID MSA-REPRESENTED
Transaction type A3 4-40
ERROR - INVALID NONATTAINMENT AREA
Transaction type Fl 5-30
ERROR - INVALID NULL SAMPLE-VALUE
Transaction type 1 7-24
Transaction type 2 7-41
ERROR - INVALID NUM-PB-SAMP-QTR
Transaction type U 6-114
ERROR - INVALID NUM-SCH-SAMP
Transaction type F3 5-63
ERROR - INVALID OBSER-1HR
Transaction type P 6-38
Transaction type R 6-58
Transaction type S 6-75
Transaction type T 6-93
Error Messages
A-16
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - INVALID OBSER-24HR
Transaction type M 6-20
Transaction type P 6-39
Transaction type S 6-76
ERROR - INVALID OPEN-PATH-NUMBER
Transaction type A3 4-42, 4-43
ERROR - INVALID PAMS REQ SAMPLING FREQUENCY
Transaction type Fl 5-33
ERROR - INVALID PARAMETER CODE
Transaction types 1-3 7-7
Transaction types 8 and 9 9-7
Transaction types Fl - F5 5-6
Transaction types M - V 6-7
Transaction types Z and 4 8-4
ERROR - INVALID PERIOD-CODE
Transaction type 3 7-47
ERROR - INVALID POC CODE
Transaction types 1-3 7-8
Transaction types 8 and 9 9-8
Transaction types Fl - F5 5-7
Transaction types M - V 6-8
Transaction types Z and 4 8-5
ERROR - INVALID POLL-INT-METH-UNITS
Transaction types 1-3 7-11, 7-12
Transaction types 8 and 9 9-11, 9-12
Transaction types Z and 4 8-8, 8-9
ERROR - INVALID PROBE-HEIGHT
Transaction type F2 5-47
ERROR - INVALID PROBE-LOC-CODE
Transaction type F2 5-46
ERROR - INVALID PROJECT-CLASS
Transaction type Fl 5-24
ERROR - INVALID QA-EFFECTIVE-DATE
Transaction type F2 5-44
ERROR - INVALID QA-PLAN
Transaction type F2 5-43
ERROR - INVALID REASON-CODE
Transaction type 4 8-23
ERROR - INVALID RECEIVER-HEIGHT
Transaction type A3 4-47
ERROR - INVALID REF-METHOD-USED
Transaction type F2 5-39
ERROR - INVALID REF-METHOD-USED-DATE
Transaction type F2 5-40
December 1993 A-17 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - INVALID REGIONAL-EVAL-DATE
Transaction type Al 4-12
ERROR - INVALID REPORT-ORG
Transaction type Fl 5-17
ERROR - INVALID REQ-SAMPLING-FREQ CODE
Transaction type F3 5-65
ERROR - INVALID RO-EFF-DATE
Transaction type Fl 5-18
ERROR - INVALID RSF-EFF-DATE
Transaction type F3 5-66
ERROR - INVALID SAMPLE-FREQUENCY
Transaction type 2 7-38
ERROR - INVALID SAMPLE-VALUE
Transaction type 1 7-24
Transaction type 2 7-41
Transaction type 3 7-51
ERROR - INVALID SAMPLING-FREQ CODE
Transaction type M 6-19
ERROR - INVALID SCALE
Transaction type A4 4-64
ERROR - INVALID SEQUENCE-NUMBER
Transaction type A3 4-31
ERROR - INVALID SHORT-TERM-DATE
Transaction type F3 5-68
ERROR - INVALID SHORT-TERM-SCH
Transaction type F3 5-67
ERROR - INVALID SITE CODE
All transaction types 3-9
ERROR - INVALID SITE-CRITERIA-MET
Transaction type F2 5-41
ERROR - INVALID SITE-LOCATION-TYPE
Transaction type A3 4-39
ERROR - INVALID START-HOUR
Transaction type 1 7-19
Transaction type 2 7-37
ERROR - INVALID STATE CODE
All transaction types 3-7
ERROR - INVALID STREET-NUMBER
Transaction type A3 4-32, 4-33
Error Messages
A-18
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - INVALID SUM-CRITERIA
Transaction type M 6-17
Transaction t>pe P 6-52
Transaction type S 6-87
Transaction type U 6-116
ERROR - INVALID SUPPORT-AGENCY
Transaction type Al 4-7
ERROR - INVALID SURROGATE-FLAG
Transaction type F3 5-62
ERROR - INVALID TIME-MAX1-1HR
Transaction type R 6-61
Transaction type S 6-79
Transaction type T 6-97
ERROR - INVALID TIME-MAX 1-3HR
Transaction type P 6-46
ERROR - INVALID TIME-MAX 1-8HR
Transaction type R 6-65
ERROR - INVALID TIME-MAX2-1HR
Transaction type R 6-63
Transaction type S 6-81
Transaction type T 6-99
ERROR - INVALID TIME-MAX2-3HR
Transaction type P 6-48
ERROR - INVALID TIME-MAX2-8HR
Transaction type R 6-67
ERROR - INVALID TIME-MAX3-1HR
Transaction type T 6-101
ERROR - INVALID TIME-MAX4-1HR
Transaction type T 6-103
ERROR - INVALID TOTAL FREQUENCIES ON SLAMS RECORDS
Transaction type V 6-124
ERROR - INVALID TRAFFIC-FLOW
Transaction type A3 4-36
ERROR - INVALID TRAFFIC-YEAR
Transaction type A3 4-37
ERROR - INVALID TRANSACTION-ID
All transaction types 3-3
ERROR - INVALID TRANSACTION-TYPE
All transaction types 3-3
ERROR - INVALID TRANSMTT-HEIGHT
Transaction type A3 4-46
ERROR - INVALID TYPE-AUDIT
Transaction type 9 9-35
December 1993 A-19 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - INVALID TYPE-MET-SITE
Transaction type A2 4-24
ERROR - INVALID TYPE-OBSTRUCTION
Transaction type F2 5-52
ERROR - INVALID TYPE-ROAD
Transaction type A3 4-35
ERROR - INVALID UNITS
Transaction type M 6-13
Transaction type N 6-26
Transaction type P 6-36
Transaction type R 6-56
Transaction type S 6-73
Transaction type T 6-91
Transaction type U 6-108
Transaction types 1-3 7-11
Transaction types 8 and 9 9-11
Transaction types Z and 4 8-8
ERROR - INVALID UNRST-AIR-FLOW
Transaction type F2 5-50
ERROR - INVALID URBAN-AREA
Transaction type Fl 5-32
ERROR - INVALID UTM-EASTING
Transaction type A4 4-54
ERROR - INVALID UTM-NORTHING
Transaction type A4 4-56
ERROR - INVALID UTM-ZONE
Transaction type A4 4-52
ERROR - INVALID VALIDITY-FLAG
Transaction type 1 7-25
Transaction type 2 7-42
Transaction type 3 7-52
ERROR - INVALID VERTICAL-DISTANCE
Transaction type F2 5-49
ERROR - INVALID WORST-SITE CODE
Transaction type F3 5-61
Error Messages
A-20
December 1993
-------
o
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - INVALID YEAR
Transaction type M 6-14
Transaction type N 6-27
Transaction type P 6-37
Transaction type R 6-57
Transaction type S 6-74
Transaction type T 6-92
Transaction type U 6-109
Transaction type V 6-120
Transaction types f-3 7-13
Transaction types 8 and 9 9-13
ERROR - INVALID ZERO-SPAN
Transaction type 9 9-60
ERROR - LAND-USE-PATH CANNOT BE BLANK
Transaction type A3 4-50
ERROR - LAND-USE-PATH MUST BE BLANK
Transaction type A3 4-50
ERROR - LAT/LONG AND UTM DATA BLANK
Transaction type A4 4-51
ERROR - LAT/LONG INVALID WITH UTM DATA
Transaction type A4 4-53, 4-55, 4-57, 4-59, 4-61
ERROR - LATITUDE CANNOT BE BLANK
Transaction type A4 4-59
ERROR - LATITUDE OUTSIDE OF COUNTY
Transaction type A4 . 4-59
ERROR - LATITUDE OUTSIDE OF STATE
Transaction type A4 4-59
ERROR - LOG CANNOT BE BLANK
Transaction type A5 4-66
ERROR - LOCAL-STD-SOURCE CANNOT BE BLANK
Transaction type 9 9-36
ERROR - LONGITUDE CANNOT BE BLANK
Transaction type A4 4-61
ERROR - LONGITUDE OUTSIDE OF COUNTY
Transaction type A4 4-61
ERROR - LONGITUDE OUTSIDE OF STATE
Transaction type A4 4-61
ERROR - MAX-BEAM-HEIGHT CANNOT BE BLANK
Transaction type A3 4-49
ERROR - MAX-BEAM-HEIGHT MUST BE BLANK
Transaction type A3 4-49
ERROR - MAX1-1HR NOT ALLOWED
Transaction type S 6-78
December 1993 A-21 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - MAXI-24HR NOT ALLOWED
Transaction type S 6-82
ERROR - MAX1-3HR NOT ALLOWED
Transaction type P 6-45
ERROR - MAX2-1HR > MAX1-1HR
Transaction type R 6-62
Transaction type S 6-80
Transaction type T 6-98
ERROR - MAX2-3HR > MAX1-3HR
Transaction type P 6-47
ERROR - MAX2-3HR NOT ALLOWED
Transaction type P 6-47
ERROR - MAX2-8HR > MAX1-8HR
Transaction type R 6-66
ERROR - MAX2-1HR NOT ALLOWED
Transaction type S 6-80
ERROR - MAX2-24HR > MAX1-24HR
Transaction type P 6-43
Transaction type S 6-84
ERROR - MAX2-24HR NOT ALLOWED
Transaction type S 6-84
ERROR - MAX3-1HR > MAX2-1HR
Transaction type T 6-100
ERROR - MAX4-1HR > MAX3-1HR
Transaction type T 6-102
ERROR - MET-SITE-ID CANNOT BE BLANK
Transaction type A2 4-25
ERROR - MET-SITE-ID MUST BE BLANK
Transaction type A2 4-25
ERROR - METHOD-OF-DETERM CANNOT BE BLANK
Transaction type A4 4-62
ERROR - METHODS MUST BE CONSECUTIVE
Transaction type U 6-110
Transaction type V 6-121
ERROR - MIN-BEAM-HEIGHT CANNOT BE BLANK
Transaction type A3 4-48
ERROR - MIN-BEAM-HEIGHT MUST BE BLANK
Transaction type A3 4-48
ERROR - MISSING REQUIRED MONITOR INFORMATION
Transaction type Fl 5-9
Transaction types F1-F5 5-4
ERROR - MONITOR DATA EXISTS FOR THIS OPEN PATH NUMBER
Transaction type A3 4-42
Error Messages
A-22
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - MONITOR INACTIVE FOR BEGIN-DATE
Transaction type 4 8-19
ERROR - MONITOR INACTIVE FOR END-DATE
Transaction type 4 8-21
ERROR - MONITOR INACTIVE FOR THIS DATE
Transaction type 1 7-17, 7-18
Transaction type 2 7-35, 7-36
Transaction type 3 7-47
Transaction type 4 8-20, 8-22
Transaction type Z 8-13, 8-14
Transaction types 1-3 7-13
Transaction types 8 and 9 9-13, 9-14, 9-15
ERROR - MONITOR INVALID DUE TO DUPLICATE "F3M
Transaction types F1-F5 5-4
ERROR - MONITOR WAS NOT NAMS OR SLAMS FOR THIS YEAR
Transaction types M-V 6-6
ERROR - MONITOR-COMMENT CANNOT BE BLANK
Transaction type F4 5-70
Transaction type F5 5-71
ERROR - MONITORING AREA CANNOT BE BLANK
Transaction type F3 5-60
ERROR - MONITORING AREA NOT ALLOWED
Transaction type F3 5-60
ERROR - MSA-REP INVALID WITH CMSA REP
Transaction type A3 4-40, 4^41
ERROR - MSA-REPRESENTED MUST BE BLANK
Transaction type A3 4-40
ERROR - MUST DELETE ALL OBSTRUCTION DATA
Transaction type F2 5-50
ERROR - MUST DELETE ALL OPEN-PATH DATA
Transaction type A3 4-43
ERROR - MUST DELETE ALL STREET DATA
Transaction type A3 4-33
ERROR - MUST DELETE DIST-FROM-INLET
Transaction type F2 5-56
ERROR - MUST DELETE HT-OF-OBSTRUCT
Transaction type F2 '. 5-58
ERROR - MUST DELETE MSA DATA
Transaction type A3 4-39
ERROR - MUST DELETE OR MODIFY DATA PAIR
Transaction type 8 9-21, 9-24
Transaction type 9 9-41, 9-43, 9-45, 9-47, 9-49, 9-51, 9-53, 9-55, 9-57, 9-59
ERROR - NON-ADBA SCREENING FILE
Transaction type Fl 5-25, 5-26
December 1993 A-23 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - NONATTAINMENT AREA MUST BE BLANK
Transaction type Fl 5-30
ERROR - NOT ALLOWED 2 CARDS WITH THESE START HOURS
Transaction type 1 7-19
ERROR - NOT ALLOWED TWO START HOURS FOR THIS INTERVAL
Transaction type 1 7-19
ERROR - NOT AUTHORIZED FOR THIS MONITOR
Transaction types 1-3 7-6
Transaction types 8 and 9 9-5
Transaction types Fl - F5 5-4
Transaction types M-V 6-6
Transaction types Z and 4 8-2
ERROR - NUM-SCH-SAMP CANNOT BE BLANK
Transaction type F3 5-64
ERROR - NUM-SCH-SAMP DOES NOT EXIST
Transaction type F3 5-64
ERROR - OBSER-1HR NOT ALLOWED
Transaction type P 6-38
Transaction type S 6-75
ERROR - OBSER-24HR CANNOT BE BLANK
Transaction type M 6-20
ERROR - OBSER-24HR NOT ALLOWED
Transaction type P 6-39
Transaction type S 6-76
ERROR - OBSTRUCTION DATA CANNOT BE BLANK
Transaction type F2 5-50, 5-52
ERROR - ONLY ADBA CAN CHANGE DATE-TYPE-EFFECTIVE OF NAMS MONITOR
Transaction type Fl 5-14
ERROR - ONLY ADBA CAN CHANGE DATE-TYPE-EFFECTIVE OF PAMS MONITOR
Transaction type Fl 5-14
ERROR - ONLY ADBA CAN CHANGE STATUS OF A MONITOR FROM NAMS
Transaction type Fl 5-12
ERROR - ONLY ADBA CAN CHANGE STATUS OF A MONITOR FROM PAMS
Transaction type Fl 5-12
ERROR - ONLY ADBA CAN CHANGE STATUS OF A MONITOR TO NAMS
Transaction type Fl 5-12
ERROR - ONLY ADBA CAN CHANGE STATUS OF A MONITOR TO PAMS
Transaction type Fl 5-12
ERROR - OPEN PATH NUMBER DOES NOT EXIST
Transaction type Fl 5-34
ERROR - PA DATA EXISTS PRIOR TO THE RO-EFFECTIVE-DATE
Transaction type Fl 5-18
Error Messages
A-24
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - PAMS REQ SAMP NOT ALLOWED
Transaction type Fl 5-33
ERROR - PREVIOUS SLAMS CARD MISSING OR INVALID
Transaction types M-V 6-6
ERROR - PROBE HEIGHT CANNOT BE BLANK
Transaction type F2 5-47
ERROR - PROBE-LOC-CODE CANNOT BE BLANK
Transaction type F2 5-46
ERROR - QA-EFFECTIVE-DATE MUST BE BLANK
Transaction type F2 5-47
ERROR - QA-EFFECTIVE-DATE MUST BE DELETED
Transaction type F2 5-44
ERROR - QA-EFFECTIVE-DATE MUST BE NUMERIC
Transaction type F2 5-44
ERROR - QA-PLAN MUST BE "Y" OR "C"
Transaction type F2 5-43
ERROR - QA-PLAN MUST BE DELETED
Transaction type F2 5-43
ERROR - RAW DATA EXISTS OUT OF THE SAMPLING DATE RANGE
Transaction type Fl 5-20, 5-21
ERROR - RECEIVER-HEIGHT CANNOT BE BLANK
Transaction type A3 4-47
ERROR - RECEIVER-HEIGHT MUST BE BLANK
Transaction type A3 4-47
ERROR - REF-METHOD-DATE CANNOT BE BLANK
Transaction type F2 5-40
ERROR - REF-METHOD-DATE NOT ALLOWED
Transaction type F2 5-40
ERROR - REQ-SAMPLING-FREQ CANNOT BE BLANK
Transaction type F3 5-65
ERROR - REQ-SAMPLING-FREQ MUST BE BLANK
Transaction type F3 5-65
ERROR - REQUIRED "Al" TRANSACTION MISSING
Transaction type Al 4-6
ERROR - REQUIRED "A2" TRANSACTION MISSING
Transaction type A2 4-13
ERROR - REQUIRED 'A3" TRANSACTION MISSING
Transaction type A3 4-30
ERROR - REQUIRED "A4" TRANSACTION MISSING
Transaction type A4 4-51
ERROR - REQUIRED "F3" TRANSACTION INVALID
Transaction types Fl - F5 5-4
December 1993 A-25 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - REQUIRED "F3" TRANSACTION MISSING
Transaction types Fl - F5 5-4
ERROR - REQUIRED "V" TRANSACTION MISSING
Transaction types M-V 6-6
ERROR - RO-EFF-DATE CANNOT BE BLANK
Transaction type Fl 5-19
ERROR - RO-EFFECTTVE-DATE NOT VALUED FOR THIS MONITOR
Transaction types 8 and 9 9-5
ERROR - RSF-EFF-DATE CANNOT BE BLANK
Transaction type F3 5-66
ERROR - SAMPLE VALUE MUST BE BLANK
Transaction type 9 9-41, 9-43, 9-49, 9-51, 9,53, 9-55
ERROR - SAMPLING-DATA CANNOT BE BLANK
Transaction type M 6-18
ERROR - SAMPLING-DATA NOT ALLOWED
Transaction type M 6-18
ERROR - SAMPLING-FREQ CANNOT BE BLANK
Transaction type M 6-19
ERROR - SCALE CANNOT BE BLANK
Transaction type A4 4-64
ERROR - SHORT-TERM-DATE CANNOT BE BLANK
Transaction type F3 5-68
ERROR - SHORT-TERM-DATE NOT ALLOWED
Transaction type F3 5-68
ERROR - SHORT-TERM-SCH CANNOT BE BLANK
Transaction type F3 5-67
ERROR - SHORT-TERM-SCH NOT ALLOWED
Transaction type F3 5-67
ERROR - SITE COMMENTS CANNOT BE BLANK
Transaction type A6 . . 4-67
Transaction type A7 . . 4-68
ERROR - SITE WAS TERMINATED - DATE-SAMPLING-ENDED CANNOT BE DELETED
Transaction type Fl 5-21
ERROR - SITE WAS TERMINATED - DATE-SAMPLING-ENDED MUST BE VALUED
Transaction type Fl 5-21
ERROR - SITE-CR-DATE CANNOT BE BLANK
Transaction type F2 5-42
ERROR - SITE-CRITERIA-DATE NOT ALLOWED
Transaction type F2 5-42
ERROR - SITE-LOG INVALID (NO MSA DATA)
Transaction type A3 4-39
ERROR - SLAMS DATA EXISTS FOR OR AFTER DATE-TYPE-EFFECTIVE
Transaction type Fl 5-14
Error Messages
A-26
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
ERROR - START-HOUR NOT ALLOWED
Transaction type 2 7-37
ERROR - STREET NUMBER DOES NOT EXIST
Transaction type F2 5-37
ERROR - STREET-ADDRESS CANNOT BE BLANK
Transaction type Al 4-8
ERROR - STREET-NAME CANNOT BE BLANK
Transaction type A3 4-34
ERROR - STREET-NUMBER CANNOT BE BLANK
Transaction type A3 4-32
ERROR - SUMMARY DATA EXISTS OUT OF THE SAMPLING DATE RANGE
Transaction type Fl 5-20, 5-22
ERROR - SUPPORT-AGENCY CANNOT BE BLANK
Transaction type Al 4-7
ERROR - SURROGATE-FLAG CANNOT BE BLANK
Transaction type F3 5-62
ERROR - SURROGATE-FLAG NOT ALLOWED
Transaction type F3 5-62
ERROR - TIME-MAX1-1HR NOT ALLOWED
Transaction type S 6-79
ERROR - TIME-MAX 1-3HR NOT ALLOWED
Transaction type P 6-46
ERROR - TIME-MAX2-1HR NOT ALLOWED
Transaction type S 6-8 J
ERROR - TIME-MAX2-3HR NOT ALLOWED
Transaction type P 6-48
ERROR - TOO MANY REPORTED VALUES FOR THIS INTERVAL
Transaction type 1 7-24
ERROR - TRAFFIC-FLOW CANNOT BE BLANK
Transaction type A3 4-36
ERROR - TRAFFIC-FLOW MUST BE BLANK
Transaction type A3 4-36
ERROR - TRAFFIC-YEAR CANNOT BE BLANK
Transaction type A3 4-37
ERROR - TRAFFIC-YEAR MUST BE BLANK
Transaction type A3 4-37
ERROR - TRANSMIT-HEIGHT CANNOT BE BLANK
Transaction type A3 4-46
ERROR - TRANSMIT-HEIGHT MUST BE BLANK
Transaction type A3 4-46
ERROR - TYPE-AUDIT CANNOT BE BLANK
Transaction type 9 9-35
ERROR - TYPE-AUDIT CANNOT BE DELETED
Transaction type 9 9-35
December 1993 A-27 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
ERROR - TYPE-ROAD CANNOT BE BLANK
Transaction type A3 4-35
ERROR - TYPE-ROAD MUST BE BLANK
Transaction type A3 4-35
ERROR - UNITS CANNOT CHANGE WITHIN A CALENDAR MONTH
Transaction types 1-3 7-11
Transaction types 8 and 9 9-11
ERROR - UNITS MUST MATCH UNITS ON DATABASE
Transaction types 1-3 7-11
Transaction types 8 and 9 9-11
ERROR - UNRST-AIR-FLOW CANNOT BE BLANK
Transaction type F2 4-50
ERROR - UTM-EASTING CANNOT BE BLANK
Transaction type A4 4-55
ERROR - UTM-EASTING OUTSIDE OF STATE
Transaction type A4 4-55
ERROR - UTM-NORTHING CANNOT BE BLANK
Transaction type A4 4-57
ERROR - UTM-NORTHING OUTSIDE OF STATE
Transaction type A4 4-57
ERROR - UTM-ZONE CANNOT BE BLANK
Transaction type A4 4-53
ERROR - VALIDITY-FLAG NOT ALLOWED
Transaction type 1 7-26
Transaction type 2 7-42
Transaction type 3 7-53
ERROR - WORST-SITE CANNOT BE BLANK
Transaction type F3 5-61
ERROR - VERTICAL-DIST MUST BE NUMERIC
Transaction type F3 5-49
ERROR - WORST-SITE NOT ALLOWED
Transaction type F3 5-61
WARNING - ALL PA DATA MUST BE SUBMITTED FOR DATA BEFORE 1987
Transaction types 8 and 9 9-5
WARNING - CANNOT VERIFY ADD-SAMP-DAYS
Transaction type M 6-21
WARNING - CANNOT VERIFY ANALYZE-LAB
Transaction type Fl 5-15
WARNING - CANNOT VERIFY AQCR
Transaction type A2 4-15
WARNING - CANNOT VERIFY AUDIT-CLASS
Transaction type 9 9-38
Error Messages
A-28
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
WARNING - CANNOT VERIFY CITY
Transaction type A2 4-14
WARNING - CANNOT VERIFY CNT-SAMPLES
Transaction type 3 7-48
WARNING - CANNOT VERIFY COLLECT-LAB
Transaction type Fl 5-16
WARNING - CANNOT VERIFY COUNTY CODE
AH transaction types 3-8
WARNING - CANNOT VERIFY DATE-SAMP-FREQ
Transaction type M 6-22
WARNING - CANNOT VERIFY DIFFERENCE-GMT
Transaction type A2 4-23
WARNING - CANNOT VERIFY EXCEED-DATA
Transaction type N 6-30
WARNING - CANNOT VERIFY EXCEED-DATE
Transaction type N 6-32
WARNING - CANNOT VERIFY EXCEED-OCCUR
Transaction type N 6-28
WARNING - CANNOT VERIFY EXCEED-VALUE
Transaction type N 6-31
WARNING - CANNOT VERIFY FIRST-EXCEED-COR
Transaction type F3 5-69
WARNING - CANNOT VERIFY FREQUENCIES
Transaction type V 6-124
WARNING - CANNOT VERIFY INTERVAL
Transaction type M 6-12
Transaction type N 6-25
WARNING - CANNOT VERIFY LAT/LONG
Transaction type A4 4-59, 4-61
WARNING - CANNOT VERIFY METHOD
Transaction type U 6-111
Transaction type V 6-121
Transaction types 1-3 7-12
Transaction types 8 and 9 9-12
Transaction types Z and 4 8-9
WARNING - CANNOT VERIFY MONITORING AREA
Transaction type F3 * 5-60
WARNING - CANNOT VERIFY MSA
Transaction type A2 4-16
WARNING - CANNOT VERIFY NONATTAINMENT AREA
Transaction type Fl 5-31
WARNING - CANNOT VERIFY OBSER-1HR
Transaction type P 6-38
Transaction type R 6-58
Transaction type S 6-75
December 1993 A-29 Error Messages
-------
Air Quality Data Coding
AIRS User's Guide
Volume AQ2
WARNING - CANNOT VERIFY OBSER-24HR
Transaction type M 6-20
WARNING - CANNOT VERIFY PERIOD-CODE
Transaction type 3 7-47
WARNING - CANNOT VERIFY QA-EFFECT-DATE
Transaction type F2 5-45
WARNING - CANNOT VERIFY REPORT-ORG
Transaction type Fl 5-17
WARNING - CANNOT VERIFY RO-EFF-DATE
Transaction type Fl 5-19
WARNING - CANNOT VERIFY SAMPLE VALUE
Transaction type 8 9-21, 9-24, 9-26, 9-28, 9-30, 9-32
WARNING - CANNOT VERIFY SHORT-TERM-DATE
Transaction type F3 5-68
WARNING - CANNOT VERIFY SHORT-TERM-SCH
Transaction type F3 5-67
WARNING - CANNOT VERIFY START-HOUR
Transaction type 1 7-20
WARNING - CANNOT VERIFY SUPPORT-AGENCY
Transaction type Al 4-7
WARNING - CANNOT VERIFY SURROGATE-FLAG
Transaction type F3 5-62
WARNING - CANNOT VERIFY UNITS
Transaction types 1-3 7-11
Transaction types 8 and 9 9-11
Transaction types Z and 4 8-8
WARNING - CANNOT VERIFY UTM DATA
Transaction type A4 4-53, 4-55, 4-57
WARNING - CANNOT VERIFY VALIDITY-FLAG
Transaction type 1 7-26
Transaction type 2 7-42
Transaction type 3 7-53
WARNING - CANNOT VERIFY WORST-SITE
Transaction type F3 5-61
WARNING - CONCENTRATION OUT OF RANGE
Transaction type 9 9^1, 9-43, 9-*5, 9-47, 9-49, 9-51, 9-53, 9-55
WARNING - DAILY VALUES FAIL SHEWART TEST
Transaction type 2 7-43
WARNING - HOURLY VALUES FAIL GAP TEST
Transaction type 1 7-30
WARNING - HOURLY VALUE FAILS PATTERN TEST
Transaction type 1 7-28
Error Messages
A-30
December 1993
-------
AIRS User's Guide
Volume AQ2 Air Quality Data Coding
WARNING - INSUFFICIENT HOURLY VALUES TO PERFORM GAP TEST
Transaction type 1 7-30
WARNING - METHOD DOES NOT MATCH METHOD ON DATABASE
Transaction type Z 8-11
Transaction types 1-3 7-12
Transaction types 8 and 9 9-12
WARNING - NOT ENOUGH DAILY HISTORICAL VALUES TO RUN SHEW ART TEST
Transaction type 2 7-43
WARNING - SOURCE ORIENTED SO2 FAILED GAP TEST
Transaction type 1 7-30
December 1993 A-31 Error Messages
-------
-------
|