You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The specs for the new zonal stats API endpoints are available via the OpenAPI docs (https://api.snodas.geog.pdx.edu/docs). One can experiment with the new endpoints on that page as well. Note that they return a json format response by default; to get a CSV like we'll want for the UI, the HTTP request ACCEPTS header needs to be set to "text/csv". To test that out, build and run a query via the test functionality on that page then copy the example curl command and change the ACCEPTS header from "/" to "text/csv".
The parameters are no longer part of the url and the query parameters are at the end of the url. Updating these endpoints to use the new api will allow us to retire the old api.
The text was updated successfully, but these errors were encountered:
lbross
added a commit
to lbross/snodas-ui
that referenced
this issue
Jun 27, 2024
* issue #7: Implement SNODAS Zonal Values - Doy Range query
* issue #7: Added date range query; Changing elev range isn't working; Need to add event listener
* issue #7: Now sending selected elev interval
* issue #8: Updated linkend strings for both queryInits to point to the new endpoint with the correct parameters.
* issue #7: Update query names per @jduh request
The specs for the new zonal stats API endpoints are available via the OpenAPI docs (https://api.snodas.geog.pdx.edu/docs). One can experiment with the new endpoints on that page as well. Note that they return a json format response by default; to get a CSV like we'll want for the UI, the HTTP request ACCEPTS header needs to be set to "text/csv". To test that out, build and run a query via the test functionality on that page then copy the example curl command and change the ACCEPTS header from "/" to "text/csv".
The parameters are no longer part of the url and the query parameters are at the end of the url. Updating these endpoints to use the new api will allow us to retire the old api.
The text was updated successfully, but these errors were encountered: