Contract Number GS-35F-4797H 

Task Order # 1518 

TDD 10.02 eBeaches 

Version 2.2.1 

July 21, 2010 

Beach Notification Database User Guide 

(For Notification Schema v2.1) 
Beach Notification Database User Guide July 21, 2010 

 iii 

Table of Contents 

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

List of Exhibits ............................................................................................................................ iv

Revision Log ............................................................................................................................... v

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

1.1 Document Purpose ....................................................................................................... 1

2 How to Submit Data ........................................................................................................... 2

2.1 Submit Data via CDX .................................................................................................... 2

2.2 Detailed XML Processing Notes ................................................................................... 4

3 How to Understand the XML Submission ........................................................................... 5

3.1 Elements in the XML Schema and XML Files ............................................................... 5

3.2 Use of Effective Date and Status Indicator Data Elements ......................................... 38

4 How to Decode the Error Messages ................................................................................. 40

4.1 System Generated Error Messages ............................................................................ 40

4.2 Common Causes of Error Messages .......................................................................... 43

4.3 Oracle Generated Error Messages ............................................................................. 47

5 How to Understand Beaches that are Similar Points of Access ........................................ 48

6 Appendix A—Schema Graphics ....................................................................................... 49

7 Appendix B—Example XML File ....................................................................................... 57

8 Appendix C—Procedure Type Codes ............................................................................... 62

9 Appendix D—Water Body Codes ..................................................................................... 69

10 Appendix E—Horizontal Collection ................................................................................... 70

11 Appendix F—Addition Notifications................................................................................... 72

12 Appendix G—Pollution Source Identification .................................................................... 75

13 Appendix H—Data Entry Forms ....................................................................................... 78

14 Appendix I—Summary Reports ........................................................................................ 81

15 Appendix J—CDX Messages ........................................................................................... 87
Beach Notification Database User Guide July 21, 2010 

 iv 

List of Exhibits 

Exhibit 2-1 Data Transfer Diagram .............................................................................................. 4

Exhibit 4-1 PRAWN Error Messages ......................................................................................... 40

Exhibit 4-2 Common Error Messages ........................................................................................ 44

Exhibit 6-1 Beach Data Submission .......................................................................................... 49

Exhibit 6-2 Organization Detail .................................................................................................. 50

Exhibit 6-3 Organization Person Detail ...................................................................................... 51

Exhibit 6-4 Beach Name Detail ................................................................................................. 52

Exhibit 6-5 Beach Activity Detail ................................................................................................ 54

Exhibit 6-6 Beach Role Detail .................................................................................................... 55

Exhibit 6-7 Beach Coordinate Detail .......................................................................................... 55

Exhibit 6-8 Beach Procedure Detail ........................................................................................... 56

Exhibit 6-9 Year Completion Indicators ..................................................................................... 56

Exhibit 9-1 Water Body Name ................................................................................................... 69

Exhibit 9-2 Water Body Type ..................................................................................................... 69

Exhibit 10-1 Horizontal Collection Method Name ...................................................................... 70

Exhibit 10-2 Horizontal Collection Reference Datum Name....................................................... 71

Exhibit 11-1 Example Notification XML Document .................................................................... 72

Exhibit 11-2 Custom XML Generation ....................................................................................... 73

Exhibit 12-1 Access Database .................................................................................................. 75

Exhibit 12-2 XML Schema ......................................................................................................... 77

Exhibit 13-1 Forms .................................................................................................................... 78

Exhibit 13-2 Main Menu ............................................................................................................ 79

Exhibit 13-3 Return to Main Menu ............................................................................................. 80

Exhibit 14-1 Reports ................................................................................................................. 81

Exhibit 14-2 Actions .................................................................................................................. 82

Exhibit 14-3 Attributes ............................................................................................................... 83

Exhibit 14-4 Monitoring ............................................................................................................. 84

Exhibit 14-5 Pollution Source .................................................................................................... 85

Exhibit 14-6 Pollution Source (cont.) ......................................................................................... 86

Exhibit 15-1 Your CDX eBeaches Data Submission .................................................................. 87

Exhibit 15-2 Validation Message ............................................................................................... 88

Exhibit 15-3 Final Email ............................................................................................................ 89
Beach Notification Database User Guide July 21, 2010 

 v 

Revision Log 

Date Version 

No. 

Description Author Reviewer Review 

Date 

7/21/10 2.2.1 Added Appendix J CDX Messages EMR 
Beach Notification Database User Guide July 21, 2010 

1 

1 Introduction 

1.1 Document Purpose 

The purpose of this document is to introduce representatives from state beach programs to the 

PRogram tracking, beach Advisories, Water quality standards, and Nutrients (PRAWN) 

database. All state beach program and notification (advisory and closing) data will be stored in 

PRAWN. In particular, this guide is intended for officials from State beach programs, the EPA's 

Beaches program, and any database administrators in charge of a state database. 

The document can be used to explain the following about beach data submissions to EPA: 

 Error! Reference source not found.—explanation on how data is transferred from the originator (in 

most cases State Beach programs) through CDX to the EPA. Details about the transfers are separated 

into a second subsection for a more technical audience. 

 Error! Reference source not found.—explanation of the data that needs to be submitted to EPA 

and how that data should be formed within the XML document. Each section of the XML schema is 

explained in detail, and a specific section is devoted to explaining the use of the effective date and

status indicator elements. 

Error! Reference source not found.—explanation of the errors that the PRAWN database will produce 

due to logic and/or technical errors in the path between the creation of the XML document and the 

loading of data into PRAWN. 
Beach Notification Database User Guide July 21, 2010 

2 

2 How to Submit Data 

States that need to submit Beach information to EPA need to take advantage of EPA’s Central Data 

exchange (CDX) initiative to submit their data through a website. 

2.1 Submit Data via CDX 

The Central Data eXchange (CDX) is an Office of Environmental Information (OEI) initiative to 

provide a single point of entry for incoming data into EPA. CDX will maintain a set of web 

pages where, once registered, States can log in and upload data files to EPA. Additional 

information on CDX and the Exchange Network can be found at: http://www.epa.gov/cdx. 

The diagram in Exhibit 2-1 describes how data can be submitted from a State database to EPA’s PRAWN 

database via CDX. For information on how to create a custom data submission, please see Section Error! 

Reference source not found.. The following table describes the steps involved in the process: 

State Steps CDX Automated Steps PRAWN Automated Steps 

1. Register in 3 places: 

A) Register with CDX via the CDX 

HelpDesk. Send an email to 

helpdesk@epacdx.net or call 888-

890-1995 

B) Register any new beaches with the 

EPA to create a unique EPA Beach ID 

for each beach in the state. 

C) Register water quality stations in 

WQX submissions 

(http://www.epa.gov/storet/wqx/index.

html) 

2. Create an XML document 

containing the appropriate data (see 

Chapter Error! Reference source 

not found. Error! Reference source 

not found. for the data to be included) 

using a local copy of the schema. 

3. Upload the XML document from a 

local State computer to CDX via 

CDX’s website: 

https://cdx.epa.gov/SSL/cdx/login.asp 

4. Archive the file and validate the 

XML document against the schema. If 

errors are found, send a CDX error log 

to the State user; otherwise, skip to 

Step 6. 

5. Visit MyCDX Inbox for 

error/success log messages. If a CDX 

error log is received, go back to Step 

2 and fix the errors. 

6. Once the XML document passes 

validation, add the header information 

and transfer the XML document to the 

PRAWN XML Parser. 
Beach Notification Database User Guide July 21, 2010 

3 

State Steps CDX Automated Steps PRAWN Automated Steps 

7. Validate the XML document 

against the business rules. If 

errors are found, create an error 

log to CDX; otherwise, skip to 

Step 10. 

8. If a PRAWN error log is created, 

pass it along to the State. 

9. Make a second visit to MyCDX 

Inbox. If a PRAWN error log is 

received, go back to Step 2 and fix the 

errors. 

10. When the XML file is received 

that passes the business rules, 

parse the data into the database 

and create a success log. 

11. If a PRAWN success log is 

created, pass it along to the State. 
Beach Notification Database User Guide July 21, 2010 

4 

Exhibit 2-1 Data Transfer Diagram

Begin on the upper left side, labeled “State Database”, and follow the flow of arrows through the 

“PRAWN Database”. 

State 

Database

CDX (if automated)

EPA (if manual)

XML

Error/ 

Success 

Log

Main 

XML 

Schema

Local State 

Computer

XML

Local 

XML 

Schema

PRAWN XML 

Parser 

XML

PRAWN 

Database

Header info 

added to XML

Beach and 

Activity Data

Error/ 

Success 

Log

2.2 Detailed XML Processing Notes 

The following technical notes support the processes described in the previous two sections of this 

chapter: 

 Empty tags such as <OrganizationCode></OrganizationCode> or <OrganizationCode/> will not be 

accepted. 

 If the XML submission passes the validation routine, information about the submission will be 

inserted into the following four XML tags: SubmissionIdentifier, SubmittingAgencyIdentifier, 

SubmittingUserIdentifier, and SubmissionDate. These four tags are enclosed in tags labeled 

HeaderInformation. The HeaderInformation tag must appear second in the file after the 

BeachDataSubmission tag. 

 When the XML load process is complete, any errors will be written to an error file of the same name, 

with a .log extension instead of the .xml extension. 
Beach Notification Database User Guide July 21, 2010 

5 

3 How to Understand the XML Submission 

This chapter describes the XML data files and the associated XML schema to be used for the 

PRAWN database. 

3.1 Elements in the XML Schema and XML Files 

The XML schema for the data submissions to PRAWN 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. 

A graphical version of this schema is provided in Appendix A and an example XML document is 

provided in Appendix B of this document. Please refer to these appendices when creating an 

XML document. 

This section contains descriptions of the data elements in the PRAWN XML Schema. For each 

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

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

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

 XML Data Type: The XML data type for this element.

 Length: The maximum length for the data element for character and numeric data types. 

 Req’d (Y/N): This value indicates if the column is required in the XML data file. Please note that 

empty tags such as <OrganizationCode></OrganizationCode> or <OrganizationCode/> will not be 

accepted when the element is not required. 

 Comments: Additional comments related to the XML data element. 

For questions on the conventions and formats used in the schema, reference the Exchange 

Network’s XML Schema Design Rules and Conventions1

. 

 

1

 The Exchange Network’s XML Schema Design Rules and Conventions can be found here: 

http://www.exchangenetwork.net/dev_schema/drc.htm 
Beach Notification Database User Guide July 21, 2010 

6 

3.1.1 Organization Information 

The organization information section of the XML submission contains data related to the 

organizations involved in the Beach Act Grant Program, such as organization code, organization 

name, organization description, and contact information. These data elements will be included in 

the XML file when organization data needs to be added or updated in the PRAWN database. 

All XML elements in this section are located in the following position on the XML element 

hierarchy—“BeachDataSubmission/OrganizationDetail/”. 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Organization 

Identifier 

Example: 

987654321098

OrganizationIdentifi

er 

STRING Y 12 ORGANIZATION.ID, 

PERSON.FK_ORGANIZATIO

N_ID, 

MAILING_ADDRESS.FK_OR

GANIZATION_ID, 

ELECTRONIC_ADDRESS.FK

_ORGANIZATION_ID, 

BEACH_ORGANIZATION_RO

LE_ASSIGN.FK_ORGANIZATI

ON_ID

An organization refers to the entity 

associated with a Notification 

submitted to PRAWN. The type of 

entity is noted in the ‘Organization 

Type Code’ field. 

EPA will maintain a list of valid 

Organization Identifiers for all 

organizations that are stored in the 

PRAWN database. These identifiers 

must be unique, as they will be used 

to update organization-level data. 

Organization 

Type Code 

Example: 

STATE_AGNC

Y

OrganizationName

Detail/Organization

TypeCode 

STRING Y 12 ORGANIZATION.ORGANI

ZATION_CODE 

This value must be set to one of the 

following: 

 STATE_AGNCY (State Agency) 

 EPA (U.S. EPA)

 PUB_INT_GRP (Public Interest 

Group) 

 LOCAL_GOV (Local 

Government) 

 PRIVATE (Private Company) 

 OW (U.S. EPA Office of Water) 

 OW_DIV (U.S. EPA Office of 

Water Division) 

 OW_BRANCH (U.S. EPA Office 

of Water Branch) 

This value is required if any 

organization name information is 

included in the XML data file. 

Organization 

Name 

Example: 

Maine 

Department of 

Environmental 

Protection

OrganizationName

Detail/Organization

Name 

STRING Y 60 ORGANIZATION.NAME This value is required if any 

organization name information is 

included in the XML data file 
Beach Notification Database User Guide July 21, 2010 

7 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Organization 

Description 

Text 

Example: 

Maine DEP

OrganizationName

Detail/Organization

DescriptionText 

STRING N 255 ORGANIZATION.DESCRI

PTION 

Organization 

Abbreviation 

Text 

Example: 

MDEP

OrganizationName

Detail/Organization

AbbreviationText 

STRING N 30 ORGANIZATION.ABBREVI

ATION 

Organization 

Mailing 

Address Type 

Code 

Example: 

MAILING

OrganizationMailin

gAddressDetail/Ma

ilingAddressTypeC

ode 

STRING Y 12 MAILING_ADDRESS.MAIL

ING_ADDRESS_CODE 

This value must be set to one of the 

following: 

 SHIPPING (Shipping Address)

 MAILING (Mailing Address)

 OTHER (Other Address)

This value is required if any 

organization mailing address 

information is included in the XML 

data file. 

Organization 

Mailing 

Address Street 

Line 1 Text 

Example: 14 

Main Rd.

OrganizationMailin

gAddressDetail/Ma

ilingAddressStreet

Line1Text 

STRING Y 100 MAILING_ADDRESS.LINE

_1 

This value is required if any 

organization mailing address 

information is included in the XML 

data file. 

Organization 

Mailing 

Address Street 

Line 2 Text 

Example: 

Suite 4

OrganizationMailin

gAddressDetail/Ma

ilingAddressStreet

Line2Text 

STRING N 100 MAILING_ADDRESS.LINE

_2 

Organization 

Mailing 

Address Street 

Line 3 Text 

Example: 

Building 12

OrganizationMailin

gAddressDetail/Ma

ilingAddressStreet

Line3Text 

STRING N 100 MAILING_ADDRESS.LINE

_3 

Organization 

Mailing 

Address City 

Text 

Example: 

Augusta

OrganizationMailin

gAddressDetail/Ma

ilingAddressCityNa

me 

STRING Y 50 MAILING_ADDRESS.CITY This value is required if any 

organization mailing address 

information is included in the XML 

data file. 

Organization 

Mailing 

Address State 

Code 

Example: ME

OrganizationMailin

gAddressDetail/Sta

teCode 

STRING Y 2 MAILING_ADDRESS.STA

TE_POSTAL_CODE 

This value is required if any 

organization mailing address 

information is included in the XML 

data file. 

This value must be a valid 2-

character State Postal Code. 
Beach Notification Database User Guide July 21, 2010 

8 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Organization 

Mailing 

Address Zip 

Code 

Example: 

04333

OrganizationMailin

gAddressDetail/Ad

dressPostalCode 

STRING Y 12 MAILING_ADDRESS.ZIP_

CODE 

This value is required if any 

organization mailing address 

information is included in the XML 

data file. 

This value must be in one of the 

following numeric formats: 

 ##### 

or 

 #####-#### 

Organization 

Mailing 

Address 

Effective Date 

Example: 

2003-01-

01T00:00:00

OrganizationMailin

gAddressDetail/Ma

ilingAddressEffecti

veDate 

DATE Y MAILING_ADDRESS.EFF

ECTIVE_DATE 

This value is required if any 

organization mailing address 

information is included in the XML 

data file. 

The date should be entered in the 

XML file in the following format: 

YYYY-MM-DDTHH:MI:SS

This value should be set to the date 

on which the mailing address 

information became effective or will 

become effective. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 

Organization 

Mailing 

Address Status 

Indicator 

Example: 

ACTIVE

OrganizationMailin

gAddressDetail/Ma

ilingAddressStatusI

ndicator 

STRING Y 8 MAILING_ADDRESS.STA

TUS 

This value is required if any 

organization mailing address 

information is included in the XML 

data file. 

This value must be set to “ACTIVE” 

or “INACTIVE”. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 

Organization 

Electronic 

Address Type 

Code 

Example: URL

OrganizationElectr

onicAddressDetail/

ElectronicAddress

TypeCode 

STRING Y 12 ELECTRONIC_ADDRESS.

ELECTRONIC_ADDRESS

_CODE 

This value must be set to one of the 

following: 

 EMAIL (E-mail)

 URL (URL)

 OTHER (Other) 

This value is required if any 

organization electronic address 

information is included in the XML 

data file. 

Organization 

Electronic 

Address Text 

Example: 

http://www.mai

ne.gov/dep/blw

q/beach.htm 

OrganizationElectr

onicAddressDetail/

ElectronicAddress

Text 

STRING Y 255 ELECTRONIC_ADDRESS.

ADDRESS 

This value is required if any 

organization electronic address 

information is included in the XML 

data file. 
Beach Notification Database User Guide July 21, 2010 

9 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Organization 

Electronic 

Address 

Effective Date 

Example: 

2003-01-

01T00:00:00

OrganizationElectr

onicAddressDetail/

ElectronicAddress

EffectiveDate 

DATE Y ELECTRONIC_ADDRESS.

EFFECTIVE_DATE 

This value is required if any 

organization electronic address 

information is included in the XML 

data file. 

The date should be entered in the 

XML file in the following format: 

YYYY-MM-DDTHH:MI:SS

This value should be set to the date 

on which the electronic address 

information became effective or will 

become effective. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 

Organization 

Electronic 

Address Status 

Indicator 

Example: 

ACTIVE

OrganizationElectr

onicAddressDetail/

ElectronicAddress

StatusIndicator 

STRING Y 8 ELECTRONIC_ADDRESS.

STATUS 

This value is required if any 

organization electronic address 

information is included in the XML 

data file. 

This value must be set to “ACTIVE” 

or “INACTIVE”. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 

Organization 

Telephone 

Type Code 

Example: 

VOICE

OrganizationTelep

