How to survey beach litter on the Great Lakes

A Great Lakes beach can change dramatically between visits. Wind direction, waves, river discharge, ice, beach grooming and public events can bury, expose or deliver debris. That variability is exactly why a monitoring method needs stable boundaries and complete field notes.

NOAA's MDMAP provides a standardized shoreline protocol and data resources. Groups intending to contribute comparable data should follow that current protocol rather than creating a local approximation and using the program name.

Pick a question before a segment#

Possible questions include:

• Is the amount or type of macro-debris changing at one beach?
• Does a tributary mouth differ from an open shoreline?
• What accumulates after major wind events?
• Which items dominate around a fishing access?

The question determines site selection and frequency. Avoid choosing only the visibly dirtiest patch and then generalizing to an entire lake.

Preserve repeatability#

Record coordinates and fixed landmarks, observation date and time, searched boundary, people and effort, wind and recent weather, water level, wrack and grooming. Photograph the same directions from the same points.

If the beach was mechanically cleaned before one survey, record it. That is not bad data; missing that fact is.

Do not improvise a microplastics result#

Tiny particles require defined size ranges, collection and contamination controls. A jar of colorful fragments is evidence that fragments were found, not a concentration estimate for Lake Michigan. Use the protocol appropriate to the intended measurement and state its detection limit.

For ordinary volunteer work, categorizing visible fragments consistently may be more honest than attempting laboratory language in the field.

Separate monitoring from removal#

Follow the chosen protocol on when material is counted and removed. Afterward, route collected material through the land manager's disposal plan. Large nets, cylinders, hazardous containers and abandoned vessels need specialist response.

Publish the dated visual series as a mapped gallery, but link to the dataset and method rather than turning photographs into measurements. Map a removal need separately when the survey identifies material beyond the monitoring team's scope.

Report only what the design supports#

“We recorded X items in a defined segment under this method” is useful. “The Great Lakes contain X items” is not supported by one volunteer survey. Keep units, categories, effort and uncertainty visible.

Create a quality check before publishing#

Have one person compare the digital entry with the original sheet. Confirm the site identifier, date, survey method, segment length, elapsed time and category totals. Preserve zeros; a blank can mean the field was missed, while zero means the team looked and found none.

Flag unusual counts and explain them rather than deleting them. A festival, storm, beach-grooming pass or overflow incident may be the most important context in the series. Retain photographs and field notes under a consistent filename so a later reviewer can trace the observation.

When volunteers disagree about an item, use the protocol's category guide and document the final choice. Do not create a new category halfway through a time series without mapping how older records will be treated.

The value of a repeat visit is not just another bag removed. It is a comparable observation that helps distinguish a one-day deposit from a persistent pathway.