-
In conversation with @jkreft-usgs, we agreed that the NLDI should be moved to the same database used by some other production projects in waterdata.usgs.gov. Not really an issue for the code in this r…
-
We should make a sitemap.xml for at least everything in info.geoconnex.us. Although it's possible we could create a "sitemap" that includes all 1:1 PIDs and all things with geoconnex regex PIDs that a…
-
Currently, the table of sources is a hand-managed database table. We need to design and implement a pull-request based scheme to allow people to 1) submit new data sources for consideration and 2) aut…
-
In the spirit of the W3C data on the web best practices, as much as possible, NLDI resources should be available in an html content type. These pages can be extremely rudimentary -- For resources that…
-
We need a "catalog view" of NLDI features (OGC-API Features)
e.g. https://labs.waterdata.usgs.gov/api/nldi/linked-data/nwissite/ should return a GeoJSON feature collection of the nwissites.
This…
-
I want to look into configuring elasticsearch into pygeoapi for info.geoconnex.us to investigate the pygeoapi-as-metadata catalog use case.
-
Hello,
This issue is based on an exchange over loading EPA NPDES data into NLDI from early Feb, 2018. I'll just try to distill it down.
So data goes into NLDI (usually via a crawler) and data c…
-
Since the UT and DD queries can be really expensive, I think we should require a distance input to be entered explicitly.
We should add swagger documentation that indicates that this is a very exp…
-
No functional changes, but the crawler code base has a number of updates pending in open PRs.
https://github.com/ACWI-SSWD/nldi-crawler/pulls
Should make sure we have the project building and u…
-
For the `...navigate/` we currently return a list of navigation option urls. Each of those urls returns the flowlines for that navigation.
Instead of the flowlines, the navigate methods should retu…