honeDetail/Teleph

oneTypeCode 

STRING Y 12 TELEPHONE.TELEPHON

E_CODE 

This value must be set to one of the 

following: 

 FAX (Fax)

 VOICE (Voice) 

 PAGER (Pager) 

 CELL (Cellular/Mobile) 

 OTHER (Other) 

This value is required if any 

organization telephone information 

is included in the XML data file. 

Organization 

Telephone 

Number 

Example: 207-

287-3901 

OrganizationTelep

honeDetail/Teleph

oneNumberText 

STRING Y 12 TELEPHONE.TELEPHON

E_NUMBER 

This value is required if any 

organization telephone information 

is included in the XML data file. 

This value must be in the following 

alphanumeric format: 

 XXX-XXX-XXXX 
Beach Notification Database User Guide July 21, 2010 

10 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Organization 

Telephone 

Effective Date 

Example: 

2003-01-

01T00:00:00

OrganizationTelep

honeDetail/Effectiv

eDate 

DATE Y TELEPHONE.EFFECTIVE

_DATE 

This value is required if any 

organization telephone information 

is included in the XML data file. 

The date should be entered in the 

XML file in the following format: 

YYYY-MM-DDTHH:MI:SS

This value should be set to the date 

on which the telephone information 

became effective or will become 

effective. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 

Organization 

Telephone 

Status 

Indicator 

Example: 

ACTIVE

OrganizationTelep

honeDetail/StatusI

ndicator 

STRING Y 8 TELEPHONE.STATUS This value is required if any 

organization telephone information 

is included in the XML data file. 

This value must be set to “ACTIVE” 

or “INACTIVE”. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 
Beach Notification Database User Guide July 21, 2010 

11 

3.1.2 Person Information 

The person information section of the XML submission contains data related to the people 

associated with the beaches overseen by the National Beach Watch Program. Examples of this 

data include person identifier code, name, title, and contact information. These data elements 

will be included in the XML file when person data needs to be added or updated in the PRAWN 

database. 

In the XML schema, each person is affiliated with exactly one organization. However, each 

organization can be associated with many people. 

 All XML elements in this section are located in the following position on the XML element 

hierarchy—“BeachDataSubmission/OrganizationDetail/OrganizationPersonDetail/”. 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Person 

Identifier 

Example: 

JOSM

PersonIdentifier STRING Y 12 PERSON.ID, 

BEACH_PERSON_ROLE_

ASSIGN.FK_PERSON_ID, 

ELECTRONIC_ADDRESS.

FK_PERSON_ID, 

MAILING_ADDRESS.FK_P

ERSON_ID, 

TELEPHONE.FK_PERSO

N_ID 

Submitting organizations will need to 

maintain a list of valid Person 

Identifiers for all people that are 

stored in the PRAWN database. 

These identifiers must be unique 

within each organization, as they will 

be used to update organization-level 

data. (For example, with an 

organization there can only be 1 

person identified as “JOSM”, but 

there could be another person 

identified as “JOSM” in another 

organization.) 

Person Status 

Indicator 

Example: 

ACTIVE

PersonNameDetail

/PersonStatusIndic

ator 

STRING Y 8 PERSON.ACTIVE This value if required if any person 

name information is included in the 

XML data file. 

This value must be set to “ACTIVE” 

or “INACTIVE”. 

Person First 

Name 

Example: 

John

PersonNameDetail

/FirstName 

STRING Y 50 PERSON.FIRST_NAME This value if required if any person 

name information is included in the 

XML data file. 

Person Last 

Name 

Example: 

Smith

PersonNameDetail

/LastName 

STRING Y 50 PERSON.LAST_NAME This value if required if any person 

name information is included in the 

XML data file. 
Beach Notification Database User Guide July 21, 2010 

12 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Person Middle 

Initial 

Example: S

PersonNameDetail

/PersonMiddleInitia

l 

STRING N 2 PERSON.MIDDLE_INITIAL The two characters in the ‘Person 

Middle Initial’ can be used as 

needed by the submitting state. For 

example, if there are two people 

within a given organization called 

‘Bob A Smith’, using the second 

letter of the Middle Name as the 

second letter of the ‘Person Middle 

Initial’ can be a valuable method 

used to differentiate between the 

two. Or, a period can be inserted 

after the first letter. Or, the second 

space can be left blank. 

Person Suffix 

Example: Jr.

PersonNameDetail

/NameSuffixText 

STRING N 5 PERSON.SUFFIX 

Person Title 

Example: Mr.

PersonNameDetail

/NamePrefixText 

STRING N 60 PERSON.TITLE 

Person Mailing 

Address Type 

Code 

Example: 

SHIPPING

PersonMailingAddr

essDetail/MailingA

ddressTypeCode 

STRING Y 12 MAILING_ADDRESS.MAIL

ING_ADDRESS_CODE 

This value must be set to one of the 

following: 

 SHIPPING (Shipping Address) 

 MAILING (Mailing Address)

 OTHER (Other Address)

This value is required if any person 

mailing address information is 

included in the XML data file. 

Person Mailing 

Address Street 

Line 1 Text 

Example: 14 

Main Rd.

PersonMailingAddr

essDetail/MailingA

ddressStreetLine1

Text 

STRING Y 100 MAILING_ADDRESS.LINE

_1 

This value is required if any person 

mailing address information is 

included in the XML data file. 

Person Mailing 

Address Street 

Line 2 Text 

Example: 

Suite 4

PersonMailingAddr

essDetail/MailingA

ddressStreetLine2

Text 

STRING N 100 MAILING_ADDRESS.LINE

_2 

Person Mailing 

Address Street 

Line 3 Text 

Example: 

Building 12

PersonMailingAddr

essDetail/MailingA

ddressStreetLine3

Text 

STRING N 100 MAILING_ADDRESS.LINE

_3 

Person Mailing 

Address City 

Text 

Example: 

Augusta

PersonMailingAddr

essDetail/MailingA

ddressCityName 

STRING Y 50 MAILING_ADDRESS.CITY This value is required if any person 

mailing address information is 

included in the XML data file. 
Beach Notification Database User Guide July 21, 2010 

13 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Person Mailing 

Address State 

Code 

Example: ME

PersonMailingAddr

essDetail/StateCod

e 

STRING Y 2 MAILING_ADDRESS.STA

TE_POSTAL_CODE 

This value is required if any person 

mailing address information is 

included in the XML data file. 

This value must be a valid 2-

character State Postal Code. 

Person Mailing 

Address Zip 

Code 

Example: 

04333

PersonMailingAddr

essDetail/Address

PostalCode 

STRING Y 12 MAILING_ADDRESS.ZIP_

CODE 

This value is required if any person 

mailing address information is 

included in the XML data file. 

This value must be in one of the 

following numeric formats: 

 ##### 

or 

 #####-#### 

Person Mailing 

Address 

Effective Date 

Example: 

2003-01-

01T00:00:00

PersonMailingAddr

essDetail/MailingA

ddressEffectiveDat

e 

DATE Y MAILING_ADDRESS.EFF

ECTIVE_DATE 

This value is required if any person 

mailing address information is 

included in the XML data file. 

The date should be entered in the 

XML file in the following format: 

YYYY-MM-DDTHH:MI:SS

This value should be set to the date 

on which the mailing address 

information became effective or will 

become effective. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 

Person Mailing 

Address Status 

Indicator 

Example: 

ACTIVE

PersonMailingAddr

essDetail/MailingA

ddressStatusIndica

tor 

STRING Y 8 MAILING_ADDRESS.STA

TUS 

This value is required if any person 

mailing address information is 

included in the XML data file. 

This value must be set to “ACTIVE” 

or “INACTIVE”. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 

Person 

Electronic 

Address Type 

Code 

Example: 

EMAIL

PersonElectronicA

ddressDetail/Electr

onicAddressTypeC

ode 

STRING Y 12 ELECTRONIC_ADDRESS.

ELECTRONIC_ADDRESS

_CODE 

This value must be set to one of the 

following: 

 EMAIL (E-mail)

 URL (URL)

 OTHER (Other)

This value is required if any person 

electronic address information is 

included in the XML data file. 

Person 

Electronic 

Address Text 

Example: 

Smith.Bob@m

aine.gov

PersonElectronicA

ddressDetail/Electr

onicAddressText 

STRING Y 255 ELECTRONIC_ADDRESS.

ADDRESS 

This value is required if any person 

electronic address information is 

included in the XML data file. 
Beach Notification Database User Guide July 21, 2010 

14 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Person 

Electronic 

Address 

Effective Date 

Example: 

2003-01-

01T00:00:00

PersonElectronicA

ddressDetail/Electr

onicAddressEffecti

veDate 

DATE Y ELECTRONIC_ADDRESS.

EFFECTIVE_DATE 

This value is required if any person 

electronic address information is 

included in the XML data file. 

The date should be entered in the 

XML file in the following format: 

YYYY-MM-DDTHH:MI:SS

This value should be set to the date 

on which the electronic address 

information became effective or will 

become effective. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 

Person 

Electronic 

Address Status 

Indicator 

Example: 

ACTIVE

PersonElectronicA

ddressDetail/Electr

onicAddressStatusI

ndicator 

STRING Y 8 ELECTRONIC_ADDRESS.

STATUS 

This value is required if any person 

electronic address information is 

included in the XML data file. 

This value must be set to “ACTIVE” 

or “INACTIVE”. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 

Person 

Telephone 

Type Code 

Example: 

CELL

PersonTelephoneD

etail/TelephoneTyp

eCode 

STRING Y 12 TELEPHONE.TELEPHON

E_TYPE_CODE 

This value must be set to one of the 

following: 

 FAX (Fax)

 VOICE (Voice)

 PAGER (Pager)

 CELL (Cellular/Mobile)

 OTHER (Other)

This value is required if any person 

telephone information is included in 

the XML data file. 

Person 

Telephone 

Number 

Example: 207- 

287-1111 

PersonTelephoneD

etail/TelephoneNu

mberText 

STRING Y 12 TELEPHONE.TELEPHON

E_NUMBER 

This value is required if any person 

telephone information is included in 

the XML data file. 

This value must be in the following 

alphanumeric format: 

 XXX-XXX-XXXX 
Beach Notification Database User Guide July 21, 2010 

15 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Person 

Telephone 

Effective Date 

Example: 

2003-01-

01T00:00:00

PersonTelephoneD

etail/EffectiveDate 

DATE Y TELEPHONE.EFFECTIVE

_DATE 

This value is required if any person 

telephone information is included in 

the XML data file. 

The date should be entered in the 

XML file in the following format: 

YYYY-MM-DDTHH:MI:SS

This value should be set to the date 

on which the telephone information 

became effective or will become 

effective. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 

Person 

Telephone 

Status 

Indicator 

Example: 

ACTIVE

PersonTelephoneD

etail/StatusIndicato

r 

STRING Y 8 TELEPHONE.STATUS This value is required if any person 

telephone information is included in 

the XML data file. 

This value must be set to “ACTIVE” 

or “INACTIVE”. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 
Beach Notification Database User Guide July 21, 2010 

16 

3.1.3 Beach Information 

The Beach Information section of the XML submission contains data related to the beaches 

overseen by the National Beach Program, such as beach name, beach description, state code, and 

county code. These data elements will be included in the XML file when beach information 

needs to be added or updated in the PRAWN database.

All XML elements in this section are located in the following position on the XML element 

hierarchy—“BeachDataSubmission/BeachDetail/”. 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Beach 

Identifier 

Example: 

ME234898

BeachIdentifier STRING Y 8 BEACH.ID, 

BEACH_ACTIVITY.FK_BE

ACH_ID, 

BEACH_PROCEDURE_AS

SIGN. FK_BEACH_ID, 

BEACH_PERSON_ROLE_

ASSIGN. FK_BEACH_ID, 

BEACH_ORGANIZATION_

ROLE_ASSIGN. 

FK_BEACH_ID, 

BEACH_LATITUDE_LONG

ITUDE_COORDINATE.FK

_BEACH_ID 

EPA maintains a list of valid Beach 

Identifiers for all beaches that are 

stored in the PRAWN database. 

Each new identifier must be 

registered with EPA before it can be 

submitted. These identifiers must be 

unique, as they will be used to 

update beach-level data. 

*Send request for new Beach ID to 

ebeaches@cgifederal.com

Beach Name 

Example: 

Sandy Beach 

Point

BeachNameDetail/

ProgramInterestNa

me 

STRING Y 60 BEACH.NAME This value is required if any beach 

name information is included in the 

XML data file. 

Beach 

Description 

Text 

Example: 

Rocky, big 

waves, no 

pollution

BeachNameDetail/

ProgramInterestDe

scriptionText 

STRING Y 255 BEACH.DESCRIPTION This value is required if any beach 

name information is included in the 

XML data file. 

Beach 

Comment Text 

Example: A 

nice place to 

surf

BeachNameDetail/

ProgramInterestCo

mmentText 

STRING N 255 BEACH.COMMENT This is an optional field that can be 

used to store other information 

about the particular beach that is not 

included in an official description. 

Beach State 

Code 

Example: ME

BeachNameDetail/

ProgramInterestSt

ateCode 

STRING Y 2 BEACH.STATE_POSTAL_

CODE 

This value is required if any beach 

name information is included in the 

XML data file. 

This value must be a valid 2-

character State Postal Code. 
Beach Notification Database User Guide July 21, 2010 

17 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Beach FIPS 

County Code 

Example: 

23001

BeachNameDetail/

ProgramInterestFI

PSCountyCode 

STRING Y 5 BEACH.FIPS_COUNTY This value is required if any beach 

name information is included in the 

XML data file. 

This value must be a valid 5 digit 

code representing a county, as 

assigned by the Federal Information 

Processing Standards Publications 

(FIPS). The first two digits represent 

the state, while the last three digits 

represent the specific county. 

FIPS county codes can be found at 

http://www.itl.nist.gov/fipspubs/cocodes/states.htm 

Water Body 

Name Code 

Example: 

ATLANTIC 

BeachNameDetail/

WaterBodyNameC

ode 

STRING N 12 BEACH.WATERBODY_NA

ME 

This value can be chosen from a list 

in Appendix D. 

This value is optional for all states 

except those on the Great Lakes. 

Water Body 

Type Code 

Example: 

OPEN_COAS

T 

BeachNameDetail/

WaterBodyTypeCo

de 

STRING N 12 BEACH.WATERBODY_TY

PE 

If Water Body Name (above) is NOT 

assigned to INLAND, this value must 

be set to one of the following: 

 OPEN_COAST (Open Coast) 

 SND_BY_INLT (Sound, Bay, or 

Inlet) 

If Waterbody Name (above) IS 

assigned to INLAND, this value must 

be set to one of the following: 

 STILL_WATER (Still Water) 

 FLOW_WATER (Flowing 

Water) 

This value is optional for all states 

except those on the Great Lakes. 

Beach 

Accessibility 

Type 

Example: 

PUB_PRV_AC

C

BeachNameDetail/

BeachAccessibility

Detail/BeachAcces

sibilityType 

STRING Y 12 BEACH.ACCESS_TYPE This value is required if any beach 

name information is included in the 

XML data file. 

The value must be set to one of the 

following: 

 PUB_PUB_ACC (Public Beach 

with Public Access) 

 PRV_PRV_ACC (Private Beach 

with Private Access) 

 PUB_PRV_ACC (Public Beach 

with Private Access) 

 PRV_PUB_ACC (Private Beach 

with Public Access) 
Beach Notification Database User Guide July 21, 2010 

18 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Beach 

Accessibility 

Comment 

Example: 

Public Property 

at the end of a 

road.

BeachNameDetail/

BeachAccessibility

Detail/BeachAcces

sibilityComment 

STRING N 255 BEACH.ACCESS_COMME

NT 

This is an optional field that can be 

used to store other information 

about the beach access that is not 

included in an official description. 
Beach Notification Database User Guide July 21, 2010 

19 

3.1.4 Beach Attribute Information 

The beach attribute section of the XML submission contains data related to beach information 

that may change over time, such as beach extent (length), swim season length, and monitoring 

frequency. 

States should submit one ‘Beach Attribute Detail’ section each year for each beach. 

All XML elements in this section are located in the following position on the XML element 

hierarchy—“BeachDataSubmission/BeachDetail/BeachAttributeDetail/”. 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Attribute 

Effective Year 

Example: 

2006

AttributeEffectiveY

ear 

STRING Y 4 BEACH_ATTRIBUTE.EFF

ECTIVE_YEAR 

This value is required if any beach 

attribute information is included in 

the XML data file. 

Attribute Effective Year is appended 

to each of the beach extent, swim 

season, and monitoring frequency 

records in PRAWN to distinguish the 

change over time. 

This value must be updated every 

year, even if the subsequent 

attribute information does not 

change, in order to verify the correct 

information for a beach. 

Beach Extent 

Length 

Measure 

Example: 5

BeachExtentDetail/

ExtentLengthMeas

ure 

NUMBE

R 

Y 14 BEACH_ATTRIBUTE.EXT

ENT_LENGTH 

This value is required if any beach 

name information is included in the 

XML data file. 

This value is the numeric equivalent 

of the length of a beach, along with 

the units of measure below. 

Beach Extent 

Length Unit of 

Measure 

Example: MI

BeachExtentDetail/

ExtentUnitOfMeas

ureCode 

STRING Y 12 BEACH_ATTRIBUTE.EXT

ENT_UNITS 

This value must be set to one of the 

following: 

 MI (Miles)

 FT (Feet) 

 YDS (Yards) 

 M (Meters) 

 KM (Kilometers) 

This value is required if any beach 

name information is included in the 

XML data file. 
Beach Notification Database User Guide July 21, 2010 

20 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Swim Season 

Start Date

Example: 

1/1/2007

BeachSwimSeaso

nLengthDetail/Swi

mSeasonStartDate 

DATE Y n/a BEACH_ATTRIBUTE.

SWIM_SEASON_START_

DATE 

Either the combination of Swim 

Season Start Date and Swim 

Season End or the combination of 

Beach Season Length and Beach 

Season Unit of Measure are 

required if any beach name 

information is included in the XML 

data file. The combination of Swim 

Season Start Date and Swim 

Season End Date is preferred. If 

both are sets of information are 

