National Park Service 

U.S. Department of the Interior 

Natural Resource Program Center 

Northeast Coastal and Barrier Network Geomorphological 

Monitoring Protocol: 

Part I—Ocean Shoreline Position 

Natural Resource Report NPS/NCBN/NRR—2010/185 
ON THE COVER 

Ballston Beach, Cape Cod National Seashore, MA. 

Photograph by: James Allen 
Northeast Coastal and Barrier Network 

Geomorphological Monitoring Protocol: 

Part I—Ocean Shoreline Position 

Natural Resource Report NPS/HTLN/NRR—2010/185 

Dr. Norbert P Psuty, Tanya M. Silveira 

Institute of Marine and Coastal Sciences National Park Service 

Rutgers, The State University of New Jersey 

Sandy Hook Cooperative Research Program 

74 Magruder Road 

Highlands, New Jersey 07732 

Mark Duffy 

Northeast Region 

National Park Service 

200 Chestnut Street

Philadelphia, Pennsylvania 19106

Jeffrey P. Pace 

Formerly of the Institute of Marine and Coastal Sciences 

Rutgers, The State University of New Jersey 

Sandy Hook Cooperative Research Program 

74 Magruder Road 

Highlands, New Jersey 07732 

Dennis E. Skidds 

Northeast Coastal and Barrier Network 

National Park Service 

105 Coastal Institute 

1 Greenhouse Road 

Kingston, Rhode Island 02881 

March 2010 

U.S. Department of the Interior 

National Park Service 

Natural Resource Program Center 

Fort Collins, Colorado 
ii 

The National Park Service, Natural Resource Program Center publishes a range of reports that 

address natural resource topics of interest and applicability to a broad audience in the National 

Park Service and others in natural resource management, including scientists, conservation and 

environmental constituencies, and the public. 

The Natural Resource Report Series is used to disseminate high-priority, current natural resource 

management information with managerial application. The series targets a general, diverse 

audience, and may contain NPS policy considerations or address sensitive issues of management 

applicability. 

All manuscripts in the series receive the appropriate level of peer review to ensure that the 

information is scientifically credible, technically accurate, appropriately written for the intended 

audience, and designed and published in a professional manner. 

This report received formal, high-level peer review based on the importance of its content, or its 

potentially controversial or precedent-setting nature. Peer review was conducted by highly 

qualified individuals with subject area technical expertise and was overseen by a peer review 

manager. 

Views, statements, findings, conclusions, recommendations, and data in this report are those of 

the author(s) and do not necessarily reflect views and policies of the National Park Service, U.S. 

Department of the Interior. Mention of trade names or commercial products does not constitute 

endorsement or recommendation for use by the National Park Service. 

This report is available from (http://www.nps.gov/nero/science) and the Natural Resource 

Publications Management website (http://www.nature.nps.gov/publications/NRPM). 

Please cite this publication as: 

Psuty, N. P., M. Duffy, J .F. Pace, D. E. Skidds, and T. M. Silveira. 2010. Northeast Coastal and 

Barrier Network geomorphological monitoring protocol: part I—ocean shoreline position. 

Natural Resource Report NPS/NCBN/NRR —2010/185. National Park Service, Fort Collins, 

Colorado. 

NPS 962/101471, March 2010 
iii 

Contents 

Page 

Figures............................................................................................................................................. v

Tables ............................................................................................................................................ vii

Background and Objectives ............................................................................................................ 3

Introduction .............................................................................................................................. 3

Goal and Objective .................................................................................................................. 3

The Ocean Beach-Dune Ecosystem ......................................................................................... 5

The Process of Evaluating Vital Signs .................................................................................... 7

The Elements of Monitoring Coastal Shoreline Position ........................................................ 9

Historical Development of Methods used for Monitoring Shoreline Position ...................... 10

Sampling Design ........................................................................................................................... 13

Selecting the Shoreline Feature and Measurement ................................................................ 13

Geographical Extent of the Surveys ...................................................................................... 17

Assateague Island National Seashore (ASIS) ................................................................... 17

Cape Cod National Seashore (CACO) ............................................................................. 17

Gateway National Recreation Area – Sandy Hook Unit (GATE-SHU) ............................ 17

Gateway National Recreation Area – Breezy Point (GATE-BP) ...................................... 17

Gateway National Recreation Area – Plumb Beach (GATE-PB) ..................................... 17

Gateway National Recreation Area – Staten Island Unit (GATE-SIU) ............................ 18

Fire Island National Seashore (FIIS) ............................................................................... 18

Survey Frequency and Timing ............................................................................................... 28

Field Methods ............................................................................................................................... 29

Field Season Preparations and Mission Planning .................................................................. 29

Conducting the GPS Shoreline Survey .................................................................................. 29
iv 

Post-survey Data Download and Initial QA/QC ................................................................... 30

Data Management ......................................................................................................................... 31

Change Calculation, Data Analysis, and Reporting ...................................................................... 33

Generation of Changes in Shoreline Position ........................................................................ 33

Data Analysis and Reports ..................................................................................................... 33

Personnel Requirements and Training .......................................................................................... 35

Roles and Responsibilities ..................................................................................................... 35

Qualifications and Training ................................................................................................... 35

Operational Requirements ............................................................................................................ 37

Annual Workload and Field Schedule ................................................................................... 37

Facility and Equipment Needs ............................................................................................... 37

Startup Costs and Budget ....................................................................................................... 37

Procedure for Revising and Archiving Previous Versions of the Protocol .................................. 39

Literature Cited ............................................................................................................................. 41

Standard Operating Procedures ..................................................................................................... 45

Standard Operating Procedure (SOP) # 1 – Equipment and Supplies ................................... 45

Standard Operating Procedure (SOP) # 2 – Training for Field Data Collection ................... 49

Standard Operating Procedure (SOP) # 3 – Survey Timing and GPS Mission Planning ...... 53

Standard Operating Procedure (SOP) # 4 – Basic GPS Settings for Position Collection ..... 61

Standard Operating Procedure (SOP) # 5 – Conducting the GPS Shoreline Survey ............ 65

Standard Operating Procedure (SOP) # 6 – Initial Post-Survey Processing ......................... 77

Standard Operating Procedure (SOP) # 7 – Change Calculation, Data Analysis, and 

Reporting ............................................................................................................................... 85

Standard Operating Procedure (SOP) # 8 – Data Management .......................................... 101

Standard Operating Procedure (SOP) # 9 – Revising the Protocol ..................................... 111
v

Figures 

Page 

Figure 1. Locations of the eight NPS units in the Inventory and Monitoring Program of the 

Northeast Coastal and Barrier Network. ......................................................................................... 4

Figure 2. The Ocean Beach-Dune Ecosystem Model illustrates the relationships amongst 

the agents of change, stressors, and ecosystem response ................................................................ 6

Figure 3. The relationship of the various topographical features of the beach-dune profile to 

the positions of water level and vertical datums ........................................................................... 14

Figure 4. The relationship of the various topographical features of a cliff coast profile to the 

positions of water level and vertical datums ................................................................................. 15

Figure 5. The recent high-tide swash line (red dashed line) on the beach face on a beachdune coast...................................................................................................................................... 16

Figure 6. The recent high-tide swash line (red dashed line) on the beach face on a cliff 

coast. ............................................................................................................................................. 16

Figure 7. Spatial extent of GPS data collection of the ASIS ocean shoreline ............................ 19

Figure 8. Spatial extent of GPS data collection of the ASIS shoreline terminating in the 

north at the Ocean City Jetty ......................................................................................................... 20

Figure 9. Spatial extent of GPS data collection of the ASIS transition zone at Toms Cove 

Hook, VA. ..................................................................................................................................... 20

Figure 10. Spatial extent of GPS data collection of the CACO ocean shoreline ........................ 21

Figure 11. Example of the spatial extent of GPS data collection at an inlet in CACO .............. 22

Figure 12. Spatial extent of GPS data collection of the GATE - Sandy Hook ocean shoreline .. 23

Figure 13. Spatial extent of GPS data collection of the GATE - Breezy Point ocean 

shoreline ........................................................................................................................................ 24

Figure 14. Spatial extent of GPS data collection of the GATE - Plumb Beach ocean 

shoreline ........................................................................................................................................ 24

Figure 15. Spatial extent of GPS data collection of the GATE - Staten Island ocean 

shoreline ........................................................................................................................................ 25

Figure 16. Spatial extent of GPS data collection of the FIIS ocean shoreline ............................ 26
vi

Figure 17. Spatial extent of GPS data collection of the FIIS shoreline terminating in the 

east at the Fire Island Inlet jetty .................................................................................................... 27

Figure 18. Spatial extent of GPS data collection of the FIIS shoreline terminating in the 

west at the Moriches Inlet jetty ..................................................................................................... 27

Figure 19. The high-tide swash line is clearly identified as a wet/dry line with wrack. ............. 30

 
vii

Tables 

Page 

Table 1. The fourteen Vital Signs identified during the Northeast Coastal and Barrier 

Network Geomorphological Change Workshops ........................................................................... 8

Table 2. Data Collection Cost Estimates (US$, 2007). ............................................................... 38

ix 

Executive Summary 

Following a review of Vital Signs in the coastal parks of the Northeast Coastal and Barrier 

Network, knowledge of shoreline change was ranked as the top variable for monitoring. 

Shoreline change is a basic element in the management of any coastal system because it 

contributes to the understanding of the functioning of the natural resources and to the 

administration of the cultural resources within the parks. Collection of information on the 

vectors of change relies on the establishment of a rigorous system of protocols to monitor 

elements of the coastal geomorphology that are guided by three basic principles: 1) all of the 

elements in the protocols are to be based on scientific principles; 2) the products of the 

monitoring must relate to issues of importance to park management; and 3) the application of the 

protocols must be capable of implementation at the local level within the NCBN Network. 

Changes in shoreline position are recognized as interacting with many other elements of the 

Ocean Beach-Dune Ecosystem and are thus both driving and responding to the variety of natural 

and cultural factors active at the coast at a variety of temporal and spatial scales. The direction 

and magnitude of shoreline change can be monitored through the application of a protocol that 

tracks the spatial position of the neap-tide, high tide swash line under conditions of temporal 

sampling. Spring and fall surveys conducted in accordance with standard operating procedures 

will generate consistent and comparable shoreline position data sets that can be incorporated 

within a data matrix and subsequently analyzed for temporal and spatial variations. 

The shoreline monitoring protocol will be applied to the four coastal parks in the NCBN: 

Assateague Island National Seashore, Cape Cod National Seashore, Gateway National 

Recreation Area, and Fire Island National Seashore. Monitoring will be accomplished with a 

sub-meter GPS unit that is mounted on an ATV and driven along the swash line. Under the 

guidance of a set of Standard Operating Procedures (SOPs), the monitoring will generate 

comparable data sets. Shoreline change metrics are developed following the methodology of the 

Digital Shoreline Analysis System developed by the United States Geological Survey. Annual 

Reports and Trend Reports will present and analyze the collected data sets. All of the data will 

be archived in the NCBN master data bank. 
 
1 

Protocol Narrative 

The following table lists all changes that have been made to this Protocol Narrative since the 

original publication date. Any recommended or required changes added to the log must be 

complete and concise and promptly brought to the attention of the NCBN Project Leader. The 

project leader will review and incorporate all changes, officially complete the revision history 

log, and change the date and version number on the title page. For complete instructions, please 

refer to SOP#9 – Revising the Protocol.

Version 1.00 - December 2009 

Revision History Log: 

New 

Version # 

Previous 

Version # 

Revision 

Date 

Author (full 

name, title, 

affiliation) 

Location in Document 

and Description of 

Change 

Reason for 

Change 

 

3 

Background and Objectives 

Introduction 

A major issue in all coastal parks is the magnitude and rate of shoreline change. This condition 

affects the quality of the natural and cultural resources as well as the general infrastructure 

present in the coastal parks. It is among the most basic concerns of being at the shore. Bird 

(1985) indicates that at least 70 % of the world’s sandy shorelines are eroding and the percentage 

is expected to increase because of sea-level rise and sediment manipulation by human actions. 

Working Groups within the Intergovernmental Panel on Climatic Change suggest that sea level 

will increase from 18 to 59 cm during the present century (IPCC 2007) and that shoreline change 

will be an immediate consequence of this inundation (Nicholls et al. 2007). Coastal 

geomorphological models exist that consider the effects of sea-level rise on shoreline change and 

landform evolution (e.g., Nummendal et al. 1987; Davidson-Arnott 2005; FitzGerald 2008). 

They are both a guide to the potential effects of continuing global change and a plea to gather 

data appropriate to the testing and calibration of the models. They are harbingers of the concern 

and interest in the quality of the coastal system, in the shepherding of coastal resources, and in 

the data sets describing these resources. 

As part of the congressionally-mandated Natural Resource Challenge, the National Park Service 

(NPS) has created thirty-two monitoring Networks to ensure the systematic collection and use of 

scientific data in managing the nation’s parks (NPS NCBN 2003). Within this structure, the 

Northeast Coastal and Barrier Network (NCBN) is developing a series of scientific protocols to 

address a variety of natural resource issues appropriate to coastal locations. This document 

represents the first of several protocols for long-term geomorphological monitoring in the eight 

parks that comprise the NPS NCBN (Figure 1). The initial protocol focuses on the collection and 

analysis of the ocean shoreline position. Additional protocols will address issues related to 

coastal topography and estuarine shorelines.

Goal and Objective 

A primary goal of the NCBN coastal geomorphological program is to provide information to 

park managers and to improve the understanding of the dynamic nature of coastlines, including 

the temporal and spatial patterns of change in NCBN parks, for use in management decisions and 

in describing the condition of marine and coastal areas. The specific objective of this shoreline 

position monitoring protocol is to identify the seasonal, annual, and long-term trends and 

variability of shoreline position in the Network parks as part of the basis for understanding the 

coastal geomorphological system. 

The NCBN coastal geomorphology program and its protocols are based upon three underlying 

principles 

1. All protocols developed by the Network must have a scientific foundation. Collaboration 

with the scientific community will ensure that all geomorphologic monitoring protocols 

are based on well-established scientific principles of coastal characterization, processes, 

and response. Because coastal geomorphology is a complex subject, valid interpretation 

of the data will require the active involvement of knowledgeable coastal scientists. 
4 

2. Data must address significant park management issues. Park managers and natural 

resource staff were active participants in the planning and scoping process in the 

development phase of the geomorphologic protocols. The objectives identified in this 

protocol reflect a consensus of issues considered relevant at the park level. This protocol 

focuses on recording and assembling the geomorphological dataset to enable betterinformed management decisions. 

3. All protocols and their components must be feasible to implement at the Network level. 

Although the scientific and management value of the monitoring data were both critical 

factors in determining which vital signs or indicators were selected for monitoring, the 

practicality and feasibility of implementation across the Network were important as well. 

Figure 1. Locations of the eight NPS units in the Inventory and Monitoring Program of the Northeast 

Coastal and Barrier Network. 
5 

Changes in shoreline position in the Network parks were identified by coastal scientists and park 

managers as geomorphologically significant, and the type of observational data that can easily be 

assembled and quickly and effectively incorporated into park management operations. Among 

these important considerations are:

• Changes in shoreline position serve as a surrogate for sediment budget measurements. 

• Changes in shoreline position document the seasonal, annual, and long-term trends in 

beach displacement. 

• Shoreline position monitoring is compatible with the historical record and ongoing 

measurement. 

• Shoreline position monitoring is feasible to implement at the Network level with existing 

technology and equipment. 

• Shoreline position data are readily used at the park level in various management 

applications. 

The ocean shoreline position protocol includes a number of highly-detailed standard operating 

procedures (SOPs). They are intended to ensure the consistency and repeatability essential to any 

long-term monitoring program. These SOPs will be modified and revised as technology 

improves and better methods for monitoring coastal geomorphological change are developed.

The Ocean Beach-Dune Ecosystem 

The basis for the ocean shoreline protocol is the beach-dune conceptual model (modified from 

Roman and Barret 1999) that relates the physical processes and cultural impacts (agents of 

change) to the vectors of change (stressors) and to the responses of the coastal ecosystem (Figure 

2). Fundamental to the model is an awareness that the coastal system is dynamic and that it is 

interacting at a variety of geographical and temporal scales. The model consists of an 

assemblage of natural and cultural agents and processes that generate characteristics of the 

coastal landscape. As the relative magnitude of the agents and processes vary, they cause 

alterations to the hydrology and sediment budget and consequently to the landscape. 

Furthermore, there is a continuous interaction and feedback amongst the evolving components 

that drive additional changes and alterations. A primary manifestation of the alteration is a shift 

in shoreline position and modification of the beach-dune topography. These coastal 

geomorphological changes result in an ecosystem response that incorporates changes in the 

physical environment and in the community structure and function (Figure 2). 

The primary natural disturbances that drive coastal geomorphological change are sea-level rise, 

sediment supply, and wave climate. These natural factors influence coastal geomorphological 

response at different temporal scales including individual events (storms), cyclic variations 

(seasonal), and annual and multi-year (long-term) trends (Carter 1988, Psuty and Ofiara 2002). 

One of the effects of the long-term trend of sea-level rise is inland displacement of the shoreline. 

When coupled with erosion produced by a prevailing sediment deficit, the rate of inland 

shoreline displacement is increased (National Research Council 1987; Warrick 1993). Whereas 

sea-level rise and sediment supply are the primary factors causing the change, wave climate is 
6 

responsible for the nearshore processes of waves and currents that steer the local sediment 

transport and interact with the existing offshore topography to consequently control the sitespecific shoreline configuration (Trenhaile 1997). 

Altered Hydrology

Nearshore Currents

Transport Vectors

Offshore Bathymetry

Altered Landscape

Inlet Formation

Inlet Migration

Offshore Topography

Overwash Topography

Shoreline Displacement

Dune Morphology

Altered Sediment 

Budget

Sediment Supply

Sediment Pathways

Sources and Sinks

Ecosystem 

Function

Changes

Productivity

Nutrient Cycling

Energy Flow

Trophic Shifts

Ecosystem 

Structure

Changes

Species Composition

Species Abundance

Invasive Species

Expansion

Physical 

Environment

Changes

Habitat Pattern

Water Quality

Soil Chemistry

Ocean Beach-Dune Ecosystem Model

Agents of Change

Stressors

Ecosystem Response

Natural Disturbance

Sea Level Rise

Sediment Supply

Wave Climate

Land Use

Shore Structures

Buildings/Infrastructure

Beach Nourishment

Dredging

Visitor and 

Recreation Use

Soil Disturbance

Vegetation Disturbance

Figure 2. The Ocean Beach-Dune Ecosystem Model illustrates the relationships amongst the agents of 

change, stressors, and ecosystem response (after Roman and Barrett 1999).
7 

Local conditions such as the underlying geologic framework, bathymetry, offshore topography, 

and sediment sources and sinks interact with the primary factors and the coastal processes to 

influence the characteristics and the rates and direction of the coastal system alterations 

(Honeycutt and Krantz 2003). In addition to natural causes, coastal changes are often accelerated 

by human perturbations such as dredging and channel relocation, groins and jetties, and beach 

and dune manipulation (Nordstrom 2000). These human influences can cause alterations to 

waves, currents, and availability and mobility of sediment. The combinations of natural 

processes and anthropogenic modifications interact to cause significant morphological change 

that leads to ecosystem response. 

Coastal ecosystem response may consist of adjustments to resource patterns and dynamics, and 

may eventually lead to the loss of fixed natural resources (Roman and Nordstrom 1988). These 

responses often elicit secondary changes in ecosystem structure or function. Structural changes 

in species composition or competitive interactions generally reflect landscape-level alterations in 

the quantity and quality of specific habitats. Similarly, functional changes in productivity or 

nutrient cycling may occur as a product of storm events and the associated reduction in habitat 

complexity. More subtle physical changes also include alterations in geo-chemical and 

hydrological conditions, such as groundwater quality and quantity. The magnitude and scope of 

the resultant coastal ecosystem response is complex, highly variable, and can often be 

cumulative. At the extreme, this includes the alteration of habitats and of core ecosystem 

processes. For example, erosion of an existing shoreline may create new aquatic habitat, or 

overwash fans may fill in a wetland environment to create new terrestrial habitat. 

The Process of Evaluating Vital Signs 

Geomorphological change is important to the evolution of the coastal ecosystem, and in some 

cases, when it affects natural and cultural resources, recreational features, and facilities or 

infrastructure, the change presents complex challenges to park management. In order to address 

the full range of scientific and management concerns, multiple scoping workshops were 

convened to identify issues of general importance and to make specific recommendations for 

monitoring. Throughout the scoping process, the lack of adequate data to track and respond to 

geomorphological change was consistently identified as a high priority management issue. 

Demonstrating the complexity of the coastal geomorphological process, twenty-nine potential 

monitoring variables (vital signs) of geomorphological change were identified by the workshops 

(NPS NCBN 2003). Following the workshops, the number was reduced by combining similar 

indicators and eliminating redundant items. The remaining fourteen vital signs were evaluated 

and ranked for data value and feasibility of implementation at the Network level (Table 1). 

Shoreline position and elements of the coastal topography were consistently identified as of high 

information value and capable of monitoring with existing methods. 
8 

Table 1. The fourteen Vital Signs identified during the Northeast Coastal and Barrier Network 

Geomorphological Change Workshops; they are ranked for data value and feasibility of implementation at 

the Network level. 

Geomorphological 

Change

Vital Sign Monitoring Methods Feasibility Data Value

Shoreline Position Shoreline position 1D & 2D GPS, 2D & 3D Survey, 

Aerial Photography, LIDAR 

high high 

Coastal 

Topography 

Dune, beach, cliff, 

bluff morphology 

LIDAR, Aerial Photography, 2D 

&3D Survey 

high high 

 Edge of vegetation LIDAR, 1D, 2D GPS, Aerial 

Photography 

high high 

 Landcover LIDAR, 2D &3D Survey high high 

Overwash fans/flood 

plains 

LIDAR, 1D & 2D GPS, 2D & 3D 

Survey, Aerial Photography 

medium high 

 Shore type Aerial Photography, 2D & 3D 

GPS, 2D & 3D Survey 

medium medium 

Anthropogenic 

Modifications 

Locations of 

structures and 

disturbances 

Aerial Photography, 1D & 2D 

GPS, 2D & 3D Survey 

medium high 

Marine 

Geomorphology 

Sediment quantity 

Sediment size 

Terrestrial and Marine Sediment 

Samples 

