NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
I'd hold off until we get this fixed. This seems like it would be a problem for any type of file that has multiple projections then? John Caron wrote:
Don Murray wrote:Robb-You'll need to add in the McIDASGridServiceProvider through the nj22Config.xml to be able to use it. It's not in NetcdfFile (I'm waiting for this issue to get fixed).Ive added it into NetcdfFile, but not checked in. do you want me to wait ?Here's what I use: <?xml version="1.0"?> <nj22Config> <ioServiceProvider class="ucar.nc2.iosp.gempak.GempakSurfaceIOSP"/> </nj22Config>for toolsUI (in my ~/.unidata directory). You'll need the fixes I checked in this morning in iosp.mcidas or else you won't be able to open GEMPAK files once you add the above.Unless you are changing GridIndex, this shouldn't be a problem. There are multiple projections in the file, but each is in it's own group. I think the netCDF file specs are okay, but that the CoordSysBuilder is picking up the projection type from the first one in the file. It looks like they all end up as Lambert Conformal. For a single projection in a file, it works fine. I don't haveany samples though. This has been a long standing problem (although it used to be worse), so I don't think it's anything you've changed.i know there are some problems in CoordSysBuilder
-- ************************************************************* Don Murray UCAR Unidata Program address@hidden P.O. Box 3000 (303) 497-8628 Boulder, CO 80307 http://www.unidata.ucar.edu/staff/donm *************************************************************