Contract Number GS-35F-4797H 

Task Order # 1518 

TDD 10.02 eBeaches 

Version 2.2.1 

July 21, 2010 

Beach Monitoring Database User Guide 

(For use with WQX) 
Beach Monitoring Database User Guide July 21, 2010 

 iii 

Table of Contents 

Table of Contents ....................................................................................................................... iii

List of Exhibits ............................................................................................................................. v

Revision Log .............................................................................................................................. vi

1 Introduction ........................................................................................................................ 1

1.1 Reference Materials ..................................................................................................... 1

2 Before Submitting Data ...................................................................................................... 2

2.1 NAAS Account .............................................................................................................. 2

2.2 WQX Organization ID ................................................................................................... 2

2.3 Submission Method Selection ....................................................................................... 2

2.4 Table Details ................................................................................................................ 2

3 Entering Data into the Database ......................................................................................... 5

3.1 Special Cases .............................................................................................................. 6

4 Preparing Update/Insert XML Submissions ...................................................................... 10

4.1 Process Overview ....................................................................................................... 10

4.2 Excluding Data from Submissions .............................................................................. 11

5 Preparing Delete XML Submissions ................................................................................. 14

6 Loading XML .................................................................................................................... 15

7 Submitting Files ................................................................................................................ 16

7.1 Preparing the File ....................................................................................................... 16

7.2 The First Submission .................................................................................................. 16

7.3 Submitting Files .......................................................................................................... 16

7.4 Retrieving Submission Results Using Node Client Lite ............................................... 17

8 Appendix A—Microsoft Access ......................................................................................... 19

9 Appendix B—Monitoring Database Change Log............................................................... 21

10 Appendix C—Table Relationships .................................................................................... 23

11 Appendix D—Data Elements ............................................................................................ 24

11.1 Organization ............................................................................................................... 24

11.2 Project ........................................................................................................................ 27

11.3 Monitoring Location .................................................................................................... 28

11.4 Activity ........................................................................................................................ 33

11.5 Result ......................................................................................................................... 43

12 Appendix E—Data Entry Forms ........................................................................................ 53
Beach Monitoring Database User Guide July 21, 2010 

 iv 

12.1 Forms Tab .................................................................................................................. 53

12.2 Return to Main Menu .................................................................................................. 56

12.3 Generate Insert/Update XML ...................................................................................... 58

13 Appendix F—Summary Reports ....................................................................................... 59

13.1 Reports Tab ................................................................................................................ 59

14 Appendix G—CDX Messages .......................................................................................... 61

14.1 WQX Submission Status ............................................................................................ 61

14.2 Transaction History ..................................................................................................... 62
Beach Monitoring Database User Guide July 21, 2010 

 v 

List of Exhibits 

Exhibit 2-1 Other Naming Conventions ....................................................................................... 4

Exhibit 4-1 Generate Insert/Update XML Form.......................................................................... 11

Exhibit 4-2 ORG_PHONE Table ............................................................................................... 12

Exhibit 4-3 Send to EPA Flag Manager ..................................................................................... 13

Exhibit 4-4 Send To EPA Flag Tables ....................................................................................... 13

Exhibit 6-1 Load XML Form and Message ................................................................................ 15

Exhibit 8-1 Beach Monitoring Database .................................................................................... 19

Exhibit 8-2 ORG_PHONE Table ............................................................................................... 19

Exhibit 10-1 Table Relationships ............................................................................................... 23

Exhibit 12-1 Microsoft Access 2000 Forms Tab ........................................................................ 53

Exhibit 12-2 Microsoft Access 2007 Forms Tab ........................................................................ 54

Exhibit 12-3 Microsoft Access 2007 Main Menu ........................................................................ 55

Exhibit 12-4 Microsoft Access 2000 Project Data Entry Screen ................................................. 56

Exhibit 12-5 Microsoft Access 2007 Project Data Entry Screen ................................................. 57

Exhibit 12-6 Microsoft Access 2007 Generate Insert/Update XML Form ................................... 58

Exhibit 13-1 Microsoft Access 2000 Reports Tab ...................................................................... 59

Exhibit 13-2 Microsoft Access 2007 Reports Tab ...................................................................... 60

Exhibit 14-1 WQX Submission Status ....................................................................................... 61

Exhibit 14-2 WQX Submission Status – Failed .......................................................................... 62

Exhibit 14-3 Transaction History ............................................................................................... 62
Beach Monitoring Database User Guide July 21, 2010 

 vi 

Revision Log 

Date Version 

No. 

Description Author Reviewer Review 

Date 

10/1/07 2.0 Final Version Andrew 

Hampton 

 

10/10/07 2.0.1 Added relationship diagram Andrew 

Hampton 

 

10/22/07 2.0.2 Added ID information to the table in section 

2.4.3 

Added Change Log Appendix 

Andrew 

Hampton 

 

11/7/07 2.0.3 Updated Change Log Appendix 

Added Analytical Method Information 

Section 

Andrew 

Hampton 

 

11/8/07 2.0.4 Updated Change Log Appendix Andrew 

Hampton 

 

2/4/08 2.1.0 Updated Change Log Appendix 

Added Load XML Section 

Erik Richards 

 

2/25/08 2.1.1 Updated Change Log Appendix Erik Richards 

 

7/2/08 2.1.2 Updated Change Log Appendix Erik Richards 

 

12/17/08 2.1.3 Updated Change Log Appendix Erik Richards 

 

8/3/09 2.2.0 Updated Change Log Appendix 

Added Appendix E 

Erik Richards 

 

7/21/10 2.2.1 Updated Change Log Appendix 

Updated Appendix E & F 

Added Appendix G 

Erik Richards 

 

 
Beach Monitoring Database User Guide July 21, 2010 

1 

1 Introduction 

The purpose of this document is to give instruction on how the WQX Access Database can be 

used to generate XML submission files for the WQX and how the file should be submitted. A 

working knowledge of the WQX XML Schema is very helpful when working with WQX data, 

and links to documents which detail the WQX XML are provided in the Reference Materials 

Section. If you are looking for more general information about WQX or the Beach Act Grant 

Program, please first visit the links in the Reference Materials section. 

1.1 Reference Materials 

For more information about the BEACH Act Grant Program or if you are new to the BEACH 

Act Grant Program, visit these links: 

 General Beach Program Information - http://www.epa.gov/waterscience/beaches/ 

 Data Users’ Corner - 

http://www.epa.gov/waterscience/beaches/grants/datausers/index.htm. 

The WQX team within the EPA has written several documents which are very useful for 

understanding WQX data and the WQX data submission process. Though these documents are 

more technical in nature, understanding their contents is very beneficial. These documents are 

located at the following URLs: 

 Basic information about WQX - http://www.epa.gov/storet/wqx/index.html

 Document Downloads - http://www.epa.gov/storet/wqx/wqx_downloads.html

 Information on WQX’s Exchange Network presence - 

http://www.exchangenetwork.net/exchanges/water/wqx.htm

One document that is particularly helpful is the WQX XML Training for Beach Monitoring Data 

(http://www.epa.gov/waterscience/beaches/grants/datausers/index.htm). The WQX XML 

Training for Beach Monitoring Data explains the details and business rules about a submission 

file. 

 

Since all WQX submission files will be traveling over the Exchange Network, a basic 

understanding of the Exchange Network is also beneficial. The Network Basics section and 

FAQs section of http://www.exchangenetwork.net/ give a good overview of how the Exchange 

Network works and its purpose. 

 

The underlying technology of the Exchange Network and submission files is XML. To learn 

more about XML, visit http://www.w3schools.com/xml/xml_syntax.asp. 
Beach Monitoring Database User Guide July 21, 2010 

2 

2 Before Submitting Data 

These are the steps that must be taken before a submission can be made. 

2.1 NAAS Account 

A Network Authorization and Authentication Service, or NAAS (pronounced noz), account is 

required to submit files on the Exchange Network. To request a NAAS account, contact your 

states Node Administrator1, or send a request to nodehelpdesk@epacdx.net. 

2.2 WQX Organization ID 

The WQX Organization ID can be created by contacting the STORET help desk by email at 

storet@epa.gov or by phone at 1-800-424-9067. Also, there is a process in place to migrate data 

from STORET to WQX which will enable states to keep the same Organization ID for WQX 

submissions. Contact the help desk for more information about this data migration process. 

2.3 Submission Method Selection 

There are several options available for choosing a method to submit data to the WQX. None of 

these options affect how data is entered into the database or how the submission file is generated. 

The submission method chosen will determine what is done with the submission file after it is 

generated. These options are outlined in a document located here: 

http://www.epa.gov/waterscience/beaches/grants/datausers/index.htm

2.4 Table Details 

This section explains the business rules of the database and gives some helpful tips. For basic 

information about Microsoft Access, see Appendix A – Microsoft Access. 

2.4.1 Foreign Keys 

There are many columns that will be filled out that require a special value which is defined in 

another table. The table and column that contains the special value are called the reference table 

and reference key, respectively. The column that uses the reference key is called a foreign key. 

For example, in the ORG_PHONE table, there is a foreign key column which stores the type of 

phone number, REF_PHONE_TYPE_NAME. Valid types of phone numbers are stored in the 

REF_PHONE_TYPE_NAME column of the REF_PHONE_TYPE_NAME table. At the time of 

this writing, the valid types of phone numbers which are stored in the reference table are Fax, 

Home, Mobile, Office, and Pager. 

2.4.1.1 Foreign Key Naming Conventions 

There are two naming categories for foreign key columns: Ref columns and UID columns 

 

1

 You can find your state’s Node Administrator’s contact information here: http://www.exchangenetwork.net/progress/index.htm 
Beach Monitoring Database User Guide July 21, 2010 

3 

2.4.1.1.1 REF Columns 

Tables that begin with “REF” are reference tables and contain reference keys. The columns that 

begin with “REF” which are not in a “REF” table are foreign keys. 

 

Generally, each foreign key column whose name begins with “REF” references values which are 

stored in an identically named reference table which contains an identically named reference key 

column. The phone type example followed this convention. Two notable exceptions to this 

general rule are time zone information and unit of measure information. Time zone reference 

keys are stored in the REF_TIME_ZONE table and time zone foreign keys have TMZONE in 

their name. Unit of measure reference keys are stored in the REF_MEASUREMENT_UNIT 

table and unit of measure foreign keys have MSUNIT in their name. 

2.4.1.1.2 UID Columns 

Most tables have a column which ends with “UID” which is automatically generated and 

uniquely identifies that row of data. For example, in the ACTIVITY table, each row has a 

unique number in the ACT_UID column. Tables may also have other columns which end in 

“UID” which relate rows of data from different tables. For example, the ACTIVITY table has a 

column named ORG_UID which signifies which organization conducted the Activity. Also, the 

ACTIVITY table has a column named PRJ_UID which signifies which project the activity is 

associated with. To summarize, columns which end with UID are either the unique identifier for 

the row or a foreign key which relates rows from different tables. 

2.4.2 Reference Data Updates 

The date contained within the reference tables2 are subject to change based on requests for 

additions made to the WQX team by the state users. The tables are currently based on the values 

from 9/28/06. Updates to the reference data will be published periodically. 

Using the Node Client Lite, the following steps can be followed to get the current valid domain 

values. 

1. Connect to a node in Node Client Lite 

2. Under “Things I can do”, click “Get Data” 

3. For the Data Flow, select WQX 

4. For the Service, select “WQX.GetDomainValueByElementName_v1.0” 

5. Enter the Element Name 

a. A valid list of elements names is available on page 15 of the WQX XML Training 

Manual. See the Reference Materials for the location of the WQX XML Training 

Manual

6. Click Submit 

7. A results screen will come up and show you where the Result File is stored 

 

2

 Reference tables are tables which begin with “REF”
Beach Monitoring Database User Guide July 21, 2010 

4 

8. Navigate to the result file, and open the result file with Internet Explorer 

2.4.3 Other Naming Conventions 

Exhibit 2-1 Other Naming Conventions 

Abbreviation Description 

CD CD stands for Code. This typically means there is a specific abbreviation 

(code) that is needed for the column. For example, in the ORG_ADDRESS 

table, there is a REF_STATE_CD column. In this case, valid values for this 

column are the two digit state codes (AK, AL, etc.) which are located in the 

REF_STATE_CD column of the REF_STATE_CD table. 

ID All columns that end with ID (e.g. ACT_ID, MLOC_ID, etc) must be unique. 

Whenever a new set of data is submitted with a previously existing ID, the old 

data is overwritten. For example, if an Activity in the 2004 data with an 

ACT_ID of CO123456-01 has been submitted, and a new Activity in the 2005 

data has the same ACT_ID, the activity from the 2004 data will be lost. A 

common naming practice is to combine multiple pieces of data to for an ID. 

For example, the combination of the Station ID, the date, and time of an 

Activity would be a good ACT_ID. 
Beach Monitoring Database User Guide July 21, 2010 

5 

3 Entering Data into the Database 

The order data should be entered into the database is not strictly enforced, but a basic 

understanding of how the XML is generated will help explain how data should be entered. The 

XML generation starts in the ORGANIZATION table and works its way through the tables in 

this order: 

 ORGANIZATION 

o ORG_ELECTRONIC_ADDRESS 

o ORG_PHONE 

o ORG_ADDRESS 

o PROJECT3

 ATTACHED_OBJECT 

o MONITORING_LOCATION 

 MONITORING_LOCATION_ALTERNATE 

 ATTACHED_OBJECT 

o ACTIVITY 

 ACTIVITY_PROJECT 

 ACTIVITY_CONDUCTING_ORG 

 ATTACHED_OBJECT 

 RESULT 

• RESULT_DETECT_QUANT_LIMIT 

• RESULT_LAB_SAMPLE_PREP 

• ATTACHED_OBJECT 

o ACTIVITY_GROUP 

 ACTIVITY_GROUP_DETAIL 

The most important thing to note about this is that data in “child tables” will be ignored unless it 

relates to a row in its “parent table”. For example, any data in the RESULT table will be ignored 

unless it relates to a row in its parent table, ACTIVITY. Also, the row in the ACTIVITY table 

will be ignored unless it relates to a row in its parent table, ORGANIZATION. 

 

3

 Methods of creating Project IDs before WQX resulted in multiple beach names assigned to a single Project ID. To avoid that error using this 

database, verify that all values in the PRJ_ID column of the PROJECT table are unique. 
Beach Monitoring Database User Guide July 21, 2010 

6 

3.1 Special Cases 

Most of the tables and columns are fairly straightforward; however there are some that can be 

confusing. The following sections are descriptions of how to handle the data which is atypical. 

3.1.1 Attached Binary Objects 

Since there can be multiple Attached Binary Objects associated with Results, Projects, 

Monitoring Locations, and Activities, there is a separate table to identify the relationships. To 

add an Attached Binary Object to the database, follow these steps: 

1. Open the ATTACHED_OBJECT table in the database 

2. In the FILE_NAME column, enter the file name of the object including the extension 

3. In the FILE_TYPE column, enter the file extension of the file you are attaching. For 

example, if you are attaching lab results in an Excel file, you would enter “xls”. 

4. In the appropriate column, enter the UID you wish to associate the file with 

5. Verify that the SEND_TO_EPA column is checked 

6. After creating the XML submission file, add the submission file and all Attached Objects 

to a zip file 

7. Submit the zip file 

3.1.2 Activity Project IDs 

Since there can be multiple Project IDs4 associated with an Activity, there is a separate table to 

identify the relationships. The ACTIVITY_PROJECT table is used to associate Projects and 

Activities. To add associations, follow these steps: 

1. Open the ACTIVITY_PROJECT table 

2. Enter the data from the ACTIVITY.ACT_UID column into the 

ACTIVITY_PROJECT.ACT_UID column 

3. Enter the data from the PROJECT.PRJ_UID column into the 

ACTIVITY_PROJECT.PRJ_UID column 

4. Close the ACTIVITY_PROJECT table 

3.1.3 Activity Conducting Organization 

Since there can be multiple Organizations involved in conducting an Activity, there is a separate 

table to identify the relationship. The ACTIVITY_CONDUCTING_ORG table is used to 

associate Activities and their Conducting Organizations. To add associations, follow these steps: 

1. Open the ACTIVITY_CONDUCTING_ORG table 

2. Enter the data from the ACTIVITY.ACT_UID column into the 

ACTIVITY_CONDUCTING_ORG.ACT_UID column 

 

4

 Project IDs and Beach IDs are the same thing. Monitoring data uses the term Project ID, and Notification Data uses the term Beach ID. 
Beach Monitoring Database User Guide July 21, 2010 

7 

3. Enter the name of the activity’s conducting organization in the 

ACTIVITY_CONDUCTING_ORG.ACORG_NAME column 

4. Close the ACTIVITY_CONDUCTING_ORG table 

3.1.4 Activity Group Activity Identifiers 

Since there can be multiple Activity Identifiers associated with an Activity Group, there is a 

separate table to identify the relationships. The ACTIVITY_GROUP_DETAIL table is used to 

associate Activity Groups and their Activities. To add associations, follow these steps: 

1. Open the ACTIVITY_GROUP_DETAIL table 

2. Enter the data from the ACTIVITY.ACT_UID column into the 

ACTIVITY_GROUP_DETAIL.ACT_UID column 

3. Enter the data from the ACTIVITY_GROUP.ACT_GRP_UID column into the 

ACTIVITY_GROUP_DETAIL.PRJ_UID column 

4. Close the ACTIVITY_GROUP_DETAIL table 

3.1.5 Analytical Method Information 

The Analytical Method information in the RESULT table is handled differently than any other 

data in WQX. There are two REF tables, REF_ANALYTICAL_METHOD and 

REF_ANALYTICAL_METHOD_CONTEXT, which contain methods which are considered 

“national” methods which have been approved by various national organizations. WQX users 

are also able to create their own methods using these tables. 

3.1.5.1 Using Analytical Methods 

To use the Analytical Methods, the following columns will be filled out in the RESULT table: 

 RES_ANALYTICAL_METH_ID 

 RES_ANALYTICAL_METH_CONTEXT 

 RES_ANALYTICAL_METH_NAME 

 RES_ANALYTICAL_METH_DESC 

 RES_ANALYTICAL_METH_QUAL_TYPE 

You can first browse the list of Analytical Methods by opening the 

REF_ANALYTICAL_METHOD table. To add the Analytical Method information to your 

result, follow these steps: 

1. Select the RES_ANALYTICAL_METH_ID from the drop down menu 

2. Select the RES_ANALYTICAL_METHOD_CONTEXT which corresponds with the 

RES_ANALYTICAL_METH_ID you chose 

3. Select the RES_ANALYTICAL_METH_NAME which corresponds with the 

RES_ANALYTICAL_METH_ID you chose 

4. Select the RES_ANALYTICAL_METH_DESC which corresponds with the 

RES_ANALYTICAL_METH_ID you chose (Note, there are no descriptions for the 

national methods) 
Beach Monitoring Database User Guide July 21, 2010 

8 

5. Select the RES_ANALYTICAL_METH_QUAL_TYPE which corresponds with the 

RES_ANALYTICAL_METH_ID you chose (Note, there are no qualifier types in the 

national methods) 

3.1.5.2 Creating New Analytical Methods 

To create new Analytical Methods, the following columns will need to be filled out: 

 REF_ANALYTICAL_METHOD_CONTEXT Table 

o AMCTX_UID 

o AMCTX_CD 

o AMCTX_NAME 

 REF_ ANALYTICAL_METHOD Table 

o ANLMTH_ID 

o AMCTX_UID 

o ANLMTH_NAME 

o ANLMTH_DESC 

o ANLMTH_QUAL_TYPE 

The business rules of WQX dictate that when a state creates their own analytical methods they 

must use their Organization ID as the context for the new method. So to fill out the 

REF_ANALYTICAL_METHOD_CONTEXT table, follow these steps: 

1. In the AMCTX_UID column, enter a unique number. The easiest way to do this is to add 

one to the last number in the column. For example, if the last number is 756, your 

AMCTX_UID would be 757. 

2. In the AMCTX_CD column, enter you Organization ID. 

3. In the AMCTX_NAME column, enter the name of your organization. This is just used as 

metadata which will enable future users to easily understand the AMCTX_CD column. 

The data in this column will not be submitted to WQX and is only for local use. 

To fill out the REF_ANALYTICAL_METHOD table, follow these steps: 

1. In the ANLMTH_ID table, enter a unique identifier for your method. This method 

identifier can be any string of characters up to 20 characters in length that is not already 

used as a national method identifier. An easy way to ensure a unique identifier is to use 

your Organization ID as a prefix. For example, if your Org ID is DI21BCH, an 

appropriate method identifier would be DI21BCH-METHOD. 

2. In the AMCTX_UID column, enter the AMCTX_UID which was created in the 

REF_ANALYTICAL_METHOD_CONTEXT table for your organization. 

3. In the ANLMTH_NAME column, enter the name of the analytical method. 

4. Optionally, in the ANLMTH_DESC column, enter a description of the method. 

5. Optionally, in the ANLMTH_QUAL_TYPE column, enter the qualifier type for the 

method. 
Beach Monitoring Database User Guide July 21, 2010 

9 

After completing these steps, the newly created analytical method can be used exactly like any 

other analytical method. 
Beach Monitoring Database User Guide July 21, 2010 

10 

4 Preparing Update/Insert XML Submissions 

4.1 Process Overview 

This database is designed to convert the data within its tables into an XML file compliant with 

the WQX Schema. These are the basic steps that must be followed to produce an XML 

Submission file: 

1. Fill out the tables in the database. 

2. Open the Generate Insert/Update XML form. 

3. Enter your name in the Author Name text box. 

4. Enter your organization in the Organization Name text box. 

5. Enter your contact information in the Contact Information text box. (At least an email 

address should be provided.) 

6. Optionally, you may enter any comments you have about the submission. 

7. Uncheck the check boxes next to any information you wish to exclude from the 

submission. (See Excluding Data from Submissions for more information.) 

8. Click the Generate XML button. 

9. Navigate to the location where you wish to create the file and enter a file name in the File 

name text box. 

10. Click Save. 
Beach Monitoring Database User Guide July 21, 2010 

11 

4.2 Excluding Data from Submissions 

Exhibit 4-1 Generate Insert/Update XML Form 

There are several methods to exclude data from a submission file. The primary reason for 

excluding data from a submission would be because the data has already been submitted. 

First, the check boxes on the Generate Insert/Update XML form can be used to specify which 

type of data you would like to exclude from the submission. You may want to use this method 

when you only want to submit specific parts of your data. For example, in the following figure, 

the XML that is generated will not include the Electronic Address Data, the Telephonic Data, 

and the Project Data since they are unchecked. 

Another method for specifying which data to exclude in the submission file is to use the 

SEND_TO_EPA column in the tables. This method is useful when you want to keep data in 

your database, but do not want to upload it to the EPA. You may wish to do this to preserve 

historical information or just to reduce the size of your submission file. When the submission 

file is being generated all rows with the SEND_TO_EPA checkbox unchecked will be ignored. 

For example, in the following picture, the phones with ORGPH_UID 1 and 5 will be included in 

the submission file, but the phone with ORGPH_UID 3 will be excluded based on its unchecked 

SEND_TO_EPA column. 
Beach Monitoring Database User Guide July 21, 2010 

12 

Exhibit 4-2 ORG_PHONE Table 

The third method for specifying which data to exclude in the submission file is to use the Send 

To EPA Flag Manager form. This method will overwrite any changes made using the second 

method. The form is intended to be used after a successful submission to prevent data from 

being submitted multiple times.5 To use the form, follow these steps: 

1. Open the Send To EPA Flag Manager form. 

2. Mark the checkboxes in the form to specify which data table should be sent to EPA. 

Uncheck any boxes for data you do not want to send to EPA. 

3. Click Set Flags. 

Once the Set Flags button is clicked, all the rows of the corresponding data type will have their 

SEND_TO_EPA columns checked OR unchecked. For example, in the following image, after 

the Set Flags button is clicked, every row in the ACTIVITY table will have its SEND_TO_EPA 

column unchecked and every row in the other corresponding tables will have their 

SEND_TO_EPA column checked. 

 

5

 Note, data submitted multiple times will be treated as an update, and if no changes have been made in the Beach Monitoring database, no 

changes will occur in the WQX database. 
Beach Monitoring Database User Guide July 21, 2010 

13 

Exhibit 4-3 Send to EPA Flag Manager 

Note that in all of the above examples, the default value for the “Send” column is always 

“checked”. You must always uncheck the column to exclude the data type. 

Exhibit 4-4 shows which tables in the database correspond to the checkboxes in the Send To 

EPA Flag Manager form. 

Exhibit 4-4 Send To EPA Flag Tables 

Send To EPA Flag Manager Name Table Name 

Electronic Address Data ORG_ELECTRONIC_ADDRESS 

Telephonic Data ORG_PHONE 

Organization Address Data ORG_ADDRESS 

Project Data PROJECT 

Monitoring Location Data MONITORING_LOCATION 

Activity Data ACTIVITY 

Activity Group Data ACTIVITY_GROUP 
Beach Monitoring Database User Guide July 21, 2010 

14 

5 Preparing Delete XML Submissions 

Users are able to delete data from the WQX by making a Delete XML submission. These are the 

basic steps that must be followed to produce a Delete XML submission file: 

1. If the data to be deleted from the WQX database is not already in the local Access 

database, fill out the corresponding tables in the database. 

2. Open the Generate Delete XML form. 

3. Enter your name in the Author Name text box. 

4. Enter your organization in the Organization Name text box. 

5. Enter your contact information in the Contact Information text box. (At least an email 

address should be provided.) 

6. Optionally, you may enter any comments you have about the submission. 

7. Navigate the Projects, Monitoring Locations, Activities, and Activity Groups tabs and 

highlight the rows which contain the data you wish to delete. 

8. Click the Generate XML button. 

9. Navigate to the location where you wish to create the file and enter a file name in the 

File name text box. 

10. Click Save. 
Beach Monitoring Database User Guide July 21, 2010 

15 

6 Loading XML 

Users are able to take a XML submission file from WQX and import the records back into their 

monitoring database. It is recommended that you either import these records into a blank 

database or make a backup of your original database. These are the basic steps to load a XML 

file. 

1. Open the Load XML form. 

2. Click Browse and select the XML file. 

3. Optionally, you may click the Delete Records button to remove all the records that exist 

in the database. 

4. Click Load XML. 

5. You will receive confirmation that your XML file was successfully loaded in the form 

of a message box. 

Exhibit 6-1 Load XML Form and Message 
Beach Monitoring Database User Guide July 21, 2010 

16 

7 Submitting Files 

Submitting files is a two step process. First, the files which you created must be added to a zip 

file. Second, the files must be uploaded via a node client. 

7.1 Preparing the File 

All submissions to WQX must first be compressed into a zip file. In Windows XP follow these 

steps: 

1. Right click the submission file. 

2. Click “Send To”. 

3. Click “Compressed (zipped) Folder”. 

4. Any files referenced in the ATTACHED_OBJECT table with SEND_TO_EPA checked 

should be added to the zip file by dragging and dropping them onto the zip file. 

7.2 The First Submission 

The CDX team requires that anyone submitting WQX data over the Exchange Network must 

first do so in a test environment to ensure proper configuration and functionality. For WQX, the 

CDX team recommends that users send a small file (for example, just monitoring activities) to 

the test environment. Data submitted to the test environment is not migrated into production, so 

you will need to resend any data submitted under test to production. A test NAAS Account as 

well as WQX Organization ID are required to send test submissions. 

Once test data is successfully submitted, please notify the STORET Team, so the new 

Organization ID can be set up in the production environment enabling you to submit production 

data. 

7.3 Submitting Files 

The Exchange Network is comprised of a group of Nodes6 which exchange data. The Nodes are 

programmed so the exchanging of information is automated. However, there are node clients that 

enable human interaction with Exchange Network Nodes. 

Since all submissions to the WQX must go across the Exchange Network to the WQX Node, a 

node client such as Node Client Lite is required to manually make a submission7. A link to the 

latest version of Node Client Lite is located in the Before Submitting Data section of this 

document. To make submissions to the WQX using Node Client Lite, follow these steps: 

1. Open Node Client Lite. 

 

6

 A Node is just a computer that has the Exchange Network Node software running on it. More information on nodes can be found at 

http://www.exchangenetwork.net/node/index.htm. 

7

 There may be a method to submit data through a web site developed in the future. More information on this will be posted on the Beach Data 

Users site when available or contact the Beach Program Director for more information. 
Beach Monitoring Database User Guide July 21, 2010 

17 

2. Select the Node8 https://cdxnode.epa.gov/cdx/services/NetworkNodePortType_V10

3. Select Status “Production”. 

4. Enter your NAAS Account username. 

5. Enter your NAAS Credentials. 

6. Click Connect. 

7. On the left under “Things I can do”, click Upload Documents. 

8. Select the Data Flow “WQX”. 

9. If applicable, remove any information in the Transaction ID field. 

10. Click “Add...” 

11. Find and select the zip file which contains your submission. 

12. Click Open. 

13. Click Submit. 

14. If you successfully submitted the document, a page titled “Document Submission 

Results” will appear. 

Note that during this process, you can use the Node Client Help Magnifying Glass to get very 

useful information about the current screen you are using. It may take several hours or days to 

process your submission. 

7.4 Retrieving Submission Results Using Node Client Lite 

Follow these steps to retrieve your submission results using the Node Client Lite: 

1. Open Node Client Lite. 

2. Select the Node https://cdxnode.epa.gov/cdx/services/NetworkNodePortType_V10

3. Select Status “Production”. 

4. Enter your NAAS Account username. 

5. Enter your NAAS Credentials. 

6. Click Connect. 

7. On the left under “Things I can do”, click Download Documents. 

8. Select WQX as the Data Flow. 

9. Enter the Transaction ID issued for the submission.

10. Select a directory to use to download the results. 

11. Click Submit. 

 

8

 If you do not already have access to the production environment, you must first submit a file to the WQX test environment at 

https://test.epacdxnode.net/cdx/services/NetworkNodePortType_V10 with the status set to “Test”. A successful submission to the WQX test 

environment is required before you gain access to the WQX production environment. 
Beach Monitoring Database User Guide July 21, 2010 

18 

12. Open Processing Report in an XML reader which interprets XSL files. 

a. Internet Explorer is the recommended application. 

13. Check to see if there were any Errors or Warnings in the file. 

a. If there are no errors or warnings: 

i. You submission was successfully submitted. 

b. If there are errors or warnings: 

i. Examine the errors in Processing Log. 

ii. Make corrections to your data as necessary. 

iii. Resubmit.
Beach Monitoring Database User Guide July 21, 2010 

19 

8 Appendix A—Microsoft Access 

If you’ve never used Microsoft Access before, this Appendix provides basic instructions for 

entering information into the database. After opening the database with Access, you will see a 

screen as displayed in Exhibit 8-1: 

Exhibit 8-1 Beach Monitoring Database 

On the left, there is a list of Objects. The only Objects you will need to use are the Tables and 

Forms. As in Exhibit 8-1, you will see the tables listed. Double-clicking on ORG_PHONE will 

give display the ORG_PHONE table, as shown in Exhibit 8-2: 

Exhibit 8-2 ORG_PHONE Table 
Beach Monitoring Database User Guide July 21, 2010 

20 

You can use the mouse to click each box and type in information. You will first need to fill out 

the tables with information before you can generate a submission file. See section 4 for 

instructions on generating a submission file. 
Beach Monitoring Database User Guide July 21, 2010 

21 

9 Appendix B—Monitoring Database Change Log 

 V2.2.1 released 7/21/2010 

o Date ranges added to XML generation form. 

o The Activity form has been revised to include the Results associated with each 

Activity record.

 V2.2.0 released 8/3/2009 

o Data entry forms have been added. 

o A pre-validation feature has been added. 

o The XML generation process has been re-coded to run faster. 

 V2.1.3 released 12/17/2008 

o The user is no longer required to enter the Project ID EPABEACH. 

 V2.1.2 released 7/2/2008 

o Domain values were updated in the reference tables to reflect those in WQX 2.0 

 V2.1.1 released 2/25/2008 

o Fixed bug with incorrect PRJ_UID being inserted into the ACTIVITY_PROJECT 

table. 

 V2.1.0 released 2/4/2008 

o Added Load XML Form. 

o Changed default value 

MONITORING_LOCATION.MLOC_SOURCE_MAP_SCALE and 

ACTIVITY.ACT_LOC_SOURCE_MAP_SCALE from 0 to nothing. 

 V2.0.4 released 11/8/2007 

o Corrected bad data in the REF_ANALYTICAL_METHOD_CONTEXT table 

 V2.0.3 released 11/7/2007 

o Updated reference tables 

o Changed columns which were decimal type to long int to facilitate database 

maintenance 

o Added the REF_ANALYTICAL_METHOD and 

REF_ANALYTICAL_METHOD_CONTEXT tables (see section 3.1.5) 

 V2.0.2 released 10/22/2007 

o Fixed bug which did not allow letters in the MLOC_ID in the ACTIVITY table 

o Changed RESULT.RES_ANALYTICAL_METH_NAME length from 50 to 120 
Beach Monitoring Database User Guide July 21, 2010 

22 

o Fixed bug with the Activity group. Sometimes the activity groups would not be 

properly added to the XML file 

o Fixed bug which caused the result detection quantification limit to not always be 

properly added to the XML file 

o Changed example data to be more like data beach users would typically use 

 V2.0.1 released 10/10/2007 

o Added Relations 

o Added descriptions of each column 

o Fixed bug which created the XML files with an incorrect Namespace 
Beach Monitoring Database User Guide July 21, 2010 

23 

10 Appendix C—Table Relationships 

Exhibit 10-1 Table Relationships 
Beach Monitoring Database User Guide July 21, 2010 

24 

11 Appendix D—Data Elements 

The XML schema for the data submissions to WQX provides a template for the XML files to be 

submitted. This schema describes the data elements to be included in the XML document and is 

also used to validate it. Files are accepted or rejected based on their conformity to the schema. 

This appendix contains descriptions of the data elements in the WQX XML Schema. For each 

table in the following sections, the following information is provided: 

 Data Name: The name of the data element stored in the XML data file. 

 XML Tag Name: The XML key associated with the data element. 

 Data Type: Information about the data type for this element. Values in parentheses are 

the maximum lengths. 

 Req’d: This value indicates if the column is required in the XML data file. Please note 

that empty tags such as <TripIdentifier></TripIdentifier> or <TripIdentifier/> will not be 

accepted when the element is not required. “Y” means the element is required. “N” 

means the element is not required. “C” means the requirement is conditional; the 

comment column contains more information about the conditional requirement. 

 Access Table Mapping: The location of the data in the Monitoring Access Database 

 Comments: Additional comments related to the XML data element. 

11.1 Organization 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Organization 

Identifier 

Example: 

21NYBCH 

OrganizationIdentifi

er 

string 

(30) 

Y ORGANIZATION.ORG_ID A designator used to 

uniquely identify a 

unique business 

establishment within a 

context. 

Primary key for 

everything, unique on 

the planet, supplied by 

EPA upon application 

of trading partner. 

Organization 

Formal Name 

Example: 

Test 

Organization 

OrganizationForma

lName 

string 

(120) 

Y ORGANIZATION.ORG_NAME The legal designator 

(i.e. formal name) of an 

organization. 

Organization Name 

according to Trading 

Partner 

Organization 

Description 

Text 

Example: 

This is the text 

organization 

that is used for 

test 

submissions. 

OrganizationDescri

ptionText 

string 

(500) 

N ORGANIZATION.ORG_DESC Information that further 

describes an 

organization. 
Beach Monitoring Database User Guide July 21, 2010 

25 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Tribal Code 

Example: 001 

TribalCode string 

(3) 

N ORGANIZATION.REF_TRIBE_

CODE 

Beach Use Unlikely 

The code that 

represents the 

American Indian tribe or 

Alaskan Native entity. 

This value must be a 

domain value

Electronic 

Address Text 

Example: 

bob@epa.gov 

ElectronicAddressT

ext 

string 

(120) 

C ORG_ELECTRONIC_ADDRES

S.EA_TEXT 

A resource address, 

usually consisting of the 

access protocol, the 

domain name, and 

optionally, the path to a 

file or location. 

Required if electronic 

address type name is 

present 

Electronic 

Address Type 

Name 

Example: 

Email 

ElectronicAddressT

ypeName 

string 

(8) 

C ORG_ELECTRONIC_ADDRES

S.REF_EA_TYPE_NAME 

The name that 

describes the electronic 

address type. 

Required if electronic 

address text is present 

This value must be a 

domain value 

Telephone 

Number Text 

Example: 

123-456-7890 

TelephoneNumber

Text 

string 

(15) 

C ORG_PHONE.ORG_PHONE_

NUM 

The number that 

identifies a particular 

telephone connection. 

Required if telephone 

number type name is 

present 

Telephone 

Number Type 

Name 

Example: 

Office 

TelephoneNumber

TypeName 

string 

(6) 

C ORG_PHONE.REF_PHONE_T

YPE_NAME 

The name that 

describes a telephone 

number type. 

Required if telephone 

number text is present 

This value must be a 

domain value 

Telephone 

Extension 

Number Text 

Example: 246 

TelephoneExtensio

nNumberText 

string 

(6) 

N ORG_PHONE.ORG_PHONE_

EXT 

The number assigned 

within an organization 

to an individual 

telephone that extends 

the external telephone 

number. 

Address Type 

Name 

Example: 

Location 

AddressTypeName string 

(8) 

C ORG_ADDRESS.REF_ADD_T

YPE_NAME 

Categorizes an address 

as either location, 

shipping, or mailing 

address. 

Required if organization 

address is present. 

This value must be a 

domain value 
Beach Monitoring Database User Guide July 21, 2010 

26 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Address Text 

Example: 123 

Main Street 

AddressText string 

(50) 

C ORG_ADDRESS.ORGADD_A

DDRESS 

The address that 

describes the physical 

(geographic), shipping, 

or mailing location of an 

organization. 

Required if Address 

Type Name is supplied.

Supplemental 

Address Text 

Example: Unit 

B 

SupplementalAddr

essText 

string 

(120) 

N ORG_ADDRESS.ORGADD_A

DDRESS_SUPPLEMENTAL 

The text that provides 

additional information 

about an address, 

including a building 

name with its 

secondary unit and 

number, an industrial 

park name, an 

installation name or 

descriptive text where 

no formal address is 

available. 

Locality Name 

Example: 

Fairfax 

LocalityName string 

(30) 

N ORG_ADDRESS.ORGADD_L

OCALITY_NAME 

The name of a city, 

town, village or other 

locality. 

State Code 

Example: VA 

StateCode string 

(2) 

C ORG_ADDRESS.REF_STATE

_CD 

A code designator used 

to identify a principal 

administrative 

subdivision of the 

United States, Canada, 

or Mexico. 

Required if 

Organization County 

Code is reported. 

This value must be a 

domain value 

Postal Code 

Example: 

20151 

PostalCode string 

(10) 

N ORG_ADDRESS.ORGADD_P

OSTAL_CD 

The combination of the 

5-digit Zone 

Improvement Plan (ZIP) 

code and the four-digit 

extension code (if 

available) that 

represents the 

geographic segment 

that is a subunit of the 

ZIP Code, assigned by 

the U.S. Postal Service 

to a geographic 

location. 
Beach Monitoring Database User Guide July 21, 2010 

27 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Country Code 

Example: US 

CountryCode string 

(2) 

N ORG_ADDRESS.REF_COUNT

RY_CD 

A code designator used 

to identify a primary 

geopolitical unit of the 

world. 

This value must be a 

domain value 

County Code 

Example: 005 

CountyCode string 

(3) 

N ORG_ADDRESS.REF_COUNT

Y_FIPS_CD 

A code designator used 

to identify a U.S. county 

or county equivalent. 

County codes must be 

reported using 3-digit 

FIPS codes. 

This value must be a 

domain value 

11.2 Project 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Project 

Identifier 

Example: 11

ProjectIdentifier string 

(35) 

Y PROJECT.PRJ_ID The Beach ID for 

Beaches Users. A 

designator used to 

uniquely identify a data 

collection project within 

a context of an 

organization. 

This short identifier 

supports the 

requirement to update 

or edit an existing 

project, subsequent to 

its initial entry, without 

repeating all of its 

component parts. 

Project Name 

Example: 

2005Acme 

River Beach

ProjectName string 

(120) 

Y PROJECT.PRJ_NAME The name assigned by 

the Organization 

(project leader or 

principal investigator) to 

the project. 
Beach Monitoring Database User Guide July 21, 2010 

28 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Project 

Description 

Text 

Example: 

River Beach 

Testing 

Conducted in 

2005

ProjectDescriptionT

ext 

string 

(1999) 

N PROJECT.PRJ_DESC Project description, 

which may include a 

description of the 

project purpose, 

summary of the 

objectives, or brief 

summary of the results 

of the project. 

Must provide either 

ProjectDescriptionText 

or supply a Project 

Attached Binary Object.

Binary Object 

File Name 

Example: 

Picture.jpg

BinaryObjectFileNa

me 

String 

(255) 

C ATTACHED_OBJECT.FILE_N

AME 

The text describing the 

descriptive name used 

to represent the file, 

including file extension. 

Required only when 

ProjectAttachedBinary

Object is reported. 

Must provide either 

ProjectDescriptionText 

or supply a Project 

Attached Binary Object. 

Binary Object 

File Type 

Code 

Example: jpg

BinaryObjectFileTy

peCode 

string 

(6) 

C ATTACHED_OBJECT.FILE_TY

PE 

The text or acronym 

describing the binary 

content type of a file. 

File text extension, free 

text not domain list 

validation. 

Required only when 

ProjectAttachedBinary

Object is reported. 

11.3 Monitoring Location 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 
Beach Monitoring Database User Guide July 21, 2010 

29 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Monitoring 

Location 

Identifier 

Example: 123

MonitoringLocationI

dentifier 

string 

(35) 

Y MONITORING_LOCATION.ML

OC_ID 

A designator used to 

describe the unique 

name, number, or code 

assigned to identify the 

monitoring location. 

This was formerly 

known as the Station 

Identifier in Monitoring 

data. 

This short identifier 

supports the 

requirement to update 

or edit an existing 

station, subsequent to 

its initial entry, without 

repeating all of its 

component parts. 

Monitoring 

Location 

Name 

Example: 

Monitoring 

Location 1

MonitoringLocation

Name 

string 

(255) 

Y MONITORING_LOCATION.ML

OC_NAME 

The designator 

specified by the 

sampling organization 

for the site at which 

sampling or other 

activities are 

conducted. 

Free text name 

assigned to the 

Monitoring Location by 

the Trading Partner. 

Monitoring 

Location Type 

Name 

Example: 

Ocean

MonitoringLocation

TypeName 

string 

(45) 

Y MONITORING_LOCATION.RE

F_MLOC_TYPE_NAME 

The descriptive name 

for a type of monitoring 

location. 

This value must be a 

domain value. For 

BEACH data users, use 

a BEACH Program Site 

domain value. (E.g.- 

BEACH Program SiteRiver/Stream, BEACH 

Program Site-Ocean, 

etc.) 

Monitoring 

Location 

Description 

Text 

Example: The 

monitoring 

location just 

south of the 

pier.

MonitoringLocation

DescriptionText 

string 

(1999) 

N MONITORING_LOCATION.ML

OC_DESC 

Text description of the 

monitoring location. 
Beach Monitoring Database User Guide July 21, 2010 

30 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

HUC Eight 

Digit Code 

Example: 

12345678

HUCEightDigitCod

e 

string 

(8) 

N MONITORING_LOCATION.ML

OC_HUC_8 

The 8 digit federal code 

used to identify the 

hydrologic unit of the 

monitoring location to 

the cataloging unit level 

of precision. 

HUC Twelve 

Digit Code 

Example: 

12345678901

2

HUCTwelveDigitCo

de 

string 

(12) 

N MONITORING_LOCATION.ML

OC_HUC_12 

The 12 digit federal 

code used to identify 

the hydrologic unit of 

the monitoring location 

to the subwatershed 

level of precision. 

Tribal Land 

Indicator 

Example: true

TribalLandIndicator Boolea

n 

N MONITORING_LOCATION.ML

OC_TRIBAL_LAND_YN 

An indicator denoting 

whether the location is 

on a tribal land. 

Tribal Land 

Name 

Example: ABC 

Tribal Lands

TribalLandName string 

(200) 

N MONITORING_LOCATION.ML

OC_TRIBAL_LAND_NAME 

The name of an 

American Indian or 

Alaskan native area 

where the location 

exists. 

Monitoring 

Location 

Identifier 

Example: 

10004041

MonitoringLocationI

dentifier 

string 

(35) 

C MONITORING_LOCATION_AL

TERNATE.MLALT_ID 

A designator used to 

describe the unique 

name, number, or code 

assigned to identify the 

monitoring location. 

Required if 

AlternateMonitoringLoc

ationIdentity is reported 

Monitoring 

Location 

Identifier 

Context 

Example: 

NJEMS

MonitoringLocationI

dentifierContext 

string 

(120) 

C MONITORING_LOCATION_AL

TERNATE.MLALT_CONTEXT 

Identifies the source or 

data system that 

created or defined the 

monitoring location 

identifier 

Required if 

AlternateMonitoringLoc

ationIdentity is reported 

Latitude 

Measure 

Example: 

34.141592

LatitudeMeasure number 

(6-8) 

Y MONITORING_LOCATION.ML

OC_LATITUDE 

The measure of the 

angular distance on a 

meridian north or south 

of the equator. 

Signed Decimal 

Latitude with positive 

values north of the 

Equator 
Beach Monitoring Database User Guide July 21, 2010 

31 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Longitude 

Measure 

Example: -

74.141592

LongitudeMeasure number 

(6-9) 

Y MONITORING_LOCATION.ML

OC_LONGITUDE 

The measure of the 

angular distance on a 

meridian east or west of 

the prime meridian. 

Signed Decimal 

Longitude with neg 

values west of 

Greenwich 

Source Map 

Scale Numeric 

Example: 

12500

SourceMapScaleN

umeric 

non 

Negativ

e 

Integer 

C MONITORING_LOCATION.ML

OC_SOURCE_MAP_SCALE 

The number that 

represents the 

proportional distance 

on the ground for one 

unit of measure on the 

map or photo. 

Mandatory only when 

HorizonitalCollectionMe

thod Code is 

"INTERPOLATION 

MAP" 

Horizontal 

Collection 

Method Name 

Example: 

INTERPOLATI

ON-MAP

HorizontalCollectio

nMethodName 

string 

(150) 

Y MONITORING_LOCATION.RE

F_H_COLLECTION_METHOD

_NAME 

The name that 

identifies the method 

used to determine the 

latitude and longitude 

coordinates for a point 

on the earth. 

Valid code values 

correspond to those 

enumerated for this 

data element in the 

FRS XML schema. 

This value must be a 

domain value 

Horizontal 

Coordinate 

Reference 

System Datum 

Name 

Example: 

NAD83

HorizontalCoordina

teReferenceSyste

mDatumName 

string 

(6) 

Y MONITORING_LOCATION.RE

F_H_REFERENCE_DATUM_N

AME 

The name that 

describes the reference 

datum used in 

determining latitude 

and longitude 

coordinates. 

Valid code values 

correspond to those 

enumerated for this 

data element in the 

FRS XML schema. 

This value must be a 

domain value 
Beach Monitoring Database User Guide July 21, 2010 

32 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Measure 

Value 

Example: 2

MeasureValue string 

(12) 

N MONITORING_LOCATION.ML

OC_VERTICAL_MEASURE 

The recorded 

dimension, capacity, 

quality, or amount of 

something ascertained 

by measuring or 

observing. 

Required if 

VerticalMeasure block 

is reported 

Measure Unit 

Code 

Example: ft

MeasureUnitCode string 

(12) 

C MONITORING_LOCATION.RE

F_VM_MSUNT_CD 

The code that 

represents the unit for 

measuring the item. 

Required if 

VerticalMeasure block 

is reported 

This value must be a 

domain value 

Vertical 

Collection 

Method Name 

Example: 

OTHER

VerticalCollectionM

ethodName 

string 

(50) 

C MONITORING_LOCATION.RE

F_V_C0LLECTION_METHOD_

NAME 

The name that 

identifies the method 

used to collect the 

vertical measure (i.e. 

the altitude) of a 

reference point. 

Required if Vertical 

Measure/MeasureValue 

is supplied 

This value must be a 

domain value 

Vertical 

Coordinate 

Reference 

System Datum 

Name 

Example: 

OTHER

VerticalCoordinate

ReferenceSystemD

atumName 

string 

(6) 

C MONITORING_LOCATION.RE

F_V_REFERENCE_DATUM_N

AME 

The name of the 

reference datum used 

to determine the 

vertical measure (i.e., 

the altitude). 

Required if Vertical 

Measure/MeasureValue 

is supplied 

This value must be a 

domain value 

Country Code 

Example: US

CountryCode string 

(2) 

N MONITORING_LOCATION.RE

F_COUNTRY_CD 

A code designator 

A code designator used 

to identify a primary 

geopolitical unit of the 

world. 

This value must be a 

domain value 
Beach Monitoring Database User Guide July 21, 2010 

33 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

State Code 

Example: NJ

StateCode string 

(2) 

C MONITORING_LOCATION.RE

F_STATE_CD 

A code designator used 

to identify a principal 

administrative 

subdivision of the 

United States, Canada, 

or Mexico. 

Required if Monitoring 

Location CountyCode is 

reported. 

This value must be a 

domain value 

County Code 

Example: 021

CountyCode string 

(3) 

N MONITORING_LOCATION.RE

F_COUNTY_FIPS_CD 

A code designator used 

to identify a U.S. county 

or county equivalent. 

County codes must be 

reported using 3-digit 

FIPS codes. 

This value must be a 

domain value 

Binary Object 

File Name 

Example: 

test.doc

BinaryObjectFileNa

me 

string 

(255) 

C ATTACHED_OBJECT.FILE_N

AME 

The text describing the 

descriptive name used 

to represent the file, 

including file extension. 

Required if Monitoring 

Location 

AttachedBinaryObject 

present 

Binary Object 

File Type 

Code 

Example: doc

BinaryObjectFileTy

peCode 

string 

(6) 

C ATTACHED_OBJECT.FILE_TY

PE 

The text or acronym 

describing the binary 

content type of a file. 

Required if Monitoring 

Location 

AttachedBinaryObject 

present 

11.4 Activity 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 
Beach Monitoring Database User Guide July 21, 2010 

34 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Activity 

Identifier 

Example: 

10001

ActivityIdentifier string 

(35) 

Y ACTIVITY.ACT_ID Designator that 

uniquely identifies an 

activity within an 

organization. 

This short identifier 

supports the 

requirement to update 

or edit an existing 

activity, subsequent to 

its initial entry, without 

repeating all of its 

component parts.

Activity Type 

Code 

Example: 

Field Msr/ObsPortable Data 

Logger

ActivityTypeCode string 

(70) 

Y ACTIVITY.REF_ACT_TYPE_C

D 

The text describing the 

type of activity. 

This value must be a 

domain value 

Activity Media 

Name 

Example: 

Water

ActivityMediaName string 

(20) 

Y ACTIVITY.REF_ACT_MEDIA_

NAME 

Name or code 

indicating the 

environmental medium 

where the sample was 

taken. 

This value must be a 

domain value 

Activity Media 

Subdivision 

Name 

Example: 

Surface 

soil/sediment

ActivityMediaSubDi

visionName 

string 

(45) 

N ACTIVITY.REF_ACT_MEDIA_

SUBD_NAME 

Beach Use Unlikely 

Name or code 

indicating the 

environmental matrix as 

a subdivision of the 

sample media. 

This value must be a 

domain value 

Activity Start 

Date 

Example: 

2007-05-13

ActivityStartDate Date 

(YYYYMMDD) 

Y ACTIVITY.ACT_START_DATE The calendar date on 

which the field activity 

was started. 

Time 

Example: 

14:20:00

Time Time - 

(hh:mm

:ss) 

C ACTIVITY.ACT_START_TIME The time of day that is 

reported. 

Required only when 

ActivityStartTime is 

reported 
Beach Monitoring Database User Guide July 21, 2010 

35 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Time Zone 

Code 

Example: 

HADT

TimeZoneCode string 

(4) 

C ACTIVITY.REF_TMZONE_CD_

START_TIME 

The time zone for which 

the time of day is 

reported. Any of the 

longitudinal divisions of 

the earth's surface in 

which a standard time 

is kept. 

Required only when 

ActivityStartTime is 

reported 

This value must be a 

domain value

Activity End 

Date 

Example: 

2007-05-13

ActivityEndDate Date 

(YYYYMMDD) 

N ACTIVITY.ACT_END_DATE The calendar date 

when the field activity 

was completed. 

Time 

Example: 

14:20:00

Time Time - 

(hh:mm

:ss) 

C ACTIVITY.ACT_END_TIME The time of day that is 

reported. 

Required only when 

ActivityEndTime is 

reported 

Time Zone 

Code 

Example: 

HADT

TimeZoneCode string 

(4) 

C ACTIVITY.REF_TMZONE_CD_

END_TIME 

The time zone for which 

the time of day is 

reported. Any of the 

longitudinal divisions of 

the earth's surface in 

which a standard time 

is kept. 

Required only when 

ActivityEndTime is 

reported 

This value must be a 

domain value 

Activity 

Relative Depth 

Name 

Example: 

Bottom

ActivityRelativeDep

thName 

string 

(15) 

N ACTIVITY.REF_ACT_REL_DE

PTH_NAME 

The name that 

indicates the 

approximate location 

within the water column 

at which the activity 

occurred. 

This value must be a 

domain value 

Activity Depth 

Height 

Example: 2

MeasureValue string 

(12) 

N ACTIVITY.ACT_DEPTH_HEIG

HT 

The recorded 

dimension, capacity, 

quality, or amount of 

something ascertained 

by measuring or 

observing. 

Required if 

ActivityDepthHeightMe

asure block is reported. 
Beach Monitoring Database User Guide July 21, 2010 

36 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Depth Height 

Measure Unit 

Code 

Example: ft

MeasureUnitCode string 

(12) 

N ACTIVITY.REF_MSUNT_CD_D

EPTH_HEIGHT 

The code that 

represents the unit for 

measuring the item. 

Required if 

ActivityDepthHeightMe

asure block is reported. 

This value must be a 

domain value 

Activity Depth 

Height Top 

Example: 2

MeasureValue string 

(12) 

N ACTIVITY.ACT_DEPTH_HEIG

HT_TOP 

Beach Use Unlikely 

The recorded 

dimension, capacity, 

quality, or amount of 

something ascertained 

by measuring or 

observing. 

Required if 

ActivityTopDepthHeight

Measure block is 

reported. 

Depth Height 

Top Measure 

Unit Code 

Example: ft

MeasureUnitCode string 

(12) 

N ACTIVITY.REF_MSUNT_CD_D

EPTH_HEIGHT_TOP 

Beach Use Unlikely 

The code that 

represents the unit for 

measuring the item. 

Required if 

ActivityTopDepthHeight

Measure block is 

reported. 

This value must be a 

domain value

Activity Depth 

Height Bottom 

Example: 2

MeasureValue string 

(12) 

N ACTIVITY.ACT_DEPTH_HEIG

HT_BOTTOM 

Beach Use Unlikely 

The recorded 

dimension, capacity, 

quality, or amount of 

something ascertained 

by measuring or 

observing. 

Required if 

ActivityBottomDepthHei

ghtMeasure block is 

reported. 

Depth Height 

Bottom 

Measure Unit 

Code 

Example: ft

MeasureUnitCode string 

(12) 

N ACTIVITY.REF_MSUNT_CD_D

EPTH_HEIGHT_BOTTOM 

Beach Use Unlikely 

The code that 

represents the unit for 

measuring the item. 

Required if 

ActivityBottomDepthHei

ghtMeasure block is 

reported. 

This value must be a 

domain value 
Beach Monitoring Database User Guide July 21, 2010 

37 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Activity Depth 

Altitude 

Reference 

Point Text 

ActivityDepthAltitud

eReferencePointTe

xt 

string 

(125) 

N ACTIVITY.ACT_DEPTH_ALTIT

UDE_REF_POINT 

The reference used to 

indicate the datum or 

reference used to 

establish the 

depth/altitude of an 

activity. 

Project 

Identifier 

Example: 11

ProjectIdentifier string 

(35) 

Y ACTIVITY_PROJECT.PRJ_UID A designator used to 

uniquely identify a data 

collection project within 

a context of an 

organization. 

Multiple instances 

possible for each 

Activity instance 

Activity 

Conducting 

Organization 

Text 

Example: NJ 

Streamwatche

rs

ActivityConducting

OrganizationText 

string 

(120) 

N ACTIVITY_CONDUCTING_OR

G.ACORG_NAME 

Beach Use Unlikely 

A name of the 

Organization 

conducting an activity. 

Multiple instances 

possible for each 

Monitoring Activity 

instance 

Monitoring 

Location 

Identifier 

Example: 123

MonitoringLocationI

dentifier 

string 

(120) 

C ACTIVITY.MLOC_ID A designator used to 

describe the unique 

name, number, or code 

assigned to identify the 

monitoring location. 

Although the schema 

doesn't enforce this, 

some activity types will 

require that a 

monitoring location is 

present. To determine 

which activity types 

require a monitoring 

location please see the 

ACTYP_MON_LOC_R

EQ_YN column in the 

REF_ACT_TYPE_CD 

table. If the value in 

that column is “Y” then 

a monitoring location is 

required. 

Activity 

Comment Text 

Example: 

Additional 

activity 

comments go 

here

ActivityCommentTe

xt 

string 

(4000) 

N ACTIVITY.ACT_COMMENTS General comments 

concerning the activity. 
Beach Monitoring Database User Guide July 21, 2010 

38 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Subject 

Taxonomic 

Name 

Example: 

Apristurus

SampleTissueTaxo

nomicName 

string 

(120) 

C ACTIVITY.REF_TISSUE_TAX

ONOMIC_NAME 

Beach Use Unlikely 

The name of the 

organism sampled as 

part of a biological 

sample. 

Required if Biological 

Result Description 

block is reported. 

Sample 

Tissue 

Anatomy 

Name 

Example: Skin

SampleTissueAnat

omyName 

string 

(30) 

N ACTIVITY.REF_SAM_TISSUE

_ANATOMY_NAME 

Beach Use Unlikely 

The name of the 

anatomy from which a 

tissue sample was 

taken. 

This value must be a 

domain value

Latitude 

Measure 

Example: 

34.141592

LatitudeMeasure Decima

l 6-8 

digits 

C ACTIVITY.ACT_LOC_LATITUD

E 

Beach Use Unlikely 

The measure of the 

angular distance on a 

meridian north or south 

of the equator. 

Signed Decimal 

Latitude with positive 

values north of the 

Equator. 

Required if 

ActivityLocation is 

supplied. 

Longitude 

Measure 

Example: 

-74.141592

LongitudeMeasure Decima

l 6-9 

digits 

C ACTIVITY.ACT_LOC_LONGIT

UDE 

Beach Use Unlikely 

The measure of the 

angular distance on a 

meridian east or west of 

the prime meridian. 

Signed Decimal 

Longitude with neg 

values west of 

Greenwich 

Required if 

ActivityLocation is 

supplied. 

Source Map 

Scale Numeric 

Example: 

12500

SourceMapScaleN

umeric 

non 

Negativ

e 

Integer 

C ACTIVITY.ACT_LOC_SOURC

E_MAP_SCALE 

Beach Use Unlikely 

The number that 

represents the 

proportional distance 

on the ground for one 

unit of measure on the 

map or photo. 

Mandatory only when 

HorizonitalCollectionMe

thod Code is 

"INTERPOLATION 

MAP" 
Beach Monitoring Database User Guide July 21, 2010 

39 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Horizontal 

Collection 

Method Name 

Example: 

INTERPOLATI

ON-MAP

HorizontalCollectio

nMethodName 

string 

(150) 

C ACTIVITY.REF_H_COLLECTI

ON_METHOD_NAME 

Beach Use Unlikely 

The name that 

identifies the method 

used to determine the 

latitude and longitude 

coordinates for a point 

on the earth. 

Valid code values 

correspond to those 

enumerated for this 

data element in the 

FRS XML schema. 

Required if 

ActivityLocation is 

supplied. 

This value must be a 

domain value 

Horizontal 

Coordinate 

Reference 

System Datum 

Name 

Example: 

NAD27

HorizontalCoordina

teReferenceSyste

mDatumName 

string 

(6) 

C ACTIVITY.REF_H_REFERENC

E_DATUM_NAME 

Beach Use Unlikely 

The name that 

describes the reference 

datum used in 

determining latitude 

and longitude 

coordinates. 

Valid code values 

correspond to those 

enumerated for this 

data element in the 

FRS XML schema. 

Required if 

ActivityLocation is 

supplied. 

This value must be a 

domain value 

Method 

Identifier 

Example: 

GRAB

MethodIdentifier string 

(20) 

C ACTIVITY.ACT_SAM_COLLEC

T_METH_ID 

The identification 

number or code 

assigned by the method 

publisher. 

Required when 

SampleCollectionMetho

d is present. 

Method 

Identifier 

Context 

Example: 

MassDEP

MethodIdentifierCo

ntext 

string 

(120) 

C ACTIVITY.ACT_SAM_COLLEC

T_METH_CONTEXT 

Identifies the source or 

data system that 

created or defined the 

identifier. 

Required when 

SampleCollectionMetho

d is present. 
Beach Monitoring Database User Guide July 21, 2010 

40 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Method Name 

Example: 

Water Grab 

Sampling – no 

gear

MethodName string 

(120) 

C ACTIVITY.ACT_SAM_COLLEC

T_METH_NAME 

The title that appears 

on the method from the 

method publisher. 

Required when 

SampleCollectionMetho

d is present. 

Method 

Qualifier Type 

Name 

MethodQualifierTyp

eName 

string 

(25) 

N ACTIVITY.ACT_SAM_COLLEC

T_METH_QUAL_TYPE 

Beach Use Unlikely 

Identifier of type of 

method that identifies it 

as reference, 

equivalent, or other. 

Method 

Description 

Text 

Example: This 

is the method 

we tested out.

MethodDescription

Text 

string 

(500) 

N ACTIVITY.ACT_SAM_COLLEC

T_METH_DESC 

A brief summary that 

provides general 

information about the 

method. 

Sample 

Collection 

Equipment 

Name 

Example: 

Hand carer

SampleCollectionE

quipmentName 

string 

(40) 

C ACTIVITY.REF_SAM_COL_EQ

UIPMENT_NAME 

The name that 

represents equipment 

used in collecting the 

sample. 

Required when 

SampleCollectionMetho

d is present. 

This value must be a 

domain value 

Sample 

Collection 

Equipment 

Comment Text 

SampleCollectionE

quipmentComment

Text 

string 

(4000) 

N ACTIVITY.ACT_SAM_COLLEC

T_EQUIP_COMMENTS 

Beach Use Unlikely 

Free text with general 

comments further 

describing the sample 

collection equipment. 

Method 

Identifier 

Example: 4

MethodIdentifier string 

(20) 

C ACTIVITY.ACT_SAM_PREP_M

ETH_ID 

The identification 

number or code 

assigned by the method 

publisher. 

Required if Sample 

Preparation Method 

block is reported.

Method 

Identifier 

Context 

Example: 

21ALBCH

MethodIdentifierCo

ntext 

string 

(120) 

C ACTIVITY.ACT_SAM_PREP_M

ETH_CONTEXT 

Identifies the source or 

data system that 

created or defined the 

identifier. 

Required if Sample 

Preparation Method 

block is reported. 

Method Name 

Example: Test 

Method

MethodName string 

(120) 

C ACTIVITY.ACT_SAM_PREP_M

ETH_NAME 

The title that appears 

on the method from the 

method publisher. 

Required if Sample 

Preparation Method 

block is reported. 
Beach Monitoring Database User Guide July 21, 2010 

41 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Method 

Qualifier Type 

Name 

MethodQualifierTyp

eName 

string 

(25) 

N ACTIVITY.ACT_SAM_PREP_M

ETH_QUAL_TYPE 

Identifier of type of 

method that identifies it 

as reference, 

equivalent, or other. 

Method 

Description 

Text 

MethodDescription

Text 

string 

(500) 

N ACTIVITY.ACT_SAM_PREP_M

ETH_DESC 

A brief summary that 

provides general 

information about the 

method. 

Sample 

Container 

Type Name 

Example: 

Aluminum 

Dish

SampleContainerT

ypeName 

string 

(35) 

C ACTIVITY.REF_CONTAINER_

TYPE_NAME 

The text describing the 

sample container type. 

Required if Sample 

Preparation block is 

reported 

This value must be a 

domain value 

Sample 

Container 

Color Name 

Example: 

Clear

SampleContainerC

olorName 

string 

(15) 

C ACTIVITY.REF_CONTAINER_

COLOR_NAME 

The text describing the 

sample container color. 

Required if Sample 

Preparation block is 

reported 

This value must be a 

domain value 

Chemical 

Preservative 

Used Name 

ChemicalPreservati

veUsedName 

string 

(250) 

C ACTIVITY.ACT_SAM_CHEMIC

AL_PRESERVATIVE 

Information describing 

the chemical means to 

preserve the sample. 

Either 

ChemicalPreservativeU

sedName or 

ThermalPreservativeUs

edName are required if 

Sample Preparation 

block is reported 

Thermal 

Preservative 

Used Name 

Example: Wet 

Ice (4 deg C)

ThermalPreservativ

eUsedName 

string 

(25) 

C ACTIVITY.REF_THERMAL_PR

ESERVATIVE_NAME 

Information describing 

the temperature means 

used to preserve the 

sample. 

Either 

ChemicalPreservativeU

sedName or 

ThermalPreservativeUs

edName are required if 

Sample Preparation 

block is reported 

This value must be a 

domain value 
Beach Monitoring Database User Guide July 21, 2010 

42 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Sample 

Transport 

Storage 

Description 

SampleTransportSt

orageDescription 

string 

(250) 

C ACTIVITY.ACT_SAM_TRANSP

ORT_STORAGE_DESC 

The text describing 

sample handling and 

transport procedures 

used. 

Required if Sample 

Preparation block is 

reported

Binary Object 

File Name 

Example: 

file.doc

BinaryObjectFileNa

me 

string 

(255) 

C ATTACHED_OBJECT.FILE_N

AME 

The text describing the 

descriptive name used 

to represent the file, 

including file extension. 

Required if 

ActivityAttachedBinary

Object present 

Binary Object 

File Type 

Code 

Example: doc

BinaryObjectFileTy

peCode 

string 

(6) 

C ATTACHED_OBJECT.FILE_TY

PE 

The text or acronym 

describing the binary 

content type of a file. 

Required if 

ActivityAttachedBinary

Object present 

Activity Group 

Identifier 

Example: 

2005-11-01

ActivityGroupIdentif

ier 

string 

(35) 

Y ACTIVITY_GROUP.ACTGRP_I

D 

Designator that 

uniquely identifies a 

grouping of activities 

within an organization. 

Activity Group 

Name 

Example: 

2005-11-01 

Field Set

ActivityGroupName string 

(50) 

N ACTIVITY_GROUP.AG_NAME A name of an activity 

group. 

Activity Group 

Type Code 

Example: 

Field Set

ActivityGroupType

Code 

string 

(50) 

Y ACTIVITY_GROUP.REF_AG_T

YPE_NAME 

Identifies the type of 

grouping of a set of 

activities 

This value must be a 

domain value 

Activity 

Identifier 

Example: 

10001

ActivityIdentifier string 

(35) 

Y ACTIVITY_GROUP_DETAIL.A

CT_UID 

Designator that 

uniquely identifies an 

activity within an 

organization. 

May have 2 to many 

occurances for each 

Activity Group block. 

This ActivityIdentifier 

needs to correspond to 

either an 

ActivityIdentifier 

reported in the Activity 

block of this submission 

or previously submitted 

to the system. 
Beach Monitoring Database User Guide July 21, 2010 

43 

11.5 Result 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Data Logger 

Line Name 

Example: 1

DataLoggerLineNa

me 

string 

(15) 

C RESULT.RES_DATA_LOGGE

R_LINE 

Beach Use Unlikely 

The unique line 

identifier from a data 

logger result text file, 

normally a date/time 

format but could be any 

user defined name, e.g. 

"surface", "midwinter", 

and or "bottom".) 

Required when Activity 

Type contains phrase 

"Data Logger". Must be 

unique within Activity. 

Result 

Detection 

Condition Text 

Example: 

Present Below 

Quantification 

Limit

ResultDetectionCo

nditionText 

string 

(35) 

C RESULT.REF_DETECTION_C

ONDITION_NAME 

The textual descriptor 

of a result. 

Required if 

"ResultValue/ValueMea

sure" is blank. 

Detection condition 

explains why there is 

no result measure 

value. 

This value must be a 

domain value 

Characteristic 

Name 

Example: 

Enterococcus 

Group 

Bacteria 

CharacteristicNam

e 

string 

(120) 

C RESULT.REF_CHRARACTERI

STIC_NAME 

The object, property, or 

substance which is 

evaluated or 

enumerated by either a 

direct field 

measurement, a direct 

field observation, or by 

laboratory analysis of 

material collected in the 

field. 

Required if 

ResultValue/ValueMea

sure is reported 

This value must be a 

domain value 
Beach Monitoring Database User Guide July 21, 2010 

44 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Result Sample 

Fraction Text 

Example: 

Total

ResultSampleFracti

onText 

string 

(25) 

C RESULT.REF_SAMPLE_FRAC

TION_NAME 

The text name of the 

portion of the sample 

associated with results 

