Skip to content

NLDI schema.org JSON LD media type

David Blodgett edited this page Sep 21, 2020 · 1 revision

The NLDI presents data that represent both monitoring features and environmental features that can be the subject of monitoring. NLDI resources, or a wrapper around them, could be used as landing-content for NHDPlusV2 catchments and Mainstems features.

All features have one or more @type ensuring compatibility with schema.org and using HY_Features types.

Content is to be minimal initially -- no new data loaded in data store to enrich responses. That is, this work provides a solid proof of concept and technical architecture for adding a JSON-LD media type t NLDI response documents.

Hydrologic locations

A semantic representation of hydrologic locations known to the NLDI. Not intended to be a source of landing content.

Include:

  • link to URI-14 identifiers for locations.
  • point location serialized as GeoJSON-LD, point location as schema.org, and link to GeoJSON from NLDI.
  • name
  • linear reference to mainstem.
  • linear reference to catchment.
  • linear reference to reachcode / measure.

Mainstems

A semantic representation of a mainstem river. Landing content for an identified mainstem.

https://geoconnex.us/ref/mainstem/1234567890 -> https://labs.waterdata.usgs.gov/api/nldi/linked-data/mainstem/

Include:

  • @id that is URI-14 for mainstem.
  • Link to NLDI UM navigation as GeoJSON representation
  • Simplified preview geometry as schema.org line.
  • name
  • links to all monitoring locations along the mainstem using URI-14 as link.

Drainage Basins

A semantic representation of a drainage basin query. Nothing special.

Include:

  • Link to NLDI basin query as GeoJSON
  • Simplified preview geometry as schema.org polygon.
  • name
  • link to mainstem

Catchments

A semantic representation of a catchment. No spatial representation.

COMID

e.g. https://labs.waterdata.usgs.gov/api/nldi/linked-data/comid/17511378

A semantic representation of a catchment feature. Mostly topology and realization links.

Includes:

  • @id that is a URI-14 for the catchment.
  • schema.org bounding box.
  • Link to flowpath, boundary, and hydrometric network realizations.
  • Link to largest drainage basin it takes part in. (encompassingCatchment)
  • Link to the drainage basin it is on the mainstem of. (encompassingCatchment)

Reachcode ??

HUCs ??

Flowpaths

e.g. https://labs.waterdata.usgs.gov/api/nldi/linked-data/comid/17511378/flowpath

A semantic representation of a flowpath feature.

Includes:

  • qualified name e.g. (Flowpath that is part of {{gnis_name}})
  • Simplified preview geometry as schema.org line geometry.
  • Link to GeoJSON representation.

COMID

Reachcode ??

Catchment Boundaries

COMID

e.g. https://labs.waterdata.usgs.gov/api/nldi/linked-data/comid/17511378/boundary

A semantic representation of a catchment boundary.

Includes:

  • Simplified preview geometry as a schema.org polygon geometry.
  • Link to geoJSON representation.

HUCs??