Response from Aeris who has amazing customer support.
First off, apologies for the delay in response. This was a very unique issue and took our team a bit to find as we wanted to verify if it was a data issue within Aeris, the PWS system or invalid data from the PWS system.
We have found out it was the latter. Reviewing our API ingest logs, it seems the station sent an errant data element from the prior day on the 19th.
At 4:15 local time to the station, you will see what looks to be an errant record. Notice that the temperature jumped, as did the humidity, pressure and the errant 24 hour precip.
In reviewing, we found other days where the station sent a single errant record. Such as on Feb 18th at 8:20, 2:20. 2:25:
Our team is taking two courses of action:
PWS weather is ignoring the 24 hour precip reading and being errant. Our Data team has already made an adjustment today to the Aeris API so that it can ignore this value as well, marking it with a caution flag. This update will be pushed on Monday or Tuesday of next week.
We are continuing to investigate this station and if we see that it consistently sends errant data, we will add a caution flag to the station itself, which will take it out of the standard search, unless requesting it directly.
I will provide an update next week once we push the update for the summary system and update the previous data. Additionally, I will inform you on the status of the station itself.