obtained from a 

physically-partitioned 

sample. 

Required for certain 

characteristics. 

This value must be a 

domain value 

Result 

Measure 

Value 

Example: 1

ResultMeasureValu

e 

string 

(60) 

C RESULT.RES_MEASURE The reportable 

measure of the result 

for the chemical, 

microbiological or other 

characteristic being 

analyzed. 

Required if Detection 

Condition is blank. No 

entry is allowed here if 

there is an entry in the 

ResultDectionCondition

Text. 

ResultValueMeasure 

must match a domain 

list value if the 

CharacteristicName 

ends with the phrase 

'Choice List' 

This value must be a 

domain value 

Measure Unit 

Code 

Example: mg/l

MeasureUnitCode string 

(12) 

C RESULT.REF_MSUNT_CD_M

EASURE 

The code that 

represents the unit for 

measuring the chemical 

substance, 

microbiological 

substance or other 

characteristic. 

Required if a non text 

result is reported; can 

also be reported for 

non-numeric results. 

This value must be a 

domain value 

Measure 

Qualifier Code 

Example: U

MeasureQualifierC

ode 

string 

(5) 

N RESULT.REF_MEASURE_QU

ALIFIER_CD 

A code used to identify 

any qualifying issues 

that affect the results. 

This value must be a 

