Can't Store Null or Missing at Measurement Endpoint
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 28
- Forks
- 25
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 20
Description
I'm having trouble storing a null or missing value for the gage-height or flow parameters at the post measurement endpoint.
Here's what I've tried for gage-height:
"gage-height": null
"gage-height": Null,"gage-height": NULLetc....
"gage-height": -340282346638528859811704183484516925440, works but it actually stores that value in cwms so it doesn't show as missing.
Also, when a measurement is successfully saved, the return is this:
I'm not sure if the null issue is bigger than this endpoint, but it would be nice to have a way to reliably write null or missing for all endpoints.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the POST measurement endpoint and reproduce the reported requests for null, missing, and the large sentinel value in gage-height or flow. Trace how the endpoint handles those inputs and verify that a supported representation of missing data is stored and that the successful response is reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100