No night information in the icon element

  • 2
  • Problem
  • Updated 2 months ago
Why is it different information in the icon and icon_url element in the forecast current_observation.

I have this information
"icon":"clear",
"icon_url":"http://icons.wxug.com/i/c/k/nt_clear.gif"
 So when i use icon element with own icons i do not get night symbols.
 /Mike
Photo of Michael Parment

Michael Parment

  • 1 Post
  • 0 Reply Likes

Posted 3 years ago

  • 2
Photo of Ravi Yadav

Ravi Yadav

  • 82 Posts
  • 9 Reply Likes
Can you share your API request URL? 

The icon URL for clear should be: 

icon: "clear",
icon_url: "href="http://icons.wxug.com/i/c/k/clear.gif"
Photo of Max

Max

  • 1 Post
  • 1 Reply Like
I got the same issue for conditions

The forecast get the correct icon name for the icon url. After sunset I receive the icon url for the night condition, but the icon name for the day condition


https://api.wunderground.com/api//ast...
please add your api key to display

cloudy in the screenshot is not the best example, but please have a look
(Edited)
Photo of Gary Abbott

Gary Abbott

  • 1 Post
  • 1 Reply Like
I would like to replace the icon set, but run into the same issue.  How to know if it is night?
I find no flag or other info in the results.  "icon" does not indicate day or night. 
At this point will have to process "icon_url" string to strip out "nt_cloudy" etc.

No answers on this?
Photo of James Anding

James Anding

  • 56 Posts
  • 42 Reply Likes
I reported this as a bug more than a month ago and got no response at all.
This was my original report:

Every “icon” in that Jason string when it is night is incorrect.

This causes a problem if you want to use a different icon set because when you get
the “icon” and use it in a different icon set it is always a daytime icon and not a nighttime icon.

"icon": "clear",
"icon_url":"http://icons.wxug.com/i/c/k/nt_clear.gif";,

The Icon field should match the icon_url field.
It Does Not.
Photo of George Zacharia

George Zacharia

  • 2 Posts
  • 0 Reply Likes
This issue still persists, any updates on this?
Photo of James Anding

James Anding

  • 56 Posts
  • 42 Reply Likes
I reported that problem about 2 years ago, and they ignored it then also. I had to do some tricks in my code to get around it. They don't fix anything unless they absolutely have to and even then they do a lousy job of it. The fix's they do usually come back again after a while.

(Edited)
Photo of George Zacharia

George Zacharia

  • 2 Posts
  • 0 Reply Likes
I checked if anybody else has the similar problem and found a reply where adding a version parameter to API call could resolve the issue. Instead of conditions one could use conditions_v11 can get the appropriate response
(Edited)
Photo of Tim Roche

Tim Roche, Official Rep

  • 317 Posts
  • 28 Reply Likes
That is an undocumented and unpublished api.  Please don't rely on it, there will be no notification of changes or deprecation.