Rogue Radar Image

Hi all,I grab a png image using the radar api every 15 minutes and then combine these to create my own animated radar image for the previous 12 hours. I have noticed recently that a "rogue" image creeps in, sometimes quite frequently. Its always the same image (I will try and attach). I also do a similar process on my brothers website using a different api key, different location etc and likewise get a rogue image, although the image is different to mine but always the same that appears.

I have deleted all my png files (my script automatically deletes images older than 12 hours anyway) to make sure somehow a rogue image was not being used but to no avail.

I grab an update once an hour and it happens several times a day for me. Interestingly, the radar image is always the same and believe from a few weeks ago. My app isn't caching so thinking it must be on the server side.

Hi Brendan,Sorry to say that the same image re-appeared at 19:00 and 19:15 UK. I deleted all my png files when you stated it should be resolved but exactly the same image as the one originally posted has re-appeared. Please see http://www.midlifedad.me.uk/weather/radar.php

I also am having the same issues. It seems that at random intervals, the image and timestamp are not accurate, with the image seemingly coming from a "cached" point in time.

I have the same random behaviors using PiClock as I do in the browser, with no consistency in whether I get a proper radar layer or timestamp (UTC vs. EST). When did the fix get implemented, so I can monitor through out the day?

EDIT: I just looked at the screen, and the time stamp for the "region" is in UTC, while the "city" timestamp is in EST. The radar layers "seem" accurate and agree, although the UTC timestamp is indicative of a forthcoming "cached" image set coming.

Tom, have been looking for the same thing. With other issuesI have seen, on forecast for example, you could quite easily spot a rogue file , always a low amount of bytes or same so you could write a small script to detect the file and call the api again until a file size greater than the criteria was met. Unfortunately with the radar png it’s not constant, my rogue image is around 10k and even this varies slightly for the same image. Problem is you can get a valid image with roughly the same size, depending on how much data is in the image so it’s difficult to spot the rogue one.

Hi I am running PiClock on a RPI 3 - it uses a WU API and it too is still showing the same rogue radar image every hour or so - possibly less frequently now in line with Brendan's update (this started about three weeks ago). I do not see a change in the time stamp it seems to be correct (UTC running a series of images up to about 5 minutes behind the actual time). So better but still not as it use to be - I have used PiClock for about a year without an issue until now.

I got one rogue image around 13:00 GMT so before above post from Brendan but none between then and now (22:30 GMT). I will keep track on it for a few days and let you know if I see any further ones. However, 1 out of 48 frames is much improved. Thanks. Andy

I've been experiencing the same issue, within .Net I casted the byte[] to an image and checked the frame timings property to make sure they matched the delay I asked for in the query string, if it did not I had it wait a second and retry up to 5 times, this seemed to work until the issue is resolved.

Two different pulls, separated by a second seem to pull vastly different overlays. I have not seen the black overlay, only incorrect timestamps and an overlay that is not related to the GPS coordinates I sent in.

As I opened the original post I thought I would pass back an update. I have had no rogue images from either of my API calls for a few weeks now so as far as I can see this issue appears to have been resolved. Thanks.