included, Swim Season Start Date 

and Swim Season End Date will be 

used. 

This value is the date the beach 

swim season starts for the year.

Swim Season 

End Date

Example: 

12/31/2007

BeachSwimSeaso

nLengthDetail/Swi

mSeasonEndDate 

DATE Y n/a BEACH_ATTRIBUTE.

SWIM_SEASON_END_DA

TE 

Either the combination of Swim 

Season Start Date and Swim 

Season End or the combination of 

Beach Season Length and Beach 

Season Unit of Measure are 

required if any beach name 

information is included in the XML 

data file. The combination of Swim 

Season Start Date and Swim 

Season End Date is preferred. If 

both are sets of information are 

included, Swim Season Start Date 

and Swim Season End Date will be 

used. 

This value is the date the beach 

swim season ends for the year. 

Beach Season 

Length 

Example: 150

BeachSwimSeaso

nLengthDetail/Swi

mSeasonLengthM

easure 

NUMBE

R 

Y 14 BEACH_ATTRIBUTE.SWI

M_SEASON_LENGTH 

Either the combination of Swim 

Season Start Date and Swim 

Season End or the combination of 

Beach Season Length and Beach 

Season Unit of Measure are 

required if any beach name 

information is included in the XML 

data file. The combination of Swim 

Season Start Date and Swim 

Season End Date is preferred. If 

both are sets of information are 

included, Swim Season Start Date 

and Swim Season End Date will be 

used. 

This value is the numeric equivalent 

of the amount of time in a swim 

season, along with the units of 

measure below. 
Beach Notification Database User Guide July 21, 2010 

21 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Beach Season 

Unit of 

Measure 

Example: 

DAYS

BeachSwimSeaso

nLengthDetail/Swi

mSeasonUnitOfMe

asureCode 

STRING Y 12 BEACH_ATTRIBUTE.SWI

M_SEASON_UNITS 

This value must be set to one of the 

following: 

 DAYS (Days)

 WEEKS (Weeks) 

 MONTHS (Months) 

Either the combination of Swim 

Season Start Date and Swim 

Season End or the combination of 

Beach Season Length and Beach 

Season Unit of Measure are 

required if any beach name 

information is included in the XML 

data file. The combination of Swim 

Season Start Date and Swim 

Season End Date is preferred. If 

both are sets of information are 

included, Swim Season Start Date 

and Swim Season End Date will be 

used. 

Swim Season 

Monitoring 

Frequency 

Example: 10 

MonitoringFrequen

cyDetail/SwimSeas

onFrequencyMeas

ure 

NUMBE

R 

Y 14 BEACH_ATTRIBUTE.SWI

M_MONITOR_FREQ 

This value is required if any beach 

attribute information is included in 

the XML data file. 

This value is the numeric equivalent 

of the frequency of monitoring 

performed during the designated 

Swim Season, as defined in the 

previous tags. The Swim Season 

Monitoring Frequency corresponds 

to the units of measure below. 

If monitoring is not performed on the 

beach during the swim season, 

please enter a 0 (zero) for this value.

Off Season 

Monitoring 

Frequency 

Example: 2 

MonitoringFrequen

cyDetail/OffSeason

FrequencyMeasure 

NUMBE

R 

Y 14 BEACH_ATTRIBUTE.OFF

_MONITOR_FREQ 

This value is required if any beach 

attribute information is included in 

the XML data file. 

This value is the numeric equivalent 

of the frequency of monitoring 

performed outside of the designated 

Swim Season, as defined in the 

previous tags. The Off Season 

Monitoring Frequency corresponds 

to the units of measure below. 

If monitoring is not performed on the 

beach during the off season, please 

enter a 0 (zero) for this value. 
Beach Notification Database User Guide July 21, 2010 

22 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Monitoring 

Frequency Unit 

of Measure 

Example: 

PER_WEEK 

MonitoringFrequen

cyDetail/Monitoring

FrequencyUnitOfM

easureCode 

STRING Y 12 BEACH_ATTRIBUTE.MON

ITOR_FREQ_UNITS 

This value must be set to one of the 

following: 

 PER_DAY (Per Day)

 PER_WEEK (Per Week) 

 PER_MONTH (Per Month) 

 PER_YEAR (Per Year) 

This value is required if any beach 

attribute information is included in 

the XML data file. 

This value corresponds to both the 

Swim Season and Off Season 

Monitoring Frequencies. For 

example, if the Swim Season 

Monitoring Frequency Measure is 

10, and the Units are PER_WEEK, 

the frequency reads “The beach is 

monitored 10 times per week during 

the swim season.”
Beach Notification Database User Guide July 21, 2010 

23 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Monitored 

Irregularly 

Indicator 

Example: Y

MonitoredIrregularl

y 

BOOLE

AN 

Y 1 BEACH_ATTRIBUTE.

MONITORED_IRREGULA

RLY 

This value is required if any beach 

attribute information is included in 

the XML data file. 

This should be “Y” if the beach is 

monitored irregularly and “N” 

otherwise. 

Monitored 

Irregularly 

Comment 

MonitoredIrregularl

yComment 

Text N 255 BEACH_ATTRIBUTE.

MONITORED_IRREGULA

RLY_COMMENT 

Any comments the about the 

regularity of the monitoring. 

Pollutions 

Sources 

Indicator 

Example: Y

NoPollutionSource

sIndicator 

BOOLE

AN 

Y 1 POLLUTION_SOURCES This should be “Y” if there are any 

possible pollution sources for the 

beach. This should be “N” if pollution 

sources were investigated and none 

were found. 

Note, see Appendix G for more 

information on populating data for 

pollution sources. 

Pollutions 

Sources 

Investigated 

Indicator 

Example: Y

PollutionsSources

UninvestigatedIndi

cator 

BOOLE

AN 

Y 1 POLLUTION_SOURCES_I

NVESTIGATED 

This should be “Y” if the beach 

pollution sources have been 

investigated and “N” otherwise. 

Note, see Appendix G for more 

information on populating data for 

pollution sources. 
Beach Notification Database User Guide July 21, 2010 

24 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Beach 

Pollution 

Source Code 

Example: 

SEWER_LINE

BeachPollutionSou

rceDetail/BeachPol

lutionSourceCode 

STRING N 12 BEACH_POLLUTION.POL

LUTION_SOURCE 

This value must be set to one of the 

following: 

AGRICULTURAL (Agricultural 

Runoff) 

BOAT (Boat Discharge) 

CAFO (Concentrated Animal 

Feeding Operation) 

CSO (Combined Sewer 

Overflow) 

POTW (Publicly-Owned 

Treatment Works) 

RUNOFF (Non-storm 

Related/Urban/Dryweather 

runoff) 

SEPTIC (Septic System 

Leakage) 

SEWER_LINE (Sewer Line 

Leak/Break/Blockage) 

SSO (Sanitary Sewer Overflow) 

STORM (Storm Related/WetWeather Runoff) 

WILDLIFE (Wildlife) 

UNKNOWN (Unknown) 

OTHER (Other-Specify in 

Description Field) 

This value is designed to allow 

states to store pollution sources 

impacting a given beach. These may 

include “possible” sources, identified 

by a citable study or attributed to by 

a credible person or entity; even if 

not confirmed to a level suitable for 

use in a court of law. 

Additionally, note that submitting a 

beach with no potential pollution 

sources is identical to saying that no 

pollution sources are known to 

impact that beach. 

Beach 

Pollution 

Source 

Description 

BeachPollutionSou

rceDetail/BeachPol

lutionSourceDescri

ption 

STRING N 255 BEACH_POLLUTION.POL

LUTION_COMMENT 

This is an optional field that can be 

used to store other information 

about the beach pollution source 

that is not included in an official 

description. 
Beach Notification Database User Guide July 21, 2010 

25 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Beach Tier 

Ranking 

Example: 2

BeachTierRanking NUMBE

R 

(0-9) 

Y 1 BEACH_ATTRIBUTE.BEA

CH_TIER 

This value is required if any beach 

attribute information is included in 

the XML data file. 

The ranking system for this value is 

set by individual states, so the 

ranges may differ (e.g., State A may 

have tiers 1 and 2, while State B 

may have tiers 1, 2, and 3) 

States with no tier system should 

enter a value of ‘1’ for all beaches. 

Beach Act 

Beach 

Indicator 

Example: Y

BeachActBeachInd

icator 

BOOLE

AN 

Y 1 BEACH_ATTRIBUTE.BEA

CH_ACT_BEACH 

This value is required if any beach 

attribute information is included in 

the XML data file. 

This should be “Y” if the beach 

qualifies as a BEACH Act beach and 

“N” otherwise. 
Beach Notification Database User Guide July 21, 2010 

26 

3.1.5 Beach Activity Information 

The beach activity section of the XML submission contains data related to beach advisories and 

closures, such as activity type code, activity name, activity description text, and activity reason. 

These data elements will be included in the XML file when activity or closure information needs 

to be added to the PRAWN database. Beach activity information can only be added to the 

PRAWN database; it cannot be updated. Since activities require a start and stop date, only 

completed activities should be submitted. 

States should submit one ‘Beach Activity Detail’ section per any one of the Activity Type Codes. 

Multiple ‘Beach Activity Detail’ sections can appear under one ‘Beach Detail’ section. 

All XML elements in this section are located in the following position on the XML element 

hierarchy—“BeachDataSubmission/BeachDetail/BeachActivityDetail/”. 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Activity Type 

Code 

Example: 

CLOSURE

ActivityTypeCode STRING Y 12 BEACH_ACTIVITY.ACTIVI

TY_CODE 

This value must be set to one of the 

following: 

 CONTAM_ADV (Contamination 

Advisory) 

 CLOSURE (Closure) 

 PERM_CLOSURE (Permanent 

Closure) 

 RAIN_ADV (Rain Advisory) 

This value is required if any beach 

activity information is included in the 

XML data file. 

States should submit one ‘Beach 

Activity Detail’ section per any one 

of the above activities. 

Activity Type Code and Activity 

Name are related in so far as the 

Activity Name can be used to keep 

track of the various activity types by 

assigning a local name to the 

various activities. There is not an 

Identifier in this portion of the data 

submission to aid in this endeavor. 

Activity Name 

Example: 

Closure 34

ActivityName STRING Y 60 BEACH_ACTIVITY.NAME This value is required if any beach 

activity information is included in the 

XML data file. 

Activity Type Code and Activity 

Name are related in so far as the 

Activity Name can be used to keep 

track of the various activity types by 

assigning a local name to the 

various activities. There is not an 

Identifier in this portion of the data 

submission to aid in this endeavor. 
Beach Notification Database User Guide July 21, 2010 

27 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Activity Actual 

Start Date 

Example: 

2002-04-

12T02:00:00

ActivityActualStart

Date 

DATE Y BEACH_ACTIVITY.ACTUA

L_START_DATE 

This value is required if any beach 

activity information is included in the 

XML data file. 

The date should be entered in the 

XML file in the following format: 

YYYY-MM-DDTHH:MI:SS

Activity Actual 

Stop Date 

Example: 

2002-04-

16T06:30:00

ActivityActualStop

Date 

DATE Y BEACH_ACTIVITY.ACTUA

L_STOP_DATE 

This value is required if any beach 

activity information is included in the 

XML data file. 

The date should be entered in the 

XML file in the following format: 

YYYY-MM-DDTHH:MI:SS

Activity 

Reason Type 

Example: 

ELEV_BACT

ActivityReasonDet

ail/ActivityReasonT

ype 

STRING Y 60 BEACH_ACTIVITY_REAS

ON.TYPE 

(BEACH_ACTIVITY_REAS

ON.CLASS = ‘REASON’) 

This value must be set to one of the 

following: 

 ELEV_BACT (Monitoring that 

revealed elevated bacteria 

levels) 

 RAINFALL (PreemptiveRainfall) 

 SEWAGE (Preemptive-Sewage 

discharge or spill) 

 CHEM_OIL (PreemptiveChemical or oil discharge or 

spill) 

 MODEL (Model prediction) 

 POLICY (Policy dictates action) 

 OTHER (Other-Please specify 

in the Description field) 

This value is required only if beach 

activity information AND beach 

activity reason information is 

included in the XML data file. 

The Beach Activity Reason Type 

field is used to supply information 

regarding the reason for the activity 

denoted in the Activity Type Code 

field. 

Any number of Reason Detail 

sections may be submitted 

(consecutively in the XML file) to 

associate many reasons to a single 

activity. 

Note that activities with Type 

‘ELEV_BACT’ must submit at least 

one Monitoring Station Identifier.
Beach Notification Database User Guide July 21, 2010 

28 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Activity 

Reason 

Description 

Text 

Example: 

Exceeded 

Water Quality 

Standards

ActivityReasonDet

ail/ActivityReasonD

escriptionText 

STRING N 255 BEACH_ACTIVITY_REAS

ON.DESCRIPTION 

(BEACH_ACTIVITY_REAS

ON.CLASS = ‘REASON’) 

The Beach Activity Reason 

Description field is used to supply 

additional information regarding the 

reason for the activity denoted in the 

Activity Type Code field. 

Activity Source 

Type 

Example: CSO

ActivitySourceDeta

il/ActivitySourceTy

pe 

STRING Y 60 BEACH_ACTIVITY_REAS

ON.TYPE 

(BEACH_ACTIVITY_REAS

ON.CLASS = ‘SOURCE’)

This value must be set to one of the 

following: 

AGRICULTURAL (Agricultural 

Runoff) 

BOAT (Boat Discharge) 

CAFO (Concentrated Animal 

Feeding Operation) 

CSO (Combined Sewer 

Overflow) 

POTW (Publicly-Owned 

Treatment Works) 

RUNOFF (Non-storm 

Related/Urban/Dryweather 

runoff) 

SEPTIC (Septic System 

Leakage) 

SEWER_LINE (Sewer Line 

Leak/Break/Blockage) 

SSO (Sanitary Sewer Overflow) 

STORM (Storm Related/WetWeather Runoff) 

WILDLIFE (Wildlife) 

UNKNOWN (Unknown)

OTHER (Other-Specify in 

Description Field) 

This value is required only if beach 

activity information AND beach 

activity source information is 

included in the XML data file. 

The Beach Activity Source Type 

field is used to supply information 

regarding the source of the activity 

denoted in the Activity Type Code 

field. 

Activity Source 

Description 

Text 

Example: 

Visible from 

CSO

ActivitySourceDeta

il/ActivitySourceDe

scriptionText 

STRING N 255 BEACH_ACTIVITY_REAS

ON.DESCRIPTION 

(BEACH_ACTIVITY_REAS

ON.CLASS = ‘SOURCE’) 

The Beach Activity Source Type 

field is used to supply additional 

information regarding the source of 

the activity denoted in the Activity 

Type Code field. 
Beach Notification Database User Guide July 21, 2010 

29 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Activity 

Indicator Type 

Example: 

PREEMPT

ActivityIndicatorDet

ail/ActivityIndicator

Type 

STRING Y 60 BEACH_ACTIVITY_REAS

ON.TYPE 

(BEACH_ACTIVITY_REAS

ON.CLASS = 

‘INDICATOR’) 

This value must be set to one of the 

following: 

 PREEMPT (Preemptive)

 ENTERO (Enterococci)

 TOTAL_COL (Total Coliform) 

 FECAL_COL (Fecal Coliform) 

 ECOLI (E. coli)

 RATIO (Total/Fecal Ratio) 

 OTHER (Other-Please specify 

in the Description field) 

This value is required only if beach 

activity information AND beach 

activity indicator information is 

included in the XML data file. 

The Beach Activity Indicator Type 

field is used to supply information 

regarding the indicator for the 

activity denoted in the Activity Type 

Code field. 

Activity 

Indicator 

Description 

Text 

Example: To 

avoid more 

actions

ActivityIndicatorDet

ail/ActivityIndicator

DescriptionText 

STRING N 255 BEACH_ACTIVITY_REAS

ON.DESCRIPTION 

(BEACH_ACTIVITY_REAS

ON.CLASS = 

‘INDICATOR’) 

This value is required only if beach 

activity information AND beach 

activity indicator information is 

included in the XML data file. 

Activity 

Monitoring 

Station ID 

Example: 

21MEBCH|Stat

ion1

ActivityMonitoringS

tationIdentifier 

STRING N 65 BEACH_ACTIVITY_STATI

ON.STATION_ID 

This value corresponds to the 

combination of a valid, preregistered STORET organization ID 

and the valid, pre-registered 

STORET station ID that impacted 

the activity. 

The two IDs must be joined together 

with a “pipe” (“|”) character (e.g., 

‘OrgID|StationID’). 

Any number of Monitoring Station 

IDs may be submitted (consecutively 

in the XML file) to associate many 

stations to a single activity. 

This value is required if the Activity 

Reason Type is ‘ELEV_BACT’.

Activity 

Description 

Text 

Example: The 

lifeguards 

closed the 

beach

ActivityDescription

Text 

STRING N 255 BEACH_ACTIVITY.DESCR

IPTION 

This is an optional field that can be 

used to describe anything about the 

activity itself. An example might be, 

“The lifeguards closed the beach.” 
Beach Notification Database User Guide July 21, 2010 

30 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Activity 

Comment Text 

Example: The 

police were not 

present

ActivityCommentT

ext 

STRING N 255 BEACH_ACTIVITY.COMM

ENT 

This is an optional field that can be 

used to store other information 

about the particular activity. An 

example might be, “The police were 

not present.” 

Activity Start 

Measure 

Example: 2

ActivityExtentDetail

/ActivityExtentStart

Measure 

NUMBE

R 

N 14 BEACH_ACTIVITY.EXTEN

T_START_MEASURE 

This value is the numeric equivalent 

of the location or mile marker where 

the length of affected beach begins. 

The activity extent length (below) is 

added to the activity start measure 

to understand the exact extent of 

beach that was affected by the 

activity. 

For example, a start measure of 2 

with an extent length of 5 and a unit 

of measure code of mi means the 

activity affected the beach from mile 

marker 2 to mile marker 7. 

Activity Extent 

Length 

Measure 

Example: 5

ActivityExtentDetail

/ActivityExtentLeng

thMeasure 

NUMBE

R 

Y 14 BEACH_ACTIVITY.EXTEN

T_LENGTH 

This value is required only if any 

beach activity information AND any 

beach activity extent information is 

included in the XML data file. 

See Activity Start Measure (above) 

for an explanation of the use of this 

value. 

Activity Unit of 

Measure Code 

Example: MI

ActivityExtentDetail

/ActivityUnitOfMea

sureCode 

STRING Y 12 BEACH_ACTIVITY.EXTEN

T_UNIT_OF_MEASURE 

This value must be set to one of the 

following: 

 MI (Miles)

 FT (Feet)

 YDS (Yards)

 M (Meters)

 KM (Kilometers) 

This value is required only if any 

beach activity information AND any 

beach activity extent information is 

included in the XML data file. 
Beach Notification Database User Guide July 21, 2010 

31 

3.1.6 Beach Role Information 

The beach role section of the XML submission allows submitting states to provide data related to 

the Organization and/or Person performing roles for a given beach. This section includes data 

elements, such as beach role type code, organization identifier, and person identifier. These data 

elements will be included in the XML file when beach role information needs to be added or 

updated in the PRAWN database. 

All XML elements in this section are located in the following position on the XML element 

hierarchy—“BeachDataSubmission/BeachDetail/BeachRoleDetail/”. 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 
Beach Notification Database User Guide July 21, 2010 

32 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Beach Role 

Type Code 

Example: 

LOCAL

BeachRoleTypeCo

de 

STRING Y 12 BEACH_ORGANIZATION_

ROLE_ASSIGN.ORG_ROL

E_CODE, 

BEACH_PERSON_ROLE_

ASSIGN.PERSON_ROLE_

CODE 

People/organizations are assigned a 

role on a beach via the ‘Beach Role 

Type Code’ field. 

For beach/organization 

assignments, this value must be set 

to one of the following: 

 LOCAL (Lead Local Agency) 

 STATE (Lead State Agency)

 CONTRACTOR (Contractor) 

 SUBCONTRACT 

(Subcontractor) 

 RESPONDENT (Respondent) 

 DETERM_AUTH 

(Determination Authority) 

 ISSUAN_AUTH (Issuance 

Authority) 

 REOPEN_AUTH (Reopening 

Authority) 

 LAB (Laboratory)

 COLLECTOR (Sample 

Collector) 

 ANALYZER (Sample Analyzer)

 OTHER (Other)

 UNKNOWN (Unknown) 

For beach/person assignments, this 

value must be set to one of the 

following: 

 STATE (Lead State Contact) 

 LOCAL (Lead Local Contact) 

 COLLECTOR (Sample 

Collector) 

 ANALYZER (Sample Analyzer)

 RESPONDENT (Respondent)

 TECHNICAL (Technical 

Contact) 

 PUBLIC (Public Contact)

 DETERM_AUTH 

(Determination Authority)

 ISSUAN_AUTH (Issuance 

Authority)

 REOPEN_AUTH (Reopening 

Authority) 

 INFO_TECH (Information 

Technology Authority) 

This value is required if any beach 

role information is included in the 

XML data file. 
Beach Notification Database User Guide July 21, 2010 

33 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Beach Role 

Organization 

Identifier 

Example: 

987654321098

BeachRoleOrganiz

ationIdentifier 

STRING Y 12 BEACH_ORGANIZATION_

ROLE_ASSIGN.FK_ORGA

NIZATION_ID, 

PERSON.FK_ORGANIZAT

ION_ID 

A beach is associated with an 

organization via this field. To do so, 

enter the Organization Identifier in 

the Beach Role Organization 

Identifier field. 

This value must correspond to a 

valid Organization Identifier in the 

XML file or in the PRAWN database. 

Beach Role 

Person 

Identifier 

Example: 

123456789012

BeachRolePersonI

dentifier 

STRING N 12 BEACH_PERSON_ROLE_

ASIGN.FK_PERSON_ID 

A beach can be associated with a 

person via this field. To do so, enter 

the Person Identifier in the Beach 

Role Person Identifier field in 

addition to entering the Organization 

Identifier in the Beach Role 

Organization Identifier field. 

The Beach Role Person Identifier 

must correspond to a valid Person 

Identifier in the XML file or in the 

PRAWN database. 

Beach Role 

Effective Date 

Example: 

2003-01-

01T00:00:00

BeachRoleEffectiv

eDate 

DATE Y BEACH_ORGANIZATION_

ROLE_ASSIGN.EFFECTIV

E_DATE, 

BEACH_PERSON_ROLE_

ASSIGN.EFFECTIVE_DAT

E 

This value is required if any beach 

role information is included in the 

XML data file. 

The date should be entered in the 

XML file in the following format: 

YYYY-MM-DDTHH:MI:SS

This value should be set to the date 

on which the beach role information 

became effective or will become 

effective. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 

Beach Role 

Status 

Indicator 

Example: 

ACTIVE

BeachRoleStatusIn

dicator 

STRING Y 8 BEACH_ORGANIZATION_

ROLE_ASSIGN.STATUS, 

BEACH_PERSON_ROLE_

ASSIGN.STATUS 

This value is required if any beach 

role information is included in the 

XML data file. 

This value must be set to “ACTIVE” 

or “INACTIVE”. 

Please see Section 3.2 Use of 

Effective Date and Status Indicator 

Data Elements for more information. 
Beach Notification Database User Guide July 21, 2010 

34 

3.1.7 Beach Coorindate Information 

The beach coordinate section of the XML submission allows submitting states to provide data 

related to the end points of a given beach. This section includes data elements, such as latitude 

measure, longitude measure, source map scale, horizontal collection method name, and 

horizontal coordinate reference system datum name. These data elements will be included in the 

XML file when beach coordinate information needs to be added or updated in the PRAWN 

database. 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Latitude 

Measure 

 

Example: 

34.141592 

LatitudeMeasure NUMBE

R 

Y 6-8 BEACH_LATITUDE_LONG

ITUDE_COORDINATES.S

TART_LATITUDE 

BEACH_LATITUDE_LONG

ITUDE_COORDINATES.E

ND_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. 

Longitude 

Measure 

Example: 

-74.141592

LongitudeMeasure NUMBE

R 

Y 6-9 BEACH_LATITUDE_LONG

ITUDE_COORDINATES.S

TART_ LONGITUDE 

BEACH_LATITUDE_LONG

ITUDE_COORDINATES.E

ND_ LONGITUDE 

The measure of the angular distance 

on a meridian east or west of the 

prime meridian. 

Signed Decimal Longitude with 

negative values west of Greenwich. 

Source Map 

Scale Numeric 

Example: 

12500 

SourceMapScaleN

umeric 

NUMBE

R 

C 14 BEACH_LATITUDE_LONG

ITUDE_COORDINATES.S

OURCE_MAP_SCALE 

The number that represents the 

relative distance on the ground for 

one unit of measure on the map or 

photo. 

This field is mandatory only when 

the Horizontal Collection Method 

Name used is INTERPOLATION 

MAP. 

Horizontal 

Collection 

Method Name 

Example: 

INTERPOLATI

ON-MAP 

INTERPOLATI

ONSATELLITE 

GPS 

HorizontalCollectio

nMethodName 

STRING Y 150 BEACH_LATITUDE_LONG

ITUDE_COORDINATES.R

EF_H_COLLECTION_MET

HOD_NAME 

The name that identifies the method 

used to determine the latitude and 

longitude coordinates for a point on 

the earth. 
Beach Notification Database User Guide July 21, 2010 

35 

Horizontal 

Coordinate 

Reference 

System Datum 

Name 

Example: 

NAD27 

NAD83 

HorizontalCoordina

teReferenceSyste

mDatumName 

STRING Y 6 BEACH_LATITUDE_LONG

ITUDE_COORDINATES.R

EF_H_REFERENCE_DAT

UM_NAME 

The name that describes the system 

used in determining the latitude and 

longitude coordinates. 

Description 

Example: 

Short 

Description. 

BeachCoordinateD

escriptionText 

STRING N 255 BEACH_LATITUDE_LONG

ITUDE_COORDINATES.D

ESCRIPTION 

This is an optional field that can be 

used to store other information 

about the particular beach’s 

coordinates. 
Beach Notification Database User Guide July 21, 2010 

36 

3.1.8 Year Completion Indicators 

The Year Completion Indicators section of the XML submission allows submitting states to 

notify the EPA when they have finished submissions for the year. This section includes data 

elements, such as Notification Data Complete Indicator, Monitoring Data Complete Indicator, 

and Location Data Complete Indicator. These data elements will be included in the XML file 

when states wish to notify that the EPA that they have finished submitting data for the year. 

NOTE: To generate a submission with the Notification Access database with year completion 

information, you can now use the Custom XML Generation form. This includes end of year 

completion information with your normal xml submission. There are no tables to fill out to 

generate this submission. 

All XML elements in this section are located in the following position on the XML element 

hierarchy—“BeachDataSubmission/YearCompletionIndicators/”. 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Length Access Table Mapping Comment 

Completion 

Year 

Example: 2007

CompletionYear NUMBE

R 

N 4 N/A This value is required if any year 

completion data is included in the XML 

data file. 

This value indicates what year the data 

has been submitted for. 

This can be created using the End Of 

Year Submission Generation form. 

Notification 

Data 

Completion 

Indicator 

Example: Y

NotificationDataCo

mpletionIndicator 

BOOLE

AN 

N N/A N/A This value indicates whether or not the 

Notification data has all been submitted 

for the calendar year. 

This can be created using the End Of 

Year Submission Generation form.

Monitoring Data 

Completion 

Indicator 

Example: Y

MonitoringDataCom

pletionIndicator 

BOOLE

AN 

N N/A N/A This value indicates whether or not the 

Monitoring data has all been submitted 

for the calendar year. 

This can be created using the End Of 

Year Submission Generation form.

Location Data 

Completion 

Indicator 

Example: Y

LocationDataComple

tionIndicator 

BOOLE

AN 

N N/A N/A This value indicates whether or not the 

Location data has all been submitted for 

the calendar year. 

This can be created using the End Of 

Year Submission Generation form.
Beach Notification Database User Guide July 21, 2010 

37 

3.1.9 Beach Procedure Information 

The beach procedure section of the XML submission contains data related to the procedures used 

by beaches for monitoring, notification, issuance, and reopening. This section includes data 

elements, such as procedure type code, procedure description text, and procedure identifier. 

These data elements will be included in the XML file when beach procedure information needs 

to be added or updated in the PRAWN database. 

All XML elements in this section are located in the following position on the XML element 

hierarchy—“BeachDataSubmission/BeachDetail/BeachProcedureDetail/”. 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Lengt

h 

Access Table Mapping Comment 

Procedure 

Type Code 

Example: 

IA_RADIO

ProcedureTypeCo

de 

STRING Y 12 PROCEDURE.PROCEDU

RE_CODE 

This value must be set to a valid 

procedure type code. See Error! 

Reference source not found. for a 

list of valid codes. 

This value is required if any beach 

procedure information is included in 

the XML data file. 

Procedure 

Description 

Text 

Example: 

Announce the 

advisory on the 

local radio 

station

ProcedureDescripti

onText 

STRING Y 255 PROCEDURE.DESCRIPTI

ON 

This value is required if any beach 

procedure information is included in 

the XML data file. 

Procedure 

Identifier 

Example: 

675849302019

ProcedureIdentifier STRING Y 12 PROCEDURE.ID Submitting organizations will need to 

maintain a list of valid Procedure 

Identifiers for all procedures that are 

stored in the PRAWN database. 

These identifiers must be unique 

within each organization, as they will 

be used to update organization-level 

data. (For example, with an 

organization there can only be 1 

procedure identified as “AB123”, but 

there could be another procedure 

identified as “AB123” in another 

organization.) 

Procedure 

Beach 

Identifier 

Example: 

ME234898

ProcedureBeachId

entifier 

STRING Y 12 BEACH_PROCEDURE_AS

SIGN.FK_BEACH_ID 

This value must correspond to 

EITHER a valid Beach Identifier 

and/or a valid Program Interest 

Identifier in the XML file or in the 

PRAWN database. 

Any number of Procedure Beach 

Identifiers may be submitted 

(consecutively in the XML file) to 

associate many beaches and/or 

program interests to a single 

procedure. 
Beach Notification Database User Guide July 21, 2010 

38 

3.1.10 Header Information 

The header information section of the XML file contains information regarding the data 

submission, such as submission date, submitting user, and submitting agency. These keys 

should not be included in the XML file submitted by the submitting agency. Instead, once an 

XML file has been successfully submitted to CDX, these XML keys will be added to the file by 

the CDX web application. 

All XML elements in this section are located in the following position on the XML element 

hierarchy—“BeachDataSubmission/HeaderDetail/”. 

Data Element XML Tag Name XML 

Data 

Type 

Req’d 

(Y/N) 

Length Access Table Mapping Comment 

Submitting 

Agency 

Identifier 

Example: 

KYDEP 

SubmittingAgencyIdentifier STRING Y 12 This key will be inserted into the 

file by the CDX web application. 

The list of valid Submitting 

Agency Identifiers will be 

maintained as part of the CDX 

registration process. 

Submitting 

User Identifier 

Example: 

BSMITH

SubmittingUserIdentifier STRING Y 12 This key will be inserted into the 

file by the CDX web application. 

The list of valid Submitting User 

Identifiers will be maintained as 

part of the CDX registration 

process. 

Submission 

Identifier 

Example: 

111111111111

SubmissionIdentifier STRING Y 12 This key will be inserted into the 

file by the CDX web application. 

This value will uniquely identify 

each submission and will be 

generated by the CDX web 

application. 

Submission 

Date 

Example: 

2003-01-

01T00:00:00

Submission Date DATE Y This key will be inserted into the 

file by the CDX web application. 

The date should be entered in 

the XML file in the following 

format: YYYY-MMDDTHH:MI:SS 

3.2 Use of Effective Date and Status Indicator Data Elements 

The Effective Date and Status Indicator data elements are used to set the effective dates in the 

PRAWN database for mailing addresses, electronic addresses, telephone numbers, beach/person 

roles, and beach/organization roles. For each of these types of data, the PRAWN database tracks 

the Start Date and Stop Date. For example, the database may track that a fax telephone number 

was valid starting on January 1, 2001. If this telephone number was updated and the new fax 

number was valid on July 1, 2001, a new record is added in the database with a Start Date of July 

1, 2001 and the same date is added as the Stop Date for the previous telephone number. 
Beach Notification Database User Guide July 21, 2010 

39 

To set this information correctly, the XML schema uses two data elements—Effective Date and 

Status Indicator—with mailing address, electronic address, telephone, beach/person role, and 

beach/organization role data. Furthermore, the user must specify the appropriate Type Code 

value (e.g., “FAX”, VOICE”, etc. for telephone number) so that the correct address, telephone 

number, beach/person role, or beach/organization role is updated. 

To update these types of data, these three data elements should be populated as follows: 

• To update an address, electronic address, telephone number, beach/person role assignment, or 

beach/organization assignment, the Effective Date and Status Indicator fields should be set as 

follows: 

o Effective Date should be set to the date on which the new address, telephone number, or 

assignment will become valid. 

o Status Indicator should be set to “ACTIVE”. 

o Type Code should be set to the type of information to be updated. (For example, this 

might be set to “STATE” for BeachRoleTypeCode.) 

o This will update the Stop Date for the current data and will create a new record with the 

updated data and the associated Start Date. 

• To indicate that an address, electronic address, telephone number, beach/person role assignment, 

or beach/organization assignment is no longer valid and there is no replacement data, the 

Effective Date and Status Indicator fields should be set as follows: 

o Effective Date should be set to the date on which the address, telephone number, or 

assignment will become invalid. 

o Status Indicator should be set to “INACTIVE”. 

o Type Code should be set to the type of information to be updated. (For example, this 

might be set to “SHIPPING” for MailingAddressTypeCode.) 

This will update the Stop Date for the current data but will not create a new record, since there is 

no new data. 
Beach Notification Database User Guide July 21, 2010 

40 

4 How to Decode the Error Messages 

This chapter provides detailed information regarding the error messages that may be produced 

during data transfer. This chapter assumes that the XML submission has passed XML schema 

validation before being processed by the data loading software. 

4.1 System Generated Error Messages 

This section describes system generated error messages associated with the validation and 

loading of National Beach Program data to the PRAWN database. The following table details the 

specific error codes and messages that may be produced during data loading and provides a short 

description of each error and appropriate corrective actions. It should be noted that error 

messages will be followed by XML tag value(s) to describe the location in the XML document 

where the error occurred. For instance, the error message ‘OrganizationName is required for 

adding/editing an Organization’ would be followed by the text ‘[OrganizationIdentifier = X]’ 

where ‘X’ is the identifier for the Organization where the error occurred. 

All errors encountered during the processing and loading of an XML data submission will be 

written to an Error Log File that can be sent to CDX and used for reporting feedback to data 

submitters. In addition to PRAWN system generated errors, Oracle specific error messages will 

also be written to this file (see Section Error! Reference source not found. for more 

information). 

Exhibit 4-1 PRAWN Error Messages 

Error Code Error Message Description/Corrective Action 

BCH-0101 OrganizationIdentifier must be unique for 

adding an Organization to the PRAWN 

system. [OrganizationIdentifier = 'X'] 

All new Organization records must have a previously

unused value for Organization Identifier in the 

PRAWN system. Confirm that you are using the 

assigned OrganizationIdentifier. 

BCH-0102 OrganizationIdentifier not found in the 

PRAWN system. [OrganizationIdentifier = 

'X'] 

You are attempting to edit a record that does not exist. 

Please confirm that you have entered the correct 

Organization Identifier for the record you are 

attempting to edit or change 

OrganizationTransactionType to add if you wish to 

create a new Organization record. 

BCH-0103 OrganizationTypeCode is invalid. 

[OrganizationIdentifier = 'X'; 

OrganizationTypeCode ='X'] 

A value unknown to the PRAWN system has been 

submitted for OrganizationTypeCode. Please see 

Chapter 3 for a list of valid values. 

BCH-0201 PersonIdentifier must be unique within an 

Organization. [OrganizationIdentifier = 

'X'; PersonIdentifier = 'X'] 

All new Person records must have a value for Person

Identifier that is previously unused by the referenced 

Organization in the PRAWN system. 

BCH-0202 PersonIdentifier not found within the 

specified Organization. 

[OrganizationIdentifier = 'X'; 

PersonIdentifier = 'X'] 

You are attempting to edit a record that does not exist 

within the specified Organization. Please confirm that 

you have entered the correct Person Identifier for the 

record you are attempting to edit or change 

PersonTransactionType to add if you wish to create a 

new Person record. 
Beach Notification Database User Guide July 21, 2010 

41 

Error Code Error Message Description/Corrective Action 

BCH-0301 MailingAddressTypeCode is invalid. 

[OrganizationIdentifier = 'X'; 

MailingAddressTypeCode = 'X'] 

A value unknown to the PRAWN system has been 

submitted for MailingAddressTypeCode. Please see 

Chapter 3 for a list of valid values. 

BCH-0302 MailingAddressStateCode is invalid. 

[OrganizationIdentifier = 'X'; 

MailingAddressStateCode = 'X'] 

MailingAddressStateCode must be a valid 2-digit 

State Postal Code (such as CA for California). Confirm 

that you are using a valid state code. 

BCH-0303 MailingAddressZipCode is invalid. 

[OrganizationIdentifier = 'X'; 

MailingAddressZipCode = 'X'] 

Provide a MailingAddressZipCode in one of the 

following numeric formats: 

##### 

or 

#####-#### 

BCH-0401 ElectronicAddressTypeCode is invalid. 

[OrganizationIdentifier = 'X'; 

ElectronicAddressTypeCode = 'X'] 

A value unknown to the PRAWN system has been 

submitted for ElectronicAddressTypeCode. Please 

see Chapter 3 for a list of valid values. 

BCH-0501 TelephoneNumber is invalid. 

[OrganizationIdentifier = 'X'; 

TelephoneNumber = 'X'] 

Provide a TelephoneNumber in one of the following 

alphanumeric formats: 

XXX-XXX-XXXX 

BCH-0502 TelephoneTypeCode is invalid. 

[OrganizationIdentifier = 'X'; 

TelephoneTypeCode = 'X'] 

A value unknown to the PRAWN system has been 

submitted for TelephoneTypeCode. Please see 

Chapter 3 for a list of valid values. 

BCH-0601 ProgramInterestStateCode is invalid. 

[BeachIdentifier = 'X'; 

ProgramInterestStateCode ='X'] 

ProgramInterestStateCode must be a valid 2-digit 

State Postal Code (such as CA for California). Confirm 

that you are using a valid state code. 

BCH-0602 BeachIdentifier must be unique for 

adding a Beach to the PRAWN system. 

[BeachIdentifier ='X'] 

All new Beach records must have a previously unused

value for Beach Identifier in the PRAWN system. 

Confirm that you are using the assigned 8-digit 

BeachIdentifier. 

BCH-0603 BeachIdentifier registered but not 

previously submitted to the PRAWN 

system. [BeachIdentifier = 'X'; 

BeachNameTransactionTypeCode = 'X'] 

You are attempting to edit a record that does not exist. 

Please confirm that you have entered the correct 

Beach Identifier for the record you are attempting to 

edit or change Beach Transaction Type Code to add if 

you wish to create a new Beach record. 

BCH-0604 BeachIdentifier not registered with EPA. 

[BeachIdentifier = 'X'] 

You are attempting to submit notification data for a 

beach with an identifier that has not been assigned by 

EPA. Contact your EPA beach coordinator for the 

appropriate beach identifier. 

BCH-0605 ProgramInterestFIPSCountyCode is 

invalid. [BeachIdentifier = 'X'; 

ProgramInterestFIPSCountyCode = 'X'] 

ProgramInterestFIPSCountyCode must be valid 5-digit

FIPS County Code. Confirm that you are using a valid 

code, and that it matches the two letter State code

submitted as ProgramInterestStateCode. 

BCH-0606 WaterBodyNameCode cannot be 

combined with WaterBodyTypeCode. 

[BeachIdentifier = 'X'; 

WaterBodyNameCode = 'X'; 

WaterBodyTypeCode = 'X'] 

The Waterbody Name Code submitted for the beach 

must correspond to an acceptable Waterbody Type 

Code. Please see Chapter 3 for acceptable matches 

(e.g., a Name of INLAND may only have a Type of 

STILL_WATER or FLOW_WATER). 
Beach Notification Database User Guide July 21, 2010 

42 

Error Code Error Message Description/Corrective Action 

BCH-0607 Beach Extent/Swim Season/Monitoring 

Frequencies already defined for the year 

on beach. [BeachIdentifier = 'X'; 

AttributeEffectiveYear = 'X'] 

The Beach Attribute information (Beach Extent/Swim 

Season/Monitoring Frequencies/Beach Tier/Pollution 

Source) you have submitted already exists for that 

particular beach, for that particular year. Please either 

revise the Attribute Effective Date to the appropriate 

year, or contact the EPA Beach program manager to 

ensure the proper information is stored in the PRAWN 

system. 

BCH-0701 ActivityTypeCode is invalid. 

[BeachIdentifier = 'X'; ActivityName = 'X'; 

ActivityTypeCode = 'X'] 

A value unknown to the PRAWN system has been 

submitted for ActivityTypeCode. Please see Appendix

B for a list of valid values. 

BCH-0702 ActivityMonitoringStationIdentifer not 

found in the STORET system. 

[BeachIdentifier = 'X'; ActivityName = 'X'; 

ActivityMonitoringStationIdentifier = 'X'] 

You are attempting to submit a monitoring station ID 

that has not been registered with STORET. Check the

validity of the Station ID and if valid, ensure is has 

been registered as a monitoring station in STORET. 

Contact your EPA beach coordinator for further 

information. 

BCH-0703 Activities with elevated bacteria 

(ELEV_BACT) as reasons must have at 

least one valid STORET Station ID. 

[BeachIdentifier = 'X'; ActivityName = 'X'] 

You are attempting to report a notification activity 

based on elevated bacteria levels without submitting a 

valid STORET Station ID. Each activity with a Reason 

Type Code of ‘ELEV_BACT’ must have at least one 

Monitoring Station ID. 

BCH-0704 Activity Reason/Source/Indicator 

Description must be included if Activity 

Reason/Source/Indicator Code is 

OTHER. [BeachIdentifier = 'X'; 

ActivityName = 'X'] 

You are attempting to submit either a Reason, a 

Source, or an Indicator for an activity labeled with type 

‘OTHER’ without submitting a description for the 

Reason, Source, or Indicator. 

BCH-0705 ActivityActualStartDate year does not 

match year of ActivityActualStopDate. 

[BeachIdentifier = 'X'; ActivityName = 'X'; 

ActivityActualStartDate = 'X'; 

ActivityActualStopDate = 'X'] 

You are attempting to submit an Activity that is 

spanning multiple years. Activities may only be 

submitted for one year at a time. Should an activity 

actually go on for more than one year, it is required 

that the initial activity end on December 31st

11:59:59pm of the current year and a new activity 

start again on January 1st 12:00:00am of the next 

year. 

BCH-0706 ActivityActualStopDate occurs prior to 

ActivityActualStartDate. [BeachIdentifier 

= 'X'; ActivityName = 'X'; 

ActivityActualStartDate = 'X'; 

ActivityActualStopDate = 'X'] 

You are attempting to submit an Activity whose stop

date occurred before it was started. Please correct the 

dates so the stop date is after the start date. 

BCH-0801 BeachRoleTypeCode is invalid. 

[BeachIdentifier = 'X'; 

BeachRoleOrganizationIdentifier = 'X'; 

BeachRoleTypeCode = 'X'] 

A value unknown to the PRAWN system has been 

submitted for BeachRoleTypeCode. Please see 

Chapter 3 for a list of valid values. 

BCH-0802 BeachRoleOrganizationIdentifier not 

found in the PRAWN system. 

[BeachIdentifier = 'X'; 

BeachRoleOrganizationIdentifier = 'X'] 

You are attempting to associate a role with an 

Organization that does not exist in the PRAWN 

system. Please confirm that you have entered the 

correct Organization Identifier and that the information 

for that Organization has been previously submitted

and successfully processed by the PRAWN system. 
Beach Notification Database User Guide July 21, 2010 

43 

Error Code Error Message Description/Corrective Action 

BCH-0803 BeachRolePersonIdentifier not found in 

the PRAWN system. [BeachIdentifier = 

'X'; BeachRoleOrganizationIdentifier = 

'X'; BeachRolePersonIdentifier = 'X'] 

You are attempting to associate a role with a person 

that does not exist in the PRAWN system. Please 

confirm that you have entered the correct Person 

Identifier and that the information for that Person has 

been previously submitted and successfully processed 

by the PRAWN system. 

BCH-0804 BeachRolePersonIdentifiercannot be 

assigned a role on a beach without a role 

assignment for the person's parent 

organization on the same beach. 

[BeachIdentifier = 'X'; 

BeachRoleOrganizationIdentifier = 'X'; 

BeachRolePersonIdentifier = 'X'] 

You are attempting to associate a Person with a 

Beach without having associated that Person’s 

Organization to the beach. Please check that the 

Organization Role Information precedes the Person 

Role Information in the XML file. 

BCH-0901 ProcedureIdentifier must be unique for 

adding a Procedure to the PRAWN 

system. [ProcedureIdentifier = 'X'] 

All new Procedure records must have a value for 

Procedure Identifier that is previously unused by the 

referenced Organization in the PRAWN system. 

To update an existing Procedure, including assigning 

more beaches to the Procedure, change the 

ProcedureTypeCode to ‘EDIT’. 

BCH-0902 ProcedureIdentifier not found in the 

PRAWN system. [ProcedureIdentifier = 

'X'] 

You are attempting to edit a record that does not exist. 

Please confirm that you have entered the correct 

Procedure Identifier for the record you are attempting 

to edit or change ProcedureTransactionType to add if 

you wish to create a new Procedure record. 

BCH-0903 ProcedureTypeCode is invalid. 

[ProcedureIdentifier = 'X'; 

ProcedureTypeCode = 'X'] 

A value unknown to the PRAWN system has been 

submitted for ProcedureTypeCode. Please see Error! 

Reference source not found. for a list of valid 

values. 

BCH-0904 ProcedureBeachIdentifier not found in 

the PRAWN system. [ProcedureIdentifier 

= 'X'; ProcedureBeachIdentifier = 'X'] 

You are attempting to associate a procedure with a 

beach that does not exist in the PRAWN system. 

Please confirm that you have entered the correct 

Beach Identifier and that the information for that 

Beach has been previously submitted and 

successfully processed by the PRAWN system. 

4.2 Common Causes of Error Messages 

When troubleshooting an error log returned by the PRAWN system, please refer to the following 

chart for help with some of the most common errors (full-text error messages can be found in 

section Error! Reference source not found.). If the error is not resolved following the 

suggestions below, please contact ebeaches@cgifederal.com. 
Beach Notification Database User Guide July 21, 2010 

44 

Exhibit 4-2 Common Error Messages 

Error Code Troubleshooting Tip Page(s) 

BCH-0101 Please check the value of the OrganizationNameTransactionTypeCode tag 

(ORGANIZATION.TRANSACTION in the Notification Access Database). Generally, 

this error occurs if the related OrganizationId already exists in PRAWN and has 

been submitted with an OrganizationNameTransactionTypeCode of ADD. 

N/A 

BCH-0102 Please check the value of the OrganizationNameTransactionTypeCode tag 

(ORGANIZATION.TRANSACTION in the Notification Access Database). Generally, 

this error occurs if the related OrganizationId does not yet exist in PRAWN and has 

been submitted with an OrganizationNameTransactionTypeCode of EDIT. 

N/A 

BCH-0103 Please check the value of the OrganizationTypeCode tag 

(ORGANIZATION.ORGANIZATION_CODE in the Notification Access Database). 

Generally, this error is the result of a misspelling in of one of the valid values used to 

indicate Organization Type (most often 'STATE_AGENCY' is input instead of 

'STATE_AGNCY', which is the correct value). Please see Chapter Error! Reference 

source not found. for additional information. 

6 

BCH-0201 Please check the value of the PersonNameTransactionTypeCode tag 

(PERSON.TRANSACTION in the Notification Access Database). Generally, this 

error occurs if the related PersonId already exists in PRAWN and has been 

submitted with an PersonNameTransactionTypeCode of ADD. 

N/A 

BCH-0202 Please check the value of the PersonNameTransactionTypeCode tag 

(PERSON.TRANSACTION in the Notification Access Database). Generally, this 

error occurs if the related PersonId does not yet exist in PRAWN and has been 

submitted with an PersonNameTransactionTypeCode of EDIT. 

N/A 

BCH-0301 Please check the value of the MailingAddressTypeCode tag 

(MAILING_ADDRESS.MAILING_ADDRESS_CODE in the Notification Access 

Database). Generally, this error is the result of a misspelling in of one of the valid 

values used to indicate Mailing Address Type. Please see Chapter Error! 

Reference source not found. for additional information. 

7, 12 

BCH-0302 Please check the value of the MailingAddressStateCode tag 

(MAILING_ADDRESS.STATE_POSTAL_CODE in the Notification Access 

Database). Generally, this error is the result of a misspelling in of one of the valid 

values used to indicate the correct state. Please confirm that a valid state code is 

being used. 

7, 13 

BCH-0303 Please check the value of the MailingAddressZipCode tag 

(MAILING_ADDRESS.ZIP_CODE in the Notification Access Database). Generally, 

this error is the result of an incorrectly formatted Zip Code. The correct formats are 

either '#####' (ZIP) or '#####-####' (ZIP+4). Please see Chapter Error! Reference 

source not found. for additional information. 

8, 13 

BCH-0401 Please check the value of the ElectronicAddressTypeCode tag 

(ELECTRONIC_ADDRESS.ELECTRONIC_ADDRESS_CODE in the Notification 

Access Database). Generally, this error is the result of a misspelling in of one of the 

valid values used to indicate Electronic Address Type Please see Chapter Error! 

Reference source not found. for additional information. 

8, 13 

BCH-0501 Please check the value of the TelephoneNumber tag 

(TELEPHONE.TELEPHONE_NUMBER in the Notification Access Database). 

Generally, this error is the result of an incorrectly formatted telephone number. The 

correct format is 'XXX-XXX-XXXX'. Please see Chapter Error! Reference source 

not found. for additional information. 

9, 14 
Beach Notification Database User Guide July 21, 2010 

45 

Error Code Troubleshooting Tip Page(s) 

BCH-0502 Please check the value of the TelephoneTypeCode tag 

(TELEPHONE.TELEPHONE_CODE in the Notification Access Database). 

Generally, this error is the result of a misspelling in of one of the valid values used to 

indicate Telephone Type. Please see Chapter Error! Reference source not found.

for additional information. 

9, 14 

BCH-0601 Please check the value of the ProgramInterestStateCode tag 

(BEACH.STATE_POSTAL_CODE in the Notification Access Database). Generally, 

this error is the result of a misspelling in of one of the valid values used to indicate 

the correct state. Please confirm that a valid state code is being used. 

16 

BCH-0602 Please check the value of the BeachNameTransactionTypeCode tag 

(BEACH.TRANSACTION in the Notification Access Database). Generally, this error 

occurs if the related BeachId already exists in PRAWN and has been submitted with 

a BeachNameTransactionTypeCode of ADD. 

N/A 

BCH-0603 Please check the value of the BeachNameTransactionTypeCode tag 

(BEACH.TRANSACTION in the Notification Access Database). Generally, this error 

occurs if the related BeachId has been registered with the EPA, but has not yet 

been submitted to PRAWN, and has been submitted with a 

BeachNameTransactionTypeCode of EDIT. 

N/A 

BCH-0604 Please check the value of the BeachIdentifier tag (BEACH.ID in the Notification 

Access Database). Generally, this error occurs if the related BeachId has not yet 

been registered with the EPA, or has been misspelled in the submission. 

16 

BCH-0605 Please check the value of the ProgramInterestFIPSCountyCode tag 

(BEACH.FIPS_COUNTY in the Notification Access Database). Generally, this error 

is the result of a misspelling in the standard 5-digit FIPS County Code. Please 

confirm that the correct FIPS Code is being used. 

17 

BCH-0606 Please check the value of the WaterBodyNameCode tag 

(BEACH.WATERBODY_NAME in the Notification Access Database) and the 

WaterBodyTypeCode tag (BEACH.WATERBODY_TYPE in the Notification Access 

Database). Generally, this error is the result of a misspelling in of one of the valid 

values used to indicate Water Body Name or Water Body Type. Please see 

Appendix D in the Beach Notification Data User Guide for additional information. 

17 

BCH-0607 Please check the value of the appropriate tag: ExtentLengthMeasure 

(BEACH_ATTRIBUTE.EXTENT_LENGTH in the Notification Access Database), 

SwimSeasonLengthMeasure (BEACH_ATTRIBUTE.SWIM_SEASON_LENGTH in 

the Notification Access Database), SwimSeasonFrequencyMeasure 

(BEACH_ATTRIBUTE.SWIM_MONITOR_FREQ in the Notification Access 

Database), OffSeasonFrequencyMeasure 

(BEACH_ATTRIBUTE.OFF_MONITOR_FREQ in the Notification Access Database) 

for the related year (AttributeEffectiveYear, 

BEACH_ATTRIBUTE.EFFECTIVE_YEAR in the Notification Access Database). 

Beach Attribute data (Beach Extent/Swim Season/Monitoring Frequencies) has 

already been submitted for this calendar year. If this is incorrect, or you have 

questions, please contact eBeaches@cgifederal.com. 

19, 20, 22 

BCH-0701 Please check the value of the ActivityTypeCode tag 

(BEACH_ACTIVITY.ACTIVITY_CODE in the Notification Access Database). 

Generally, this error is the result of a misspelling in of one of the valid values used to 

indicate Activity Type. Please check Chapter 3 and Appendix B in the Beach 

Notification Data User Guide for additional information. 

26 
Beach Notification Database User Guide July 21, 2010 

46 

Error Code Troubleshooting Tip Page(s) 

BCH-0702 Please check the value of the ActivityMonitoringStationIdentifier tag 

