Migrate from api.water.usgs.gov geoserver to pygeoapi

[dblodgett-usgs]

Is your feature request related to a problem?

We have recently established a pygeoapi instance to host the layers made available from https://[api.water.usgs.gov/geoserver/ows?service=WFS&version=1.0.0&request=GetCapabilities](https://api.water.usgs.gov/geoserver/ows?service=WFS&version=1.0.0&request=GetCapabilities)

The qa tier of this service is available here: https://labs-beta.waterdata.usgs.gov/api/fabric/pygeoapi and will soon be available at https://api.water.usgs.gov/fabric/pygeoapi.

This will require migration of the geoserver client in pynhd to use paginated OGC-API calls. We don't have a planned retirement date for geoserver but want to retire it soon as we are increasingly having a hard time updating it when new versions come out.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

[cheginit]

Thanks for the heads-up. I will work on (hopefully only) refactoring the WaterData class. I need to minimize the changes to the high-level API and maintain backward compatibility as much as possible.

[dblodgett-usgs]

The public QA has been up and down while we iron out some performance issues. It should be back tonight and generally available going forward. You can follow my progress over here: DOI-USGS/nhdplusTools#437

I'm using the rudimentary client that I had written for geoconnex as the starting point.

[cheginit]

Awesome! Thanks for the update.

[dblodgett-usgs]

It's back now and should be more or less in its final configuration. Please go easy on it while you are spinning up development and report scalability concerns you run into.