domain value. 
Beach Monitoring Database User Guide July 21, 2010 

45 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Result Status 

Identifier 

Example: 

Final

ResultStatusIdentifi

er 

string 

(12) 

C RESULT.REF_STATUS_IDEN

TIFIER_NAME 

Indicates acceptability 

of the result with 

respect to QA/QC 

criteria. 

Required if result is 

reported. 

This value must be a 

domain value. 

Note: Set this field to 

Final to add to the 

warehouse. 

Statistical 

Base Code 

Example: 

Maximum

StatisticalBaseCod

e 

string 

(25) 

N RESULT.REF_STATISTICAL_

BASE_CD 

The code for the 

method used to 

calculate derived 

results. 

This value must be a 

domain value. 

Result Value 

Type Name 

Example: 

Actual

ResultValueTypeN

ame 

string 

(12) 

C RESULT.REF_VALUE_TYPE_

NAME 

A name that qualifies 

the process which was 

used in the 

determination of the 

result value (e.g., 

actual, estimated, 

calculated). 

Required if result is non 

text, Default is actual. 

This value must be a 

domain value. 

Result Weight 

Basis Text 

Example: Wet

ResultWeightBasis

Text 

string 

(15) 

N RESULT.REF_WEIGHT_BASI

S_NAME 

The name that 

