1 of 43

Community Lightening Slides - Kyle

NMWDI Directing Agencies Work Group Meeting

August 12, 2020

Kyle Onda: kyle.onda@duke.edu

Integrating Federal Data with the NMWDI

2 of 43

Internet of Water is:

An aspirational concept of linked water data systems

A decentralized, collaborative multi-organization initiative to organize water data on the internet

A project (currently at Duke University) providing key social and technological infrastructure supporting the above

  • Particular focus on state/local agencies and NGOs

3 of 43

How will Federal Data be Integrated with NM Data?

How will Federal data be interacted with through NMWDI services?

How will other Federal data about a given feature in NM be discovered or de-duplicated from NM data about the same and related feature?

4 of 43

How will Federal Data be Integrated with NM Data?

How will Federal data be interacted with through NMWDI services?

How will other Federal data about a given feature in NM be discovered or de-duplicated from NM data about the same and related feature?

1: Application Layer (see NMWDI Architecture)

2. Via API proxying (see NMED)

- USGS NWIS

- USBR RISE

- USEPA SDWIS/ ATTAINS/ WQX

- USACE A2W

- NOAA NCDC CDO

5 of 43

How will Federal Data be Integrated with NM Data?

How will Federal data be interacted with through NMWDI services?

How will other Federal data about a given feature in NM be discovered or de-duplicated from NM data about the same and related feature?

1: Application Layer (see NMWDI Architecture)

2. Via API proxying (see NMED)

- USGS NWIS

- USBR RISE

- USEPA SDWIS/ ATTAINS/ WQX

- USACE A2W

- NOAA NCDC CDO

6 of 43

Currently…

I wonder how much water is in my favorite lake to visit?

Favorite Lake water levels

7 of 43

Future Vision

I wonder how much water is in my favorite lake to visit?

Oh, I didn’t know these other data existed… Is it safe to swim or fish…

Favorite Lake water levels

8 of 43

CURRENT STATUS

9 of 43

sdfsfsdfs

(1) Unique IDs – a persistent identifier unique to each dataset

Geoconnex Does 3 Things

Well #1

Well #1

Same ???

The water version of a DOI

https://geoconnex.us/epa/hmw/020700110204

Geoconnex

version

of DOI

Organization’s

Unique ID for

Data

+

Registered

organization

name

+

10 of 43

sdfsfsdfs

(1) Unique IDs – a persistent identifier unique to each dataset

Geoconnex Does 3 Things

Well #1

Well #1

Same ???

The water version of a DOI

https://geoconnex.us/epa/hmw/020700110204

Geoconnex

version

of DOI

Organization’s

Unique ID for

Data

+

Registered

organization

name

+

https://geoconnex.us/

Persistent Identifier Registry

github.com/internetofwater/geoconnex.us

Anyone can mint PIDs!

11 of 43

sdfsfsdfs

(1) Unique IDs – a persistent identifier unique to each dataset

(2) Locates Data – provides a stable landing page and redirects users to where data are currently hosted

Geoconnex Does 3 Things

12 of 43

sdfsfsdfs

(1) Unique IDs – a persistent identifier unique to each dataset

Geoconnex Does 3 Things

(2) Locates Data – provides a stable landing page and redirects users to where data are currently hosted

13 of 43

sdfsfsdfs

(1) Unique IDs – a persistent identifier unique to each dataset

(2) Locates Data – provides a stable landing page and redirects users to where data are currently hosted

Geoconnex Does 3 Things

14 of 43

sdfsfsdfs

(1) Unique IDs – a persistent identifier unique to each dataset

(2) Locates Data – provides a stable landing page and redirects users to where data are currently hosted

(3) Links Data – enables data to be linked together based on geography and key words

Geoconnex Does 3 Things

This monitoring station is located inside this watershed

15 of 43

sdfsfsdfs

(1) Unique IDs – a persistent identifier unique to each dataset

(2) Locates Data – provides a stable landing page and redirects users to where data are currently hosted

(3) Links Data – enables data to be linked together based on geography and key words

Geoconnex Does 3 Things

This monitoring station is located inside this watershed

And so are all of

these sites…

16 of 43

sdfsfsdfs

(1) Unique IDs – a persistent identifier unique to each dataset

(2) Locates Data – provides a stable landing page and redirects users to where data are currently hosted

(3) Links Data – enables data to be linked together based on geography and key words

Geoconnex Does 3 Things

Are data located WITHIN a watershed (aquifer, city, county, service area…)?

Does a watershed CONTAIN a stream gauge, well, water intake, etc.

17 of 43

sdfsfsdfs

Locations (e.g. stream gages, wells,

dam locations)

Features of Interest (e.g. public water

systems, lakes)

Cataloging Features (e.g. HUC boundaries, administrative boundaries)

Finding Linked Data

selfie:within/contains

The metadata contains information about how data intersects a container

(“cataloging features”)

18 of 43

Finding Linked Data

