Tyler,
to understand more of the Rainbow5 data format, you have to read the
"Instruction Manual Rainbow5 File Format". This usually comes with every
Selex (Gematronik) Software. So asking your data vendor to get access to
this manual might be a good idea.
In this manual the data file layout is extensively described.
Also your data vendor surely knows, what data (scantype, moments) is in
the provided files.
What wradlib is doing, it imports the rainbow data regardless of knowing
what is inside into a python dictionary. Then user has to know how to
handle the data inside the dictionary.
wradlib provides just an example on what to do and where to look.
I encourage you to play with the imported dictionaries, find out whats
inside etc. If you have problems with it, I suggest that you provide the
data file and a problem description so that we or other wradlib users
might help with the problem.
Cheers,
Kai
Am 12.02.2016 um 20:52 schrieb Tyler Russell:
> Kai,
>
> Thanks for helping earlier. Any comments on the below would get me a
> long ways. I am working with a vendor to get me some velocity data, but
> I feel like I should learn how to use the wradlib library on the dbz
> files before we move on.
>
> Also, you mentioned in the comments that the array the Rainbow file
> format is very versatile and can change. Does that mean that I have to
> examine each file and adapt code for each one? When the data set is
> delivered, I will have approximately 300,000 files!
>
> Thanks again!
>
> Tyler Russell
>
> On Friday, December 4, 2015 at 12:01:53 PM UTC-6, Tyler Russell wrote:
>
> Hi Kai,
>
> Thanks so much for your info. It was helpful! At this point in
> time, I'm trying to understand the workflow you used to come up with
> the solution as I'm trying to learn to "help myself" in the future.
> Let me see if I understand from your notes correctly. First, this
> is a script, so you were able to decide 'on the fly' what you were
> doing? My understanding since I'm new to Python is it runs like
> Matlab and does not need to compile fully at runtime. Your steps were:
>
> 1. Open the file from your Downloads folder into a dictionary
> (still unclear on the term dictionary)
> 2. Print the slicedata keys from the loaded dictionary
> 3. Print the rayinfo from the dictionary
> 4. Radar data has 2 azimuth arrays (2 different elevations? Indexed
> 0 and 1?) - Index the printed information to zeroth spot on array
> 5. Print the rawdata keys from the dictionary
> 6. Extract the reflectivity data and apply a formula to do some
> sort of normalization?
> 7. Extract the ranges from the dictionary (turned out they were
> broken - how did you know this?)
> 8. Print out the "shape" data to find the problem in the r.shape
> 9. Fix the r.shape by applying zeros to the array?
> 10. Make annotation data
> 11. Plot the annotation data
> > <mailto:
wradlib-user...@googlegroups.com>.
> <
https://groups.google.com/d/optout>.