1.) We need to break down the radards into smaller groups still. Being a programmer, I decided to try and break it like most good programmer would do. Anyway, long story short, ouch lol . I checked one group of radars (Short Range Reflectivity) and watched my v0.616 Client grow to well over 1GB in size. I think too many people will do that (or worse), and that's a bad thing. Even with warning and such, we either need to mitigate that risk even further, or dissallow them from doing that (currently impossible I think).
2.) Can we make the legend layer so that it requires explicit turn-on to be visible? I know that if people go through and set it like they want it with regards to legends on or not, those will keep their state even over refreshes....but it might be nice to maybe separate them completely from the actual radar to declutter, and make the legends a separate folder to be able to turn them on if the need arises.
3.) Maybe further separate the radars by Coast (ie. Atlantic & Gulf) to further reduce the possibility of a catastrophic checkbox?
This is one reason why I wish that we could get the raw reflectivity data and display it as we wish by generating our own images from it etc......but I still think this is a mountain of work and probably not the right course. Let me know what you think and thanks for the work Jacko .
Previous
Index
Next
Flat
Re: Coastal Radar Network Link (v1.0)
Edit
Reply
Quote
.