sdfsfsdfs

Locations (e.g. stream gages, wells, dam locations)

Features of Interest (e.g. public water systems, lakes)

Cataloging Features (e.g. HUC boundaries, admin boundaries)

19 of 43

Finding Linked Data

sdfsfsdfs

Locations (e.g. stream gages, wells, dam locations)

Features of Interest (e.g. public water systems, lakes)

Cataloging Features (e.g. HUC boundaries, admin boundaries)

20 of 43

Embedded Link to a Watershed

Persistent Id

HUC 12

21 of 43

FUTURE PLANS

22 of 43

“Knowledge Graph”

A search index for water data

Integration with NHD

23 of 43

Bridge monitoring location

Reservoir

HUC12

Link: within

Link: within

https://geoconnex.us/ref/{feature_type}/{feature_id}

Building a Water Knowledge Graph: Community Reference Features

24 of 43

Bridge monitoring location

Reservoir

HUC12

Link: within

Link: within

https://geoconnex.us/ref/{feature_type}/{feature_id}

Building a Water Knowledge Graph: Organizations publish data

https://geoconnex.us/{org}/{feature}/{data_id}

25 of 43

Bridge monitoring location

Reservoir

HUC12

Link: within

Link: within

https://geoconnex.us/ref/{feature_type}/{feature_id}

https://geoconnex.us/{org}/{feature}/{data_id}

Building a Water Knowledge Graph: Organizations Link Data

26 of 43

Bridge monitoring location

Reservoir

HUC12

Link: within

Link: within

https://geoconnex.us/ref/{feature_type}/{feature_id}

https://geoconnex.us/{org}/{feature}/{data_id}

Building a Water Knowledge Graph: Crawl

Web crawler

27 of 43

Bridge monitoring location

Reservoir

HUC12

Link: within

Link: within

https://geoconnex.us/ref/{feature_type}/{feature_id}

https://geoconnex.us/{org}/{feature}/{data_id}

Building a Water Knowledge Graph: Crawl

Web crawler

Goes to any site with a geoconnex PID

28 of 43

Bridge monitoring location

Reservoir

HUC12

Link: within

Link: within

https://geoconnex.us/ref/{feature_type}/{feature_id}

https://geoconnex.us/{org}/{feature}/{data_id}

Building a Water Knowledge Graph: Crawl

Web crawler

Harvests links

29 of 43

Bridge monitoring location

Reservoir

HUC12

Link: within

Link: within

https://geoconnex.us/ref/{feature_type}/{feature_id}

https://geoconnex.us/{org}/{feature}/{data_id}

Building a Water Knowledge Graph: Crawl

Web crawler

Harvests links

30 of 43

Bridge monitoring location

Reservoir

HUC12

Link: within

Link: within

https://geoconnex.us/ref/{feature_type}/{feature_id}

https://geoconnex.us/{org}/{feature}/{data_id}

Building a Water Knowledge Graph: Crawl

Web crawler

Harvests links

31 of 43

Search and Browse the Graph!

Find all relevant (participating) water data

Database

User Interface

Search by:

  • Organization
  • Parameter
  • Site name
  • Site type
  • Location (lat/lon)
  • Watershed
  • State/county/place
  • Upstream/downstream
  • And more!

Search

32 of 43

Integrating with NHD

USGS is developing the Hydro-Network-Linked Data Index

https://waterdata.usgs.gov/blog/nldi-intro

An open-source, publicly accessible system to index any geospatially-referenced data to NHDPlus catchments and reach codes

Enable hydrologically-relevant search (e.g. upstream/downstream)

33 of 43

Integrating with NHD

https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-364700114080301

34 of 43

Integrating with NHD

https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-364700114080301/UM?distance=100

35 of 43

Integrating with NHD

https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-364700114080301/UT?distance=100

36 of 43

Integrating with NHD

https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-364700114080301/UT/nwissite?distance=100

37 of 43

Integrating with NHD

https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-364700114080301/UT/wqp?distance=100

38 of 43

Integrating with NHD

https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/USGS-364700114080301/UT/wade?distance=100

39 of 43

Integrating with NHD

40 of 43

Integrating with NHD

To contribute data:

Need:

  1. 1) Locations with lat/lon

  • 2) Location-specific landing pages

  • 3) Persistent identifiers for those landing pages

41 of 43

Integrating with NHD

To contribute data:

Require:

  1. 1) Locations with lat/lon

  • 2) Location-specific landing pages

  • 3) Persistent identifiers for those landing pages

NMWDI representations can be used for this

42 of 43

In summary:

This use case can be accomplished only if everyone is willing and able to document and add links in their data to data that is not theirs

Are we all willing to care

a little

about how our data relates to others’?

43 of 43

Learn More

Internet of Water : https://internetofwater.org

Project Geoconnex: https://geoconnex.us

Geoconnex reference features: https://info.geoconnex.us

Contact: kyle.onda@duke.edu