Skip to content

Open data standard for automated exchange of recreational water quality data

License

Notifications You must be signed in to change notification settings

swimdrinkfish/opendata

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

55 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Open Data Standard for Recreational Water Quality

Welcome! Swim Drink Fish is developing a standard for exchanging recreational water quality data.

We need your help.

Goals:

  • Create a single standard for presenting recreational water quality data, so that different people monitoring different waters can share their results
  • Make the standard open, so that everyone can see it and shape it
  • Ensure data is shared in a machine-readable format (i.e., not pdf, not csv, not RSS) so that sharing is easy and automated

We need your help to refine the standard for the automated exchange of recreational water quality data.

Read on, or visit our project website for more information.

Background

The purpose of recreational water quality monitoring is to protect public health from contaminated water. Even where water is tested, however, it can be very difficult for the public to get an answer to the question “is it safe to swim?”

Hundreds of counties, municipalities, park organizations and nonprofits regularly test water for indicator bacteria, algae, and/or other harmful pollutants. The data should be shared quickly (within 24 hours) and with as wide an audience as possible in order to help people avoid waterborne illnesses; yet, this rarely happens.

The public faces four common barriers when they try to understand the health of their beach or swimming hole:

  • Access. Much of the water quality information collected is never published. It lives in data silos that are not accessible to the public.
  • Ease of Access. Public water quality does exist, but it can often be hard to find. It may be buried on websites or phone hotlines that aren’t easy for people to locate.
  • Clarity. The data is presented in a way that is difficult for the general public to understand and usually differs from place to place.
  • Age. When data is shared, it is often very out of date. Many places, for example, still only publish annual or monthly testing results.

Lack of water quality information means that people - often unknowingly - swim in contaminated waters. Studies from the Environmental Protection Agency estimate the between 3%-8% of people experience acute gastrointestinal illness (AGI) after swimming. An estimated 3.5 million Americans get sick each year. In Canada, the number is approximately 400,000. Children are the most likely to get sick.

The main reason water quality is not shared more widely is because there is no standardized way to present data.

Since 2011, Swim Guide has spent thousand of hours each manually compiling water quality information from websites (some using legacy technologies), phone hotlines, and spreadsheets so that 1.5 million people can access beach water information. Meanwhile, regulators in different countries struggle to consolidate water quality results from different communities to inform policy and funding decisions.

That’s why we decided to develop an open data exchange standard for recreational water quality information.

An open data standard will increase data exchange, improve public awareness of water quality, and aid researchers trying to protect recreational waters. The initiative will reduce the number of people getting sick from contact with polluted water and increase the number of environmental protection plans for communities affected by pollution.

This project is funded by the Canadian Internet Registration Authority (CIRA.ca).

Authors

Chris Wilson (cwilson@surfrider.org) Surfrider Foundation

Rajbir Parmar (Parmar.Rajbir@epa.gov) Environmental Protection Agency, Office of Research and Development

Adam Griggs (agriggs@rivernetwork.org ) River Network

Joan Yee (Joan.Yee@albertahealthservices.ca) Alberta Health Services

Dylan Neild (dylan@codeandstrings.com)

Gabrielle Parent-Doliner (gabrielleparent@gmail.com)

Krystyn Tully (krystyn@mac.com)

Project timeline

Oct 2017: Expert workshop to lay the groundwork for the open data standard

Dec 2017: Draft consultation period begins

Feb 2018: Comment period ends

March 2018: Pilot projects begins

June 2018: Launch of Open Data Standard

Invitation to Comment on the Open Data Standard for Recreational Water Quality - Version 1

Current Status

The current version of this standard proposal is version 1.0.1. Any comments, discussion, and decisions relating to the v1.0.1 standard will be implemented in subsequent releases.

Current version (v1.0.1): https://github.com/swimdrinkfish/opendata/tree/master/v1.0.1

Instructions for commenting

We encourage you to contribute to this standard on Github: https://github.com/swimdrinkfish/opendata/

Comments can also be sent to: Gabrielle Parent-Doliner Swim Guide Program Manager (gabrielle@swimdrinkfish.ca)

Github instructions

Search existing issues

Before creating a new discussion, please look through existing issues to see whether your questions has already been asked or your comments have already been raised. If an issue addressing your question, comment, or problem has already been created, please contribute.

Join an existing discussion or comment on existing issue

To join an existing discussion or comment on an existing issue add new comments at the bottom of a discussion/issue. You can contribute in text, or richer content and links using Markdown syntax.

Create a new discussion

You must have a Github account and be logged in to create a new discussion. Click on the "New Issue" button to create a new conversation.

Label a discussion

Once you have created a new issue, you can add a label. The label should reflect the discussion item. This will make it obvious to other users that it is meant for review and comment.

Add a mention in a discussion

If you want to direct your comment, question or issue to a specific person you can add a mention in the text of your discussion or comment (type the '@' symbol and adding the person’s GitHub user name).

Use Markdown syntax

This forum supports the use of Github flavored Markdown syntax.

More info on the how-tos of contributing? Click here