11.07.2014 Views

Central California Ozone Study (CCOS) - Desert Research Institute

Central California Ozone Study (CCOS) - Desert Research Institute

Central California Ozone Study (CCOS) - Desert Research Institute

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>CCOS</strong> Field Operations Plan Version 2: 5/31/00<br />

5.0 DATA MANAGEMENT AND VALIDATION<br />

The <strong>CCOS</strong> database will be compiled, documented, evaluated, and distributed by the<br />

Planning and Technical Support Division (PTSD) of the Air Resources Board (ARB). Common<br />

data management and validation conventions need to be assembled in a consistent and efficient<br />

manner. These conventions are described in this section. Greg O’Brien of the ARB will serve as<br />

the <strong>CCOS</strong> data manager. He will be responsible for establishing and maintaining computerbased<br />

data archives and managing the overall data storage and Level 1A-1B validation activities.<br />

The data manager will interact with the field manager and the program management and provide<br />

feedback to them concerning the status of unresolved data management problems and potential<br />

for resolution. Liz Niccum of T&B Systems will assist the <strong>CCOS</strong> data manager with data<br />

compilation and formatting. Eric Fujita of the <strong>Desert</strong> <strong>Research</strong> <strong>Institute</strong> will assist with Level 2<br />

data validation. This draft version will be updated with more specific conventions and reporting<br />

structures after <strong>CCOS</strong> measurement investigators have provided their suggestions and<br />

recommendations. To the greatest extent possible, <strong>CCOS</strong> field data structures, processing,<br />

validation, and delivery procedures will be consistent with those being established for the<br />

CRPAQS (Watson et al., 1998).<br />

5.1 Data Specifications<br />

Data management conventions and methods for <strong>CCOS</strong> and CRPAQS build on experience<br />

from and development supported by the 1990 San Joaquin Valley Air Quality <strong>Study</strong> (SJVAQS)<br />

(Blumenthal et al., 1993), the 1995 Integrated Monitoring <strong>Study</strong> (IMS-95) (Solomon and<br />

Magliano, 1997), and the 1997 Southern <strong>California</strong> Oxidant <strong>Study</strong> (SCOS-97) (Fujita et al.,<br />

1997). The following specifications are maintained by the data manager and are to be made<br />

available to all project participants via the Internet:<br />

• Monitoring Sites: Each site location for <strong>CCOS</strong> measurements is identified with a<br />

unique alphanumeric site ID accompanied by its name, address, coordinates,<br />

elevation, primary operator, and a summary of measurements taken at the site. The<br />

field manager with a Global Positioning System (GPS), pressure-based altimeter, and<br />

topographical maps verify the coordinates and elevations of each site. Immediate<br />

surroundings are recorded with a digital camera of the area surrounding the site to be<br />

displayed on the CCAQS web site.<br />

• Instruments: The make, model and serial number of instruments used to acquire<br />

measurements at each site is recorded with its threshold, range, expected accuracy<br />

and precision.<br />

• Parameters: Each observed parameter is assigned a unique code that is accompanied<br />

by its definition, units, averaging time, applicable temperature and pressure<br />

adjustments, and data reporting format.<br />

• Data validation flags: Flags specific to each measurement investigator are translated<br />

into a common set of validation flags that are carried with each data point. These are<br />

listed in Section 5.3<br />

Chapter 5: DATA MANAGEMENT 5-1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!