represents the form of 

the sample or portion of 

the sample which is 

associated with the 

result value (e.g., wet 

weight, dry weight, ashfree dry weight). 

This value must be a 

domain value. 

Result Time 

Basis Text 

Example: 24 

Hours

ResultTimeBasisTe

xt 

string 

(12) 

N RESULT.REF_TIME_BASIS_N

AME 

The period of time (in 

days) over which a 

measurement was 

made. For example, 

BOD can be measured 

as 5 day or 20 day 

BOD. 

This value must be a 

domain value. 
Beach Monitoring Database User Guide July 21, 2010 

46 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Result 

Temperature 

Basis Text 

Example: 10 

Deg C

ResultTemperature

BasisText 

string 

(12) 

N RESULT.REF_TEMPERATUR

E_BASIS_NAME 

The name that 

represents the 

controlled temperature 

at which the sample 

was maintained during 

analysis, e.g. 25 deg 

BOD analysis. 

This value must be a 

domain value. 

Result Particle 

Size Basis 

Text 

ResultParticleSize

BasisText 

string 

(15) 

N RESULT.RES_PARTICLE_SIZ

E_BASIS 

User defined free text 

describing the particle 

size class for which the 

associated result is 

defined. 

This is usually done for 

a physical sediment 

analysis, where the 

