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
{{ message }}
This repository has been archived by the owner on May 31, 2024. It is now read-only.
We need to be able to pull counts of these items from the database:
planned HWMs
flagged HWMs
surveyed HWMs
approved / unapproved HWMs
deployed Sensors
recovered Sensors
uploaded Sensors
approved Sensors
We also need to filter those counts by sensor type (storm-tide / wave / RDG / precip) or by State. So rather than creating a huge mess of new endpoints for counting, I'm thinking the easiest thing might be to add a "counts_only=true" attribute to the FilteredHWMs and FilteredSensors endpoints. Then I can use all the existing filtering logic of those two endpoints, rather than creating a bunch of new counting endpoints.
The text was updated successfully, but these errors were encountered:
We need to be able to pull counts of these items from the database:
planned HWMs
flagged HWMs
surveyed HWMs
approved / unapproved HWMs
deployed Sensors
recovered Sensors
uploaded Sensors
approved Sensors
We also need to filter those counts by sensor type (storm-tide / wave / RDG / precip) or by State. So rather than creating a huge mess of new endpoints for counting, I'm thinking the easiest thing might be to add a "counts_only=true" attribute to the FilteredHWMs and FilteredSensors endpoints. Then I can use all the existing filtering logic of those two endpoints, rather than creating a bunch of new counting endpoints.
The text was updated successfully, but these errors were encountered: