Json returns nulls instead of integers

  • 7
  • Problem
  • Updated 4 years ago
Hello there!

I've noticed that there were a change in weather data delivered in Json feedback.
In forecast parameter snow and precipitation Json returns {null} instead of "0"
Is that permanent change?

"qpf_allday": {
"in": null,
"mm": null
"snow_allday": {
"in": null,
"cm": null

Looking forward to hearing from You!
Photo of ryboszukaczekran20DR

ryboszukaczekran20DR

  • 2 Posts
  • 0 Reply Likes

Posted 5 years ago

  • 7
Photo of aaron.weber11

aaron.weber11

  • 1 Post
  • 0 Reply Likes
I am wondering if this is a "different" problem. For example, it is currently raining here in NJ. Pulling a 10day forecast shows me this for today:
"qpf_allday": {
"in": null,
"mm": null
},
"qpf_day": {
"in": 0.09,
"mm": 2
},
"qpf_night": {
"in": 0.04,
"mm": 1
},

So not only is qpf_allday null's, but shouldn't it be 0.09 + 0.04 ?
Photo of albertorenen

albertorenen

  • 6 Posts
  • 0 Reply Likes
I am experiencing the same on xml as well. Is that a permanent change?
Photo of dhhockinson

dhhockinson

  • 1 Post
  • 0 Reply Likes
I am also seeing the same issue with XML. Has there been a change in how this data is reported or is this functionality currently down?
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 123 Reply Likes
We are looking into this field and its disappearance. We are working on restoring it.
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 123 Reply Likes
There is a weird workaround if you need it right away. Add /hourly/ to your request. The data is in the hourly data and will fill into the /forecast/ data if you call both. If you just call /forecast/ it will be null. We will work on restoring it, but this is something you could do right away to get it back.
Photo of ryboszukaczekran20DR

ryboszukaczekran20DR

  • 2 Posts
  • 0 Reply Likes
Thank you for reply.

Actually, I've replaced qpf_allday with qpf_day as a quick fix. Not ideal solution but at least qpf_day returns some values from time to time...

have a nice day!
Photo of tkr1

tkr1

  • 5 Posts
  • 0 Reply Likes
The XML format is wrong too. Those fields are empty.
Photo of Tim

Tim

  • 1 Post
  • 0 Reply Likes
Any update on timing for getting the null response for qpf_allday and snow_allday issue resolved without using the /hourly workaround? Thanks!
Photo of MyFarms

MyFarms

  • 2 Posts
  • 0 Reply Likes
I also just encountered this. qpf_night is showing values, but qpf_allday is null.
Photo of janoostijen

janoostijen

  • 8 Posts
  • 0 Reply Likes
What is the status of this issue? Is it already solved?
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 123 Reply Likes
This fix was just launched. It should return the allday values now.
Photo of Glen Carreras

Glen Carreras

  • 2 Posts
  • 0 Reply Likes
Is it definitely implemented already? Still seeing nulls here:

"qpf_day": {
"in": null,
"mm": null
},
"qpf_night": {
"in": 0.15,
"mm": 4
},
"snow_allday": {
"in": 0.0,
"cm": 0.0
},
"snow_day": {
"in": null,
"cm": null
},
Photo of Glen Carreras

Glen Carreras

  • 2 Posts
  • 0 Reply Likes
Sigh, 2 months later and:

"qpf_allday": {
"in": 0.00,
"mm": 0
},
"qpf_day": {
"in": null,
"mm": null
},
"qpf_night": {
"in": 0.00,
"mm": 0
},
"snow_allday": {
"in": 0.0,
"cm": 0.0
},
"snow_day": {
"in": null,
"cm": null
},