(BEACH_ACTIVITY_STATION.STATION_ID in the Notification Access Database). 

Generally, this error occurs if the related StationId has not been properly formatted 

("OrgId|StationId"), has not yet been registered with STORET, or has been 

misspelled in the submission. 

29 

BCH-0703 Please check the value of the ActivityMonitoringStationIdentifier tag 

(BEACH_ACTIVITY_STATION.STATION_ID in the Notification Access Database). 

Generally, this error occurs if the related StationId has been omitted, but has also 

been known to occur if a BCH-0702 error (incorrectly formatted StationId) has 

occurred in the same submission. 

29 

BCH-0704 If the ActivityReasonType (BEACH_ACTIVITY_REASON.TYPE in the Notification 

Access Database where BEACH_ACTIVITY_REASON.CLASS = Reason), 

ActivitySourceType (BEACH_ACTIVITY_REASON.TYPE in the Notification Access 

Database where BEACH_ACTIVITY_REASON.CLASS = Source), or 

ActivityIndicatorType (BEACH_ACTIVITY_REASON.TYPE in the Notification 

Access Database where BEACH_ACTIVITY_REASON.CLASS = Indicator) are 

equal to OTHER, the corresponding description field must be filled in. 

27, 28, 29 

BCH-0705 The ActivityActualStartDate (BEACH_ACTIVITY.ACTUAL_START_DATE in the 

Notification Access Database) year does not match the ActivityActualStopDate ( in 

the Notification Access Database) year. Activities can only occur during one 

calendar year. In the event that an event does cross into another year, it must be 

split into two activities, one for each year. 

27 

BCH-0706 ActivityActualStartDate (BEACH_ACTIVITY.ACTUAL_START_DATE in the 

Notification Access Database) occurs after the ActivityActualStopDate ( in the 

Notification Access Database). The order of these dates must be reversed in order 

to achieve a successful submission. 

27 

BCH-0801 Please check the value of the BeachRoleTypeCode tag 

(BEACH_ORGANIZATION_ROLE_ASSIGN.ORG_ROLE_CODE and 

BEACH_PERSON_ROLE_ASSIGN.PERSON_ROLE_CODE in the Notification 

Access Database). Generally, this error is the result of a misspelling in of one of the 

valid values used to indicate Beach Role Type. Please check Chapter 3 in the 

Beach Notification Data User Guide for additional information. 

32 

BCH-0802 Please check that the OrganizationIdentifier (ORGANIZATION.ID in the Notification 

Access Database) has already been submitted to PRAWN. Generally this error 

occurs if the Organization in question does not already exist in PRAWN, but has 

also been known to occur if BCH-0101, BCH-0102, and/or BCH-0103 errors (related 

OrganizationIds) have occurred in the same submission. 

6 

BCH-0803 Please check that the PersonIdentifier (PERSON.ID in the Notification Access 

Database) has already been submitted to PRAWN. Generally this error occurs if the 

Person in question does not already exist in PRAWN, but has also been known to 

occur if BCH-0201 and/or BCH-0202 errors (related PersonIds) have occurred in the 

same submission. 

11 

BCH-0804 Please check the order of the Organization and Person assignments on a given 

beach. Persons cannot be assigned a role on a beach until the Organization they 

belong to has been assigned a role on that beach. 

33 

BCH-0901 Please check the value of the ProcedureTransactionTypeCode tag 

(PROCEDURE.TRANSACTION in the Notification Access Database). Generally, 

this error occurs if the related ProcedureId already exists in PRAWN and has been 

submitted with an ProcedureTransactionTypeCode of ADD. 

N/A 
Beach Notification Database User Guide July 21, 2010 

47 

Error Code Troubleshooting Tip Page(s) 

BCH-0902 Please check the value of the ProcedureTransactionTypeCode tag 

(PROCEDURE.TRANSACTION in the Notification Access Database). Generally, 

this error occurs if the related OrganizationId does not yet exist in PRAWN and has 

been submitted with an ProcedureTransactionTypeCode of EDIT. 

N/A 

BCH-0903 Please check the value of the ProcedureTypeCode tag 

(PROCEDURE.PROCEDURE_CODE in the Notification Access Database). 

Generally, this error is the result of a misspelling in of one of the valid values used to 

indicate Procedure Type. Please see Appendix C in the Beach Notification Data 

User Guide for additional information. 

37 

BCH-0904 Please check to be sure that the BeachId listed in the ProcedureBeachIdentifier tag 

(BEACH_PROCEDURE_ASSIGN.FK_BEACH_ID in the Notification Access 

Database) has been entered into PRAWN. Generally, this error occurs if the related 

BeachId has not yet been submitted to PRAWN, but an association between a 

procedure and the related BeachId has been submitted. 

37 

4.3 Oracle Generated Error Messages 

In addition to error messages generated by the PRAWN system, it is also possible that Oracle 

specific errors may occur during XML processing. These errors would most likely be associated 

with the administration and maintenance of the Oracle database instance (for example, exceeding 

the allocated table space size). Oracle specific errors will be captured by the XML data loading 

software and reported in the Error Log File together with the PRAWN system generated errors 

(see Section Error! Reference source not found. Error! Reference source not found.). Oracle 

specific errors will be prefixed with the text ‘Oracle Error:’ and will contain the error message 

number and text produced by the Oracle database at the time the error occurred. 
Beach Notification Database User Guide July 21, 2010 

48 

5 How to Understand Beaches that are Similar Points of Access 

This chapter provides detailed information regarding similar points of access. This chapter 

assumes that the XML submission has passed XML schema validation before being processed by 

the data loading software. 

1. Enter Beach Information and Beach Attribute Information prior to Beach Extent Length, go to 

step 2.

2. Is this entry a SPA? If yes, you may enter an actual length that does not exceed: 100 ft. If no go to 

step 3.

3. Enter Beach Extent Length (note: a separate length will be calculated from your L/L data as 

indexed to the RAD to enable mapping and for allotment formula calculations.)

4. Enter Swim Season Monitoring Frequency and so on.
Beach Notification Database User Guide July 21, 2010 

49 

6 Appendix A—Schema Graphics 

This appendix provides a graphical representation of the Beaches Notification v2.0 XML 

Schema. The figures that follow offer an expanded view of each of the four major sections that 

comprise a Beach Data Submission (Organization Detail, Person Detail, Beach Detail, and Beach 

Procedure Detail). 

• Dashed lines represented optional elements, solid lines represent mandatory elements. 

o Please note: Empty tags (e.g., <BeachIdentifier></BeachIdentifier>) for optional 

elements cannot appear in the XML file. 

• The figures 0..∞ and 1..∞ mean that the field may be repeated, as long as the repetitions 

are next to each other, as many times as the user wishes. 

o For example, a user may submit as many BeachDetail sections as necessary in a 

single file. 

o 1..∞ means that there must be at least one field included and 0..∞ means the field 

is entirely optional. 

• A + sign at the end of the box means more elements exist under that element. 

Exhibit 6-1 Beach Data Submission 
Beach Notification Database User Guide July 21, 2010 

50 

Exhibit 6-2 Organization Detail 
Beach Notification Database User Guide July 21, 2010 

51 

Exhibit 6-3 Organization Person Detail 
Beach Notification Database User Guide July 21, 2010 

52 

Exhibit 6-4 Beach Name Detail 
Beach Notification Database User Guide July 21, 2010 

53 

Exhibit 6-5 Beach Attribute Detail 
Beach Notification Database User Guide July 21, 2010 

54 

Exhibit 6-5 Beach Activity Detail 
Beach Notification Database User Guide July 21, 2010 

55 

Exhibit 6-6 Beach Role Detail 

Exhibit 6-7 Beach Coordinate Detail 
Beach Notification Database User Guide July 21, 2010 

56 

Exhibit 6-8 Beach Procedure Detail 

Exhibit 6-9 Year Completion Indicators 
Beach Notification Database User Guide July 21, 2010 

57 

7 Appendix B—Example XML File 

The following is text from an example XML file that would be sent to PRAWN from a State. 

The file appears with spacing to provide a more clear view of the data. The spacing is not 

required or standard. 

<?xml version="1.0"?> 

<!--Beach Data Submission created 11/15/2006 10:23:56 AM--> 

<BeachDataSubmission xsi:schemaLocation="http://www.exchangenetwork.net/schema/BEACHES/2 

index.xsd" xmlns="http://www.exchangenetwork.net/schema/BEACHES/2" 

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 

 <OrganizationDetail> 

 <OrganizationIdentifier>2349fwe</OrganizationIdentifier> 

 <OrganizationNameDetail> 

 <OrganizationTypeCode>PRIVATE</OrganizationTypeCode> 

 <OrganizationName>Tested</OrganizationName> 

 <OrganizationDescriptionText>Testeddesc</OrganizationDescriptionText> 

 <OrganizationAbbreviationText>TD</OrganizationAbbreviationText> 

 </OrganizationNameDetail> 

 <OrganizationMailingAddressDetail> 

 <MailingAddressTypeCode>MAILING</MailingAddressTypeCode> 

 <MailingAddressStreetLine1Text>123 Long 

Drive</MailingAddressStreetLine1Text> 

 <MailingAddressStreetLine2Text>Suite 534</MailingAddressStreetLine2Text> 

 <MailingAddressStreetLine3Text>The Last 

Stop</MailingAddressStreetLine3Text> 

 <MailingAddressCityName>Testerville</MailingAddressCityName> 

 <StateCode>VA</StateCode> 

 <AddressPostalCode>45387</AddressPostalCode> 

 <MailingAddressEffectiveDate>2002-05-05T12:00:00-

05:00</MailingAddressEffectiveDate> 

 <MailingAddressStatusIndicator>ACTIVE</MailingAddressStatusIndicator> 

 </OrganizationMailingAddressDetail> 

 <OrganizationElectronicAddressDetail> 

 <ElectronicAddressTypeCode>EMAIL</ElectronicAddressTypeCode> 

 <ElectronicAddressText>my@my.com</ElectronicAddressText> 

 <ElectronicAddressEffectiveDate>2001-01-

01T00:00:00</ElectronicAddressEffectiveDate> 

 

 <ElectronicAddressStatusIndicator>ACTIVE</ElectronicAddressStatusIndicator> 

 </OrganizationElectronicAddressDetail> 

 <OrganizationTelephoneDetail> 

 <TelephoneTypeCode>VOICE</TelephoneTypeCode> 

 <TelephoneNumberText>123-456-7890</TelephoneNumberText> 

 <TelephoneEffectiveDate>2001-01-01T00:00:00-05:00</TelephoneEffectiveDate> 

 <TelephoneStatusIndicator>ACTIVE</TelephoneStatusIndicator> 

 </OrganizationTelephoneDetail> 

 <OrganizationPersonDetail> 

 <PersonIdentifier>9e8ef7</PersonIdentifier> 

 <PersonNameDetail> 

 <PersonStatusIndicator>ACTIVE</PersonStatusIndicator> 

 <FirstName>Johnny</FirstName> 

 <LastName>Jones</LastName> 

 <PersonMiddleInitial>J</PersonMiddleInitial> 

 <NameSuffixText>Jr</NameSuffixText> 

 <NamePrefixText>Mr.</NamePrefixText> 

 </PersonNameDetail> 

 <PersonMailingAddressDetail> 

 <MailingAddressTypeCode>MAILING</MailingAddressTypeCode> 

 <MailingAddressStreetLine1Text>830 My 

Drive</MailingAddressStreetLine1Text> 

 <MailingAddressStreetLine2Text>Suite 

223</MailingAddressStreetLine2Text> 

 <MailingAddressStreetLine3Text>The last 

row</MailingAddressStreetLine3Text> 

 <MailingAddressCityName>The Big House</MailingAddressCityName> 
Beach Notification Database User Guide July 21, 2010 

58 

 <StateCode>VA</StateCode> 

 <AddressPostalCode>27886</AddressPostalCode> 

 <MailingAddressEffectiveDate>2001-01-01T12:00:00-

05:00</MailingAddressEffectiveDate> 

 

 <MailingAddressStatusIndicator>ACTIVE</MailingAddressStatusIndicator> 

 </PersonMailingAddressDetail> 

 <PersonElectronicAddressDetail> 

 <ElectronicAddressTypeCode>EMAIL</ElectronicAddressTypeCode> 

 

 <ElectronicAddressText>agnes.flemming@vdh.virginia.gov</ElectronicAddressText> 

 <ElectronicAddressEffectiveDate>2001-01-01T12:00:00-

05:00</ElectronicAddressEffectiveDate> 

 

 <ElectronicAddressStatusIndicator>ACTIVE</ElectronicAddressStatusIndicator> 

 </PersonElectronicAddressDetail> 

 <PersonTelephoneDetail> 

 <TelephoneTypeCode>VOICE</TelephoneTypeCode> 

 <TelephoneNumberText>617-254-0845</TelephoneNumberText> 

 <TelephoneEffectiveDate>2001-01-

01T00:00:00</TelephoneEffectiveDate> 

 <TelephoneStatusIndicator>ACTIVE</TelephoneStatusIndicator> 

 </PersonTelephoneDetail> 

 </OrganizationPersonDetail> 

 </OrganizationDetail> 

 <OrganizationDetail> 

 <OrganizationIdentifier>394e785</OrganizationIdentifier> 

 <OrganizationNameDetail> 

 <OrganizationTypeCode>LOCAL_GOV</OrganizationTypeCode> 

 <OrganizationName>testing</OrganizationName> 

 <OrganizationDescriptionText>testingdesc</OrganizationDescriptionText> 

 <OrganizationAbbreviationText>T</OrganizationAbbreviationText> 

 </OrganizationNameDetail> 

 <OrganizationPersonDetail> 

 <PersonIdentifier>foi34e0</PersonIdentifier> 

 <PersonNameDetail> 

 <PersonStatusIndicator>ACTIVE</PersonStatusIndicator> 

 <FirstName>Chris</FirstName> 

 <LastName>Johnson</LastName> 

 <NamePrefixText>Manager</NamePrefixText> 

 </PersonNameDetail> 

 </OrganizationPersonDetail> 

 <OrganizationPersonDetail> 

 <PersonIdentifier>JH</PersonIdentifier> 

 <PersonNameDetail> 

 <PersonStatusIndicator>ACTIVE</PersonStatusIndicator> 

 <FirstName>Jill</FirstName> 

 <LastName>Holander</LastName> 

 </PersonNameDetail> 

 <PersonElectronicAddressDetail> 

 <ElectronicAddressTypeCode>EMAIL</ElectronicAddressTypeCode> 

 <ElectronicAddressText>my@my.com</ElectronicAddressText> 

 <ElectronicAddressEffectiveDate>2001-01-

01T00:00:00</ElectronicAddressEffectiveDate> 

 

 <ElectronicAddressStatusIndicator>ACTIVE</ElectronicAddressStatusIndicator> 

 </PersonElectronicAddressDetail> 

 </OrganizationPersonDetail> 

 </OrganizationDetail> 

 <BeachDetail> 

 <BeachIdentifier>AK162093</BeachIdentifier> 

 <BeachNameDetail> 

 <ProgramInterestName>Demo Beach</ProgramInterestName> 

 <ProgramInterestDescriptionText>For 

Demonstration</ProgramInterestDescriptionText> 

 <ProgramInterestCommentText>Delete this 

record.</ProgramInterestCommentText> 

 <ProgramInterestStateCode>NV</ProgramInterestStateCode> 

 <ProgramInterestFIPSCountyCode>21000</ProgramInterestFIPSCountyCode> 

 <WaterBodyNameCode>ATLANTIC</WaterBodyNameCode> 

 <WaterBodyTypeCode>OPEN_COAST</WaterBodyTypeCode> 
Beach Notification Database User Guide July 21, 2010 

59 

 <BeachAccessibilityDetail> 

 <BeachAccessibilityType>PUB_PUB_ACC</BeachAccessibilityType> 

 <BeachAccessibilityComment>Test 

Comment.</BeachAccessibilityComment> 

 </BeachAccessibilityDetail> 

 </BeachNameDetail> 

 <BeachAttributeDetail> 

 <AttributeEffectiveYear>2002</AttributeEffectiveYear> 

 <BeachExtentDetail> 

 <ExtentLengthMeasure>28.45</ExtentLengthMeasure> 

 <ExtentUnitOfMeasureCode>MI</ExtentUnitOfMeasureCode> 

 </BeachExtentDetail> 

 <BeachSwimSeasonLengthDetail> 

 <SwimSeasonStartDate>2001-05-01</SwimSeasonStartDate> 

 <SwimSeasonEndDate>2001-09-30</SwimSeasonEndDate> 

 </BeachSwimSeasonLengthDetail> 

 <!-- Although discouraged, BeachSwimSeason is also allowed to be in the 

form 

 <BeachSwimSeasonLengthDetail> 

 <SwimSeasonLengthMeasure>3</SwimSeasonLengthMeasure> 

 <SwimSeasonUnitOfMeasureCode>MONTHS</SwimSeasonUnitOfMeasureCode> 

 </BeachSwimSeasonLengthDetail> 

 --> 

 <MonitoringFrequencyDetail> 

 <SwimSeasonFrequencyMeasure>3</SwimSeasonFrequencyMeasure> 

 <OffSeasonFrequencyMeasure>1</OffSeasonFrequencyMeasure> 

 

 <MonitoringFrequencyUnitOfMeasureCode>PER_WEEK</MonitoringFrequencyUnitOfMeasureCode> 

 <MonitoredIrregularly>true</MonitoredIrregularly> 

 <MonitoredIrregularlyComment>This beach is also monitored whenever 

there is heavy rain.</MonitoredIrregularlyComment> 

 </MonitoringFrequencyDetail> 

 <!-- 

 <MonitoringFrequencyDetail> 

 <MonitoredIrregularly>true</MonitoredIrregularly> 

 </MonitoringFrequencyDetail> 

 --> 

 <BeachPollutionSourceDetail> 

 <BeachPollutionSource> 

 <BeachPollutionSourceCode>CSO</BeachPollutionSourceCode> 

 <BeachPollutionSourceDescription>Comment for 

CSO</BeachPollutionSourceDescription> 

 </BeachPollutionSource> 

 <BeachPollutionSource> 

 <BeachPollutionSourceCode>POTW</BeachPollutionSourceCode> 

 <BeachPollutionSourceDescription>Comment for 