user is free to 

document the particle 

size classification 

structure used in the 

analysis. 

Precision 

Value 

PrecisionValue string 

(60) 

N RESULT.RES_MEASURE_PR

ECISION 

A measure of mutual 

agreement among 

individual 

measurements of 

the same property 

usually under 

prescribed similar 

conditions. 

Bias Value BiasValue string 

(60) 

N RESULT.RES_MEASURE_BIA

S 

The systematic or 

persistent distortion of a 

measurement process 

which causes error in 

one direction. 

Confidence 

Interval Value 

ConfidenceInterval

Value 

string 

(15) 

N RESULT.RES_MEASURE_CO

NF_INTERVAL 

A range of values 

constructed so that this 

range has a specified 

probability of including 

the true population 

mean. 

Upper 

Confidence 

Limit Value 

UpperConfidenceLi

mitValue 

string 

(15) 

N RESULT.RES_MEASURE_UP

PER_CONF_LIMIT 

Value of the upper end 

of the confidence 

interval. 

Lower 

Confidence 

Limit Value 

LowerConfidenceLi

mitValue 

string 

(15) 

N RESULT.RES_MEASURE_LO

WER_CONF_LIMIT 

Value of the lower end 

of the confidence 

interval. 
Beach Monitoring Database User Guide July 21, 2010 

47 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Result 

Comment Text 

Example: 

Lake condition 

was poor 

(heavy debris) 

potentially due 

to heave rain 

in past 48 

hours.

ResultCommentTe

xt 

string 

(4000) 

N RESULT.RES_COMMENTS Free text with general 

comments concerning 

the result. 

Measure 

Value 

Example: 2

MeasureValue string 

(12) 

N RESULT.RES_DEPTH_HEIGH

T 

Beach Use Unlikely 

The recorded 

dimension, capacity, 

quality, or amount of 

something ascertained 

by measuring or 

observing. 

Required if 

ResultDepthHeightMea

sure block is reported. 

Measure Unit 

Code 

Example: ft

MeasureUnitCode string 

(12) 

N RESULT.REF_MSUNT_CD_D

EPTH_HEIGHT 

Beach Use Unlikely 

The code that 

represents the unit for 

measuring the item. 

Required if 

ResultDepthHeightMea

sure block is reported. 

This value must be a 

domain value

Result Depth 

Altitude 

Reference 

Point Text 

ResultDepthAltitud

eReferencePointTe

xt 

string 

(125) 

N RESULT.RES_DEPTH_ALTIT

UDE_REF_POINT 

Beach Use Unlikely 

The reference used to 

indicate the datum or 

reference used to 

establish the 

depth/altitude of a 

result. 
Beach Monitoring Database User Guide July 21, 2010 

48 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Method 

Identifier 

Example: 

Method001

MethodIdentifier string 

(20) 

C RESULT.RES_ANALYTICAL_

METH_ID 

The identification 

number or code 

assigned by the method 

publisher. 

Required if Result 

Analytical Method block 

is reported. 

Domain Values: This 

field will be validated 

against a domain value 

list only if the 

MethodIdentifierContext 

element (05.02.02) is 

set to one of a 

predefined list of 

