Cool - thanks.

I've signed up for the Beta-Dev program - we'll see what happens in due course when they respond.

It looks like a great idea (and I can think of other uses for it too, aside from this project ).

If we can do it, it's probably better-suited to Paul's original idea of actually grabbing ALL the data, and reprocessing it into a bunch of similarly-scaled images, so that there is less overall pressure on the NWS servers.

It would mean a fair bit of re-coding here, but I might work on it if anyone's still interested (and if time permits).

At the moment, I have a PHP file on my home-server, which fetches the geo-location data, and rebuilds the KMZ file every hour. People using the Network-Link re-fetch that KMZ from me every hour, and then their machines in turn, fetch the selected images direct from the NWS (but with hopefully geo-location positions that are less than an hour old, so not too far drifted).

Currently, I have the PHP running as a sheduled task on my server, so it merely 'dumps' the new KMZ to the location where the Network Link points to...

...which leads me to another problem... is there a way of making a NING PHP app run on a scheduled basis, or have they coded the site in such a way that they expect people to actually VISIT the php file itself?

I guess I can re-code it, so that it goes back to a network-link to a php file which does a 'live' re-fetch from NWS and spits out the geo-formatted KMZ - but that then means 'random-access' hits on NWS for the geo-location data, thus adding to their load.

I wish we could make the NWS host this themselves - it'd be great!

More to the point, I wish GE could be made a little 'smarter' so we can stop users from dragging the whole set of radar images back at once, by clicking that top-level folder... Surprised we've not heard any comment from the GE Devs on this score