POTW</BeachPollutionSourceDescription> 

 </BeachPollutionSource> 

 <!-- 

 

 <NoPollutionSourcesIndicator>true</NoPollutionSourcesIndicator> 

 

 

 <PollutionSourcesUninvestigatedIndicator>true</PollutionSourcesUninvestigatedIndicator> 

 

 --> 

 </BeachPollutionSourceDetail> 

 <BeachTierRanking>3</BeachTierRanking> 

 <BeachActBeachIndicator>true</BeachActBeachIndicator> 

 </BeachAttributeDetail> 

 <BeachActivityDetail> 

 <ActivityTypeCode>CLOSURE</ActivityTypeCode> 

 <ActivityName>Demo Activity 1</ActivityName> 

 <ActivityActualStartDate>2002-01-01T08:30:00</ActivityActualStartDate> 

 <ActivityActualStopDate>2003-01-01T23:59:59</ActivityActualStopDate> 

 <ActivityReasonDetail> 

 <ActivityReasonType>ELEV_BACT</ActivityReasonType> 

 <ActivityReasonDescriptionText>Demo 

Description</ActivityReasonDescriptionText> 

 </ActivityReasonDetail> 

 <ActivitySourceDetail> 
Beach Notification Database User Guide July 21, 2010 

60 

 <ActivitySourceType>SEWER_LINE</ActivitySourceType> 

 <ActivitySourceDescriptionText>Shut her down Clancy, she's pumpin' 

mud!</ActivitySourceDescriptionText> 

 </ActivitySourceDetail> 

 <ActivityIndicatorDetail> 

 <ActivityIndicatorType>OTHER</ActivityIndicatorType> 

 <ActivityIndicatorDescriptionText>Demo Description 

2</ActivityIndicatorDescriptionText> 

 </ActivityIndicatorDetail> 

 

 <ActivityMonitoringStationIdentifier>NV004|rs001</ActivityMonitoringStationIdentifier> 

 

 <ActivityMonitoringStationIdentifier>NV004|rs002</ActivityMonitoringStationIdentifier> 

 <ActivityDescriptionText>Demo activity 

description</ActivityDescriptionText> 

 <ActivityCommentText>Demo</ActivityCommentText> 

 <ActivityExtentDetail> 

 <ActivityExtentStartMeasure>4</ActivityExtentStartMeasure> 

 <ActivityExtentLengthMeasure>16</ActivityExtentLengthMeasure> 

 

 <ActivityExtentUnitOfMeasureCode>MI</ActivityExtentUnitOfMeasureCode> 

 </ActivityExtentDetail> 

 </BeachActivityDetail> 

 <BeachRoleDetail> 

 <BeachRoleTypeCode>COLLECTOR</BeachRoleTypeCode>

 <BeachRoleOrganizationIdentifier>2349fwe</BeachRoleOrganizationIdentifier> 

 <BeachRolePersonIdentifier>SD</BeachRolePersonIdentifier> 

 <BeachRoleEffectiveDate>2001-01-01T00:00:00</BeachRoleEffectiveDate> 

 <BeachRoleStatusIndicator>ACTIVE</BeachRoleStatusIndicator> 

 </BeachRoleDetail> 

 <BeachRoleDetail> 

 <BeachRoleTypeCode>ANALYZER</BeachRoleTypeCode> 

 <BeachRoleOrganizationIdentifier>394e785</BeachRoleOrganizationIdentifier> 

 <BeachRoleEffectiveDate>2006-01-01T00:00:00</BeachRoleEffectiveDate> 

 <BeachRoleStatusIndicator>ACTIVE</BeachRoleStatusIndicator> 

 </BeachRoleDetail> 

 <BeachRoleDetail> 

 <BeachRoleTypeCode>ANALYZER</BeachRoleTypeCode> 

 <BeachRoleOrganizationIdentifier>394e785</BeachRoleOrganizationIdentifier> 

 <BeachRolePersonIdentifier>JH</BeachRolePersonIdentifier> 

 <BeachRoleEffectiveDate>2001-01-01T00:00:00</BeachRoleEffectiveDate> 

 <BeachRoleStatusIndicator>ACTIVE</BeachRoleStatusIndicator> 

 </BeachRoleDetail> 

 </BeachDetail> 

 <BeachDetail> 

 <BeachIdentifier>AK177449</BeachIdentifier> 

 <BeachNameDetail> 

 <ProgramInterestName>test</ProgramInterestName> 

 <ProgramInterestDescriptionText>test</ProgramInterestDescriptionText> 

 <ProgramInterestCommentText>test</ProgramInterestCommentText> 

 <ProgramInterestStateCode>NV</ProgramInterestStateCode> 

 <ProgramInterestFIPSCountyCode>21000</ProgramInterestFIPSCountyCode> 

 <WaterBodyNameCode>ATLANTIC</WaterBodyNameCode> 

 <WaterBodyTypeCode>OPEN_COAST</WaterBodyTypeCode> 

 <BeachAccessibilityDetail> 

 <BeachAccessibilityType>PUB_PUB_ACC</BeachAccessibilityType> 

 <BeachAccessibilityComment>Test 

Comment.</BeachAccessibilityComment> 

 </BeachAccessibilityDetail> 

 </BeachNameDetail> 

 <BeachRoleDetail> 

 <BeachRoleTypeCode>TESTOR</BeachRoleTypeCode> 

 <BeachRoleOrganizationIdentifier>394e785</BeachRoleOrganizationIdentifier> 

 <BeachRolePersonIdentifier>foi34e0</BeachRolePersonIdentifier> 

 <BeachRoleEffectiveDate>2001-01-01T00:00:00</BeachRoleEffectiveDate> 

 <BeachRoleStatusIndicator>ACTIVE</BeachRoleStatusIndicator> 

 </BeachRoleDetail> 

 <BeachCoordinateDetail> 

 <BeachCoordinateStartPointDetail> 

 <LatitudeMeasure>34.141592</LatitudeMeasure> 

 <LongitudeMeasure>-74.141592</LongitudeMeasure>
Beach Notification Database User Guide July 21, 2010 

61 

 <SourceMapScaleNumeric>12500</SourceMapScaleNumeric> 

 <HorizontalCollectionMethodName>INTERPOLATIONMAP</HorizontalCollectionMethodName> 

 

 <HorizontalCoordinateReferenceSystemDatumName>NAD27</HorizontalCoordinateReferenceSystemD

atumName> 

 </BeachCoordinateStartPointDetail> 

 <BeachCoordinateEndPointDetail> 

 <LatitudeMeasure>36.564398</LatitudeMeasure> 

 <LongitudeMeasure>-44.124812</LongitudeMeasure>

 <SourceMapScaleNumeric>12500</SourceMapScaleNumeric> 

 <HorizontalCollectionMethodName>INTERPOLATIONMAP</HorizontalCollectionMethodName> 

 

 <HorizontalCoordinateReferenceSystemDatumName>NAD27</HorizontalCoordinateReferenceSystemD

atumName> 

 </BeachCoordinateEndPointDetail> 

 <BeachCoordinateDescriptionText>Short 

description.</BeachCoordinateDescriptionText> 

 </BeachCoordinateDetail> 

 </BeachDetail> 

 <BeachProcedureDetail> 

 <ProcedureTypeCode>DA_ASES_RISK</ProcedureTypeCode> 

 <ProcedureDescriptionText>Our Procedure to Assess Risk</ProcedureDescriptionText> 

 <ProcedureIdentifier>PRESS_RELEAS</ProcedureIdentifier> 

 <ProcedureBeachIdentifier>AK162093</ProcedureBeachIdentifier> 

 <ProcedureBeachIdentifier>AK162093</ProcedureBeachIdentifier> 

 </BeachProcedureDetail> 

 <YearCompletionIndicators> 

 <CompletionYear>2008</CompletionYear> 

 <NotificiationDataCompleteIndicator>true</NotificiationDataCompleteIndicator> 

 <MonitoringDataCompleteIndicator>true</MonitoringDataCompleteIndicator> 

 <LocationDataCompleteIndicator>true</LocationDataCompleteIndicator> 

 </YearCompletionIndicators> 

</BeachDataSubmission> 
Beach Notification Database User Guide July 21, 2010 

62 

8 Appendix C—Procedure Type Codes 

Due to the large number of Procedure Type codes, this appendix provides a separate table to 

explain the acceptable codes. See Section Error! Reference source not found. for a description 

of when to use these codes in the XML schema. 

Code Name Description 

DA_ASES_RISK ADVISORY: 

Assess risk 

Assess risks to potential swimmers 

DA_ASES_SICK ADVISORY: 

Asses 

sickness 

Assess number of complaints of sickness 

DA_DIS_AGNCY ADVISORY: 

Discuss with 

agencies 

Discuss situation with other agencies 

DA_PRECAUTN ADVISORY: 

Precautionary 

Perform a precautionary closing in response to hazardous discharges 

DA_PREEMPTVE ADVISORY: 

Preemptive 

Compare conditions to preemptive closing criteria 

DA_WTR_STAND ADVISORY: 

Compare with 

water 

standards 

Compare bacterial concentrations with water quality standards to determine 

whether standards are exceeded 

DA_W_Q_MONTR ADVISORY: 

Water quality 

monitoring 

Perform water quality modeling 

DB_ASES_RISK COMBINED: 

Assess risk 

Assess risks to potential swimmers 

DB_ASES_SICK COMBINED: 

Asses 

sickness 

Assess number of complaints of sickness 

DB_DIS_AGNCY COMBINED: 

Discuss with 

agencies 

Discuss situation with other agencies 

DB_PRECAUTN COMBINED: 

Precautionary 

Perform a precautionary closing in response to hazardous discharges 

DB_PREEMPTVE COMBINED: 

Preemptive 

Compare conditions to preemptive closing criteria 

DB_WTR_STAND COMBINED: 

Compare with 

water 

standards 

Compare bacterial concentrations with water quality standards to determine 

whether standards are exceeded 

DB_W_Q_MONTR COMBINED: 

Water quality 

monitoring 

Perform water quality modeling 
Beach Notification Database User Guide July 21, 2010 

63 

Code Name Description 

DC_ASES_RISK CLOSING: 

Assess risk 

Assess risks to potential swimmers 

DC_ASES_SICK CLOSING: 

Asses 

sickness 

Assess number of complaints of sickness 

DC_DIS_AGNCY CLOSING: 

Discuss with 

agencies 

Discuss situation with other agencies 

DC_PRECAUTN CLOSING: 

Precautionary 

Perform a precautionary closing in response to hazardous discharges 

DC_PREEMPTVE CLOSING: 

Preemptive 

Compare conditions to preemptive closing criteria 

DC_WTR_STAND CLOSING: 

Compare with 

water 

standards 

Compare bacterial concentrations with water quality standards to determine 

whether standards are exceeded 

DC_W_Q_MONTR CLOSING: 

Water quality 

monitoring 

Perform water quality modeling 

IA_BEACH ADVISORY: 

Post at Beach 

Post advisory or closing at the beach 

IA_DIF_AGNCY ADVISORY: 

Different 

Agency(ies) 

Provide announcement to other government agency(ies) 

IA_INTERNAL ADVISORY: 

Internal 

Agency 

Provide announcement to internal agency staff 

IA_INTERNET ADVISORY: 

Post on 

Internet 

Post advisory or closing on the Internet 

IA_NEWSPAPER ADVISORY: 

Newspaper 

article 

Publish advisory or closing in local newspaper 

IA_PHONE ADVISORY: 

Provide phone 

line 

Provide results on hotline/water quality information/result phone line 

IA_PHYS_ISOL ADVISORY: 

Physical 

Isolation 

Physically isolate contaminated area (e.g., block access, fence off area) 

IA_RADIO ADVISORY: 

Radio 

announcement 

Have advisory or closing announced on local radio station 

IA_RESP_PRSN ADVISORY: 

Notify 

responsible 

person 

Notify owner/manager/operator/lifeguards of results
Beach Notification Database User Guide July 21, 2010 

64 

Code Name Description 

IA_TV_ANNCE ADVISORY: 

TV 

announcement 

Have advisory or closing announced on local TV station 

IB_BEACH COMBINED: 

Post at Beach 

Post advisory or closing at the beach 

IB_DIF_AGNCY COMBINED: 

Different 

Agency(ies) 

Provide announcement to other government agency(ies) 

IB_INTERNAL COMBINED: 

Internal 

Agency 

Provide announcement to internal agency staff 

IB_INTERNET COMBINED: 

Post on 

Internet 

Post advisory or closing on the Internet 

IB_NEWSPAPER COMBINED: 

Newspaper 

article 

Publish advisory or closing in local newspaper 

IB_PHONE COMBINED: 

Provide phone 

line 

Provide results on hotline/water quality information/result phone line 

IB_PHYS_ISOL COMBINED: 

Physical 

Isolation 

Physically isolate contaminated area (e.g., block access, fence off area) 

IB_RADIO COMBINED: 

Radio 

announcement 

Have advisory or closing announced on local radio station 

IB_RESP_PRSN COMBINED: 

Notify 

responsible 

person 

Notify owner/manager/operator/lifeguards of results

IB_TV_ANNCE COMBINED: 

TV 

announcement 

Have advisory or closing announced on local TV station 

IC_BEACH CLOSING: 

Post at Beach 

Post advisory or closing at the beach 

IC_DIF_AGNCY CLOSING: 

Different 

Agency(ies) 

Provide announcement to other government agency(ies) 

IC_INTERNAL CLOSING: 

Internal 

Agency 

Provide announcement to internal agency staff 

IC_INTERNET CLOSING: 

Post on 

Internet 

Post advisory or closing on the Internet 
Beach Notification Database User Guide July 21, 2010 

65 

Code Name Description 

IC_NEWSPAPER CLOSING: 

Newspaper 

article 

Publish advisory or closing in local newspaper 

IC_PHONE CLOSING: 

Provide phone 

line 

Provide results on hotline/water quality information/result phone line 

IC_PHYS_ISOL CLOSING: 

Physical 

Isolation 

Physically isolate contaminated area (e.g., block access, fence off area) 

IC_RADIO CLOSING: 

Radio 

announcement 

Have advisory or closing announced on local radio station 

IC_RESP_PRSN CLOSING: 

Notify 

responsible 

person 

Notify owner/manager/operator/lifeguards of results

IC_TV_ANNCE CLOSING: TV 

announcement 

Have advisory or closing announced on local TV station 

MO_BEACH Post at Beach Post results at beach 

MO_DIF_AGNCY Different 

Agency 

Provide results to different agency staff for evaluation 

MO_INTERNAL Internal 

Agency 

Provide results to internal agency staff for evaluation 

MO_INTERNET Post on article Post results on the Internet 

MO_NEWSPAPER Newspaper 

article 

Publish results in local newspaper 

MO_ON_REQUST Provide on 

request 

Provide results to anyone on request 

MO_PHONE Provide phone 

line 

Provide results on hotline/water quality information/results/phone line 

MO_RADIO Radio 

announcement 

Have results announced on local radio station 

MO_RESP_PRSN Notify 

responsible 

person 

Notify owner/manager/operator/lifeguards of results

MO_TV_ANNCE TV 

announcement 

Have results announced on local TV station 

OT_OTHER Other Other 

RA_ASES_RISK ADVISORY: 

Assess risks 

Assess risks to potential swimmers 

RA_ASES_SICK ADVISORY: 

Assess 

sickness 

Assess number of complaints of sickness 
Beach Notification Database User Guide July 21, 2010 

66 

Code Name Description 

RA_BEACH ADVISORY: 

Post at beach 

Post announcement at the beach 

RA_DIF_AGNCY ADVISORY: 

Discuss with 

agencies 

Discuss situation with other agencies 

RA_INTERNAL ADVISORY: 

Agency 

Provide announcement to agency staff 

RA_INTERNET ADVISORY: 

Post on 

Internet 

Post reopening on the Internet 

RA_LOCAL_GOV ADVISORY: 

Local 

government 

Provide announcement to local government staff 

RA_NEWSPAPER ADVISORY: 

Newspaper 

article 

Publish reopening in local newspaper 

RA_PHONE ADVISORY: 

Provide phone 

line 

Provide results on hotline/water quality information/result phone line 

RA_PHYS_ISOL ADVISORY: 

Remove 

physical 

isolation 

Remove physical barriers set when closed 

RA_RADIO ADVISORY: 

Radio 

announcement 

Have reopening announced on local radio station 

RA_RESAMPLE ADVISORY: 

Resample 

Resample and compare bacterial concentrations with water quality standards 

to determine whether levels are below 

RA_RESP_PRSN ADVISORY: 

Notify 

responsible 

person 

Notify owner/manager/operator/lifeguards of results

RA_STD_RAIN ADVISORY: 

Standard rain 

reopening 

Reopen after a set number of days following rainfall 

RA_TV_ANNCE ADVISORY: 

TV 

announcement 

Have reopening announced on local TV station 

RB_ASES_RISK COMBINED: 

Assess risks 

Assess risks to potential swimmers 

RB_ASES_SICK COMBINED: 

Assess 

sickness 

Assess number of complaints of sickness 

RB_BEACH COMBINED: 

Post at beach 

Post announcement at the beach 
Beach Notification Database User Guide July 21, 2010 

67 

Code Name Description 

RB_DIF_AGNCY COMBINED: 

Discuss with 

agencies 

Discuss situation with other agencies 

RB_INTERNAL COMBINED: 

Agency 

Provide announcement to agency staff 

RB_INTERNET COMBINED: 

Post on 

Internet 

Post reopening on the Internet 

RB_LOCAL_GOV COMBINED: 

Local 

government 

Provide announcement to local government staff 

RB_NEWSPAPER COMBINED: 

Newspaper 

article 

Publish reopening in local newspaper 

RB_PHONE COMBINED: 

Provide phone 

line 

Provide results on hotline/water quality information/result phone line 

RB_PHYS_ISOL COMBINED: 

Remove 

physical 

isolation 

Remove physical barriers set when closed 

RB_RADIO COMBINED: 

Radio 

announcement 

Have reopening announced on local radio station 

RB_RESAMPLE COMBINED: 