medium medium 

 Geologic framework Acoustic Survey, Seismic Survey, 

Core Samples 

low high 

 Depths Acoustic Survey, Bathymetric 

LIDAR, 

Sled survey 

low medium 

Migrating shoals & 

bodies 

Acoustic Survey, Bathymetric 

LIDAR 

low high 

Marine Hydrography Tide range Local & Regional Tide Gauge high high 

Relative sea level 

position 

Water Level Gauge high high 

Wave and current 

characteristics 

Local Gauge -Regional Gauge low high 
9 

The Elements of Monitoring Coastal Shoreline Position 

Detailed knowledge of the hydrodynamic forcing of sediment mobilization, transport, and 

deposition, and measurements of morphologic change and ecosystem response at the park level 

are key to understanding the coastal geomorphology of NCBN parks (Allen 2000). Although a 

number of these geomorphological processes and responses are somewhat difficult to measure 

and monitor, there are several, such as shoreline position, that have high value (Table 1), can be 

measured effectively, and can be used to address park management issues. 

From a scientific perspective, shoreline position represents the morphological response of wave 

and current processes acting upon sediment supply (Komar 1998; Short 1999). Understanding 

the dynamics of changes in shoreline position over time, through standardized data collection, 

will provide a scientific basis for informed resource management (National Research Council 

1995). Additionally, historical shoreline position data exist for many of the NCBN parks, 

thereby providing the opportunity for long-term comparison. The assemblage of reliable and 

consistent data enables robust statistical analysis, yielding a better understanding of episodes, 

cycles, and trends (Colwell and Thom 1994; Dolan and Hayden 1983; Graham et al. 2003). 

Shoreline monitoring provides knowledge of the spatial and temporal variation in sediment 

transfers and sediment budget and creates a fundamental database for use in park management. 

Collecting a record of the changes in the shoreline position over time chronicles variation in 

sediment supply and distribution, and may function as a surrogate for sediment budget (Allen et. 

al. 1995; Farris and List 2007). The collection of the shoreline position twice a year, in the early 

spring (the fully developed winter beach) and the early fall (the fully developed summer beach), 

leads to the accumulation of a time series of seasonal shoreline positions that represent the 

annual theoretical maximum and minimum configurations of the beach. Each annual pair of 

shorelines portrays the magnitude of variation caused by the changes in the seasonal wave 

climate acting on the beach sediment supply. Longer term comparisons of shoreline positions 

reveal changes created by differences in sediment availability and intensity of formational 

processes. In addition, there are aspects of shoreline variability, such as geotemporal trends and 

cycles, that can only be revealed through long-term data collection. 

The objective of the NCBN shoreline position monitoring protocol is to identify the seasonal, 

annual, and long-term trends and variability of shoreline position in the Network parks. Meeting 

this objective will address the following questions: 

• What is the displacement of the shoreline? 

• What are the seasonal dimensions of the displacement? 

• What are the annual dimensions of the displacement? 

• What are the long-term dimensions of the displacement? 

• What are the spatial and temporal trends in the shoreline displacement? 
10 

Accomplishing the objective of this protocol requires the following steps: 

 1) standardization of the survey methodology, 

 2) design and construction of the database, 

 3) reporting of the assembled data and, 

 4) scientific analysis and interpretation. 

Historical Development of Methods used for Monitoring Shoreline Position 

Coastal mapping and the measuring of coastal features have utilized an evolving suite of data 

collection methods (Boak and Turner 2005). Early techniques in the United States involved the 

Coast & Geodetic Survey conducting surveys of the coast beginning in the early 1800s. This 

method was extremely labor intensive and the long time periods required to complete a survey 

proved to be problematic in capturing anything resembling an instantaneous shoreline position. 

However, these early efforts did result in systematically collected datasets that were suitable for 

general delineation and comparison of coastal features, and they established general baselines in 

many coastal areas (Graham et al. 2003). 

The development of aerial photography in the early twentieth century created the opportunity for 

rapid data collection and the extraction of multiple features from the images (Moore 2000). 

Comparison studies between ground surveys and aerial photography showed a general level of 

compatibility between the data (Kraus and Rosati 1997). The ability to capture large 

geographical areas of the coast continues with space-based satellites. Satellite technology is 

becoming a viable option for many coastal data acquisition purposes. Currently, there are 

several studies within the NCBN to assess the utility of satellite imagery for coastal mapping. 

The last twenty years have seen a revolution in mapping sciences in general and coastal mapping 

sciences in particular. The development of Geographic Information Systems (GIS) allows the 

simultaneous display, manipulation, and analysis of multiple datasets. In the 1980s and 1990s, 

GIS technology was augmented by the addition of satellite-based Global Positioning Systems 

(GPS), creating the opportunity for more efficient, frequent, and precise measures of 

geomorphological features. Recent GPS survey approaches produce topographical portrayals 

with sub-meter accuracy (Pardo-Pascual et al. 2005). Together these technologies have greatly 

increased the capacity for updating, analyzing, and reporting changes in coastal conditions. 

The revolution in coastal mapping continued into the 1990s when LIDAR (LIght Detection And 

Ranging) technology was applied to the coastal zone (Krabill et al. 2000). The airborne laser 

mapping system can deliver high-resolution measurements of the entire non-vegetated beach and 

dune system and use the three-dimensional data to extract a variety of coastal features, including 

shoreline position. LIDAR technology has evolved rapidly and systems now exist that can 

penetrate sparse to moderate vegetation (Wright and Brock 2002) and some shallow waters to 

provide detailed topography and bathymetry over large segments of coastal systems. 

NPS geomorphological monitoring has generally mirrored the developments in the coastal 

sciences (Allen and LaBash 1997). In some cases, the NPS has played a major role in the 

development of modern, technology-based data acquisition efforts (Brock et al. 2001). Network 
11 

parks were early users of GPS shoreline surveys and a park-focused NASA research experiment 

in the mid-1990s was one of the earliest cases of LIDAR technology applied to beach mapping. 

Currently, there are a variety of independent data collection activities underway in individual 

NCBN parks. At present, none of these efforts meets the rigorous data collection and data 

management standards established by the service-wide inventory and monitoring program. 

However, many of the concepts, methods, and techniques used in individual park programs are 

applicable to Network-wide long-term monitoring. By providing a consistent and systematic 

framework for collection, analysis, and reporting, the NCBN will utilize this collective 

knowledge and experience from existing park programs to build a long-term, Network 

monitoring program. 

13 

Sampling Design 

Selecting the Shoreline Feature and Measurement 

The shoreline represents the intersection between water and land surfaces. The location of the 

shoreline intercept on the beach-dune profile (Figure 3) or at a cliff profile (Figure 4) varies due 

to the effects of tides, waves, and atmospheric conditions. Further, shorelines may be delineated 

based on a datum intercept, or identification of some morphological feature, or some visual 

characteristic. Multiple conventions, definitions, and terms are used to describe the various 

positions of the intercept. Datum shorelines such as Mean High Water (MHW) are quantitative 

and use a calculated identification of an exact elevation to extract the intercept (Parker 2003; 

Pajak and Letherman 2002), whereas morphological features such as berm crest or cliff base or 

visual features such as the high water mark, high-tide swash line, or water’s edge are typically 

qualitative and are based on a visual interpretation (Figures 5 and 6). Any of these quantitative 

or qualitative features may be used to represent a shoreline position under specific 

circumstances. 

Datum-based derivations such as calculated water levels (Mean Sea level, Mean High Water, 

etc.) or national datums (North American Vertical Datum of 1988, or National Geodetic Vertical 

Datum of 1929) are precise measures of shoreline position based on a specific vertical elevation 

(shown in combination on Figures 3 and 4). However, the present-day needs across the Network 

to support data collection necessary to extract this feature at the geotemporal scale required to 

identify seasonal and episodic variability cause this approach to be impractical. 

On the other hand, although qualitative shorelines are less precise, their derivation is feasible for 

use in a long-term, Network-wide monitoring program (Pajak and Leatherman 2002). Further, 

with the application of a standardized and repetitive means for shoreline identification and 

recording, a very good comparative shoreline position can be attained. Among the qualitative 

features described above, the neap high-tide swash line is consistently available, least variable, 

readily identified, and easily collected; and thus it is selected as the indicator of shoreline 

position in this protocol (Figures 5 and 6). In the context of the NPS Network based monitoring 

program, a systematically planned and executed survey utilizing the high-tide swash line as 

shoreline position is well suited to the needs, resources, and capabilities of the program. 

Properly planned and executed GPS surveys can provide sufficient data to monitor the long-term 

trends and variability in shoreline position. Further, the timing of the survey can be adjusted for 

local tides and weather conditions, making GPS surveys comparable and more convenient than 

many other established methods of shoreline mapping. 

Because the shoreline is feature-based and there is some variation in both the natural creation of 

the swash line on the beach face and the interpretation of the position of the swash line, there is a 

measure of uncertainty associated with the surveyed shoreline. Potential sources of positional 

uncertainty of the shoreline are: 1) GPS accuracy, 2) differential tide position, 3) meteorological 

effects – wave dimension and run-up, and 4) interpretation of the line. It is estimated that the 

total level of uncertainty of shoreline position is within 5 m in each survey. That is, there is a 

potential range of shoreline position of up to 5 m in each surveyed shoreline. 
14 

Figure 3. The relationship of the various topographical features of the beach-dune profile to the positions 

of water level and vertical datums: mean higher high water; mean high water; North American Vertical 

Datum 1988; mean sea level; National Geodetic Vertical Datum 1929; mean low water; and mean lower 

low water. 
15 

Mean Sea Level

Neap High Tide

Swash Zone

Neap High Tide

Swash Line

Cliff Edge

Beach Face

Cliff Edge

Beach Face

Figure 4. The relationship of the various topographical features of a cliff coast profile to the positions of 

water level and vertical datums: mean higher high water; mean high water; North American Vertical 

Datum 1988; mean sea level; National Geodetic Vertical Datum 1929; mean low water; and mean lower 

low water. 
16 

Figure 5. The recent high-tide swash line (red dashed line) on the beach face on a beach-dune coast. 

Figure 6. The recent high-tide swash line (red dashed line) on the beach face on a cliff coast. 
17 

Geographical Extent of the Surveys 

In order to determine shoreline displacement and alongshore variability, the survey will 

encompass the entire length of the ocean beach at four of the Network’s ocean parks: 

Assateague, Cape Cod, Fire Island, and Gateway. The survey will also include the natural inlet 

shoreline from the oceanside to a bayside transition area characterized by a distinct orientation 

change and a reduction of wave and current energies. All of the spatial data will be recorded in 

Universal Transverse Mercator (UTM) coordinates; Assateague, Fire Island, and Gateway are in 

UTM NAD83 Zone 18 North, whereas Cape Cod is in UTM NAD83 Zone 19 North. 

Assateague Island National Seashore (ASIS) 

The ASIS shoreline (Figure 7) extends for approximately 63 kilometers of ocean beach from 

Ocean City Inlet, MD to Toms Cove Hook, VA. The northern terminus of the shoreline is at the 

jetty at Ocean City Inlet, MD (Figure 8). There is one transition area from ocean to bay at the 

south end of the survey, at Toms Cove Hook, VA (Figure 9). This transition area continues the 

shoreline around the end of the hook and terminates on the bayside where there is a distinct 

orientation change of the shoreline and a reduction of wave and current energies.

Cape Cod National Seashore (CACO) 

The CACO shoreline extends for approximately 87 kilometers of ocean beach from Race Point at 

the north to the southern end of Nauset Beach (Figure 10). There are a number of inlets along the 

ocean shoreline (Figure 11). The survey will extend into the bayside (beyond the initial 

orientation change) to track changes in inlet position as the spits migrate. Both termini 

incorporate hook-like appendages; the survey will extend to beyond their distal limits to record 

shifts and extensions. 

Gateway National Recreation Area – Sandy Hook Unit (GATE-SHU) 

The GATE-Sandy Hook shoreline extends for approximately 11 kilometers of ocean beach from 

the southern boundary with the township of Sea Bright, NJ to the US Coast Guard property in the 

north (Figure 12). At the northern terminus, the monitoring will extend into Sandy Hook Bay to 

record the elongation of Sandy Hook bayward. 

Gateway National Recreation Area – Breezy Point (GATE-BP) 

The GATE-Breezy Point shoreline consists of the approximately 3.5 kilometers of ocean beach 

at Breezy Point and 4 kilometers of ocean beach at Jacob Riis Park (Figure 13). The survey will 

continue between these two units of the parks to include the jurisdictional transition area fronting 

the Breezy Point Cooperative. The distal end of Breezy Point will be monitored into the bayside, 

including any beach accumulations west of the jetty. The eastern end of the survey is at the 

groin at the eastern margin of Jacob Riis Park. 

Gateway National Recreation Area – Plumb Beach (GATE-PB) 

The GATE-Plumb Beach Park is located inland of Rockaway Inlet and, therefore, is not a typical 

ocean shoreline. Nonetheless, the characteristics of the shoreline at Plumb Beach are similar to 

those of an ocean shoreline and are being subjected to the same kind of seasonal 

geomorphological response. The shoreline will be monitored for approximately 1.6 kilometers 

between an artificial shore-perpendicular structure to the west, and a natural channel to the east 

(Figure 14). The survey will extend farther east to incorporate the spit that has been accreting 

over a marsh area. 
18 

Gateway National Recreation Area – Staten Island Unit (GATE-SIU) 

The GATE-Staten Island shoreline is approximately 4 kilometers of ocean beach at Great Kills, 

approximately 0.5 kilometers of beach at Miller Field, and approximately 1.0 kilometer of beach 

at Fort Wadsworth (Figure 15). The westernmost end is the bulkhead at the boat basin. The 

easternmost end is the groin near the Verrazano Narrows Bridge. Between these park sections 

are jurisdictional transition areas on privately-owned and New York City properties. 

Fire Island National Seashore (FIIS) 

The FIIS shoreline extends for approximately 51 kilometers of ocean beach from Democrat Point 

to Moriches Inlet (Figure 16). There are jetty structures at both termini of the island. The 

western transition area is the expanding spit beyond the Fire Island Inlet jetty at the transition 

from ocean to bay processes (Figure 17). The eastern margin is at the Moriches Inlet jetty 

(Figure 18). 
19 

Figure 7. Spatial extent of GPS data collection of the ASIS ocean shoreline. Image from NPS ASIS. 
20 

Figure 8. Spatial extent of GPS data collection of the ASIS shoreline terminating in the north at the 

Ocean City Jetty. Image from NPS ASIS. 

Figure 9. Spatial extent of GPS data collection of the ASIS transition zone at Toms Cove Hook, VA.

Image from NPS ASIS. 
21 

Figure 10. Spatial extent of GPS data collection of the CACO ocean shoreline. Image from NPS CACO. 
22 

Figure 11. Example of the spatial extent of GPS data collection at an inlet in CACO. Image from NPS 

CACO. 
23 

Figure 12. Spatial extent of GPS data collection of the GATE - Sandy Hook ocean shoreline. Image from 

NPS-GATE. 
24 

Figure 13. Spatial extent of GPS data collection of the GATE - Breezy Point ocean shoreline. Image from 

NPS-GATE 

Figure 14. Spatial extent of GPS data collection of the GATE - Plumb Beach ocean shoreline. Image 

from NPS-GATE 
25 

Figure 15. Spatial extent of GPS data collection of the GATE - Staten Island ocean shoreline. Image from 

NPS-GATE 
26 

Figure 16. Spatial extent of GPS data collection of the FIIS ocean shoreline. Image from NPS FIIS. 
27 

Figure 17. Spatial extent of GPS data collection of the FIIS shoreline terminating in the east at the Fire 

Island Inlet jetty. Image from NPS FIIS. 

Figure 18. Spatial extent of GPS data collection of the FIIS shoreline terminating in the west at the 

Moriches Inlet jetty. Image from NPS FIIS. 
28 

Survey Frequency and Timing 

Weather induced changes in wave climate produce a distinct seasonal response in the shoreline 

position (List and Farris 1999). These locational responses typically reach their peak expression 

around the end of the winter and end of the summer seasons. In order to track this seasonal 

variation, shoreline surveys will be conducted on a twice per year basis and timed to capture the 

general occurrence of the maximum seasonal (winter/summer) state. Attention should be given 

to local weather conditions so as not to perform the seasonal survey within one week of a storm 

event (SOP#3 - Survey Timing and GPS Mission Planning). 

The shoreline survey should also be conducted when minimum satellite availability and satellite 

geometry specifications are met (SOP#5 - Conducting the Shoreline Survey). In addition there 

may be park specific issues such as the presence of species of concern or public activities that 

constrain the conducting of the shoreline survey. Managers of the park and adjacent lands that 

will be surveyed or crossed should always be consulted in advance when planning the survey. 

Details for timing and mission planning are provided in SOP #3 - Survey Timing and GPS 

Mission Planning 

As stated above, storm-affected beaches should be avoided when conducting the seasonal 

shoreline survey (Morton and Sallenger 2003). However, storm-response shorelines provide 

important measures of short-term variation and can be of great value to both park managers and 

coastal scientists. The protocol described here can also be applied to the storm-altered shoreline 

to derive supplemental measures of change. Pre-and-post-storm shoreline position surveys 

should be considered whenever possible. Because numerous storms of varying intensity and 

duration are expected to affect a given park in a typical year, the decision of when to conduct 

these additional surveys is problematic. At this time, there is no quantifiable measure or formula 

to calculate what constitutes a storm event and each park may have to establish its threshold 

conditions, incorporating wave dimensions, storm surge, erosion, and washover potential. Local 

observation and judgment must be exercised in making the determination whether or not to 

conduct the supplemental surveys. 
29 

Field Methods 

Field Season Preparations and Mission Planning 

Prior to the survey window, the entire protocol should be reviewed by the NCBN 

geomorphological monitoring project leader, the designated field observer at each park, and any 

park or Network staff or cooperators who will collect, process, or otherwise handle the shoreline 

data. Immediately following the protocol review, Internet URLs should be checked and mission 

planning for tides and satellite availability and satellite geometry should be initiated (SOP#3 - 

Survey Timing and GPS Mission Planning). Field equipment should be checked (SOP#1 - 

Equipment and Supplies). Two of the determining factors for the timing of the survey are tide 

situation and satellite availability. Both tide situation and satellite availability should be 

analyzed and a list of potential survey dates and times established and prioritized (SOP#3 - 

Survey Timing and GPS Mission Planning). As the survey window approaches, extended 

weather forecasts should be obtained and analyzed so that storm conditions can be avoided 

(SOP#3 - Survey Timing and GPS Mission Planning). It is strongly recommended that a trial 

survey be conducted to familiarize a first-time surveyor with the visual expression of the high 

tide swash line. A limited pre-survey test run is sufficient. 

Conducting the GPS Shoreline Survey 

The survey is designed to capture as closely as possible the position of the high-tide swash line 

during the period of neap tides (Figure 19). Surveys along the ocean shoreline are accomplished 

by driving a four-wheel all terrain vehicle (ATV) or four-wheel-drive truck along the high tide 

swash line. For the purposes of this monitoring program, the target ocean shoreline is represented 

as the position of the most recent and highest swash line (SOP#5 - Conducting the GPS 

Shoreline Survey). The GPS receiver is configured to record positions at a very short spatial 

interval for the best representation of the shoreline position (SOP#4 - Basic GPS Settings for 

Position Collection). The ATV should be driven so that the position of the antenna is located 

over the swash line. At least two survey monuments or some other marker with known 

coordinates should be included in the survey for general accuracy assessment. Additional details 

are included in SOP #5 - Conducting the GPS Shoreline Survey. 
30 

Figure 19. The high-tide swash line is clearly identified as a wet/dry line with wrack. 

Post-survey Data Download and Initial QA/QC 

Immediately upon completion of the survey and return to the office, the GPS data file will be 

downloaded from the receiver to a computer hard-drive and a backup copy created (SOP#6 - 

Initial Post-Survey Processing). The data should be retained on the datalogger until quality 

checks can be made. The downloaded data should be visually checked for general spatial 

integrity and the file attributes reviewed for field notations. The Field Data Form (FDF) should 

be completed and reviewed (SOP#5 - Conducting the GPS Shoreline Survey). Following all of 

the quality control procedures, the final shoreline data set will be sent to the NCBN data 

manager. 
31 

Data Management 

The NCBN Shoreline Change Monitoring Protocol generates a variety of data products that will 

be archived in a central MS Access database, overseen and controlled by the NCBN Data 

Manager. These data sets will be retrievable for broad-based usage and analysis. To better 

understand the structure of the archiving system, and the type of information available, a User’s 

Guide to the database has been produced that describes the elements of the data input and the 

categories of shoreline data (Appendix A). The User’s Guide also describes the procedures for 

retrieving information. Data storage and retrieval are vital elements of the NCBN shoreline 

monitoring effort. 

33 

Change Calculation, Data Analysis, and Reporting 

Generation of Changes in Shoreline Position 

The comparison of GPS shoreline positions and the quantification of their differences require 

that each GPS shoreline survey produces a continuous line feature from which distances to a preestablished baseline are measured. SOP #7 (Change Calculation, Data Analysis, and Reporting) 

describes how a baseline is created and explains how shoreline change is calculated using the 

Digital Shoreline Analysis System (DSAS) (Thieler et al. 2009). DSAS is the recommended tool 

for transforming the surveyed shoreline into a data matrix of distance measurements from which 

temporal and spatial changes are determined. Creation of the data matrix provides the basis to 

characterize the dimensional changes of the entire park’s shoreline as well as subsets of the park 

(special areas of interest). 

Data Analysis and Reports 

An analysis of the change of shoreline position will consist of the production of a suite of 

summary statistics that will describe the dimensions of the change, such as mean value and 

standard deviation. It will also identify the spatial distribution of the changes as a means to 

highlight locations of greater or lesser mobility. Annual reports will be produced to describe the 

seasonal changes as well as the year-to-year variations (SOP #7 - Change Calculation, Data 

Analysis, and Reporting). Longer-term reports will be produced at five-year intervals to look at 

trends in the temporal and spatial changes, covering the general shoreline of the Park as well as 

special areas of interest (SOP #7 - Change Calculation, Data Analysis, and Reporting). 

35 

Personnel Requirements and Training 

Roles and Responsibilities 

The NCBN is responsible for the development and implementation of the protocol and has 

assigned a Network staff-person as project leader. The NCBN project leader is responsible for 

coordinating protocol development as well as an implementation plan and schedule that is suited 

to the needs of the individual Network parks. The project leader will work closely with Network 

parks and their designated cooperators to develop and implement this protocol. 

The shoreline position protocol is designed to utilize local staff for field data collection. The data 

collection is improved through the use of personnel who have a basic understanding and working 

knowledge of the park and its resources. Because of their familiarity with its appearance, local 

personnel are much better situated to perform periodic observations of the beach. Their 

participation will thus greatly enhance accurate and consistent identification of the shoreline 

feature. The use of local staff also limits or prevents the problem of schedule overlap - where 

Network staff and cooperators might be expected to work in multiple parks at or around the same 

time. 

Inconsistencies inherent to qualitative (visual) identification of the shoreline are reduced when 

the number of observers is limited. Because it is a qualitative feature, no two observers will see 

or drive exactly the same shoreline. Spatial variability due to observer interpretation must be 

recognized and acknowledged. However, because an objective of the protocol is the 

establishment of long-term trends, it is likely that the minor inconsistencies introduced through 

the use of multiple observers will not seriously affect the value of the data. Nonetheless, 

consistent feature identification and measurement is important and assignment of data collection 

to a single or small number of Network-trained observers is highly recommended. 

The data management aspect of the monitoring effort is the shared responsibility of the field 

surveyor, the park and Network data managers, and the NCBN project leader. The field surveyor 

is responsible for field data collection, initial data download, and initial QA/QC, as well as 

providing information essential to the metadata file. The field surveyor should work closely with 

the Network and/or park GIS specialist for additional post-processing, differential correction, 

data verification and data validation, preliminary data editing, and export to the designated GIS 

format. The NCBN project leader is responsible for data documentation (metadata), data 

summary, and basic analysis and reporting. Ultimately, the NCBN geomorphological 

monitoring project manager has the responsibility to see that adequate QA/QC procedures are 

built into the database management system and that appropriate data handling procedures are 

followed. 

Qualifications and Training 

An essential component in the collection of shoreline data is a knowledgeable, competent, and 

attentive field surveyor. Because visual interpretation of the shoreline is the essential element of 

the protocol, the ability of the field surveyor to consistently identify the target feature is critical 

to accurate data collection. The field surveyor should have a basic understanding of coastal and 

shoreline processes, familiarity with the resource and appearance of the shoreline expression on 

the local beach, and competence and experience in the operation of all equipment being used in 
36 

the survey. The NCBN staff will assess the situation in each park and train local staff as required. 

(SOP #2 - Training for Field Data Collection). 
37 

Operational Requirements 

Annual Workload and Field Schedule 

GPS surveys will be conducted in early spring (mid-March to late April) and early fall (midSeptember to late October), a period that coincides with the peak expression of seasonal beach 

variability in the NCBN ocean parks. Extreme tide and weather events will preclude the 

scheduling of surveys to specific annual dates. Shoreline surveys require one person, although 

the survey could benefit from the use of one or more additional staff if qualified persons and the 

necessary supplemental equipment were available. Due to the different lengths of ocean 

shoreline in Network parks, time required for data collection will vary. In general, approximately 

five days should be allocated to complete all requirements of each field survey. 

Facility and Equipment Needs 

The equipment needed for the field survey consists of a four-wheel-drive vehicle (ATV is 

recommended), appropriate safety gear such as helmet, goggles, and gloves, and a GPS unit 

capable of sub-meter accuracy, single point position collection, and post-processed differential 

correction (e.g., Trimble GeoXT or equivalent). If two or more surveyors work simultaneously, 

field equipment requirements will increase accordingly. Should a park lack the proper 

equipment, the Network will attempt to arrange access to the items necessary to conduct the 

survey. 

A computer and peripheral devices with appropriate ports and cables, GPS processing software 

(e.g., Trimble Pathfinder Office) for download, initial QA/QC, and export to ESRI GIS format 

are required to complete the initial tasks. The GIS component consists of the ESRI ArcGIS 

software. Office computing needs and other equipment items are detailed in SOP #1 - 

Equipment and Supplies. 

Startup Costs and Budget 

Startup costs consist of the ATV, the GPS unit, and if the survey is planned and executed locally, 

the surveyor’s time (Table 2). If NCBN staff or their partners are required to perform the survey, 

staff time plus travel expenses must be included in the costs. Equipment consists of a GPS unit, 

an ATV, and a computer running GPS and ESRI GIS software. All of these items are available 

at Network parks. Gasoline for survey vehicle, media for backup of data, and other such costs 

are considered minimal and incidental. 
38 

Table 2. Data Collection Cost Estimates (US$, 2007). 

Item/Activity 1st Year 

Cost

5 Year 

Total Cost

Annual 

Cost

Annual Cost 

per Park

Per Survey 

Cost 

ATVs (4)1 26,000 26,000 5,200 1,300 650 

GPS (4)2 40,000 40,000 8,000 2,000 1,000 

Personnel3 12,000 60,000 12,000 3,000 1,500 

Computer4 

with ESRI GIS 12,000 18,400 3,680 920 460 

Total 90,000 144,400 28,880 7,220 3,610 

1= 1 ATV for each ocean park 

2= 1 GPS per ocean park 

3= Based on 8 weeks (2 weeks per park) at GS9 

4= 1 Computer and 1 annual ESRI GIS license per ocean park 
39 

Procedure for Revising and Archiving Previous Versions of 

the Protocol 

Over time, revisions to both the Protocol Narrative and to specific Standard Operating 

Procedures (SOPs) are to be expected. Complete documentation of changes to the protocol, and 

a library of previous protocol versions are essential for maintaining consistency in data collection 

and for appropriate treatment of the data during data summary and analysis. The MS Access 

database for each monitoring component contains a field that identifies which version of the 

protocol was being used when the data were collected. The rationale for including a narrative 

with supporting SOPs is based on the following: 

• The Protocol Narrative is a general overview of the protocol that gives the history and 

justification for doing the work and an overview of the sampling methods, but it does not 

provide all of the procedural details. The Protocol Narrative will only be revised if major 

changes are made to the protocol. 

• The SOPs, in contrast, are very specific step-by-step instructions for performing a given 

task. They are expected to be revised more frequently than the Protocol Narrative. 

• When a SOP is revised, in most cases, it is not necessary to revise the Protocol Narrative 

to reflect the specific changes made to the SOP. 

• All versions of the Protocol Narrative and SOPs will be archived in a Protocol Library. 

The steps for changing the protocol (either the Protocol Narrative or the SOPs) are outlined in 

SOP #9 - Revising the Protocol. Each SOP contains a Revision History Log that should be filled 

out each time a SOP is modified to explain why the change was made, and to assign a new 

Version Number to the revised SOP. The new version of the SOP and/or Protocol Narrative 

should then be archived in the Long Term Ecological Monitoring Protocol Library. 

41 

Literature Cited 

Allen, J. R., 2000. Vital Signs of Northeast Coastal Park Resource Change: Shoreline Monitoring 

Group Report. National Park Service Internal Report. 

Allen, J. R. and C. L. LaBash, 1997. Measuring shoreline change on Fire Island. Maritimes, 39: 

13-16. 

Allen, J. R., N. B. Shaw, and A. F. Lange, 1995. Modeling shoreline dynamics at Sandy Hook, 

New Jersey using GIS/GPS. Proceedings of CoastGIS ’95, pp 191-228. 

Bird, E. C. F., 1985. Coastal Changes: A Global Review. John Wiley & Son, London. 

Boak, E. H. and I. L. Turner, 2005. Shoreline definition and detection: A review. Journal of 

Coastal Research, 21: 688-703. 

Brock, J. C., M. Duffy, W. Krabill, M. Harris, L. Moore, and A. Sallenger, 2001. USGS-NPSNASA research on coastal change and habitats within U.S. National Seashores. Abstracts 

with Programs - Geological Society of America, Annual Meeting. Boston, Massachusetts. 

Carter, R. W. G., 1988. Coastal Environments: An Introduction to the Physical, Ecological, and 

Cultural Systems of Coastlines, Academic Press, London. 

Colwell, P. J., and B. G. Thom, 1994. Morphodynamics of coastal evolution. In: Carter, R. W. G. 

and C. D. Woodroffe, Eds. Coastal Evolution: Late Quaternary Shoreline Morphodynamics. 

Cambridge University Press, London. 

Davidson-Arnott, R., 2005. Conceptual model of the effects of sea level rise on sandy coasts. 

Journal of Coastal Research, 21: 1166-1172. 

Dolan, R., M. S. Fenster, and S.J. Holme, 1992. Spatial analysis of shoreline recession and 

accretion. Journal of Coastal Research, 8: 263-285. 

Farris, A. S. and List, J. H., 2007. Shoreline change as a proxy for subaerial beach volume 

change. Journal of Coastal Research, 23(3): 740-748. 

FitzGerald, D. M., M. S. Fenster, B. A. Argow, and I. V. Buynevich, 2008. Coastal impacts due 

to sea-level rise. Annual Review of Earth and Planetary Sciences, 36: 601-647. 

Graham, D., M. Sault, and J. Bailey, 2003. National Ocean Service shoreline - past, present, and 

future. Journal of Coastal Research Special Issue 38, pp 14-32. 

Honeycutt, M.C. and D. E. Krantz, 2003. Influence of the geologic framework on spatial 

variability in long-term shoreline change, Cape Henlopen to Rehoboth Beach, Delaware. 

Journal of Coastal Research Special Issue 38, pp 147-167. 
42 

IPCC, 2007: Climate Change, 2007: The Physical Science Basis. Contribution of Working 

Group I to the Fourth Assessment Report of the Intergovernmental Panel on Climate Change, 

Solomon, S., D. Qin, M. Manning, Z. Chen, M. Marquis, K. B. Averyt, M. Tignor and H. L. 

Miller, Eds. Cambridge University Press, Cambridge, London and New York, New York. 

Komar, P.D., 1998. Beach Processes and Sedimentation, Second Edition. Prentice Hall, Upper 

Saddle River, New Jersey. 

Krabill, W. B., C. W. Wright, R. N. Swift, E. B. Frederick, S. S. Manizade, J. K. Yungel, C. F. 

Martin, J. G. Sonntag, M. Duffy, W. Hulslander, and J. C. Brock, 2000. Airborne laser 

mapping of Assateague National Seashore beach. Journal of Photogrammetric Engineering 

and Remote Sensing. 66: 65-71. 

Kraus, N. C. and J. D. Rosati, 1997. Interpretation of Shoreline Position Data for Coastal 

Engineering Analysis. Coastal Engineering Technical Note II-39. U.S Army Engineers 

Waterways Experimental Station. Vicksburg, Mississippi. 

List, J. H. and A. S. Farris, 1999. Large-scale shoreline response to storms and fair weather. 

Proceedings, Coastal Sediments ’99. 2: 1324-1338. 

Moore, L. J., 2000. Shoreline mapping techniques. Journal of Coastal Research, 16: 111-124. 

Morton, R. A. and A. H. Sallenger, 2003, Morphological impacts of extreme storms on sandy 

beaches and barriers: Journal of Coastal Research, 19: 560-573. 

NPS NCBN - National Park Service Northeast Coastal and Barrier Network, 2003. 

Geomorphological Monitoring Workshops Report. NPS Internal Report. 

National Research Council, 1987. Responding to Changes in Sea Level: Engineering 

Implications. National Academy Press, Washington, D. C. 

National Research Council, 1995. Beach Nourishment and Protection. National Academy Press, 

Washington, D. C. 

Nicholls, R. J., P. P. Wong, V. R. Burkett, J. O. Codignotto, J. E. Hay, R. F. McLean, S. 

Ragoonaden and C. D. Woodroffe, 2007. Coastal systems and low-lying areas. In: M. L. 

Parry, O. F. Canziani, J. P. Palutikof, P. J. van der Linden and C. E. Hanson, Eds., Climate 

Change 2007: Impacts, Adaptation and Vulnerability. Contribution of Working Group II to 

the Fourth Assessment Report of the Intergovernmental Panel on Climate Change, 

Cambridge University Press, Cambridge, London, pp. 315-356. 

Nordstrom, K.F., 2000. Beaches and Dunes of Developed Coasts. Cambridge: University Press, 

Cambridge, London. 

Nummedal, D, O. H. Pilkey, and J. D. Howard, Eds., 1987. Sea-level Fluctuation and Coastal 

Evolution. Society of Economic Paleontologists and Mineralogists, Special Publication. 
43 

Pajak, M. J. and S. P. Leatherman, 2002. The high water line as shoreline indicator, Journal of 

Coastal Research, 18: 329-337. 

Pardo-Pascual, J. E., L. García-Asenjo, J. Palomar-Vásquez, and P. Garrigues-Talens, 2005. New 

methods and tools to analyze beach-dune system evolution using a Real-time Kinematic 

Global Positioning System and Geographic Information Systems. Journal of Coastal 

Research, Special Issue 49, pp. 34-39. 

Parker, B. B., 2003. The difficulties in measuring a consistently defined shoreline-The problem 

of vertical referencing. Journal of Coastal Research, Special Issue 38, pp. 44-56. 

Psuty, N. P. and D. D. Ofiara, 2002. Coastal Hazard Management: Lessons and Future 

Directions from New Jersey. Rutgers University Press, New Brunswick, New Jersey. 

Roman, C. T. and N. E. Barrett, 1999. Conceptual Framework for the Development of Long 

Term Monitoring Protocols at Cape Cod National Seashore. USGS Patuxent Wildlife 

Research Center. Cooperative National Park Service Studies Unit, Narragansett, Rhode 

Island. 

Roman, C. T. and K. F. Nordstrom, 1988. The effect of erosion rate on vegetation patterns of an 

East Coast barrier island. Estuarine, Coastal and Shelf Science, 26: 233-242. 

Short, A. D., 1999. Beach systems: Definition and global perspective. In: Short, A.D., Ed., 

Handbook of Beach and Shoreface Morphodynamics. Wiley and Sons, New York, New 

York. 

Thieler, E. R., E .A. Himmelstoss, J. L. Zichichi, and A. Ergul, 2009. Digital Shoreline Analysis 

System (DSAS) version 4.0—An ArcGIS Extension for Calculating Shoreline Change: U.S. 

Geological Survey Open-File Report 2008-1278. Available online at 

(http://pubs.usgs.gov/of/2008/1278/). Accessed 9 March 2010. 

Trenhaile, A. S., 1997. Coastal Dynamics and Landforms. Oxford University Press, New York, 

New York. 

Warrick, R .A., E. M. Barrow, and T. M. L. Wigley, Eds, 1993. Climate and Sea Level Change: 

Observations, Projections and Implications. Cambridge University Press, Cambridge, 

London. 

Wright, C. W. and J. C. Brock, 2002. EAARL: A LiDAR for Mapping Shallow Coral Reefs and 

other Coastal Environments. Conference on Remote Sensing for Marine and Coastal 

Environments. Miami, Florida. 

45 

Standard Operating Procedures 

Standard Operating Procedure (SOP) # 1 – Equipment and Supplies 

Version 1.0 (December 2009) 

The following table lists all changes that have been made to this Standard Operating Procedure 

since the original publication date. Any recommended or required changes added to the log must 

be complete and concise and promptly brought to the attention of the NCBN Project Leader. 

The project leader will review and incorporate all changes, officially complete the revision 

history log, and change the date and version number on the title page. For complete instructions, 

please refer to SOP#9 – Revising the Protocol. 

Revision History Log: 

New 

Version # 

Previous 

Version # 

Revision 

Date 

Author (full 

name, title, 

affiliation) 

Location in Document 

and Description of 

Change 

Reason for 

Change 

 

This standard operating procedure (SOP) details the items needed to execute the ocean shoreline 

position monitoring protocol. The ocean shoreline position protocol requires three major types 

of equipment, as well as a field data form and a field item checklist. The equipment types 

include: 

1. GPS system with sub-meter horizontal accuracy 

2. off-road vehicle and mounting device to carry the GPS 

3. PC capable of communicating with the datalogger on the GPS unit for pre- and postsurvey activities. 

GPS System 

Any GPS system may be used that has sub-meter accuracy and is capable of post-processed 

differential correction, or can accommodate real-time differential-correction of the survey points, 

such as the Trimble GeoXT (Figure S1.1). Operational settings and parts for each of the GPS 

systems may be different, but there are critical settings (SOP #5 - Conducting the GPS Shoreline 

Survey) and components that allow for consistent data collection across platforms. 
46 

Transportation Requirements 

Vehicle with spark resistor plugs (to eliminate radio interference) 

1. Off-road vehicle with GPS mount or, 

2. Quad or All-Terrain Vehicle (ATV) with GPS mount (Figure S1.1). 

Emergency and Safety Supplies: 

1. Cell phone or radio 

2. Park contact and emergency phone numbers 

Only with vehicle other than ATV: 

1. Shovels (4x4 only) 

2. Wooden boards (4x4) 

3. Extra fuel 

Figure S1.1. Example of a Trimble GeoXT GPS unit, with internal antenna and datalogger, mounted 

on an ATV. 

 
47 

Office Computer Equipment 

A PC that meets the minimum specifications for running GPS and GIS software is required. The 

NPS minimum standard for computer equipment meets these requirements. 

Software: 

A program capable of post-processing the collected field data (for example, Trimble Pathfinder 

Office); such a program is necessary if a real-time beacon receiver is not employed in the survey. 

Internet Connectivity: 

An internet connection (28.8kbps modem or faster) is needed for viewing the satellite almanac 

and tide charts (SOP #3 - Survey Timing and GPS Mission Planning), if not collecting real-time 

data, then conducting part of the differential correction (SOP #7 - Change Calculation, Data 

Analysis, and Reporting), and maintaining the GPS software/firmware updates. 

Forms and Checklist 

In addition to the GPS and transportation equipment, there are field forms and SOPs used in the 

preparation and execution of each survey: 

1. field copy of SOP#5 - Conducting the GPS Shoreline Survey 

2. field copy of the Field Data Form (Form #SOP5-1) 

3. office copy of the Field Equipment Checklist (Form #SOP1-1) 
48 

FIELD ITEM CHECKLIST 

Form # SOP1-1 

1. GPS Equipment

□ GPS receiver with datalogger, fully charged (required) 

 

2. Transportation Equipment 

□ ATV or 4x4 (required unless walking entire survey) 

□ Boards/rope or tow cable/shovel (recommended) 

□ Sufficient fuel (required) 

□ Extra fuel can (recommended) 

□ Tire pressure gauge (recommended) 

3. Auxiliary Items 

□ Cell phone or radio with charged battery (required) 

□ Field copy of SOP#5 - Conducting the GPS Shoreline Survey (required) 

□ Field copy of Field Data Form (required)

□ GPS receiver manual (optional)

□ Satellite availability and PDOP information (recommended) 

□ List of emergency phone numbers (required) 

□ List of park contact numbers (required) 

□ Camera (required) 
Standard Operating Procedure (SOP) # 2 – Training for Field Data Collection 

Version 1.0 (December 2009) 

The following table lists all changes that have been made to this Standard Operating Procedure 

since the original publication date. Any recommended or required changes added to the log must 

be complete and concise and promptly brought to the attention of the NCBN Project Leader. 

The project leader will review and incorporate all changes, officially complete the revision 

history log, and change the date and version number on the title page. For complete instructions, 

please refer to SOP#9 – Revising the Protocol. 

Revision History Log:

New 

Version # 

Previous 

Version # 

Revision 

Date 

Author (full 

name, title, 

affiliation) 

Location in Document 

and Description of 

Change 

Reason for 

Change 

 

This SOP establishes the responsibility for conducting training, details the content and frequency 

of Network training, and identifies the target audience of training. Because there are a number of 

decision-making steps in the shoreline-monitoring protocol, there is a need to provide for an 

understanding of coastal processes as a foundation for making shoreline identification. Training 

also explains and demonstrates the procedures for mission planning, operation of the GPS 

equipment, and post-survey data handling. Therefore, training is the basis for consistency in the 

execution of this protocol. 

Implementation of Training 

A critical component of the shoreline protocol is the GPS field survey of the shoreline. 

Successful execution of this task is contingent on properly-trained personnel. The shoreline 

survey requires specific steps in preparation, collection, and processing. It is the responsibility 

of the NCBN to develop and deliver a training program to provide a scientific and technical 

foundation for consistent and accurate data collection. 

Frequency of the Training Sessions 

Training shall be conducted prior to initial implementation of the protocol and thereafter at an 

interval of once every two years, or as needed due to staff or procedural changes.
50 

Target Audiences 

The Network shall provide training for two persons at each park. This will establish a core of 

competent and qualified shoreline surveyors. Additionally, data collection is improved when 

conducted by surveyors with local knowledge. Training two persons per park also helps to 

reduce problems related to staffing or scheduling.

Training Syllabus 

The purpose of training is to develop and maintain competence in the following: 

1. Basic Coastal Geomorphology 

a. Basic understanding of coastal process/response modeling 

b. Fundamentals of cross-shore profile development 

c. Characteristics of alongshore shoreline position variation 

d. Development of swash on the beach face and its relationship with the shoreline 

e. Importance of non-storm conditions for seasonal measurement 

2. Mission Planning – Choosing the right time to survey – SOP #3 

a. Seasonal timing 

b. Tides 

c. Storms 

d. Survey window 

3. Conducting the Survey 

a. How to choose the right line 

b. Obstacle avoidance 

c. Dealing with shoreline perturbations 

4. Using the GPS, including preparation of the equipment, setup, and field usage. 

a. GPS equipment components and preparation – SOP #1 

b. GPS setup and operation –SOP #4 

c. Datalogger Setup – SOP #4 

1. Configuration 

2. Begin the logging process 

3. Conducting the survey 
51 

4. Collecting benchmarks 

5. Finalizing the survey 

d. Filling out the Field Data Form – SOP #5 

 1. File naming 

 2. Form completion 

 3. Note-taking 

5. Park specific issues 

6. Post-survey processing – SOP #6 

a. Data downloading 

b. Data backup 

c. Initial quality assurance/quality control (QA/QC). 

Standard Operating Procedure (SOP) # 3 – Survey Timing and GPS Mission 

Planning 

Version 1.0 (December 2009) 

The following table lists all changes that have been made to this Standard Operating Procedure 

since the original publication date. Any recommended or required changes added to the log must 

be complete and concise and promptly brought to the attention of the NCBN Project Leader. 

The project leader will review and incorporate all changes, officially complete the revision 

history log, and change the date and version number on the title page. For complete instructions, 

please refer to SOP#9 - Revising the Protocol. 

Revision History Log: 

New 

Version # 

Previous 

Version # 

Revision 

Date 

Author (full 

name, title, 

affiliation) 

Location in Document 

and Description of 

Change 

Reason for 

Change 

 

The objective of this Standard Operating Procedure is to detail the process for selecting the 

temporal window for conducting the survey. The spring and fall seasons are the most likely times 

of the narrowest and widest beaches for the year, respectively (Trenhaile 1997). There is an 

opportunity to pre-select a survey period within these seasons that will maximize the opportunity 

to capture the seasonal variation. A standardized GPS survey window allows for comparability 

of the seasonal data set by collecting similarly-derived shorelines each year. 

The comparability of shoreline positions collected with GPS equipment depends greatly on the 

timing of the record. The variables that determine the timing within the window are either 

predictable or observable and can be established in the preceding months, weeks, or days to 

maximize the repeatability and the efficiency of the survey. This SOP describes the procedure 

for the long-range identification of neap tide conditions as well as the satellite availability and 

geometric configuration (PDOP). It establishes the basis for short-term evaluation of storm 

conditions that may affect shoreline position. It addresses the variety of local resource-related 

variables that may constrain conducting the survey, such as endangered species zones or 

accessing restricted areas. 

Creating the Survey Window 

One objective of this protocol is to record the seasonal change in shoreline position. Over the 

course of a year, a sandy beach goes through a landward and seaward oscillation as the 
54 

land/water surface contact (the shoreline) varies in position based on wave energy, sediment 

supply, and water level. These seasonal oscillations result in a narrowing and broadening of the 

beach. Observations of past summer and winter beaches at the Sandy Hook Unit of Gateway 

National Recreation Area demonstrate that beaches are at their narrowest by the middle of April 

(end of winter) and widest near the beginning of October (end of summer). Based on these 

observations and the general trends on other beaches in the Northeast Coastal Barrier Network, 

the optimal time for recording the seasonal oscillation of the beach is a six-week window in midMarch to late April and in mid-September to late October. 

Applying the neap tide variable 

The NCBN parks have semidiurnal tides; there are two high tides and two low tides each day. 

Each month there are two periods when the difference between high and low tide (the tidal 

range) is at a maximum, SPRING TIDE, and when it is at a minimum, NEAP TIDE (Figure 

S3.1). 

Figure S3.1. Predicted semi-diurnal tide levels during a six-week window at a coastal Virginia site 

(source: NOAA http://co-ops.nos.noaa.gov website). There are two uneven high and low tides each 

day. The spring tides occur on March 28th, April 10th and April 25th. The highest spring tide occurs on 

April 10th. The neap tides occur on March 19th, April 3rd, and April 18th. The red line is the water level 

threshold established three days on either side of the peak spring tide. The days available for 

surveying are highlighted in translucent green. Moon phases associated with the tides are displayed 

at the top of the graph. The solid moon symbol represents full moon; the open symbol is new moon.
55 

There are periods of mixed tides, when there is not a clean neap/spring signal. Times of elevated 

water levels relative to spring tide have the potential to have wave-generated run-up (swash) 

overtop the berm crest and spill onto the berm surface. Times of reduced tidal range, such as 

neap tide, minimize the water level variations within the monthly tidal cycle and therefore 

minimize variations in the shoreline position. Therefore, the neap high-tide swash line provides 

an optimal reference line because it will form on the beach face will represent similar shoreline 

positions (SOP#5 – Figure S5.1). Consequently, the optimum opportunity for shoreline 

collection in the six-week window is any day within three or four days of a neap tide, when the 

tide level is minimum. Running the survey during the minimum tide levels will guarantee that 

the swash line location between surveys is consistent. Exceptionally, the survey may be run 

during a period of mixed tides, during the lowest water levels predicted. For example, the tidal 

ranges over a six-week period in Figure S3.1 show that on the order of eighteen days will be 

excluded by the spring tide water levels, leaving a potential twenty-four days for surveying in 

each seasonal window. Daylight hours are an additional constraint that further limit which 

periods are most appropriate. 

To determine the predicted tides for the six-week survey window: 

1. Go to the predicted tide calculations available at the following NOAA website: 

 http://co-ops.nos.noaa.gov

2. Select Products → Tides → Observed Data – Active Stations 

3. Select the station according to its Station ID: 

• ASIS # 8570283 Ocean City Inlet, MD 

• GATE # 853160 Sandy Hook, NJ 

• FIIS # 853160 Sandy Hook, NJ 

• CACO # 8449130 Nantucket Island, MA 

4. Set “Data Units” to feet 

5. Set “Time Zone” to LST (local standard time) 

6. Select MLLW as the datum 

7. Tide data can only be displayed in 31-day increments. Set Begin date to one week prior 

to the first day of the six-week survey window, and the End date to one month following 

that date. 

8. Select View Plot for graphical form or View Data for tabular form. 

9. Repeat the process, advancing the Begin date forward by one month until the End date 

encompasses one week after the last day of the six-week survey window. 

Within each of the six-week survey windows designated for the spring and fall surveys, there 

will be many available survey days around the dates of neap tide water levels. The selected 

survey day should be the earliest convenient day in the window to allow for rescheduling if 

necessary. 
56 

Applying the Variable of Satellite Availability 

The GPS data used to record shoreline positions are derived from the time signals sent from 

satellites. Each surveyed position requires simultaneous readings from a minimum of four 

satellites (Trimble manual; p. 21; April, 2004). Five or more satellites will improve accuracy 

slightly. More important than the finite number of satellites is the combination of their number 

and their geometry, called PDOP (position dissolution of precision). PDOP is a unitless value 

that describes the accuracy of the derived position based on satellite count and geometry. This 

numerical value may vary during the course of a survey and thus it needs to be considered in the 

date and time selection. A PDOP between zero and six is necessary to collect accurate and 

precise shoreline positions. 

PDOP is a predictable value that can be plotted for the planned survey day. To view a PDOP 

plot, open the “Quick Plan” in Trimble Pathfinder Office (Figure S3.2) or access the satellite 

predictions by downloading the free mission planning software from the Trimble website 

(http://www.trimble.com). This plot identifies predicted PDOP values in advance of the survey. 

The “Quick Plan” plot represents the potential PDOP; this number will be increased (worsened) 

if the GPS receiver/antenna has an obstructed view of the sky, or if satellites become unavailable. 

PDOP fluctuates throughout the day as the satellites move in their orbits and change their 

relative geometry. PDOP values are generally within the zero to six threshold at all times in the 

Northeastern Parks, with occasional values greater than six near midday. Predictions of PDOP 

value are valid for a maximum of thirty days in advance. 

Figure S3.2. An example of the distribution of PDOP values using the Trimble Quick Plan software. 

PDOP values between 0 and 6 meet the survey criteria. The red line is the threshold PDOP value of 6. 
57 

To obtain a prediction of PDOP prior to the survey: 

1. On the Trimble website http://www.trimble.com/gpsdataresources.shtml, click “GPS 

almanac in SSF file format.” 

2. When prompted, Save the File to Disk in the folder C:\Program Files\Common 

Files\Trimble\Almanacs. 

3. Open the Trimble Pathfinder Office Software (TPO), or The Trimble Planning Software 

(TPS) – Planning Utility available at http://www.trimble.com. 

4. Choose Utilities → Quick Plan (TPO) or the File → Station (TPS). 

5. Select the date corresponding with the first day in the survey window. 

6. Select location of the city nearest the survey site, or enter coordinates within the park. 

• ASIS – Norfolk, VA 

• GATE and FIIS – New York, NY 

• CACO – Provincetown, MA 

7. Choose Options → Almanac, select the SSF file type, and browse to the almanac file 

downloaded in step 1. Click ‘OK’. 

8. Choose Options → Time Zone and select Eastern Std USA. Click ‘OK’. 

9. Choose Options → Elevation Mask, and enter “15.” Click ‘OK’. 

10. Choose Graphs → PDOP or ‘DOP – Position.’ 

11. Verify that PDOP is between zero and six for at least the majority of the survey day. If 

the PDOP frequently exceeds six, reschedule the survey to the next day in the survey 

window, and repeat the above steps. 

Evaluation of a Storm Event on the Survey Window 

Because the objective of this monitoring protocol is to track long-term changes in the shoreline 

position, surveys should not occur within one week after a storm event. If the survey were to 

occur after a recent storm the shoreline position might represent short-term changes, and not the 

net or longer-term change in position due to changes in sediment budget. 

A storm event, for this protocol, is defined as an event that produces an actual tide level of 

greater than one foot (0.32 meters) above the predicted high tide (Figure S3.3). A storm surge of 

greater than one foot at high tide may significantly displace the beach face and the subsequent 

position of the swash line. It can take up to a week for the beach to recover. 
58 

Figure S3.3. The depiction of water level and surge at Lewes, DE for the period Feb 23 – Feb 25, 2005 

(Source: NOAA http://co-ops.nos.noaa.gov). The horizontal dark green line represents the one foot surge 

threshold. February 23 – February 24 at noon would be acceptable survey days. On February 24 at 9 

pm, a surge (light green line) of greater than one foot occurs at high tide, and therefore the day is 

classified as stormy. The survey should not occur within one week following this condition. 

Storm surge elevation is determined by comparing the actual vs. predicted tides at the local 

NOAA tide gauge. The difference between the two data points represents the change in elevation 

of the water due to local conditions, referred to as surge. Stations to be used for surge calculation 

were selected because they have similar tidal ranges (approximately 5-6 feet (1.6-1.9 meters)) 

and therefore the one-foot surge threshold is consistent and proportional to this range. 

Beginning six days prior to the planned survey day: 

1. Access the NOAA tide gauges through the CO-OPS website at 

 http://co-ops.nos.noaa.gov. 

2. Select Products → Tides → Observed Data – Active Stations 

3. Select the appropriate station: 

• ASIS # 8570283 Ocean City Inlet, MD 

• GATE # 853160 Sandy Hook, NJ 

• FIIS # 853160 Sandy Hook, NJ 

• CACO # 8449130 Nantucket Island, MA 
59 

4. View the plot of water levels. The data may also be viewed in tabular form by clicking 

the Data Listing link. The difference between the Prediction and Actual

Observation is the Residual, or storm surge. It is this residual value that must not 

exceed one foot at high tide in the week prior to the chosen survey day. If the 

presence of a storm surge prevents the shoreline survey from occurring during the 

allotted timeframe, reschedule the survey to the next convenient day in the survey 

window. 

5. Steps 1-4 should be repeated four and two days prior to the survey and on the morning 

of the survey because the site only displays information for the previous two days. 

Resource Related Issues 

A complete shoreline position survey requires access to the beach face over the course of the 

survey. There may be time periods when access may be restricted to portions of the beach due to 

resource management issues that overlap with the survey window, such as periods of endangered 

species nesting, or park activities. Advanced planning is required to ensure complete spatial 

coverage. 

- Rare, Threatened, and Endangered Species 

If the beaches are closed for resource related issues such as bird nesting, surveying the shoreline 

may require the assistance of Natural Resource staff. The surveyor may require an escort 

through these areas, or the shoreline may need to be walked. If there are substantial areas that 

must be walked, allow extra time for the survey. If access to the shoreline will be completely 

restricted, plan the survey for an alternate day. 

-Other Constraints 

There may be access restrictions or other activities that will need to be addressed through park 

management. Scheduled events on the beach may restrict vehicular access to portions of the 

shoreline. If an event is planned on the survey day, allow extra time to walk the survey, or move 

the survey to one of the other days in the survey window. If high beach visitation is expected 

during the potential survey dates, try to schedule the survey for a day when neap high tide falls 

outside of the peak visitation hours, such as early morning. 

Points of Contact 

Resource and other related issues may require cooperation between multiple agencies and 

divisions within the shoreline survey area. A contact list should be kept up-to-date and stored 

with the GPS equipment. Contact should be made with any cooperating or neighboring agency, 

including management at State Parks, County Parks, other Federal Agencies, or other 

jurisdictional partners, in the weeks prior to the survey. 

Standard Operating Procedure (SOP) # 4 – Basic GPS Settings for Position 

Collection 

Version 1.0 (December 2009) 

The following table lists all changes that have been made to this Standard Operating Procedure 

since the original publication date. Any recommended or required changes added to the log must 

be complete and concise and promptly brought to the attention of the NCBN Project Leader. 

The project leader will review and incorporate all changes, officially complete the revision 

history log, and change the date and version number on the title page. For complete instructions, 

please refer to SOP#9 - Revising the Protocol. 

Revision History Log: 

New 

Version # 

Previous 

Version # 

Revision 

Date 

Author (full 

name, title, 

affiliation) 

Location in Document 

and Description of 

Change 

Reason for 

Change 

 

This SOP details the critical settings of the sub-meter GPS system for collecting the position of 

the shoreline and reference points, and gives a specific example of settings for the Trimble 

GeoXT equipment. There are a number of parameters that need to be preconfigured within the 

GPS system so that data collection is within the sub-meter quality specification. Additionally, 

standardizing the criteria for collecting GPS positions assures that the survey is replicable and 

comparable. Once the datalogger is configured, the settings should be re-confirmed immediately 

prior to conducting the survey. 

Critical GPS System Settings 

The following values need to be set on any GPS unit used to execute the ocean shoreline position 

protocol. They are set on the GPS unit prior to the survey through a variety of menus identified 

below. They are identified here as part of the necessary inputs. 
62 

1. Logging Settings: 

The frequency at which observations will be recorded: 

Feature Logging style Logging 

interval 

Point (monument, control point) Time 1 sec 

Line (shoreline) Distance 5 m 

2. Minimum positions per point observation – 12 positions 

The GPS system uses a minimum number of positions to determine an individual point/ 

vertex. A greater number of observed positions results in a more accurate feature. The 

setting value balances accuracy and field time. 

3. GPS Settings: 

 PDOP mask – 6.0 (default value) 

The PDOP value is the unitless representation of satellite geometry. A PDOP threshold 

of 6 is necessary to achieve sub-meter accuracy. 

 Elevation mask – 15 degrees (default value) 

The elevation mask is the angle relative to the horizon above which satellites will be used 

to generate the GPS positions. Satellites very low on the horizon degrade the PDOP and 

have signal errors due to increased distance that the signal travels through the 

atmosphere, and should therefore not be used. 

SNR (Signal to Noise Ratio) – 4.0 (default value) 

The signal to noise (SNR) ratio is a representation of the amount of usable information 

received versus the amount of discarded information (noise). A threshold of 4.0 is 

necessary to achieve sufficient signal for sub-meter positions. 

4. Real-time settings: Apply real time – no (default value) 

Application of real-time data correction precludes post-processing with some systems. In 

order to guarantee the ability to post-process the collected values, real time data 

correction should always be set to NO. If the individual GPS unit allows processing of 

real-time corrected data, Apply real-time may be set to YES. 

5. Antenna Height – 1.5 m 

Because only horizontal positions are being used to determine shoreline position, vertical 

elevations are not relevant. However, an approximate elevation should be entered to 

avoid complications in position calculations. 
63 

6. Coordinate System 

The Coordinate System Zone identifies the reference system on which the geographical 

data will be projected. The Datum refers to the mathematical model of the surface of the 

earth on which a mapping and coordinate system is based. 

 System: UTM 

 Zone: 18 North for GATE, ASIS and FIIS, and 19 North for CACO 

 Datum: North American Datum 1983 (NAD83) 

Units: Meters

Standard Operating Procedure (SOP) # 5 – Conducting the GPS Shoreline Survey 

Version 1.0 (December 2009) 

The following table lists all changes that have been made to this Standard Operating Procedure 

since the original publication date. Any recommended or required changes added to the log must 

be complete and concise and promptly brought to the attention of the NCBN Project Leader. 

The project leader will review and incorporate all changes, officially complete the revision 

history log, and change the date and version number on the title page. For complete instructions, 

please refer to SOP#9 – Revising the Protocol. 

Revision History Log: 

New 

Version # 

Previous 

Version # 

Revision 

Date 

Author (full 

name, title, 

affiliation) 

Location in Document 

and Description of 

Change 

Reason for 

Change 

 

The objective of this SOP is to detail the procedure for identifying and systematically recording 

the position of the shoreline. To reduce the effects of short-term variations in shoreline position, 

the optimal shoreline would be collected during a period of low tidal range (neap-tide) and 

during non-stormy conditions (SOP #3 - Survey Timing and GPS Mission Planning). Therefore, 

the target shoreline, for the purposes of this protocol, is the neap high-tide swash line (Figure 

S5.1). It is a representative qualitative feature that identifies a water/land surface intercept (a 

shoreline). It is easily collected using existing equipment, it is feasible to implement on the 

network level, and its collection as a dataset allows it to be compared to archives of historical 

shoreline positions. 

A preliminary part of the monitoring program is the selection of a shoreline survey window 

using the procedure in SOP #3 - Survey Timing and GPS Mission Planning. Unless constrained 

by a storm event or very high spring tides, the survey is scheduled for the first convenient hightide in mid-March to late April (spring survey) and mid-September to late October (fall survey). 

The shoreline data collection will begin soon after high tide (30-60 minutes), allowing sufficient 

time for the water level to recede. This will expose sufficient beach face for collection to be 

possible and leave a clearly identifiable high-tide swash mark. 
66 

Figure S5.1. Conceptual dune-beach profile showing the juxtaposition of water level, topographic 

features, and the identification of the neap high-tide swash line. 

 

This SOP consists of four components. The first component is the initial preparation procedures 

that include the visual identification of the line, initialization of the data form, and collection of 

the optional benchmarks. The second component is the survey of the shoreline with the GPS. 

The third component deals with natural or artificial perturbations to the shoreline, including 

natural features (e.g., cusps, scarps), hard structures (e.g., groins, jetties), and human interference 

(e.g., anglers). The fourth component ends the survey and records the position of any final 

benchmark. 

Component 1 - Preparatory Procedures: 

Before beginning data collection, go to the beach and visually confirm that the swash line is 

identifiable and on the beach face. The line may be a damp sand and shell hash line, a debris 

line, or some combination of these characteristics (Figure S5.2). The swash line’s presence on 

the beach face assures that no unusual wave or water levels were present. If the swash line is 

landward of the berm crest it is likely that the surge and tides that created this line exceeded the 

threshold for a low tide and/or non-stormy conditions. Therefore, the survey must be 

rescheduled using the procedures described in SOP #3 - Survey Timing and GPS Mission 

Planning. 

 

There may be more than one shell hash/debris line on the beach face. The more recentlydeposited high-tide swash lines are more distinctive than older, more muted lines (Figure S5.3). 

Less distinct lines will also be deposited as the tide recedes (Figure S5.3). It is essential to 

survey the most recent and highest of the shell hash lines on the beach face. 
67 

Figure S5.2. This high-tide swash line (dashed red line), on the beach face, is composed of the upper 

limit of damp sand, shell hash, and small amounts of debris. 

Figure S5.3. This recent high-tide swash line (dashed red line) is a damp sand and shell hash line 

with debris. There are older more muted lines landward and there are lower lines seaward. 
68 

Initiate the Field Data Form 

The Field Data Form (FDF) is used for all field notations (Figure S5.4). This information is 

necessary for post-processing of the data and facilitates the generation of accurate metadata. 

Once the shoreline has been visually identified on the beach face, fill in all fields (except for End 

time) in the “Event Information” and “GPS Device” sections of the FDF using the following 

formats. 

1. Date (mm/dd/yyyy) - Write the date in the format shown. Include the forward 

slash. Examples are 05/05/2005 and 12/31/2005. 

2. Park Unit – The 4 character park identifier, CACO, ASIS, GATE, FIIS, and the 

unit if applicable. For example, ASIS or GATE-SHU. 

3. Observers Name (First Middle Last) – Write the surveyor’s full name. 

4. Protocol/SOP Version (GMP version #/SOP version #) – Version of the protocol 

used to guide field data collection. Example is GMP v1.0/SOP#5 v1.1 

5. Date of last storm event – This information should have been gathered during 

mission planning (see SOP#3 - Survey Timing and GPS Mission Planning). 

Figure S5.4. Example of entries on the Field Data Form.
69 

Many of these initial values may be entered prior to going into the field. Additional items on the 

FDF (e.g., Start Time, End time, Survey Notes, Download options) will be logged later in the 

survey or can be derived from the GPS file in the post-processing phase. Any notes regarding 

equipment problems, obstacles encountered, etc., should be logged in the Survey Notes section, 

and the time from the GPS unit noted. Either the FDF or the comment/note function of the 

datalogger will be used to record observations and notes during the survey. If stored on the GPS 

unit, a copy of all comments should be attached to the FDF (either digitally or with a hard copy) 

prior to submitting all data products to the NCBN project leader. 

Incorporating Benchmarks into the Survey 

All GPS positions are independent data points, and collecting reference locations (benchmarks) 

at a variety of locations and times can help to verify the continued precision of the GPS 

measurements of the shoreline position. Benchmarks can serve as high quality reference points 

and can be collected when available as a check for accuracy both during and following the 

survey. 

To collect a reference point, position the GPS antenna directly over the benchmark and begin 

point feature collection. The GPS records the position of the antenna, so do not begin collection 

until the antenna is directly over the feature to be recorded. Store the benchmark and log the 

benchmark information on the FDF or make comments in the datalogger. Be sure to include the 

following information in the notes: 

1. time and point number of each benchmark recorded, as displayed on the GPS datalogger 

2. the unique benchmark identifier stamped on the benchmark 

3. the condition of the benchmark, especially if the condition is degraded or questionable 

Component 2 - Shoreline Survey Procedure

Beginning the Survey 

Mount the GPS antenna on the ATV or 4x4 vehicle. Position the vehicle at the starting point for 

the shoreline collection. Place the antenna between the observer’s position and a front tire (or 

over the driver’s side tire on a 4x4 vehicle) to make it easier for the operator to accurately drive 

the shoreline. Regardless of the placement of the antenna on the vehicle, the GPS always records 

the position of the antenna. Once the antenna is directly over the shoreline, collection can begin. 

Make a note on the FDF of the starting point number and time, or obtain this information from 

the GPS file after the survey. 

Notes should be as detailed as possible, and must include point numbers (if applicable) and 

detailed descriptions. These notes are crucial in the QA/QC procedure and are the only 

documentation for decisions made in the field. Do not use abbreviations in note taking. 
70 

To begin data collection: 

1. Open the pre-configured GPS file and pause the datalogger 

2. Position the antenna over the beginning of the shoreline 

3. Unpause logging to start the datalogger and begin collecting the line feature 

4. Ensure that the positions are being collected by observing the point count increasing 

and/or hearing the audible clicks (depending on one’s unit / settings) 

5. Once logging is verified, proceed to drive the shoreline, maintaining the antenna’s 

position over the high-tide swash line. 

Tracking the Shoreline 

The natural shape of the shoreline may be linear, it may be cuspate (scalloped), or there may be 

broad sweeping curvilinearforms in the beach (FigureS5.5). These configurations may be

indicative of a change in processes and are important to the shoreline collection. Make every 

effort possible to maintain antenna position over the high-tide swash line while following these 

features. 

Figure S5.5. Example of a cuspate shoreline where the high-tide swash line tracks the shape of the 

cusps. Cusp dimensions are approximately 10-15 meters alongshore and the swash line should be 

followed as part of the shoreline survey. 

If the features are very small (on the order of a few meters), driving the line will naturally 

average these features because it would be impractical to position the antenna to follow every 

nuance of the line (Figure S5.6). The dashed line in Figure S5.6 shows the path that should be 

taken in surveying the very irregular swash line on a nearly linear beach face. These smalldimensioned irregularities are related to the micro-topography of the beach and are therefore 

representative of short-term conditions, rather than long-term (seasonal and longer) trends. 

Large dimension cusps, on the order of 50 meters or greater, may be indicative of sediment 
71 

budget processes that are representative of trends of seasonal and annual time scales, and 

therefore their location should be recorded. Cusps greater than 10 meters alongshore should be 

followed wherever possible. 

Figure S5.6. The high-tide swash line (red dashed line) has small irregularities that will be 

smoothened, recording the average position of the line. 

Verification of the Survey 

Every 15-20 minutes, visually verify that points are still being collected, and visually note the 

location. Verification of the datalogger’s functionality reduces the potential loss of data. If 

points are no longer being collected, rectify the problem and return to the previous verification 

point and resume shoreline collection. These brief stops provide an opportunity to survey 

supplemental benchmarks if they are available and nearby. Anytime logging is stopped and 

restarted, a note should be made on the Field Data Form or in the datalogger. 

During any stop: 

1. Confirm points are still being collected

a. If points are being collected, continue survey 

b. If points are not being collected, rectify problem, and return to last known verified 

point location and resume shoreline survey. 

2. (Optional) If a benchmark is nearby and convenient, record the position of the 

benchmark as a point feature 3 

3. (Optional) End and store the line feature, and start a new line feature in the same GPS 

file. Any time the survey is stopped there is an opportunity to store the feature to help 

prevent loss of data. 
72 

Photographs 

Take a photograph at sites along the survey that have an identifiable geographical reference, such 

as a prominent natural feature, or some cultural feature. Similar views will allow for visual 

comparison between surveys. Take a photograph in areas of special concern or anytime some 

irregularity occurs on the beach, such as the presence of scarps. Also, the photo should include 

the neap-tide, high-tide swash line that is being followed 

Component 3 - Interruption Procedure

Interruptions to the Shoreline Survey 

During the survey, a variety of landforms and obstacles may be encountered. Natural landforms 

such as scarps or cliffs may either temporarily impede the collection of the line, cause a break in 

the line (where the line has to be paused and restarted after the obstacle is passed), or cause a 

different collection method to be used (such as walking the shoreline). The shoreline may also be 

physically interrupted by artificial structures (groins, jetties, seawalls). Additionally, shoreline 

collection may be interrupted by human obstacles (anglers, bathers). Other than these situations, 

and in the presence of unusual interruptions, the field surveyor should make a note on the Field 

Data Form. 

The shoreline, in some places, may be difficult to survey with a vehicle because the beach may 

become excessively steep, it may be very narrow, or there may be restricted access. For example, 

the swash line may be at the base of a steep scarp, or beach visitors may make it impossible to 

drive the beach face. In this case, pause the datalogger and remove the GPS unit from the 

vehicle. Position yourself on the swash line location, and re-start the datalogger. Walk the 

shoreline (Figure S5.7), recording the swash line location until the shoreline can be reoccupied 

using a vehicle. Pause the datalogger until the vehicle is brought to that point. 

Figure S5.7. Conducting the survey and holding the GPS receiver. The operator walks along the 

wet/dry line on the beach face to capture the position of the neap high-tide swash line. 
73 

Hard Structures: Physical obstacles may impede the collection of a continuous shoreline. In 

this case, the datalogger must be paused so that only the dynamic sandy portion of the shoreline 

is collected. This will guarantee that the shoreline collected is comparable to other datasets and 

prevents the need for portions of the shoreline to be interpreted differently. If the static structure 

at the shoreline is collected, the feature must be coded separately or collected as a separate 

feature to ensure it is not misinterpreted. Make detailed and specific field notes on the data sheet 

to aid subsequent processing, editing, and metadata notations. If the structure causes an offset in 

the shoreline, such as the displacement of the shoreline on the updrift and downdrift sides of a 

groin (Figure S5.8), pause and store the line feature, go around the obstacle, and start a new line 

feature (in the same file) once the antenna has been repositioned over the shoreline. Anytime the 

GPS is removed from the vehicle there is an opportunity to add a supplemental benchmark.

Anglers: Anglers tend to congregate near the high-tide swash line. Their fishing lines and 

equipment can create a hazard to a surveyor in an ATV or vehicle. Also, GPS equipment can cut 

or break fishing lines. If anglers are encountered, pause the datalogger, go around the obstacle, 

reposition the antenna over the shoreline, and resume the datalogger and driving. 

Figure S5.8. This aerial view of GATE-SHU demonstrates the offset of the shoreline at an 

interruption. Source: NPS-GATE 

Component 4 - Completion of the Survey 

Completion 

After the spatial extent of the shoreline survey is completed, pause and store the line and collect 

the end of survey benchmark. 

1. Pause and store the survey shoreline while stopped on the swash line. 

2. Make a note on the Field Data Form of the End Time (if making all notes on the 

FDF). Use the time displayed on the GPS receiver, not off a watch. 24-hour 

(military) time should be used, in local standard time. For example, 0800 and 

1350 for 8am and 1:50pm, local time, respectively. 
74 

3. Store the line feature 

4. Optional - Drive to the nearest or most convenient benchmark 

5. Remove the GPS from the vehicle. 

6. Position the GPS antenna over the benchmark. 

7. Create a new point feature 

8. Once at least 12 positions have been recorded, store the point feature. 

9. Record the position of the final benchmark and log the information on the Field 

Data Form. 

10. Turn off datalogger 

Upon return to the office, download the data and make a backup copy (SOP #6). If the data are 

not downloaded immediately there is a chance they could be lost due to an equipment 

malfunction. 
75 

Form SOP#5-1: 

77 

Standard Operating Procedure (SOP) # 6 – Initial Post-Survey Processing 

Version 1.0 (December 2009) 

The following table lists all changes that have been made to this Standard Operating Procedure 

since the original publication date. Any recommended or required changes added to the log must 

be complete and concise and promptly brought to the attention of the NCBN Project Leader. 

The project leader will review and incorporate all changes, officially complete the revision 

history log, and change the date and version number on the title page. For complete instructions, 

please refer to SOP#9 – Revising the Protocol.

Revision History Log: 

New 

Version # 

Previous 

Version # 

Revision 

Date 

Author (full 

name, title, 

affiliation) 

Location in Document 

and Description of 

Change 

Reason for 

Change 

 

The objective of this protocol is to convert the collected shoreline position data into a useable 

dataset that is in the correct format and has undergone initial quality control (QA/QC) checks. 

Quality control checks ensure that the data collected are of the maximum quality possible. 

Download and QA/QC of the survey data are to occur immediately following the field data 

collection to ensure that no data are lost due to equipment failure. In addition, prompt data 

processing immediately informs the surveyor if a repeat survey day is required due to equipment 

issues. 

This protocol summarizes the data download procedures and initial quality control steps 

necessary for accurate and systematic processing. It demonstrates how to connect the Trimble 

GeoXT datalogger to a computer running Pathfinder Office software (for example), how to 

perform initial quality checks, and how to set up appropriate output specifications. It describes 

the process for converting the evaluated point shapefile into a single shoreline feature (polyline 

shapefile), generating FGDC-compliant metadata for that polyline file; and assembling all 

original, corrected, and processed data products for delivery to the NCBN for storage and 

analysis. 
78 

Connection of the datalogger to the computer for survey transfer 

Data collected in the field should be transferred to a PC for backup as soon as possible after the 

survey. The data should not be left in the datalogger overnight without first downloading. Even 

after the data are transferred, do not delete the data file until confirmed backups have been made. 

1. Connect datalogger to PC using a USB or serial data cable, or using a Bluetooth 

connection. 

2. Power on the GeoXT. 

3. On the PC, open the Trimble Pathfinder Office software. 

4. In the Select Project dialog box that appears, select ‘New...’ 

a. Project name: Park Code _ Season _ 4-digit Year (e.g. FIIS_FALL_2007). 

b. Comment: Adjust to match the survey date and start time. 

c. The project folder and sub-folders may be left as the default setting or 

changed to a custom location on the PC as desired. 

5. Click ‘OK’ twice. 

6. Select Utilities → Data Transfer. The software should automatically connect to the 

datalogger. If the software does not automatically connect, check the cable 

connections and port settings under “Device,” and click the ‘Connect’ button . 

7. Click ‘Add’ → Data File, and browse to the file(s) to transfer. 

8. Click ‘Transfer All’. 

9. Click ‘Close’. 

The transferred files will be in “.ssf” format. If using a computer which has a version of 

Microsoft ActiveSync installed 

(http://www.microsoft.com/windowsmobile/activesync/default.mspx), a connection to the 

GeoXT may be automatically established upon plugging the datalogger into the machine. In this 

case, the .ssf file can be directly dragged-and-dropped from the GeoXT onto the computer’s hard 

drive. Note: if the shoreline survey data were collected using a shapefile uploaded to the 

GeoXT, be sure to also transfer that file along with the .ssf file. 

Differential Correction of the Shoreline Survey (unless accomplished in real-time collection 

with Beacon) 

The raw data downloaded in steps 1-4 of this SOP need to be differentially corrected to reach the 

maximum accuracy possible for the Trimble GeoXT equipment. The process of differential 

correction compares the records received at one or more local known GPS base stations to those 

received in the field. 

Use the "Differential Correction" tool in Pathfinder Office and chose the reference station(s) 

closer to the location of the survey site to guarantee the most accurate differential correction. 

Wait 24 hours after data collection to post-process the data to ensure that all base files have been 

posted. The post-corrected output file has the extension “.cor”. A log file will also be saved with 
79 

the “.cor” file detailing the differential correction process and any errors that have occurred. 

Typically, 100% of the points will be corrected. 

Data Export 

Once the data have been downloaded, differentially corrected, and passed through initial 

QA/QC, they should be backed up. Making duplicate copies of the data should be a standard 

practice to prevent problems associated with loss of files and possible data corruption. 

Use the "Export" tool in Pathfinder Office to export the ".cor" file to a file with the "ESRI 

Shapefile" format. Make sure that the "Export Setup" properties are as follows: 

i. Data 

1. Features – Positions and Attributes – selected 

a. Export all Features 

2. Notes – checked 

3. Velocity Records – unchecked 

4. Sensor Records – unchecked 

ii. Output 

1. Select “Combine all input files and output to the project export folder” 

2. Select DOS files 

iii. Attributes – Export Menu Attributes As – Select “Attribute Value” 

1. All Feature Types – select ONLY 

a. PDOP 

b. Date Recorded 

c. Time Recorded 

2. Point Features – select ONLY 

a. Position 

b. Horizontal Precision 

3. Line Features – select ONLY 

a. Length (2d) 

b. Avg Horizontal Precision 

4. Area Features – select NONE 

iv. Units 

1. Use Export Units – select: 

a. Meters 

b. Square Meters 

c. Meters per second 

2. Decimal Places 

a. Lat/Long – 9 

b. North/east – 3 

c. Height – 3 

d. Distance – 3 
80 

e. Area – 3 

f. Velocity – 3 

g. Precision – 1 

h. Time – 0 

v. Position Filter – Select Filter by GPS Position Info 

1. Minimum Satellites – 2D (four or more SVs) 

2. Maximum PDOP (any) 

3. Maximum HDOP (any) 

4. Include positions that are – select ONLY 

a. Real-time Differential 

b. Differential 

c. RTK (fixed) 

d. Phase Processed (fixed) 

vi. Coordinate System – UTM 18 North/19 North (CACO Only) 

vii. Arcview Shapefile – select NONE 

Copy the exported data, along with the original “.ssf”, the initial “.cor”, any supporting text log 

files, and an image scan of the Field Data Form, to an external media (CD or external drive) so 

that there are separate backup locations (one on the hard disk drive and one on the removable 

media). Place all files in a folder labeled with the survey location and time. 

Once the data have been exported and backed up, verify that the backups exist in various 

locations, including the PC and a least one type of removable media. This guarantees that 

duplicate copies of the raw and corrected files exist. Once the duplicate copies are verified, the 

data may be deleted from the datalogger. 

Initial QA/QC 

QA/QC (Quality Assurance/Quality Control) is a verification step that ensures the data collected 

have had obvious errors removed and that the remaining data are likely to accurately represent 

the shoreline. Verification of the known benchmarks embedded in the survey adds credence to 

the collected shoreline positions. 

1. Using GIS software such as ESRI ArcGIS, open the “.shp” file exported above. 

2. Add current orthophotography and other available base data to the view and the known 

benchmarks (points) with their known values. 

3. During this procedure the surveyor should be present, along with the notes on the Field 

Data Form. Visually compare the expected feature locations with the recorded 

locations. If any features have obvious errors, they should be corrected. 
81 

4. Compare the collected benchmarks with their known values. If the difference between 

the recorded position and its known value is greater than one meter, the shoreline may 

need to be re-surveyed. 

Generating the Shoreline Line Shapefile from a Point Shapefile 

The utilization of some combinations of GPS units and software may necessitate the shoreline be 

collected as a point dataset rather than a line. In such a case, once the “cleaned” point shapefile 

has been exported, it must be converted into a continuous line feature in order to be analyzed by 

shoreline-change analysis software (see SOP #7 - Change Calculation, Data Analysis, and 

Reporting). This general procedure can be accomplished using any number of GIS software 

packages capable of rendering and editing shapefiles. The following steps describe the process of 

generating a line feature from a point shapefile using ESRI ArcMap software, the most common 

product used by NPS GIS personnel. 

1. If for some reason x and y coordinates are not present in the point shapefile’s attribute 

table, use the “Add XY Coordinates” tool to create these fields, or use the 

“addxy_management” command at the command line. 

2. Open the attribute table of the point shapefile. 

3. Under ‘Options’ choose ‘Export’; save the attribute table as a dbf file. 

4. Using Microsoft Excel, Word, or another spreadsheet or word processing program, 

generate a text file in which each point is represented with a line of text in the following 

format: ID number, x-coordinate, y-coordinate. The last line should simply contain the 

word “end.” 

5. Save the file with the extension “.gen” (e.g., points.gen). 

6. Use the “Generate” tool in ArcMap to create the line shapefile. 

7. View both the point and line shapefiles together in ArcMap to assure that the conversion 

completed successfully*. 
82 

* Alternatively, there are many free ArcMap extensions capable of converting point shapefiles 

into line features with a single step. An excellent example is the Convert Locations To Paths

tool found in the HawthsTools suite (http://www.spatialecology.com/htools/tooldesc.php). 

Creating Metadata for the Shoreline Shapefile 

The NCBN has created a metadata template for the Shoreline Change Protocol that already 

contains much of the relevant information regarding creation of the line shapefile. Most of the 

remaining information to be included will be derived directly from the field sheet completed 

prior-to and during the data collection process. Table S6.1 summarizes where this information 

should be included in the metadata file. At a minimum, the metadata should be parsed and 

exported in XML format using the NPS Metadata Tools available at 

http://www.nature.nps.gov/im/units/mwr/gis/ . 

Field form data Metadata tag

Park Unit Abstract 

Keywords 

GPS unit Make and Model Process step, Process description 

Expected Accuracy with differential correction Positional accuracy, Horizontal positional 

accuracy, Horizontal positional accuracy report 

GPS Unit Settings Positional accuracy, Horizontal positional 

accuracy, Horizontal positional accuracy report 

Who processed the data Process step, Process contact 

Software used to download, post-process data; 

Base station(s) used; description of any data editing Process step, Process description 

Table S6.1. Organizational comparison of field data and metadata files. 

Final Product Delivery 

The following raw data products should be delivered to the NCBN Data Manager for storage, 

analysis, and archiving in the Shoreline Change Database: 

1. All original GPS data files (.ssf) downloaded from the GPS unit 

2. All differentially corrected GPS data files (.cor), if real-time correction was not employed 

3. Cleaned, exported ESRI point shapefile (.shp; if applicable) 

4. Cleaned, continuous shoreline line shapefile (.shp) 

5. Metadata for the above line shapefile. 
83 

6. Hard or scanned copies of all field sheets. 

7. Photographs taken during survey. 

These items should be emailed to the Data Manager (see website for address: 

http://www.nature.nps.gov/im/units/ncbn/), posted via the NPS public FTP site, or saved to disc 

and mailed to: 

Northeast Coastal & Barrier Network 

Data Manager 

URI Dept. of Natural Resources Science 

1 Greenhouse Rd. 

Kingston, RI 02881 

85 

Standard Operating Procedure (SOP) # 7 – Change Calculation, Data Analysis, 

and Reporting 

Version 1.0 (December 2009) 

The following table lists all changes that have been made to this Standard Operating Procedure 

since the original publication date. Any recommended or required changes added to the log must 

be complete and concise and promptly brought to the attention of the NCBN Project Leader. 

The project leader will review and incorporate all changes, officially complete the revision 

history log, and change the date and version number on the title page. For complete instructions, 

please refer to SOP#9 - Revising the Protocol. 

Revision History Log: 

New 

Version # 

Previous 

Version # 

Revision 

Date 

Author (full 

name, title, 

affiliation) 

Location in Document 

and Description of 

Change 

Reason for 

Change 

 

The comparison of GPS shoreline positions and the quantification of their differences requires 

that each GPS shoreline survey be transformed into a continuous line feature from which 

distances to a pre-established offshore baseline are made. Distances from each GPS shoreline 

feature to the baseline are measured using pre-established transects at regular intervals. The 

results of these comparisons are then entered into a distance matrix. Creation of the data matrix 

provides the means to characterize the entire shoreline (as a whole) as well as subsets of the 

shoreline (smaller areas of interest). This SOP identifies the Digital Shoreline Analysis System 

as the recommended tool for measuring and reporting the changes in shoreline position. 

Additionally, this SOP describes a suite of summary statistics and trend analyses that can be used 

in describing and comparing the spatial measures of change. It concludes with an organization 

structure for the Annual Report and the Project Trend Report. 

Objectives of this SOP 

Unlike the previous SOPs that describe an activity to be accomplished as a means to collect, 

download, and transmit the collected shoreline position data, this SOP describes the approach 

that is used to transform the shoreline survey polyline into a suite of measurements that comprise 

a data matrix that serves as the basis for subsequent calculations of dimensions of change. The 

transformation is conducted by the NCBN project leader rather than the field investigator and the 

output is shared within the Park and within the Northeast Coastal and Barrier Network. This SOP 

therefore, in part, provides information and contributes to an understanding regarding the 
86 

generation of the matrix of measurements of shoreline change and the format of the data output. 

Further, this SOP presents a series of guidelines that describe the composition of the data 

portrayal and analysis to be used in the production of the Annual Report and in the Project Trend 

Report. 

Procedural Background Steps 

The procedures described in this SOP utilize a program developed by the United States 

Geological Survey entitled Digital Shoreline Analysis System (DSAS) that has been developed 

to measure, calculate, and statistically analyze changes in shoreline position (Thieler et al. 2009). 

DSAS is an open source extension to ESRI ArcMap 9.x software. The latest version, along with 

installation instructions, a detailed user’s manual, and additional background information can be 

found at: http://woodshole.er.usgs.gov/project-pages/dsas/. 

The basic concept underlying the comparison of the GPS shoreline positions and quantification 

of their differences within the DSAS program is that a series of preliminary steps are required to 

enable the calculation of shoreline change. These steps incorporate the development of a 

trendline (a general shoreline), a corresponding offshore baseline, and the generation of equallyspaced transects extending inland from the offshore baseline. After these line products are 

created (they are generated once for each park), they are used in the processing of each GPS 

shoreline. The following section describes the steps by which the DSAS requirements of a 

Shoreline Trendline, Baseline, and Transects are generated. 

Creation of the Trendline and the Baseline 

The Trendline represents the general trend of the shoreline (Figure S7.1) as determined using 

current orthophotography for each Park. It is created by drawing a smoothed line along the 

entire length of the ocean beach shoreline. The Trendline is digitized using ESRI ArcMap 

software and saved as a geodatabase polyline feature. The Trendline is used to generate the 

offshore Baseline from which distances to the surveyed GPS shorelines are measured. The 

Baseline is developed by re-creating the Trendline approximately 200 meters seaward and 

parallel to the smoothed shoreline (Figure S7.2) using the buffer function in ArcMap. This 

creation of an offset reference for subsequent comparison is necessary so that future positions of 

the eroding or accreting shoreline will not intercept the Baseline and thereby complicate the 

mathematical calculations. The Trendline and Baseline are created once for each park, and will 

only need to be modified if they no longer represent the general trend of the shoreline; for 

example, if there is a major (catastrophic) change. The Trendline and the Baseline are retained in 

the Geodatabase for each Park (Appendix A, Database User’s Guide). 
87 

Figure S7.1. The Trendline is a smoothed representation of the general trend of the shoreline that 

removes the minor features caused by local conditions (this example is a part of the Fire Island National 

Seashore). 

Figure S7.2. The Baseline is positioned 200 m offshore, parallel to the Trendline. 
88 

Creation of Transects 

Once the Baseline is created, transects are generated using the DSAS toolbar in ArcMap. The 

process for creating these transects is demonstrated in the user guide, Section 6, available on the 

DSAS website (http://woodshole.er.usgs.gov/project-pages/DSAS/version4/). Details of how to 

correctly format files for import and use in the DSAS extension are also provided in the DSAS 

tutorial and user guide. Additionally, the DSAS website provides a sample data set to be used as 

a model. The DSAS software allows the user to generate transects at equally spaced locations (10 

m in this case) originating at the Baseline. These initial transects are created automatically in 

DSAS and may be subsequently adjusted using DSAS and ArcGIS so that they intersect the 

Trendline at approximately 10m intervals and are all approximately perpendicular to the 

Trendline (Figure S7.3). These transects are used in DSAS to measure distances between each 

GPS-measured shoreline and the Baseline. The even spacing of transects along the Trendline 

supports the unbiased and systematic calculations of descriptive summary statistics, such as the 

mean value and the standard deviation of shoreline change as well as trends in change over time. 

Figure S7.3. The yellow lines originating at the Baseline are the transects created by DSAS that will be 

used to measure distances from the Baseline to the surveyed shoreline position at each of the intercepts. 

Adjustment of Transects 

Transects crossing relatively straight sections of shoreline need little if any adjustment. However 

transects crossing the Trendline in more curvilinear sections will need to be adjusted, e.g. added, 

deleted, or moved, so that all transects intersect the Trendline perpendicularly at roughly 10 m 

intervals (Figures S7.4a-b). These adjustments can be accomplished using the smoothing 

function routine when casting transects in DSAS and/or utilizing the feature editing capabilities 

of GIS software packages such as ArcMap. 
89 

Figures S7.4a-b. Example of transects created automatically by DSAS for a curved portion of the Sandy 

Hook shoreline (left panel) and those same transects after manual adjustment (right panel). Transects 

are shown in yellow in both panels. 

In summary, the steps required to generate measurements of shoreline change and subsequent 

analyses of these changes consist of: 

1. Producing a smoothed shoreline (Trendline) and an offshore Baseline 

2. Creating a series of evenly-spaced transects originating from the offshore Baseline in 

DSAS 

3. Adjustment of transects using DSAS and/or ArcGIS so that each transect intersects the 

Trendline perpendicularly at approximate 10 m intervals 

The most current versions of the Baseline and transects reside as line feature classes in a 

Geodatabase for each park, which is maintained by the NCBN Data Manager. 

Collection and Storage of the Shoreline Survey

Continuous Shoreline Creation 

Depending on the equipment and settings used, the initial survey of the GPS shoreline position 

produces either a continuous line feature or a dataset consisting of a series of points spaced 10 

meters apart. If the latter is the case, then the GPS shoreline data must be transformed into a 

continuous line feature in order to generate comparative distance measurements and summary 
90 

statistics of the entire ocean shoreline (Figure S7.5). Procedures for converting a point dataset to 

a continuous line dataset are presented in SOP#6 - Initial Post-Survey Processing. 

Once created, the new shoreline polyline shapefile will be exported and saved to the appropriate 

park’s geodatabase and a record will be added into the appropriate table in the protocol database 

(See SOP#8 - Data Management). 

Figure S7.5. Example of GPS Shoreline used for measuring distance from the Baseline to the survey line. 

The shoreline survey consists of the blue points that are connected to create a continuous line. The 

distance between the Baseline and this surveyed line is measured at each transect intercept (approx. 

every 10 meters). 

Data Matrix of Shoreline Distances 

Each GPS-shoreline will be used to generate a series of distance measurements from the offshore 

Baseline at each of the transects (Figure S7.6). These measurements will be automatically 

calculated in DSAS and exported in tabular format for summary and analyses purposes. 

Formatted results are shown in Table S7.1. 

The distance output from DSAS (Table S7.1) can be formatted so that the shoreline position data 

are represented by a matrix of sequential shoreline distance measurements. The product of 

multiple surveys will be a matrix of comparable distance values (Table S7.2). The matrix 

approach supports the generation of comparisons among any of the shoreline positions and 

requires that each shoreline be processed only once. 
91 

Figure S7.6. Transects are used to measure distances from the Baseline to multiple GPS-surveyed 

shorelines. This figure shows three shoreline positions recorded in the fall, represented by red lines, and 

three shoreline positions recorded in the spring, represented by blue lines. 
92 

Object ID Transect ID Baseline ID Shoreline date Distance 

--- --- --- --- --- 

30 7 1 4/1/2006 217.21 

29 7 1 10/3/2006 251.84 

27 7 1 4/3/2007 233.90 

28 7 1 9/31/2007 269.99 

26 7 1 3/31/2008 241.41 

25 7 1 10/1/2008 273.02 

36 8 1 4/1/2006 218.51 

35 8 1 10/3/2006 252.37 

33 8 1 4/3/2007 233.00 

34 8 1 9/31/2007 269.55 

32 8 1 3/31/2008 242.06 

31 8 1 10/1/2008 273.46 

--- --- --- --- --- 

Table S7.1. A matrix of distance measurements exported from DSAS, incorporating distance 

measurements along Transects 7 and 8 from different survey dates. A full description of each of the 

columns in this table is in the DSAS User Guide and Tutorial (Himmelstoss et al. 2005). 

Transect 

ID 

Distance from Baseline (m) (±5m) 

Spring 

'06 Fall '06 Spring '07 Fall '07 Spring '08 Fall '08 

--- --- --- --- --- --- --- 

7 217.21 251.84 233.90 269.99 241.41 273.02 

8 218.51 252.37 233.00 269.55 242.06 273.46 

9 219.76 252.24 231.22 268.28 241.99 272.96 

10 220.87 247.37 218.88 262.76 238.11 267.63 

11 217.99 244.15 215.58 260.17 233.76 265.82 

12 81.48 48.51 72.61 34.26 59.54 28.87 

13 79.51 51.11 77.02 35.58 60.37 31.03 

14 215.45 240.57 214.00 257.39 231.45 265.05 

15 212.12 237.49 212.39 255.27 229.74 263.67 

16 211.36 235.07 210.39 253.90 228.72 263.07 

17 211.46 233.49 208.55 253.14 227.48 262.71 

--- --- --- --- --- --- --- 

Table S7.2. Distance output from DSAS reformatted into Distance Matrix format. 
93 

Quantifying Change by Comparison of Shoreline Positions

A comparison of shoreline positions is produced through a calculation of the differences in the 

distances from the baseline to any pair or combination of shorelines. The result is a table of the 

measured alongshore displacement of the shoreline for a specific span of time (temporal 

variation). However, any comparison of shoreline position needs to acknowledge the shoreline 

position uncertainty (5 m) and use this limitation to create the equivalent of error bars with any 

measure of displacement. This measure of uncertainty will apply in the comparison of change at 

any individual transect as well as the collation of measurements along the ocean shoreline. They 

will also apply as these numerical data are processed further to produce summary statistics, such 

as a mean valueof change and a standard deviation from the mean. Thus, the variety of 

quantitative comparisons of shoreline position based on geomorphological features will require 

the establishment of thresholds to define the error bars at the variety of temporal/spatial scales 

Temporal Comparison 

A temporal comparison is the calculation of the change in the surveyed shoreline position over 

some time period. Because shoreline position is surveyed twice per year, the comparison of 

successive shorelines reveals seasonal contrasts; a comparison of surveys conducted in the same 

season during successive years highlights the annual variation; and the comparison of shoreline 

positions surveyed over longer periods begins to reveal the trends in the direction and magnitude 

of change. Any change calculated from a period of more than one year, for the purposes of this 

SOP, is referred to as long-term change. 

Seasonal Comparisons

The seasonal change, either winter-to-summer or summer-to-winter change for this SOP, 

is the difference in shoreline position between consecutively-surveyed shorelines (Table 

S7.3). Generally, the summer season should be represented by a seaward displacement of 

the shoreline, whereas the winter season should show a landward displacement, or 

erosion. Following the determination of the difference between two consecutive 

shorelines, summary statistics may be generated with an uncertainty of 10 m assigned to 

the comparisons. The mean seasonal change is the average difference in the position of 

the shoreline for the totality of measured points. The standard deviation of seasonal 

change is a measure of the spread of difference values about the mean change calculation. 

Other statistical measurements may be calculated, such as median and mode, to describe 

and display the distributional characteristics of the dataset (Figure S7.7). 

Annual Comparisons

The measure of annual change compares the position of the surveyed shoreline in the 

same season over a span of twelve months (Table S7.4). Because the seasonal variation is 

absent from this comparison, the change reflects the short-term balance of sediment 

supply (loss of sediment should produce a net inland displacement of the shoreline, 

whereas gain of sediment should produce a net seaward displacement). Although the 

displacement does represent the positive or negative sediment budget, it may also 

represent the contrast in storm frequency and severity. Thus, annual comparisons are 

valuable but they are short-term measures that incorporate a variety of variables. 

Summary statistics, such as mean and standard deviation, should be calculated to 
94 

characterize the annual changes using an uncertainty of 10 m for any comparison of two 

surveyed shorelines (Figure S7.8). 

Transect ID 

Distance from Baseline (m) 

(±5m) 

Seasonal Difference 

Fall '06 - Spring '06 

Spring '06 Fall '06 (±10m) 

--- --- --- --- 

7 217.21 251.84 34.64 

8 218.51 252.37 33.86 

9 219.76 252.24 32.48 

10 220.87 247.37 26.51 

11 217.99 244.15 26.16 

12 81.48 48.51 -32.97 

13 79.51 51.11 -28.40 

14 215.45 240.57 25.12 

15 212.12 237.49 25.37 

16 211.36 235.07 23.70 

17 211.46 233.49 22.03 

--- --- --- --- 

Table S7.3. An example of the comparison of differences in shoreline position between successive 

 surveys in the data matrix, from Spring 06 to Fall 06, to produce a measure of seasonal change. 

Figure S7.7. Distribution of difference measurements comparing two consecutive shoreline positions, 

incorporating the mean change value (-7.6m) and standard deviation values from the mean. Information 

such as mean difference, standard deviation, skewness, and other statistical descriptors may be 

calculated by importing the distance output from DSAS into a statistical software package. 

Change (m)

Frequency

-57.4 -47.3 -27.4 -7.6 12.3 32.0 61.4

300

250

200

150

100

50

0

Seasonal Change (Fall '06 minus Spring '06)
95 

Transect ID 

Distance from Baseline (m) (±5m) Annual Difference 

Spring ’07 - Spring ‘06 

Spring '06 Fall '06 Spring ‘07 (±10m) 

--- --- --- --- --- 

7 217.21 251.84 233.90 16.69 

8 218.51 252.37 233.00 14.49 

9 219.76 252.24 231.22 11.46 

10 220.87 247.37 218.88 -1.99 

11 217.99 244.15 215.58 -2.41 

12 81.48 48.51 72.61 -8.87 

13 79.51 51.11 77.02 -2.49 

14 215.45 240.57 214.00 -1.45 

15 212.12 237.49 212.39 0.27 

16 211.36 235.07 210.39 -0.97 

17 211.46 233.49 208.55 -2.91 

--- --- --- --- --- 

Table S7.4. Measurements and comparisons of differences in shoreline position between similar 

seasons quantify the annual change. 

Figure S7.8. Distribution of the annual difference in shoreline position comparing two consecutive spring 

seasons, with mean (-8.9 m) and standard deviation values. 

Change (m)

Frequency

-97.0 -46.3 -26.6 -8.9 9.8 28.5 48.1

300

250

200

150

100

50

0

Annual Change (Spring '07 minus Spring '06)
96 

Long-term Comparisons

Long-term change in shoreline position is the change over any period of time greater than 

one year. If only two shorelines are used to represent a long time period, they should be 

from the same season so that seasonal change does not bias the calculation of differences. 

The use of only two shorelines separated by more than one year is referred to as an endpoint calculation. This calculation focuses on net change of shoreline position over the 

period of comparison (Figure S7.9). The differences in shoreline position between these 

endpoints will generate a numerical array of values and thus the variety of statistical 

summary measures similar to those described above (mean, standard deviation) may be 

derived. 

Figure S7.9. The array of mean differences from successive GPS surveys. Comparisons may be made 

of end-point positions as well as the sequence of shorter-term changes, or trends in the direction and 

magnitude of the changes. 

Trends may also be calculated by using more than two shorelines, thus producing a series of 

shorter-term differences. By comparing the sequence of difference measurements over time, the 

trend in the dataset may be determined. The trend may be a simple observation of the increase or 

decrease in the mean difference per year (Figure S7.9). The trend could also be the calculation of 

the mean rate of change of the annual differences, as well as a similar comparison of the seasonal 

differences. This approach identifies the internal variation in shoreline position in reaching its 

final location. Any of these measures of change in shoreline position will generate a suite of 

numbers upon which statistical analysis may be performed to summarize the trend of the change. 

Trend analysis becomes more meaningful with a longer record of shoreline change. A minimum 

of five years should be used to begin to depict trends of change. 

DSAS automatically provides a number of useful statistical tools for examining long-term 

change. The most basic of measure of change is the end-point rate (EPR) which is calculated by 

dividing the distance in shoreline movement by the time elapsed between the earliest and latest 

measurements (Figure S7.9). Whereas this value is straightforward and only requires 
97 

information about the two data endpoints, it ignores all of the intermediate data points that are 

also useful in describing cycles and trend in the shoreline movement behavior. In order to 

examine trends in shoreline change over time, DSAS provides estimates of the linear regression 

rate of change. The rate of change is the slope of the regression line fit shoreline data with 

distance being the response (y-variable) and time being the explanatory variable (x-variable). In 

this case the estimated rate of change or slope estimated for each transect location represents the 

average change in shoreline location per year. 

Spatial Comparisons 

Changes in the shoreline position will likely vary in both magnitude and direction along the 

ocean shoreline of the park. This alongshore variation constitutes the spatial component of the 

comparisons in a seasonal, annual, or long-term time period. Spatial comparisons will be 

depicted in a map view to display the juxtaposition of the measures of change for the ocean 

shoreline (Figure S7.10). 

Figure S7.10. Alongshore distribution of differences in shoreline position depicting the spatial association 

of change, incorporating the value of mean change for the entire data set and the measure of one 

standard deviation for the data set. The scale of change includes color as well as length of the bars for 

easier recognition of the comparative values. 

The generation of the maps depicting the magnitude of shoreline change between two dates, is 

accomplished by using the Shoreline Change Mapper, a software application that works within 

the ArcGIS software from ESRI, and developed by Rutgers University for the purpose of this 

Protocol. This application is available from the data manager, and includes a short user guide 

describing the process for creating the maps. The application generates a new geographical data 
98 

set that represents the actual or exaggerated distance of change as a bar-graph-type series of lines 

- corresponding to the location of a sampling transect - that can be overlaid on existing base 

maps. The length of each line represents the magnitude of change between two chosen dates. 

The measures of change may be the net differences in shoreline position in an alongshore view, 

or the mean of the incorporated differences, or the rates of change. In any of the portrayals of 

the numerical differences of shoreline position, the statistical values of mean and standard 

deviation may be superimposed on the alongshore plots of the data. In long-term comparisons of 

changes, an alongshore plot of the frequency of exceeding one standard deviation of change 

during any of the shorter time intervals would emphasize areas of major change. 

Focus on Special Areas of Interest (AOI) 

In addition to summaries of the entire shoreline, there may be areas of interest to management 

that would benefit from a more focused analysis. Therefore, spatial subsets of the distance 

matrix may be identified to summarize change in smaller, local areas, or at specific points of 

interest, such as an element of infrastructure. Areas or points of interest are to be identified by 

the park resource management specialist and this information conveyed to the data manager. 

Subsequently, a specific measurement will be conducted at this location to document the changes 

within the context of the concern 

The AOI will be defined as a spatial subset within the data matrix of distances. If distance 

measurements are needed for a segment or region of the shoreline, the aforementioned

procedures will apply. If a single distance measurement is required and one of the evenly-spaced 

calculation points does not define the point of interest, a supplemental point may be calculated. 

This point should not be included in mean and standard deviation summaries, because it would 

alter the systematic basis of the calculation. 

In addition to general summary statistics, AOIs may be monitored for specific change. Threshold 

values may be determined by park management or may be based on a previous analysis to signal 

or “flag” critical dimensions. For example, the distance matrix may be used to identify if and

when the position of a shoreline approached a minimum threshold distance to the infrastructure 

element. 

Production of Reports on Shoreline Change

There will be reports produced periodically by the park or by the NCBN project leader that 

portray the measured changes in shoreline position in narrative, tabular, and graphical formats. 

There are two types of products: an Annual Project Report and a Project Trend Report. The 

Annual Project Report summarizes the data from the previous year whereas the Project Trend 

Report covers a five-year period of time and includes information on trends and interpretations 

of the observations. These reports will be submitted to the park management and will also be 

included in the protocol geodatabase. 
99 

Annual Project Report 

The Annual Project Report is a summary of the shoreline change data over the period of one year 

(three surveys). General statistics (mean and standard deviation) will be included for the two 

seasonal changes as well as the one annual change, incorporating the measure of uncertainty. In 

addition, spatial analysis will be conducted on each of the seasonal changes and the annual 

change.

The Annual Project Report is organized into sections to present the data in narrative, tabular, and 

graphical form. The sections are as follows: 

2. Introduction 

3. Site and Situation 

4. Timing of Shoreline Position Surveys 

5. Natural and Cultural Events Affecting Shoreline Position 

6. Areas of Special Interest 

7. Changes to the protocol 

8. Shoreline position data sets 

9. Summary Statistics and Tables of Change 

10. Information for Management 

11. Problems/Concerns 

12. Appendices 

13. Bibliography 
100 

Project Trend Report

The Project Trend Report is a summary of the full database of shorelines, with an emphasis on 

the previous five years. It is a comprehensive complement of analyses that synthesize the 

shoreline change data, and provide scientific interpretation of the trends revealed in the 

numerical analyses. There are two additional sections to the information described above for the 

Annual Report: 

1. Introduction 

2. Site and Situation 

3. Timing of Shoreline Position Surveys 

4. Natural and Cultural Events Affecting Shoreline Position 

5. Areas of Special Interest 

6. Changes to the protocol 

7. Shoreline position data sets 

8. Summary Statistics and Tables of Change 

9. Presentation and Description of Trend Analysis 

10. Interpretation of trends 

11. Information for Management and Recommendations 

12. Problems/Concerns 

13. Appendices 

14. Bibliography 

References

Himmelstoss, E.A., T.L. Miller, and E.R. Thieler, 2005. User Guide and Tutorial for the Digital 

Shoreline and Analysis System (DSAS) version 3.2. Available online at: 

http://woodshole.er.usgs.gov/project-pages/dsas/version3/images/pdf/DSASv3_2.pdf

Thieler, E.R., E.A. Himmelstoss, J.L. Zichichi, and A. Ergul, 2009. Digital Shoreline Analysis 

System (DSAS) version 4.0—An ArcGIS Extension for Calculating Shoreline Change: U.S. 

Geological Survey Open-File Report 2008-1278. Available online at 

http://pubs.usgs.gov/of/2008/1278/. 
101 

Standard Operating Procedure (SOP) # 8 – Data Management 

Version 1.0 (December 2009) 

The following table lists all changes that have been made to this Standard Operating Procedure 

since the original publication date. Any recommended or required changes added to the log must 

be complete and concise and promptly brought to the attention of the NCBN Project Leader. 

The project leader will review and incorporate all changes, officially complete the revision 

history log, and change the date and version number on the title page. For complete instructions, 

please refer to SOP#9 – Revising the Protocol. 

Revision History Log: 

New 

Version # 

Previous 

Version # 

Revision 

Date 

Author (full 

name, title, 

affiliation) 

Location in Document 

and Description of 

Change 

Reason for 

Change 

 

Proper data management and standardization are essential to the effective utilization of 

information gained through long-term ecological monitoring activities. This SOP provides 

guidelines to the NCBN Data Manager and to the NCBN Project Leader for the development, 

storage, and distribution of monitoring data associated with the Network’s Ocean Shoreline 

Position Monitoring Protocol. The SOP describes how the many disparate pieces of information 

that are generated at various points in the data-gathering, analysis, and reporting processes are to 

be organized, stored, and disseminated. 

More specifically, this SOP describes the overall file management system for the protocol, as 

well as the details of monitoring-data storage in a Microsoft Access database. The SOP also 

outlines the procedures for performing QA/QC on the data, archiving the various spatial and 

tabular datasets, and making the data publicly accessible via biological information clearing 

houses. 

A formal information management plan for all NCBN monitoring protocols is available at 

http://www.nature.nps.gov/im/units/ncbn/d_im_plan.cfm and should be consulted for more 

detailed procedural and policy information. 
102 

Definition of the Ocean Shoreline Dataset

The Ocean Shoreline Monitoring program will produce a number of electronic files that will 

include formal written reports, GPS and GIS spatial datasets, a Microsoft Access database, and 

paper field forms. The large number of files of various formats will require conscientious and 

formal attention to their management. 

Once initial post-processing and export procedures have been completed by field personnel (see 

SOP#6), the following datasets will be delivered to the NCBN project leader in digital format 

(CD/DVD by mail, compressed archive via email or FTP, etc.): 

1. Original GPS data files (e.g., .ssf format for Trimble) downloaded from the GPS unit 

2. If real-time correction was not employed during data collection, differentially-corrected 

GPS data files (e.g., .cor format for Trimble units) 

3. A cleaned, exported ESRI point shapefile (.shp) (if applicable) 

4. A continuous shoreline line-feature shapefile (.shp) 

5. A metadata file for the above line shapefile which complies with Federal Geographic 

Data Committee (FGDC) standards. 

6. Original hard-copies or scanned versions of all field data sheets (Adobe .pdf format) 

7. All photographs taken during survey. 

In addition to the collection and initial processing of shoreline positional data, Networkcontracted investigators or technicians will periodically conduct analysis of shoreline change 

using the USGS Digital Shoreline Analysis System (DSAS). This analysis involves the 

calculation of distances between multiple shoreline features and an established baseline along 

pre-defined azimuths, resulting in a matrix of distance measurements that can be used for 

subsequent statistical trend analyses. 

Finally, outside investigators may be contracted to produce annual and long-term (five-year) 

reports summarizing and interpreting the results from the above analyses. Copies of these reports 

will be delivered to the NCBN project leader and stored primarily in Adobe .pdf format. 

 

File Management and Documentation

It is the responsibility of the NCBN project leader to assemble and maintain the various 

components of the Ocean Shoreline Dataset described above. The Shoreline Monitoring 

protocol generates a number of raw data products and reports that are not suitable for direct 

storage within the database, including uncorrected (.ssf) and corrected (.cor) GPS data files, as 

well as exported ESRI shapefiles (.shp). In order to ensure proper functioning of the Shoreline 

Change Monitoring Database and to generally ease the data retrieval process, the Database 

User’s Guide (Appendix A) identifies a coherent, consistent directory structure to store data files. 
103 

Figure S8.1. Top Level Shoreline Monitoring File Structure 

In order for hyperlinks within the database to work properly, the main folder 

‘Shoreline_datasets’ (Figure S8.1) should be placed at the same directory level (i.e., within the 

same folder) as the Microsoft Access monitoring database itself. 

This directory structure, along with naming conventions for the various file types, is outlined in 

detail in Section 1.1 of the Database User’s Guide. 

Baseline Shoreline Datasets

For each monitoring location, investigators will have developed a generalized shoreline trend 

line, against which all subsequent GPS’ed shorelines will be compared during shoreline change 

analyses. Along with these baselines will be a suite of permanent transects that will be used to 

measure distances between the shoreline position and the baseline at approximately 10m 

intervals. (These analyses and the procedures used to generate the baseline and transect datasets 

are outlined in detail in SOP #7.) Each baseline and transect dataset is stored in an ESRI 

Personal Geodatabase as a feature class with tabular attributes required by the USGS’ DSAS 

shoreline change analysis software. These geodatabases are then linked to the Shoreline 

Monitoring Database by the NCBN project leader according to the steps outlined in the Database 

User’s Guide, Section 3.1. 

Raw GPS Data

The original GPS data points are an integral component of the ocean shoreline dataset, allowing 

for the recreation and replication of any subsequent calculations or derivations. The raw data file 

directly downloaded from the GPS data collector contains information beyond the horizontal 

point position, including precision and accuracy of the position, time and date of collection, 

equipment used, PDOP, number of satellites, signal to noise ratio, etc. If Trimble GPS data 

collectors such as the ProXR or GeoXT are used, these data will be in the proprietary .ssf file 

format; however, other file formats may be generated depending on which sub-meter accuracy 

GPS unit is utilized. 

If there is any question as to whether prescribed GPS data collection parameters have been 

exceeded (see SOP #4), the NCBN project leader should refer to these files to determine that 

GPS unit settings for data collection have been correctly applied. 
104 

Because these files are typically in non-tabular and proprietary formats, they are linked in the 

database rather than entered as text. Step-by-step procedures for linking these files to the 

Database User’s Guide, Section 5.1. 

Corrected GPS Data

Post-processed data products, described in SOP #6, consist of differentially-corrected versions of 

the raw GPS data file (e.g., a .cor file, in the case of using the Trimble units). An accompanying 

log file is created along with the .cor file and contains references to the CORS beacon base files 

used for correction, as well as estimates of the accuracy of the positions. This log file should be 

bundled with the .cor file (i.e., placed alongside the .cor file in the same directory location). As 

with the raw GPS file, the .cor file is in a non-tabular and proprietary format and is linked to the 

Database as opposed to entered as text (see Database User’s Guide, Section 5.1). 

It is recommended that NCBN project leader inspect the .cor and log file in the unlikely event 

that a substantial number or positions were not able to be corrected with the CORS beacon file 

that was downloaded by the field technician. In such cases, correction data from one or more 

nearby beacons should be downloaded and the original .ssf file re-processed to yield additional 

corrected positions. 

Note: Data which have been corrected in real time through the use of a DGPS beacon receiver 

can be considered corrected data. However, if field technicians have access to PathFinder Office 

or other software capable of differential correction, it is encouraged that they still post-process 

these data using a suitable CORS beacon file. This would be done to ensure against a substantial 

number of positions failing to be corrected due to problems such as an unforeseen loss of the 

beacon signal. 

Shoreline Shapefiles

In addition to the .ssf and .cor file, SOP#6 outlines the procedures for correcting the GPS files 

and creating a cleaned shoreline line-feature shapefile. This line dataset represents the final GIS 

product on which all subsequent trend-analyses are based. Required attributes for these 

shapefiles are specified in SOP#6. 

Note: Depending on the equipment and settings used, the initial survey of the GPS shoreline 

position produces either a continuous line feature or a dataset consisting of a series of points 

spaced 10 meters apart. If the latter is the case, then the GPS shoreline data must be 

transformed into a continuous line feature in order permit position-change calculations. 

Procedures for converting a point dataset to a continuous line dataset are presented in SOP#6. 

Variation due to interpolation between the points is minimal because the spacing of the points is 

dense (10 meters). If applicable, the point shapefile should be retained in the ‘shp_pts’ folder 

outlined above and the location entered in the protocol database as outlined in the Users’ Guide. 

The ESRI line shapefile, similar to the raw GPS .ssf and corrected .cor files, is a non-tabular, 

proprietary data format and is likewise linked to the Shoreline Monitoring Database rather than 

entered as text. The steps for doing so are outlined in the Database User’s Guide, Section 5.1. 

At a minimum, the NCBN project leader should inspect this final product for completeness 

against known, trusted GIS base datasets (e.g., the shoreline trendlines described in SOP #7), as 

well as ensure that an FGDC-compliant metadata file accompanies the line-feature shapefile. 
105 

The metadata file should be included as an .xml document using the same naming conventions as 

the other components of the multi-file shapefile format. Metadata in .xml format can be viewed 

in a number of web browsers and metadata editing software packages, including ESRI 

ArcCatalog. 

Finally, the completed line shapefile and its metadata should be imported into the 

aforementioned Baseline Shoreline Geodatabase outlined in section A above. This can be done 

in ArcCatalog using the following steps: 

1. Navigate to the Shoreline_datasets\baselines folder outlined above 

2. Right-click on the appropriate geodatabase and choose “Import -> Feature class (single)” 

3. In the Input Features field browse to the line shapefile 

4. In the Output Feature Class field repeat the name of the shapefile, minus the .shp file 

extension 

5. Click OK. 

Field Data Forms

The Field Data Form collected in conjunction with the GPS position data provides information 

essential to the usability and verification of the dataset. If not already converted, the NCBN 

project leader will scan hard-copy field data forms and export them as Adobe .pdf files. These 

files are then linked to the Shoreline Monitoring Database according to the steps outlined in the 

Database User’s Guide, Section 5.1. 

In addition to the above electronic versions, all original paper Field Data Sheets will be housed 

in the NCBN central files at the University of Rhode Island, Kingston, RI. The central files are 

maintained by a URI FTSC staff member under the guidance of the Network Data Manager and 

Coordinator. 

Distance Matrices 

Shoreline datasets collected over various periods of time (seasons within a single year, seasons 

across several years, etc.) are processed relative to a pre-determined baseline shoreline feature 

generated for each park. Distances from the baseline to each shoreline are calculated at 10-m 

intervals at set azimuths (see treatment of analyses using the DSAS program in SOP #8). The 

DSAS program provides tools for exporting these distance calculations as a matrix in Excel

spreadsheet format (.xls) (Figure S8.2), which itself can be assimilated into a Microsoft Access 

data table. 

As periodic analyses are conducted and annual and long-term reports generated (see SOP #7), 

additional shorelines will be added to these matrices. The NCBN project leader should acquire 

exported .xls files from the investigators conducting regular shoreline change analyses and 

incorporate these distance calculations into the Shoreline Monitoring Database each time a new 

shoreline is entered. Procedures for doing so are outlined in Section 7 of the Database User’s 

Guide. 
106 

Reports

The final products to be included in the Shoreline Monitoring Database are the regular reports 

produced in SOP #7. These reports are completed for each park unit and are of two types: an 

annual report summarizing the change in shoreline position over the past year, and a long-term 

trend report that summarizes and analyzes the trends of changes in shoreline position every five 

years. Both types of reports should be delivered to the NCBN project leader as Adobe .pdf files 

and linked to the Monitoring Database as described in Section 8 of the Database User’s Guide. 

Figure S8.2. Example Data Matrix in Microsoft Excel spreadsheet format. 

Database Administration and Maintenance

Data Entry QA/QC

The NCBN project leader will be responsible for entering all pertinent data into the Shoreline 

Monitoring Database in a timely manner. To minimize transcription errors, each line of data will 

ideally be checked against the original field data sheets by a second person. However, if no staff 

is available, the Network Data Manager should check 100% of the data entry on the following 

day. 

Database Backup

Tape backups of the Shoreline Monitoring project directory (including the Shoreline Monitoring 

Database) will be made daily per an arrangement with the University of Rhode Island Field 

Technical Support Center (URI FTSC). Incremental (daily) backups of NCBN data drives are 

maintained on a weekly basis, culminating in a full backup at the end of each week. Weekly 

backup tapes are retained for six months. One full backup per month is retained in perpetuity, 

with two redundant copies held in separate off-site data archives. 
107 

Database Revision Control

Because the Shoreline Change Database follows the NPS I&M Program’s Natural Resource 

Database Template v.3 (NRDTv.3), a table describing database revision history 

(tbl_Db_Revisions) and linking to the database metadata (tbl_Db_Meta) is an included core 

table. Revisions will be performed periodically by or in conjunction with NCBN staff as the 

need arises and should be documented fully in the above table, as well as in the database 

metadata produced though cooperative agreement by NCSU FTSC. 

The NCBN project leader will also be responsible for reflecting pertinent changes to the 

Shoreline Monitoring Database in the accompanying User’s Guide, as well as this Data 

Management SOP #8. 

Export to ASCII for backup

As software and hardware evolve, datasets must be consistently migrated to new platforms, or 

they must be saved in formats that are independent of specific platforms or software (e.g., ASCII 

delimited files). Thus, NCBN archiving procedures include saving datasets in both their native 

format (typically MS-Access or Excel spreadsheet format) and as sets of ASCII text files. As a 

platform- and software-independent format, ASCII text files ensure future usability of the data in 

a wide range of applications and platforms. 

As part of the annual archiving of the Shoreline Monitoring Database, the NCSU will produce 

such ASCII text files for all tabular data within the database. However, if the NCBN project 

leader wishes to periodically generate such files for backup purposes at the Network level, a 

utility to do so written in Microsoft Access called “Exportdb” is available 

(http://science.nature.nps.gov/im/datamgmt/data_tools/exportdb.mdb). Exportdb will write the 

following ASCII comma-delimited text files for each database: 

• TABLEDEF.txt - This file will contain one record for every table in the selected 

database. Fields in the file include Table_Name, Table_Description, 

Table_Format, Number of Fields, Export_Date. 

• FIELDDEF.txt - This file will contain one record for every column in every table 

in the selected database. Fields in the file include Table_Name, Field_Name, 

Field_Description, Field_Type, Field_Width. 

• One comma-delimited ASCII text file containing all the data rows in each table in 

the selected database. 
108 

Exportdb displays a single form containing three function buttons: 

The "Clear all attached tables" button will clear all tables linked from previous sessions. The 

"Link Database Tables" button will open a browse window to allow the selection of the 

Microsoft Access database to be exported. (Note: the utility will not export tables that are linked 

to a back-end database. 

The "Export Tables" button will open a browse window to allow selection of the destination 

directory for the text files. Once a directory is selected, the export will be performed. 

Alternatively, the following procedure can be used to export tables directly from the Monitoring 

Database: 

1. In the Database window click the name of the table to be exported and then on the 

File menu, click Export. 

2. In the “Save As Type” box, click Text Files (*.txt; *.csv; *.tab; *asc). 

3. Click the arrow to the right of the “Save In” box, and select the drive or folder to 

export to. 

4. In the File Name box, enter a name for the file (or use the suggested name), and then 

click Export. 

Archiving

NCBN has entered into a cooperative agreement with the North Carolina State University NPS 

Field Technical Support Center (NCSU FTSC) for the maintenance, storage, and archiving of 

datasets produced as part of the Networks vital signs monitoring program. Datasets associated 

with the Shoreline Change Protocol will be archived on an annual basis, both in their native 

formats as well as ASCII text files. Archived datasets will include both tabular data in MSAccess format as well as spatial data. Network staff are responsible for preparing tabular data 

from the protocol for archival following completion of standard QA/QC procedures. NCSU 

FTSC staff then prepares the tabular data for archiving by creating: 

 a set of ASCII comma-delimited text files for the tabular data files and tables 

comprising the dataset 
109 

 an XML file that preserves relationships between tables for each MS-Access database 

 a readme.txt file that explains the contents of each ASCII file, file relationships, and 

field definitions 

Quality control checks are then performed on these ASCII files to ensure that the numbers of 

records and fields correspond to the source dataset and that conversion has not created errors or 

data loss. If possible, a second reviewer, preferably a program scientist, checks the ASCII files 

and documentation to verify that tables, fields, and relations are fully explained and presented in 

a way that is useful to secondary users. 

Digital spatial data associated with short or long-term project data described above will also be 

archived at the NCSU FTSC. These data include ArcGIS shapefiles, coverages and geodatabases; global positioning system (GPS) data. Procedures for maintaining spatial data differ 

from those that apply to tabular data. 

Spatial data in ArcGIS shapefile format will be maintained in formats that are accessible by the 

current ArcGIS version. If necessary, NCSU FTSC is responsible for converting ArcGIS data to 

an upgraded format. Shapefiles will also be converted to sets of ASCII text files for archiving. 

Two ASCII files are required for each spatial data file. One file stores coordinate data with a 

unique identification code for each feature, and the second file stores attribute information that 

can be linked to the corresponding coordinate data by means of a common identification code. 

On an annual basis, the Data Manger will forward to the NCSU FTSC dataset consisting of the 

following elements: 

1. an updated Shoreline Change Monitoring database, 

2. updated versions of the Baseline Geodatabases for each park unit, 

3. line shapefiles metadata for all shorelines collected during the past year, 

4. all uncorrected (.ssf) and corrected (.cor) GPS data from which the line shapefiles 

were created, 

5. a digital (.pdf) copy of the field forms from each survey for that year, 

6. a digital (.pdf) copy of the final Annual Report, and 

7. once every five years, as a copy of the Long-term Report. 

When a project dataset is ready to be archived, Network staff will send the data to NCSU FTSC 

accompanied by a transmittal document in the form of an ASCII text file that includes specific 

information about the data or imagery. This information includes: 

1. name and address of the sender 

2. brief project description, including topic and park name(s) 

3. type and number of digital media (e.g., 3 CDs, 1 DVD) 
110 

4. name of each data file that comprises the dataset (Federal Geographic Data 

Committee (FGDC) compliant metadata or a data dictionary must be present for each 

data file) 

Upon receipt, NCSU FTSC staff will: 

1. check the digital media for physical damage 

2. count and record the number of media received 

3. count and record the number of data/image files received 

4. check data file integrity (i.e. makes sure that each file opens and displays appropriate 

data) 

NCBN staff will be notified if any problems or discrepancies are found. NCSU staff will enter 

the information about short-term and long-term monitoring project data into an Excel 

spreadsheet, referred to as the Digital Data Tracking Database. 

Data Distribution

Access to NCBN data products will be facilitated via a variety of information systems that allow 

users to browse, search, and acquire Network data and supporting documents. These systems 

include the NCBN website (http://www.nature.nps.gov/im/units/ncbn/), and national applications 

with internet interfaces, such as the NR-GIS Data Store (http://science.nature.nps.gov/nrdata/). 

Because Network data will reside in the repositories listed above, they will automatically be 

searchable via the integrated metadata and image management system and search gateway called 

“NPS Focus.” This system is being built with Blue Angel Enterprise software for metadata 

management and the LizardTech Express Server for image management. Currently, ten NPS and 

two non-NPS databases have been integrated into the NPS Focus prototype in either full or test 

bed form for one-stop searching. NPS Focus has been released as an Intranet version only 

(http://focus.nps.gov/) – release of a public version is projected in the near future. 

Requests for data and reports before they are published in the above repositories should be 

directed to: 

Northeast Coastal & Barrier Inventory & Monitoring Network 

Data Manager 

University of Rhode Island 

Room 105 Coastal Institute 

1 Greenhouse Road 

Kingston, RI 02881 

Fax: 401-874-4561 
111 

Standard Operating Procedure (SOP) # 9 – Revising the Protocol 

Version 1.0 (December 2009) 

 

The following table lists all changes that have been made to this Standard Operating Procedure 

since the original publication date. Any recommended or required changes added to the log must 

be complete and concise and promptly brought to the attention of the NCBN Project Leader. 

The project leader will review and incorporate all changes, officially complete the revision 

history log, and change the date and version number on the title page. For complete instructions, 

please refer to this SOP.

Revision History Log: 

New 

Version # 

Previous 

Version # 

Revision 

Date 

Author (full 

name, title, 

affiliation) 

Location in Document 

and Description of 

Change 

Reason for 

Change 

 

The following Master Version Table tracks the relationships between the protocol narrative and 

the associated Standard Operating Procedures, as discussed in this Protocol. 

Master Version Table: NCBN Ocean Shoreline Position Monitoring Protocol and Standard 

Operating Procedures

Date of 

Revision Protocol Narrative SOP 

#1 

SOP 

#2 

SOP 

#3 

SOP 

#4 

SOP 

#5 

SOP 

#6 

SOP 

#7 

SOP 

#8 

SOP 

#9 

SOP 

#10 

12/14/2009 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 

 

Scope and Applicability 

Due to the long-term nature of the NCBN monitoring program, revisions to the Protocol 

Narrative and to individual Standard Operating Procedures (SOPs) will be necessary from time 

to time (O’Ney 2005). Careful documentation of changes to the Narrative and its related SOPs, 

along with a library of previous versions, are essential for maintaining consistency in the 

collection, summary, analysis, and reporting of data. 
112 

The Revision History Logs found at the beginning of the narrative and each SOP list all edits to 

that section since the original publication date. Information entered in these logs should be 

complete and concise. The logs track the previous version date and number, date of revision and 

new version number, author(s) of revision, location of changes within the document, description 

of change, and the reason the change was made. Author information must include full name, 

title, and affiliation. 

The Master Version Table found in SOP #9 - Revising the Protocol tracks the relationships 

between the narrative and the associated SOP’s. The use of this table is discussed in detail 

below. 

Instructions for Recording Revisions

Protocol users must promptly notify the NCBN project leader about recommended and/or 

required changes. The NCBN project leader will then review and incorporate all changes, update 

the Revision History Log and Master Version Table, and change the date and version number on 

the title page of the master document as well as any SOPs the revisions apply to. 

Minor Revisions 

Minor revisions are those that do not represent a change in the underlying methods or procedures 

used to generate data values for the protocol’s existing data set. Minor revisions include small 

changes in, or clarification of procedures. Version numbers for minor revisions increase 

incrementally by hundredths (1.01, 1.02 . . .). 

Major Revisions 

Major revisions are those that involve changes in methodology that could influence the resulting 

data values and the ability to compare newly-collected data with data collected using a previous 

version, such as: 

• addition of monitoring objectives 

• changes to the sampling design 

• changes to reporting requirements 

• addition of new variables 

Major revisions are designated with the next whole number in the sequence (2.0, 3.0, 4.0...). 

Coordinating Narrative and SOP Versions

 

In order to track the most current version numbers of all SOPs associated with a particular 

protocol version, the NCBN project leader will also maintain the Master Version Table, which 

immediately precedes the narrative’s Revision History Log. A new entry must be made each 

time the narrative and/or any SOPs are modified. In cases where the narrative and/or one or 

more SOP have undergone only minor revisions, the overall protocol version number will itself 

increase incrementally by hundredths. In cases where the narrative and/or one or more SOP have 

undergone a major revision (whether or not other sections have undergone minor revisions), the 
113 

overall protocol version number will increase incrementally by whole numbers. This Master 

Version Table tracks the relationships between the Protocol Narrative and the associated 

Standard Operating Procedures (Figure S9.1). 

Master Version Table: NCBN Ocean Shoreline Position Monitoring Protocol and 

Standard Operating Procedures

Date of 

Revision Protocol Narrative SOP #1 

SOP 

#2 

SOP 

#3 

SOP 

#4 

SOP 

#5 

SOP 

#6 

SOP 

#7 

SOP 

#8 

SOP 

#9 

SOP 

#10 

1/1/2007 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 

6/1/2007 1.01 1.01 1.01 1.00 1.00 1.00 1.01 1.00 1.00 1.00 1.01 1.01 

8/2/2007 2.00 1.01 1.01 1.00 1.00 2.00 1.01 1.00 1.00 1.00 1.01 1.01 

1/10/2008 3.00 2.00 1.01 1.00 1.01 2.01 1.02 1.00 1.00 1.01 1.02 1.01 

Figure S9.1. Example of a Master Version Table reflecting possible revision scenarios and 

associated numbering of the protocol. 

The NCBN project leader will also update all associated field forms to reflect the change in 

protocol version. Users noting discrepancies in versions between the protocol, SOPs, data values, 

and field forms should notify the NCBN project leader so that corrections can be made and 

documentation kept current. 

Reviewing suggested protocol revisions 

All suggested edits require review by the NCBN project leader for clarity and technical 

soundness. Small changes or additions to existing methods will be reviewed by NCBN staff. 

However, if a significant change in methods is recommended, additional expert review may be 

required. 

 

Communicating changes to investigators / users

Once changes have been made, the updated document is posted on the NCBN web site 

(http://www.nature.nps.gov/im/units/ncbn/) and is added to the National Vital Signs Monitoring 

Protocol Database (http://science.nature.nps.gov/im/monitor/protocoldb.cfm). All previous 

versions are archived in the NCBN information system and can be obtained by contacting the 

Data Manager. Each time an SOP is revised, the NCBN project leader ensures that all known 

users obtain a current copy of the SOP and receive the necessary briefing material and/or training 

to understand and incorporate the change(s). Users are encouraged to visit the network web site 

and/or contact the NCBN project leader at least once per season to check for updates associated 

with the monitoring protocol. 

 
114 

References 

O’Ney S.E., 2005. Standard operating procedure #11: Revising the protocol, Version 1.0. In: 

O’Ney, S.E. 2005. Regulatory water quality monitoring protocol. Version 1.0. Bozeman 

(MT): National Park Service, Greater Yellowstone Network. 
115 

Appendix A: 

NCBN Shoreline Change Monitoring Database 

User’s Guide 

Northeast Coastal and Barrier Network 

Inventory and Monitoring Program 

NCBN SHORELINE CHANGE 

MONITORING DATABASE 

USER’S GUIDE 

Version 1.1 

 December 11, 2009 

Created by: 

URI Environmental Data Center 

Kingston, RI 
116 

Table of Contents 

1 Getting Started 

1.1 Creating the Initial Directory Structure 

1.2 Backing up and Saving Data 

2 The Main Menu 

2.1 Main Menu Options 

2.2 Data Entry 

3 Defining Locations 

3.1 Adding a New Location 

3.2 Editing previously entered monitoring locations 

3.3 Deleting a monitoring location 

4 Entering Contact Information 

4.1 Adding a new contact 

4.2 Editing previously entered contact information 

4.3 Deleting Contacts 

5 Shoreline Change Monitoring Data 

5.1 Entering Shoreline Change Monitoring Data 

5.2 Editing Shoreline Change Monitoring Events 

5.3 Deleting a Shoreline Change Monitoring Event 

6 Filtering and Sorting Monitoring Data 

6.1 Applying a filter or sort to shoreline change monitoring data 

6.2 Removing a filter or sort from shoreline change monitoring data 

7 Distance Matrices 

7.1 Uploading a new or updated distance matrix 
117 

1 Getting Started 

The Shoreline Change Monitoring database consists of a single, main MS Access file 

(NCBN_[version date]_ShorelineMonitoring_Database.mdb), along with a number of associated 

file folders in a defined directory structure. This User’s Guide was created to serve several 

purposes. Primarily, the document instructs approved Network personnel in the methods for data 

entry. However, the guide also serves to outline the organization of the database and to provide 

general instructions for non-Access-users who may wish to browse its contents. It is a foundation 

for understanding what is incorporated in the database and its structure. Only authorized 

personnel may actually input or alter information in the database. 

1.1 Creating the Initial Directory Structure 

In order to ensure proper functioning of the database and to ease the process of data archiving, 

the following guidelines are provided for creating a coherent, consistent directory structure to 

store associated data files and applications. The Shoreline Change Monitoring Protocol 

generates a number of raw data products and field data sheets that are not suitable for direct 

storage within the monitoring database. These include raw (.ssf) and corrected (.cor) GPS data 

files, exported ESRI line (and sometimes point) shapefiles (.shp), as well as shoreline features 

stored in geodatabase format used for subsequent statistical analyses. 

Therefore, the following directory structure will be used for storage of protocol-related datasets, 

with the folder ‘Shoreline_datasets’ placed in the same directory as the main Access database file 

(NCBN_[version date]_ShorelineMonitoring_Database.mdb): 

 

1. SSF contains raw, uncorrected Trimble GPS data (points) stored in .ssf format 

2. COR contains differentially-corrected GPS points in .cor format 

3. SHP_PTS contains point data exported from the above .cor files, with any errors or 

extraneous data removed (if applicable) 

4. SHP_LINES contains GPS shoreline data in line feature format, either exported directly 

using Trimble software (e.g., Pathfinder Office, GPSAnalyst extension for ESRI 

ArcMap), or converted to a line feature from the SHP_PTS file 

5. DISTANCE_MATRICES contains Microsoft Excel speadsheets containing cumulative 

shoreline change measurements. (See SOP #8 – Change Calculation, Data Analysis, and 

Reporting for more information on how these matrices are generated.) 

6. FIELD_FORMS contains scanned versions of field data sheets in .PDF format 

7. GEODATABASES contains all shoreline features, generalized shoreline base lines, and 

sampling transects for each park in geodatabase format. These datasets are used in the 
118 

USGS Digital Shoreline Analysis Software (DSAS) as part of the shoreline change 

analysis process (See SOP #8). 

Each park will submit their monitoring data (items 1-4 above) in the formats described, and as 

outlined in SOP #8 of the Monitoring Protocol. Note: FGDC compliant metadata must 

accompany at least each line shapefile dataset (SHP_LINES), fully describing the datacollection and processing steps used in creating this file. 

To ensure consistency and to aid in data retrieval, the following naming conventions have been 

established for the corresponding file types above: 

• [Park/location code]_[date mm/dd/yy] (date started, if multiple).ssf [e.g., 

GATE_SHU_040106.ssf] 

• [Park/location code]_[date mm/dd/yy] (date started, if multiple).cor [e.g., 

ASIS_041205.cor] 

• [Park/location code]_[date mm/dd/yy] (date started, if multiple)_pts.shp [e.g., 

GATE_SHU_040106_pts.shp] 

• [Park/location code]_[date mm/dd/yy] (date started, if multiple)_line.ssf [e.g., 

CACO_031204_line.shp] 

1.2 Backing up and Saving Data 

Microsoft Access does not save data the way most programs do. Each time a field or record in 

the database is edited , Access automatically saves it. Unlike Word or Excel, Access does not 

require the file to be saved at the end of a session. 

For this reason, it is strongly recommended that users back up current data before each new dataentry or editing session. Select Back up Monitoring Data from the Main Menu and the following 

dialog box will appear. 

Click Yes on the dialog box to back up the current version of the data, and the Save As dialog 

box will appear. Use the browse button to select a directory in which to store any backups. It is 

recommended that users create a separate subdirectory below that of the current database file or 

elsewhere on a network. 

If a backup is named with the same name as an existing file, the user will be asked whether to 

overwrite the existing file or select a new file name. A message box will appear when the data 

have successfully been backed up. 
119 

2 The Main Menu 

The title bar of this window indicates the network, the database protocol, and the version date of 

the database. 

At any time, F11 can be pressed to open the database window, which provides direct access to all 

of the tables, forms, reports, and code modules incorporated in the database. These objects are 

also all available “in context” through the Monitoring Menu and other menus and forms. In 

general, it recommended to use the links off of the Monitoring Menu and linked forms for all 

data entry. 

2.1 Main Menu Options 

 Monitoring Data – opens the main Shoreline Change Monitoring Data Entry form. 

 Locations – opens the Monitoring Locations Data Entry form. 

 Contacts – opens the Contacts / Observers Data Entry form 
120 

 Import Data Matrix – opens a form that guides the user through the process of importing 

Microsoft Excel files containing shoreline change data matrices. 

 Exit Database 

2.2 Data Entry 

When a user enters data, moves to a new record, or closes a form, Access automatically saves the 

data. 

If a mistake is made when entering data in a field, the previous value can be recovered by 

pressing the Esc key to clear that field. This will only work if the focus (cursor) has not left the 

field and it is still actively being edited. Once the focus is moved from a field, the information in 

that field is saved with the record. However, an entire record can be returned to its previous 

values if the focus has not yet left the record). This can be done by pressing Esc Esc to clear all 

of the associated fields. Once the focus has moved to another record, the Esc or Esc Esc

shortcuts will be available. 

To delete any record, select the record and press the Delete button in the upper right of the form, 

or use Delete Record from the Edit menu of the Access main toolbar. 

Most data forms include the Access record navigation buttons at the bottom. 

In order left to right, these buttons are 1) go to the first record, 2) go back one record, 3) current 

record number, 4) go to the next record, 5) go to the last record, 6) add a new record, and 7) total 

number of records in the table. 

In the case of forms containing one or more drop down boxes, one of the provided options from 

the drop down box must be chosen when creating a new record. For example, when creating 

new monitoring events, the user is required to specify an existing location for that event. An 

error message will appear if an option from a drop down box is not selected. 

3 Defining Locations 

Locations, contacts, and monitoring events for shoreline monitoring sampling can all be updated 

via forms accessible from the Monitoring Data menu. The underlying tables for these forms can 

also be directly accessed (F11), but it is highly recommended that the forms be used to ensure the 

integrity of all monitoring data. For example, data entry for the database has been given a 

logical, structured sequence (e.g., a Location or a Contact must exist in the locations and contacts 

table already before the user can enter data for a monitoring event). Observing these simple 
121 

hierarchies will make data entry much easier and reduce the number of error messages 

encountered. 

Locations (as with Contacts and Monitoring Events) have unique identifiers which are generated 

automatically by the database. 

3.1 Adding a new location 

1. Bring up the Monitoring Locations form by clicking on Locations on the Main menu. 

2. Click New Location at the top of the form. 

3. Select the Park (Unit Code) corresponding to this location from the drop down lists. 

4. Enter a unique Location Name. This name should begin with the park unit code 

followed by an underscore (e.g., “CACO_Naussett”). 

5. The database will automatically create a new LocationID. 

6. Enter a NPS GIS Location ID, if known. 

7. Enter the NR-GIS Metadata Database ID (Meta_MID), if known 

8. Enter the date that this record was last updated (for new records, the current date is 

the default). 

9. Browse to the directory location of the generalized shoreline baseline (geodatabase 

format) to be used for analyzing shoreline change at this location. 

10. Enter the geographic information used for locating the site, including a reference 

coordinate system, coordinate units, UTM zone (if using UTMs), and datum. X and 

Y coordinates will generally be rough center points for the shoreline being mapped. 

11. Enter estimated horizontal error and positional accuracy notes, if applicable. 
122 

3.2 Editing previously entered monitoring locations 

1. Bring up the Monitoring Locations form by clicking on Locations on the Main Menu. 

2. Use the record selectors at the bottom of the form to select the location to edit. 

3. Make the appropriate changes. 

4. When the changes are complete, move off the record or form, and it will be saved 

automatically. 

3.3 Deleting a monitoring location 

(Note: There is NO way to undo this operation. Once a record is deleted, it is gone, 

permanently!) 

1. Bring up the Monitoring Locations form by either clicking New next to the Location 

field in the monitoring data form, or by clicking Locations on the Main Menu. 

2. Use the record selectors at the bottom of the form to select the location to edit. 

3. Check that this is the correct location to be deleted! 

4. Click the Delete button. 

5. A dialog box will appear to protect against accidental deletions. Carefully check the 

location one last time. If this is the correct record, click Yes. If not, click No to start 

again and find the correct record. 
123 

4 Entering Contact Information 

The Shoreline Change database includes tables for storing information about 1) shoreline 

positions, and 2) how the monitoring data were collected. Each event includes fields for 

indicating where, when, and by whom the monitoring data were collected. By including this 

information in the database, future questions about monitoring events or data can be referred to 

those who collected and processed this data. 

The Monitoring Events forms include drop-down lists of contacts to make entering data about 

field observers easier. Each individual observer must first be added into the Contact Information 

table before he or she can be associated with a Monitoring Event record. 

4.1 Adding a new contact 

1. Select Contacts from the Main Menu to bring up the Contact Information form. 

2. Click the New Contact button in the top right of the form. 

3. Fill in the form’s fields 

 observer’s name: first, middle initial, last 

 type of address (work, home, both) 

 employment organization, agency, university, company, or other 

 title 

 telephone numbers -- work, cell, fax 

 email address 

 notes (e.g., if this is a student or summer intern who may only participate for one 

year) 
124 

4. The new contact will be saved when the user leaves the record, presses the Save

button, or exits the form. 

4.2 Editing previously entered contact information 

1. Select Contacts from the Main Menu. 

2. Use the record selectors at the bottom of the form to select the record to be edited. 

3. Change any incorrect values. Refer to 4.1 Adding a New Contact for related 

instructions. 

4. When the necessary changes have been made, click Save in the upper right of the form 

or exit the form. 

5. Optionally, select another record to change, or exit the form. 

4.3 Deleting Contacts 

(Note: There is NO way to undo this operation. Once a record is deleted, it is gone, 

permanently! Do not delete information concerning any contact that has been involved with the 

monitoring program in the past but who may not currently be associated with the project. In 

other words, only delete a contact that was incorrectly entered.) 
125 

1. Select Contacts from the Main Menu. 

2. Use the record selectors at the bottom of the form to select the location to edit. 

3. Check that this individual is the contact to be deleted. 

4. Use the main Access Edit menu and select the Delete Record item or click the Delete

button. 

5. A dialog box will appear to protect against accidental deletions. 

If this person has already been entered into a monitoring event as someone who collected field 

data or who performed data entry, Access will not allow the record to be deleted. To delete the 

record, all records of events that this individual was involved with must be deleted or reference a 

different observer. Only at that point can the contact record be deleted. This should only be 

done if the current observer information included in the database is incorrect. 

Once the record is deleted, the form will display the next observer in the table.

5 Shoreline Change Monitoring Data 

5.1 Entering Shoreline Change Monitoring Data 

A form for entering sampling data is accessible from the Main Menu. 

A monitoring event is considered one field visit to a specific point to make measurements or 

collect data. In the context of the NCBN Shoreline Position Change Monitoring Protocol, this 

means a visit to a specific shoreline location where a neap high-tide swashline is walked or 

driven while collecting GPS location data. If more than one day is required to GPS a shoreline, 

this is still considered a single monitoring event. If a location is sampled more than once during 

a season or year, each visit is considered a distinct event. 

All data for an event will be associated with a specific location, a record of which must have 

been previously created in the database. In order to save time, it is recommended to first verify 

that such a location record has been entered. Once entered, this location becomes available for 

all subsequent data entry sessions. 
126 

1. From the Main Menu, open the Monitoring Data form. 

2. The Monitoring Data window opens, by default, to a new event. Use the record 

selectors at the bottom of the form to select an existing event. 

(Note that once a user has browsed to an existing event, it becomes necessary to navigate 

to the last event or click the New Event button on the top right of the form to open a new 

record.) 

11. The database generates the EventID automatically. After completion of the form, the 

EventID will appear in the EventID lookup box in the top left of the form. This 
127 

EventID can be used to look up or modify the event data in during a subsequent 

session. 

(Note: Once data have been entered for a field or record, the database may not allow 

deletion of that record because of field conflicts. If an error message appears while 

trying to delete a record, press Esc Esc to delete the current record or Esc to delete the 

current field. This pair of Esc sequences works on other forms as well. However, it 

should be kept in mind that all information entered into that current record will be lost 

if the Esc Esc sequence is used.) 

3. Use the drop-down box to select a previously entered location. If this is a new 

location that has not yet been entered in the database, then close the Monitoring 

Events form and select Locations and Sites from the Main Menu to enter new location 

information. (See Section 3 Defining Locations for more information.) It is more 

efficient to add all new sites and locations at once and then return to this form to 

finish entering the monitoring data for specific events. 

4. If no default protocol has been preset, select the appropriate protocol in the dropdown box. 

5. Select the observer who collected the data in the field. If the observer is not yet in the 

list, return to the Main Menu and select Contacts to add them into the database. (See 

Section 4 Contacts, above, for instructions. 

6. Enter the date and time the observer went into the field and took measurements. The 

date is stored in the format MM/DD/YYYY, and the time is stored in 24-hour, 

“military time” format (e.g., 1:00pm = 13:00) 

7. Enter the date and time when measurements were completed. 

8. Enter the type of GPS unit used to collect the shoreline data. (The unit should be 

nominally capable of collecting positions at sub-meter accuracies.) 

9. The Notes field is optional. Include anything unusual or interesting about this 

monitoring event, e.g., if an observer was forced to omit a section of shoreline due to 

an obstacle or if a GPS unit started to behave oddly. 

The “Data File Locations” section of the Monitoring Data form contains fields for documenting 

the locations of the many associated files generated by the collection and processing of GPS 

data. Please see section 1.1 Creating the Initial Directory Structure before entering this data. 

(Note: An Access error message will appear during data entry if required fields are not 

completed. By design, users must complete each form completely in order to enable all of the 

tables and queries in the database to update correctly.) 

1. Enter the directory location and file name of all original GPS files in .ssf format, or 

use the Browse button to automatically select this information. 
128 

2. In a similar manner, enter the directory location and file name of all original, 

differentially-corrected GPS files (.cor format). 

3. If applicable, browse to the composite, “cleaned” point shapefile created from the 

above corrected (.cor) GPS files. (There should only be one per shoreline location.) 

4. Browse to the cleaned line shapefile. (There should only be one per shoreline 

location.) 

5. Browse to the scanned field data sheet for this monitoring event (Adobe .pdf format). 

The section “Data Export for Analysis in DSAS” of the Monitoring Data form contains fields 

meant to ensure that the shoreline feature has been suitably processed and incorporated into the 

proper geodatabase in preparation for subsequent statistical analyses. Please see SOP #7 – Initial 

Post-Survey Processing for specific information on processing the line shapefiles. 

1. Indicate whether the shoreline feature has been added to the geodatabase associated 

with that location. 

2. Enter or browse to the path of the associated geodatabase. Select the 

baseline/shoreline file to which the current line shapefile was appended. 

3. Indicate whether a record for the metadata associated with the shoreline feature has 

been added to the geodatabase’s “Metadata” table and that the .xml metadata file has 

been loaded to the appropriate field as a Binary Large Object (BLOB). 

4. Select the Contact who updated the geodatabase. 

5. Enter the date that the geodatabase was updated. 

5.2 Editing Shoreline Change Monitoring Events 

1. Open the Shoreline Change Monitoring form by selecting it from the Main Menu. 

2. Go to the event for these shoreline survey data by using the navigation buttons at the 

bottom of the window. The Filter and Sort By tools can also be used to narrow the 

number of events displayed. This is particularly helpful when using the navigation 

buttons to step to the next record. Refer to section 6 Filtering and Sorting 

Monitoring Data below for instructions on using these tools. 

3. Change the incorrect monitoring data. 

4. The changes will be saved when the focus is taken off of the record or the form is 

exited. 
129 

5. When the necessary changes are complete, select another record to change, or close 

the form. 

5.3 Deleting a Shoreline Change Monitoring Event 

(Note: There is NO way to undo this operation. Once a record is deleted, it is gone, 

permanently! 

1. From the Main Menu, select the Monitoring Data form 

2. Go to the event for the shoreline survey data to be deleted by using the navigation 

buttons at the bottom of the window. The Filter and Sort By tools can also be used to 

narrow the number of events displayed. This is particularly helpful when using the 

navigation buttons to step to the next record. Refer to section 6 Filtering and Sorting 

Monitoring Data below for instructions on using these tools. 

3. Check that this event is in fact the event to be deleted. 

4. Select Delete from the Edit menu of the Access main menu bar. 

5. A dialog box will appear to protect against accidental deletions. . 

6. Carefully check the record again. If this is the record to be deleted, click Yes. If not, 

start again and find the correct record. 

7. Click Done when the record has been deleted, or proceed to add a new event or edit 

an existing event. 

6 Filtering and Sorting Monitoring Data 

The forms for entering and editing shoreline change monitoring data include Filters and Sorts to 

help organize your data 

A sort displays the data in order based on chosen criteria. For example, a sort using EventID

lists the data in alphabetical order by their EventIDs. A sort using date will put the earliest 

events first, and the most recent events last. 
130 

A filter displays a subset of the data at the top of the table. As when using a sort, a field is first 

selected, but a value for that field is then also chosen. For example, to apply a date filter, 1) 

select the date field and 2) a specific date from the drop-down list of dates. Only those data 

collected on that specified day will be displayed. To display data collected for a specific 

location, 1) select locations from the drop-down list, and 2) select the location whose records are 

to be displayed. (Note that sorting and filtering do not change the contents of the underlying 

table. They simply change the display order. 

6.1 Applying a Filter or Sort to shoreline change monitoring data 

1. From the Main Menu, open the Shoreline Change Monitoring Data form. 

2. At the bottom of the form are controls for Filter and Sort functions. 

3. Select either Filter (Show Only) or Sort By in the radio buttons on the left. 

4. Select from the first drop-down list the field to use for the filter or sort. 

5. If a filter is selected, a second drop-down list will be visible. Use this to select a 

value for filter. 

6. Click the Do Filter or Do Sort button. 

7. To use a filter and a sort concurrently, repeat the steps above for the second function. 

6.2 Removing a Filter or Sort from shoreline change monitoring data 

1. The Shoreline Change form should already be open. 

2. Select either Filter (Show Only) or Sort By in the radio buttons on the left, depending 

on which is to be removed. 

3. Click the Clear Filter or Clear Sort button, as appropriate. 

To remove both a filter and a sort, repeat the steps above for the second function. 

Note that after a filter or sort is cleared, a user must reselect a new filter or sort field before 

pressing Do Filter or Do Sort again. If the Do Filter or Do Sort buttons are pressed repeatedly 

without reselecting a field and field value first, an error message will occur. Also, if another 

filter is run on a set of already filtered data, an area message will appear indicating incorrect or 

null values. 

For example, if the data have already been filtered by the year 2003 and then another filter is 

attempted with the year 2006, there are no values to display, and Access generates a null value 
131 

message. To avoid confusion, execute Filters and Sorts carefully, and try to sort or filter one 

field at a time. Then Clear the filter and reselect a new field to sort or filter. 

Note also that data on the main form are being filtered or sorted, and not the sub-form (i.e., the 

main monitoring data form, not the .ssf or .cor subforms). This means a user can filter by most 

event information — e.g., protocol, location, and year — but not by .sff or .cor file names.

7 Distance Matrices 

Shoreline features incorporated into a location’s master shoreline shapefile are subsequently 

analyzed for long- and short-term changes using a tool such as the USGS Digital Shoreline 

Analysis System (DSAS). These tools can derive data matrices of distances between shoreline 

features and an established baseline along certain pre-defined azimuths. 

These matrices are cumulative, expanding each time another feature is added to the master 

shapefiles, and then analyzed. They should therefore be updated within the Shoreline Change 

Monitoring Database each time a new shoreline is entered. 

Distance matrices should be prepared as Microsoft Excel spreadsheets with formats similar to 

that shown below: 

The distance matrix for each location should be stored in a single Excel file (.xls) using the 

naming convention ParkCode_matrix.xls (e.g., ASIS_matrix.xls), which can be stored in the 

same directory as the associated GPS/GIS data folders (‘shoreline_datasets’) described in section 

1.1 Creating the Initial Directory Structure, above. 

7.1 Uploading a new or updated distance matrix 
132 

Once properly formatted, the distance matrix can be uploaded as a table in the database via the 

following procedure. 

1. From the Main Menu, open the Import Distance Matrix form. 

2. Browse to the correctly-formatted Excel file (.xls) 

3. Click on the corresponding location. 

If this is the first time a data matrix has been uploaded for a site, a confirmation message will 

appear, and a table will be saved to the database using the naming convention 

‘tbl_ParkCode_matrix’. 

If a matrix has previously been saved and the file to be uploaded represents an update, the older 

table will be replaced, but a backup of the former version will be saved using the naming 

convention ‘tbl_ParkCode_matrix_PREVIOUS. 

(Note: Previous versions will not be saved indefinitely: only two are maintained in the database 

at once. Once a third iteration of the matrix is uploaded, the first will be deleted. If more 

versions are desired, they should be exported and saved outside of the database.) 
The Department of the Interior protects and manages the nation’s natural resources and cultural heritage; provides scientific and 

other information about those resources; and honors its special responsibilities to American Indians, Alaska Natives, and affiliated 

Island Communities. 

NPS 962/101471, March 2010 
National Park Service 

U.S. Department of the Interior 

Natural Resource Program Center

1201 Oakridge Drive, Suite 150 

Fort Collins, CO 80525 

www.nature.nps.gov 

EXPERIENCE YOUR AMERICA TM