Many people here write out their data in grads binary files. I'd like to view them in the IDV, so am working on an IOSP for this. I plan on using the GridServiceProvider framework that I used for the GEMPAK and McIDAS grid readers. At this point, I'm only going to handle lat/lon grids.
One question I have is about the RandomAccessFile that gets passed to the IOSP. For grads, there is a data description file (sometimes called the ctl file) which describes the structure of the binary data file (see: http://www.iges.org/grads/gadoc/descriptorfile.html). I've attached a sample CTL file. My idea is that the user would open the ctl file which would set up the grid structure for the GridServiceProvider, but when the data is read, it reads from the binary file described in the ctl file. So, the initial RandomAccessFile would be the CTL, but I'm wondering about accessing the binary file. Do I just hold a handle internally to a RandomAccessFile and read from that? Are there other IOSPs that handle metadata in one file and the data in another that I could use as a guide?
I also have to figure out where this IOSP lives. Right now I'm just coding in ucar.nc2.iosp.grads (won't check it in until it works), but since the code is not being developed at UCAR, I'm not sure I want to use your licensing which gives all copyright/licensing to UCAR.
Thanks for an help you can give.
Do you want to meet for lunch or a walk next week?
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.