contexts (e.g. USEPA, 

ASTM, USDOI 

This value must be a 

domain value 

Method 

Identifier 

Context 

Example: 

NELAC

MethodIdentifierCo

ntext 

string 

(120) 

C RESULT.RES_ANALYTICAL_

METH_CONTEXT 

Identifies the source or 

data system that 

created or defined the 

identifier. 

Required if Result 

Analytical Method block 

is reported. 

Method Name 

Example: 

NJMethod242

MethodName string 

(120) 

C RESULT.RES_ANALYTICAL_

METH_NAME 

The title that appears 

on the method from the 

method publisher. 

Required only if Method 

Identifier and Method 

Identifier Context are 

not from WQX Domain 

Value list (i.e. userdefined method) 

Method 

Qualifier Type 

Name 

MethodQualifierTyp

eName 

string 

(25) 

N RESULT.RES_ANALYTICAL_

METH_QUAL_TYPE 

Identifier of type of 

method that identifies it 

as reference, 

equivalent, or other. 

Method 

Description 

Text 

MethodDescription

Text 

string 

(500) 

N RESULT.RES_ANALYTICAL_

METH_DESC 

A brief summary that 

provides general 

information about the 

method. 

Laboratory 

Name 

Example: ABC 

Labs

LaboratoryName string 

(60) 

N RESULT.RES_LAB_NAME The name of the Lab 

responsible for the 

result 
Beach Monitoring Database User Guide July 21, 2010 

49 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Analysis Start 

Date 

Example: 

2007-05-26

AnalysisStartDate date 

(YYYYMMDD) 

N RESULT.RES_LAB_ANALYSIS

_START_DATE 

The calendar date on 

which the analysis 

began. 

Time 

Example: 

14:20:00

Time Time - 

(hh:mm

:ss) 

C RESULT.RES_LAB_ANALYSIS

_START_TIME 

The time of day that is 

reported. 

Required only when 

AnalysisStartTime is 

reported 

Time Zone 

Code 

Example: EST

TimeZoneCode string 

(4) 

C RESULT.REF_TMZONE_CD_L

AB_ANALYSIS_START 

The time zone for which 

the time of day is 

reported. Any of the 

longitudinal divisions of 

the earth's surface in 

which a standard time 

is kept. 

Required only when 

AnalysisStartTime is 

reported 

This value must be a 

domain value 

Analysis End 

Date 

Example: 

2007-05-27

AnalysisEndDate date 

(YYYYMMDD) 

N RESULT.RES_LAB_ANALYSIS

_END_DATE 

The calendar date on 

which the analysis was 

finished. 

Time 

Example: 

03:00:00

Time Time - 

(hh:mm

:ss) 

C RESULT.RES_LAB_ANALYSIS

_END_TIME 

The time of day that is 

reported. 

Required only when 

AnalysisEndTime is 

reported 

Time Zone 

Code 

Example: EST

TimeZoneCode string 

(4) 

C RESULT.REF_TMZONE_CD_L

AB_ANALYSIS_END 

The time zone for which 

the time of day is 

reported. Any of the 

longitudinal divisions of 

the earth's surface in 

which a standard time 

is kept. 

Required only when 

AnalysisEndTime is 

reported 

This value must be a 

domain value 

Result 

Laboratory 

Comment 

Code 

Example: CNT

ResultLaboratoryC

ommentCode 

string 

(3) 

N RESULT.REF_RESULT_LABO

RATORY_COMMENT_CD 

Remarks which further 

describe the laboratory 

procedures which 

produced the result. 

This value must be a 

domain value 
Beach Monitoring Database User Guide July 21, 2010 

50 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Detection 

Quantitation 

Limit Type 

Name 

Example: 

Method 

detection level 

(MDL)

DetectionQuantitati

onLimitTypeName 

string 

(35) 

C RESULT_DETECT_QUANT_LI

MIT.REF_DET_QUANT_LIMIT

_TYPE_NAME 

Text describing the type 

of detection or 

quantitation limit used 

in the analysis of a 

characteristic. 

Required when 

ResultDetectionconditio

n is either 

*Not Detected" 

"Present Above 

Quantification Limit" 

or "Present and Below 

Quantification Limit" 

This value must be a 

domain value 

Measure 

Value 

Example: 0.5

MeasureValue string 

(12) 

C RESULT_DETECT_QUANT_LI

MIT.RDQLMT_MEASURE 

The reportable 

measure of the result 

for the chemical, 

microbiological or other 

characteristic being 

analyzed. 

Required when 

ResultDetectionconditio

n is either 

*Not Detected" 

"Present Above 

Quantification Limit" 

or "Present and Below 

Quantification Limit"; 

Also required when 

DetectionQuantitationLi

mitMeasure block is 

reported. 
Beach Monitoring Database User Guide July 21, 2010 

51 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Measure Unit 

Code 

Example: mg/l

MeasureUnitCode string 

(12) 

C RESULT_DETECT_QUANT_LI

MIT.REF_MEASURE_MSUNT_

CD 

The code that 

represents the unit for 

measuring the chemical 

substance, 

microbiological 

substance or other 

characteristic. 

Required when 

ResultDetectionconditio

n is either 

*Not Detected" 

"Present Above 

Quantification Limit" 

or "Present and Below 

Quantification Limit"; 

Also required when 

DetectionQuantitationLi

mitMeasure block is 

reported. 

This value must be a 

domain value 

Method 

Identifier 

Example: 

Method001

MethodIdentifier string 

(20) 

C RESULT_LAB_SAMPLE_PRE

P.RLSPRP_METHOD_ID 

The identification 

number or code 

assigned by the method 

publisher. 

Required when 

LaboratorySamplePrep

aration is present. 

Method 

Identifier 

Context 

Example: 

NELAC

MethodIdentifierCo

ntext 

string 

(120) 

C RESULT_LAB_SAMPLE_PRE

P.RLSPRP_METHOD_CONTE

XT 

Identifies the source or 

data system that 

created or defined the 

identifier. 

Required when 

LaboratorySamplePrep

aration is present. 

Method Name 

Example: 

NJMethod242

MethodName string 

(120) 

C RESULT_LAB_SAMPLE_PRE

P.RLSPRP_METHOD_NAME 

The title that appears 

on the method from the 

method publisher. 

Required when 

LaboratorySamplePrep

aration is present. 

Method 

Qualifier Type 

Name 

MethodQualifierTyp

eName 

string 

(25) 

N RESULT_LAB_SAMPLE_PRE

P.RLSPRP_METHOD_QUAL_

TYPE 

Identifier of type of 

method that identifies it 

as reference, 

equivalent, or other. 

Method 

Description 

Text 

MethodDescription

Text 

string 

(500) 

N RESULT_LAB_SAMPLE_PRE

P.RLSPRP_METHOD_DESC 

A brief summary that 

provides general 

information about the 

method.
Beach Monitoring Database User Guide July 21, 2010 

52 

Data Name XML Tag Name Data 

Type 

Req’d Access Table Mapping Comment 

Preparation 

Start Date 

Example: 

2007-05-05

PreparationStartDa

te 

date 

(YYYYMMDD) 

N RESULT_LAB_SAMPLE_PRE

P.RLSPRP_START_DATE 

The calendar date 

when on which the 

preparation/extraction 

of the sample for 

analysis began. 

Time 

Example: 

14:20:00

Time Time - 

(hh:mm

:ss) 

C RESULT_LAB_SAMPLE_PRE

P.RLSPRP_START_TIME 

The time of day that is 

reported. 

Required only when 

PreparationStartTime is 

reported 

Time Zone 

Code 

Example: EST

TimeZoneCode string 

(4) 

C RESULT_LAB_SAMPLE_PRE

P.REF_TMZONE_CD_START_

TIME 

The time zone for which 

the time of day is 

reported. Any of the 

longitudinal divisions of 

the earth's surface in 

which a standard time 

is kept. 

Required only when 

PreparationStartTime is 

reported 

This value must be a 

domain value 

Preparation 

End Date 

Example:2007

-05-05

PreparationEndDat

e 

date 

(YYYYMMDD) 

N RESULT_LAB_SAMPLE_PRE

P.RLSPRP_END_DATE 

The calendar date 

when on which the 

preparation/extraction 

of the sample for 

analysis was finished.

Time 

Example: 

14:20:00

Time Time - 

(hh:mm

:ss) 

C RESULT_LAB_SAMPLE_PRE

P.RLSPRP_END_TIME 

The time of day that is 

reported. 

Required only when 

PreparationEndTime is 

reported 

Time Zone 

Code 

Example: EST

TimeZoneCode string 

(4) 

C RESULT_LAB_SAMPLE_PRE

P.REF_TMZONE_CD_END_TI

ME 

The time zone for which 

the time of day is 

reported. Any of the 

longitudinal divisions of 

the earth's surface in 

which a standard time 

is kept. 

Required only when 

PreparationEndTime is 

reported 

This value must be a 

domain value 
Beach Monitoring Database User Guide July 21, 2010 

53 

12 Appendix E—Data Entry Forms 

Access forms have been added to ease the data entry process. To access the data entry forms, 

click the Forms tab. It is still possible to copy and paste records directly into the Access tables. 

12.1 Forms Tab 

The main menu lists the forms in the order of entry. For example, organization data should be 

entered before projects. 

Exhibit 12-1 Microsoft Access 2000 Forms Tab 
Beach Monitoring Database User Guide July 21, 2010 

54 

Exhibit 12-2 Microsoft Access 2007 Forms Tab 
Beach Monitoring Database User Guide July 21, 2010 

55 

Exhibit 12-3 Microsoft Access 2007 Main Menu 
Beach Monitoring Database User Guide July 21, 2010 

56 

12.2 Return to Main Menu 

On the data entry screens there exists a menu item labled Return to Main Menu. This will close 

the currently opened screen and open the Main Menu form. 

Exhibit 12-4 Microsoft Access 2000 Project Data Entry Screen 
Beach Monitoring Database User Guide July 21, 2010 

57 

Exhibit 12-5 Microsoft Access 2007 Project Data Entry Screen 
Beach Monitoring Database User Guide July 21, 2010 

58 

12.3 Generate Insert/Update XML 

The Generate Insert/Update XML form has been changed in v2.2.1. Calendar objects have been 

added to the form to allow the user to specify date ranges. Only the activities between the 

specified dates will be included in the XML. 

Exhibit 12-6 Microsoft Access 2007 Generate Insert/Update XML Form 
Beach Monitoring Database User Guide July 21, 2010 

59 

13 Appendix F—Summary Reports 

Summary Reports have been added to assist in the QA process. To access the summary reports, 

click the Reports tab. 

13.1 Reports Tab 

Exhibit 13-1 Microsoft Access 2000 Reports Tab 
Beach Monitoring Database User Guide July 21, 2010 

60 

Exhibit 13-2 Microsoft Access 2007 Reports Tab 
Beach Monitoring Database User Guide July 21, 2010 

61 

14 Appendix G—CDX Messages 

14.1 WQX Submission Status 

Exhibit 14-1 displays the first email you will receive from CDX. This email will contain the 

status of your WQX submission. 

Exhibit 14-1 WQX Submission Status 

The WQX submission in Exhibit 14-2 has FAILED. Download the Validation Results and 

Processing Report files to identify the errors in the submission. 
Beach Monitoring Database User Guide July 21, 2010 

62 

Exhibit 14-2 WQX Submission Status – Failed 

14.2 Transaction History 

Click on the Transaction History menu item in CDX to view the submission’s processing files. 

Click on the Validation Results and Processing Report hyperlinks to download and view those 

files on your computer. 

Exhibit 14-3 Transaction History