Resample 

Resample and compare bacterial concentrations with water quality standards 

to determine whether levels are below 

RB_RESP_PRSN COMBINED: 

Notify 

responsible 

person 

Notify owner/manager/operator/lifeguards of results

RB_STD_RAIN COMBINED: 

Standard rain 

reopening 

Reopen after a set number of days following rainfall 

RB_TV_ANNCE COMBINED: 

TV 

announcement 

Have reopening announced on local TV station 

RC_ASES_RISK CLOSING: 

Assess risks 

Assess risks to potential swimmers 

RC_ASES_SICK CLOSING: 

Assess 

sickness 

Assess number of complaints of sickness 

RC_BEACH CLOSING: 

Post at beach 

Post announcement at the beach 

RC_DIF_AGNCY CLOSING: 

Discuss with 

agencies 

Discuss situation with other agencies 
Beach Notification Database User Guide July 21, 2010 

68 

Code Name Description 

RC_INTERNAL CLOSING: 

Agency 

Provide announcement to agency staff 

RC_INTERNET CLOSING: 

Post on 

Internet 

Post reopening on the Internet 

RC_LOCAL_GOV CLOSING: 

Local 

government 

Provide announcement to local government staff 

RC_NEWSPAPER CLOSING: 

Newspaper 

article 

Publish reopening in local newspaper 

RC_PHONE CLOSING: 

Provide phone 

line 

Provide results on hotline/water quality information/result phone line 

RC_PHYS_ISOL CLOSING: 

Remove 

physical 

isolation 

Remove physical barriers set when closed 

RC_RADIO CLOSING: 

Radio 

announcement 

Have reopening announced on local radio station 

RC_RESAMPLE CLOSING: 

Resample 

Resample and compare bacterial concentrations with water quality standards 

to determine whether levels are below 

RC_RESP_PRSN CLOSING: 

Notify 

responsible 

person 

Notify owner/manager/operator/lifeguards of results

RC_STD_RAIN CLOSING: 

Standard rain 

reopening 

Reopen after a set number of days following rainfall 

RC_TV_ANNCE CLOSING: TV 

announcement 

Have reopening announced on local TV station 
Beach Notification Database User Guide July 21, 2010 

69 

9 Appendix D—Water Body Codes 

This Appendix provides a separate table to explain the acceptable water body codes for name and type. 

Exhibit 9-1 Water Body Name 

Code Description 

ATLANTIC Atlantic Ocean 

PACIFIC Pacific Ocean 

GULF_MEXICO Gulf of Mexico 

LAKE_SUPR Lake Superior 

LAKE_MCHGN Lake Michigan 

LAKE_HURON Lake Huron 

LAKE_ERIE Lake Erie 

LAKE_ONTR Lake Ontario 

INLAND Inland 

Exhibit 9-2 Water Body Type 

Code Description 

OPEN_COAST Open Coast 

SND_BY_INLT Sound, Bay, or Inlet 

STILL_WATER Still Water 

FLOW_WATER Flowing Water 
Beach Notification Database User Guide July 21, 2010 

70 

10 Appendix E—Horizontal Collection 

This appendix provides a list of valid domain values for Horizontal Collection Method Name and 

Horizontal Collection Reference Datum Name. 

Exhibit 10-1 Horizontal Collection Method Name 

Address Matching-House Number 

Address Matching-Block Face 

Address Matching-Street Centerline 

Address Matching-Nearest Intersection 

Address Matching-Primary Name 

Address Matching-Digitized 

Address Matching-Other 

Census Block-1990-Centroid 

Census Block/Group-1990-Centroid 

Census Block/Tract-1990-Centroid 

Census-Other 

GPS Carrier Phase Static Relative Position 

GPS Carrier Phase Kinematic Relative Position 

GPS Code (Pseudo Range) Differential 

GPS Code (Pseudo Range) Precise Position 

GPS Code (Pseudo Range) Standard Position (SA Off) 

GPS Code (Pseudo Range) Standard Position (SA On) 

Interpolation-Map 

Interpolation-Photo 

Interpolation-Satellite 

Interpolation-Other 

Loran C 

Public Land Survey-Quarter Section 

Public Land Survey-Section 

Classical Surveying Techniques 

Zip Code-Centroid 

Unknown 

GPS-Unspecified 

GPS, With Canadian Active Control System 

Interpolation-Digital Map Srce (Tiger) 

Interpolation-Spot 

Interpolation-MSS 

Interpolation-TM 

Public Land Survey-Eighth Section 
Beach Notification Database User Guide July 21, 2010 

71 

Public Land Survey-Sixteenth Section 

Public Land Survey-Footing 

Zip+4 Centroid 

Zip+2 Centroid 

Exhibit 10-2 Horizontal Collection Reference Datum Name 

NAD27

NAD83 

OTHER 

UNKWN

AMSMA

ASTRO 

GUAM 

JHNSN 

OLDHI 

PR 

SGEOR

SLAWR

SPAUL 

WAKE 

WGS72

WGS84 
Beach Notification Database User Guide July 21, 2010 

72 

11 Appendix F—Addition Notifications 

One feature of the notification schema is that users can submit activities over time as they happen, rather 

than being forced to submit them all at once. The primary Notification XML element is comprised of 

three main sub-elements: 

• OrganizationDetail, containing information related to the organizations involved in the Beach Act 

Grant Program. 

• BeachDetail, containing information related to the beaches overseen by the National Beach 

Program. 

• BeachProcedureDetail, contains information related to the procedures used by beaches for 

Monitoring, Notification, issuance, and reopening. 

An XML document containing additional activities needs only contain a portion of the BeachDetail 

element. 

The BeachDetail element contains information on specific beaches, including the BeachId, name data, 

attribute data, activity data, and role data. During the initial submission (or initial submission for a given 

beach), all required information in the BeachDetail element must be included. During subsequent 

submissions (to add activities to specific beaches) only the activity data should be included*

. This activity 

data falls under the BeachDetail sub-element, BeachActivityDetail. 

Exhibit 11-1 is an example Notification XML document containing two activities for the beach 

TX259473. Note that additional activities for TX259473 would be added by inserting additional 

BeachActivityDetail elements to the existing BeachDetail element. Activities on additional beaches 

would be added through the addition of BeachDetail elements. 

Exhibit 11-1 Example Notification XML Document

<BeachDataSubmission xsi:noNamespaceSchemaLocation="BeachesNotification.xsd" 

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 

 <BeachDetail> 

 <BeachIdentifier>TX259473</BeachIdentifier>

 <BeachActivityDetail> 

 <ActivityTypeCode>CONTAM_ADV</ActivityTypeCode> 

 <ActivityName>Advisory</ActivityName> 

 <ActivityActualStartDate>2003-12-23T09:27:00</ActivityActualStartDate> 

 <ActivityActualStopDate>2003-12-23T09:27:00</ActivityActualStopDate> 

 <ActivityReasonDetail> 

 <ActivityReasonType>ELEV_BACT</ActivityReasonType> 

 <ActivityReasonDescriptionText>1367 cfu</ActivityReasonDescriptionText> 

 </ActivityReasonDetail> 

 <ActivitySourceDetail> 

 <ActivitySourceType>UNKNOWN</ActivitySourceType> 

 </ActivitySourceDetail> 

 <ActivityIndicatorDetail> 

 <ActivityIndicatorType>ENTERO</ActivityIndicatorType> 

 </ActivityIndicatorDetail> 

<ActivityMonitoringStationIdentifier>21TXBCH|NUE030</ActivityMonitoringStationIdentifier> 

 </BeachActivityDetail> 

 <BeachActivityDetail> 

 <ActivityTypeCode>CONTAM_ADV</ActivityTypeCode> 

 <ActivityName>Advisory</ActivityName> 

 <ActivityActualStartDate>2003-11-14T16:10:00</ActivityActualStartDate> 

 <ActivityActualStopDate>2003-11-14T04:10:00</ActivityActualStopDate> 

 

*

 Beach Name data can be updated in the subsequent Notification XML submissions. This is accomplished through the inclusion of the 

BeachNameDetail element (see the Beach Notification User’s Guide, pages 3-13 to 3-15, 5-4). 
Beach Notification Database User Guide July 21, 2010 

73 

 <ActivityReasonDetail> 

 <ActivityReasonType>ELEV_BACT</ActivityReasonType> 

 <ActivityReasonDescriptionText>119 cfu</ActivityReasonDescriptionText> 

 </ActivityReasonDetail> 

 <ActivitySourceDetail> 

 <ActivitySourceType>UNKNOWN</ActivitySourceType> 

 </ActivitySourceDetail> 

 <ActivityIndicatorDetail> 

 <ActivityIndicatorType>ENTERO</ActivityIndicatorType> 

 </ActivityIndicatorDetail> 

<ActivityMonitoringStationIdentifier>21TXBCH|NUE034</ActivityMonitoringStationIdentifier> 

 </BeachActivityDetail> 

 </BeachDetail> 

</BeachDataSubmission>

Previously, users of the PRAWN Notification Access database were unable to generate valid XML files 

for these additional, interim submissions. With the addition of the Custom XML Generation macro, users

now have more control over which data to include in individual submissions. 

Exhibit 11-2 Custom XML Generation 

This form allows a user to choose which of the three main data sub-elements to submit, as well as which 

sections of the BeachDetail element (Names, Attributes, Activities, and Roles) should be included. The

calendars allow a user to narrow down the Activities to a specific timeframe. If the BeachActivityDetail 

element is not included in a submission, the calendars become inactive. 

To generate a custom file, simply follow these steps: 

1. Open the Notification Access Database. 

2. From the ‘Macros’ window, select the ‘Custom XML Generation’ macro. 
Beach Notification Database User Guide July 21, 2010 

74 

3. Once the Custom XML Generation macro is started, a screen (Error! Reference source not 

found.) will be presented. 

4. Select which data should be included in the Notification XML submission by checking or unchecking the boxes in the center of the windows. 

a. Note that the calendars allow for the selection of activities within a specific date range. If 

activities are not included in a given submission, these calendars will be inactive. 

5. Click the “Browse...” button to select a name and location for the Notification XML submission. 

6. Once the selections have been made, click the “Go!” button to generate a Notification XML 

submission with the selected data. 

7. A message will display with details of the file generation, along with confirmation that the 

Notification XML submission was generated successfully. 

A note on activity submissions: 

• Because it is possible for multiple activities to overlap on portions of the same beach, it is not 

possible to determine if duplicate activities have been submitted. For this reason, it is critically 

important that State users track those activities that have been previously submitted; submitting 

an activity twice will result in a duplicate activity in PRAWN. Should an activity be submitted 

multiple times, please contact the EPA Beach program manager to correct the error. 
Beach Notification Database User Guide July 21, 2010 

75 

12 Appendix G—Pollution Source Identification 

This appendix provides logical tables of how to enter data concerning pollution sources for both 

the Access database and XML schema. 

NOTE: All references to “pollution sources” are only “POSSIBLE sources” – see Page 24 of 

User Guide. 

Notification Access Database (Revised to avoid double negatives in Schema’s Boolean logic, 

will be translated back to schema in XML) 

Exhibit 12-1 Access Database

 BEACH_ATTRIBUTE (Beach – all activities) (Activity specific) 

Example Case [POLLUTION_SOURCES] 

Is it possible that there are 

pollution sources for the 

beach? Y/N 

[POLLUTION_SOURCES_INV

ESTIGATED] 

Have the pollution sources 

been investigated for the 

beach? Y/N 

BEACH_POLLUTION 

[POLLUTION_SOURCE] 

BEACH_ACTIVITY_RE

ASON 

1a. No Activity - 

No Investigation 

Done. 

“May or may not be 

sources” 

[Y] 

Because no investigation was 

done the schema uses “Y” in 

this case to indicate that there 

may be sources, but they are 

unknown 

[N] 

It is unknown whether or not 

pollution sources exist for this 

beach because they were not 

investigated - no pollution 

sources are to be listed in the 

[BEACH_POLLUTION] table. 

Leave Blank Leave Blank 

1b. No Activity – 

Investigation Done 

– No Sources 

Identified (Rare) 

[N] 

Investigated, but no sources 

found (rare) 

“N” will make the schema force 

a “Y” into 

[POLLUTION_SOURCES_INV

ESTIGATED] 

[Y] 

If no pollution sources were 

found, i.e.: 

POLLUTION_SOURCES] = 

[N] 

The schema is set to assume 

that the pollution sources were 

investigated. 

Leave Blank Leave Blank 

1c. No Activity – 

Investigation Done 

– Sources 

Identified 

[Y] 

Investigated and sources 

found 

[Y] 

It is known that pollution 

sources exist for this beach 

because they were 

investigated and listed in the 

[BEACH_POLLUTION] table 

List all identified for that 

beach, even though no 

activity that year 

Leave Blank 

2a. Activity 

Reported - No 

Investigation Done. 

[Y] 

Because no investigation was 

done the schema uses “Y” in 

[N] 

It is unknown whether or not 

pollution sources exist for this 

Leave Blank ‘UNKNOWN’ 
Beach Notification Database User Guide July 21, 2010 

76 

“May or may not be 

sources” 

this case to indicate that there 

may be sources, but it is 

unknown 

beach because they were not 

investigated and no pollution 

sources were listed in the 

[BEACH_POLLUTION] table. 

2b. Activity 

Reported – 

Investigation Done 

– Sources 

Unidentified 

“May or may not be 

sources” 

[Y] 

Because there were no 

sources found, the schema 

uses “Y” in this case to 

indicate that there may be 

sources, but they are 

unknown. 

[Y] 

It is known that pollution 

sources exist for this beach 

because there was an activity. 

However, although there was 

an investigation, the sources 

were not identifiable at the 

time of the investigation. 

‘UKNOWN’ ‘UNKNOWN’ 

2c. Activity 

Reported – 

Investigation Done 

– Sources 

Identified 

[Y] 

Investigated and sources 

found 

[Y] 

It is known that pollution 

sources exist for this beach 

because they were 

investigated and listed in the 

[BEACH_POLLUTION] table 

List all identified for all 

activities at that beach 

List all identified for that 

activity 
Beach Notification Database User Guide July 21, 2010 

77 

XML Schema (Boolean Logic with Double Negatives) 

Exhibit 12-2 XML Schema

Example Case Beach Attribute Beach Pollution Beach Activity Reason 

1a. No Activity - 

No Investigation Done. 

“May or may not be 

sources” 

NoPollutionSourcesIndicator = ‘false’ 

PollutionSourcesUninvestigatedIndicator = ‘true’ if

no investigation done 

Leave Blank Leave Blank 

1b. No Activity – 

Investigation Done – No 

Sources Identified (Rare) 

NoPollutionSourcesIndicator = ‘true’ investigated 

but no sources found 

Leave Blank Leave Blank 

1c. No Activity – 

Investigation Done – 

Sources Identified 

NoPollutionSourcesIndicator = ‘false’ investigated 

and sources found 

PollutionSourcesUninvestigatedIndicator = ‘false’ 

investigation done 

BeachPollutionSourceCode = 

list all identified for that 

beach, even though no activity 

that year 

Leave Blank 

2a. Activity Reported - No 

Investigation Done. 

“May or may not be 

sources” 

NoPollutionSourcesIndicator = ‘false’ 

PollutionSourcesUninvestigatedIndicator = ‘true’ if

no investigation done 

Leave Blank ActivityReasonType = 

‘UNKNOWN’ 

2b. Activity Reported – 

Investigation Done – 

Sources Unidentified 

“May or may not be 

sources” 

NoPollutionSourcesIndicator = ‘false’ investigated 

and sources found 

PollutionSourcesUninvestigatedIndicator = ‘false’ 

investigation done 

BeachPollutionSourceCode = 

‘UKNOWN’ 

ActivityReasonType = 

‘UNKNOWN’ 

2c. Activity Reported – 

Investigation Done – 

Sources Identified 

NoPollutionSourcesIndicator = ‘false’ investigated 

and sources found 

PollutionSourcesUninvestigatedIndicator = ‘false’ 

investigation done 

BeachPollutionSourceCode = 

list all identified for all 

activities at that beach 

ActivityReasonType = 

List All Identified for that 

activity 
Beach Notification Database User Guide July 21, 2010 

78 

13 Appendix H—Data Entry Forms 

Forms have been added to ease the data entry process; however, it is still possible to copy and paste 

records directly into the tables. To access the data entry forms, click the Forms tab. 

Exhibit 13-1 Forms 

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

before beach data.
Beach Notification Database User Guide July 21, 2010 

79 

Exhibit 13-2 Main Menu 

 

On each data entry form there is a Return to Main Menu button. Use this button to navigate back 

to the Main Menu form.
Beach Notification Database User Guide July 21, 2010 

80 

Exhibit 13-3 Return to Main Menu 
Beach Notification Database User Guide July 21, 2010 

81 

14 Appendix I—Summary Reports 

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

Reports tab. 

Exhibit 14-1 Reports 
Beach Notification Database User Guide July 21, 2010 

82 

Exhibit 14-2 Actions 
Beach Notification Database User Guide July 21, 2010 

83 

Exhibit 14-3 Attributes 
Beach Notification Database User Guide July 21, 2010 

84 

Exhibit 14-4 Monitoring 
Beach Notification Database User Guide July 21, 2010 

85 

The pollution source report takes up twice as many pages due to the number of columns it displays. 

Exhibit 14-6 displays the other half of the report. 

Exhibit 14-5 Pollution Source 
Beach Notification Database User Guide July 21, 2010 

86 

Exhibit 14-6 Pollution Source (cont.) 
Beach Notification Database User Guide July 21, 2010 

87 

15 Appendix J—CDX Messages 

The first email will notify the user that CDX has received their submission. It will also notify 

them to expect two additional emails from PRAWN. 

Exhibit 15-1 Your CDX eBeaches Data Submission 

The second email will notify the user whether their XML validated against the schema. A list of 

errors will be provided if the XML does not validate according to the schema.
Beach Notification Database User Guide July 21, 2010 

88 

Exhibit 15-2 Validation Message 

The final email will notify the user of any data errors/warnings they may need to correct within 

the submission.
Beach Notification Database User Guide July 21, 2010 

89 

Exhibit 15-3 Final Email