I see the problem, but like you, don't have a solution for it. I guess really it just behoves the layperson to WISE UP and take the time to learn something they don't understand. We can do this with maybe judicious use of URLs linking to the 'Idiot's guide to radar-returns' (if there is such a document ) or maybe just the NWS FAQs?
My mission here is "enablement" primarily - giving people who know what they need
I hear ya, and still agree that it's a problem, but if we can't come up with an obvious answer, then all we can do is what we can do......until and unless we find a better way.
Quote:
LOL - I know exactly what you mean (especially having spent time this morning doing exactly that myself, in terms of tidying up the attached KMZ!) Anyway, cool - I may be able to pseudocode the logic for "how to fetch and apply the GIS files", in such a way that when you rebuild it in .NET/C# that it's a quick job. We'll see. I really ought to get more involved with .NET.... I've tended to shun it, because it looks like M$ hold all my code remotely by the short-and-curlies, and I'm not 100% sure I like that. But I've probably got the wrong end of the stick... it wouldn't be the first time
You ought to give C# a look definitely.......the ability to rapidly develop is unrivaled. And in fact, you aren't tied down to MS because C# is an open spec and currently has implementations for *nixes included Mac, Linux, etc via the Mono Project.
Now to comment on your points 1 by 1.
1.) Agree totally......like I said before, that's one of my biggest worries with a large dataset. I guess the only thing we can do is group the stuff as smartly as possible.
2.) Good to go.
3.) Good to go.
4.) Why in the heck does it change? Am I missing something here or is the radar moving? I haven't looked into it properly yet, but I don't understand why this would change periodically. Not a huge deal if we have to fetch it, but it violates my "keep it simple" policy lol.
Sorry it took me awhile to get back to you on this, but I had a lot of paying work to do today. In any case, it's very nicely done. A lot of data mind you, but a very nice start. We may want to think about how we group it in order to mitigate #1 above. Maybe a top level folder with all base reflectivities, and another folder with all relative velocities, and another with all 1hr precips etc. Just something to think about how it would be most useful for people using it...maybe the arrangement you currently have it in is best.....I just don't know until we talk about it and/or get some feedback.