This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hey tom: Nope, 4.3 is a different beast. We could fix the tables, but 4.2 doesnt handle differing reference times correctly, as in the sample files you sent. The best I can do is get you a 4.3 alpha release asap. John > > John, > > The issue is referenced in the attached email. Any chance we can > drop-in/replace the grib decoder jar from the 4.3 branch? > > > > > Tom > > On Nov 4, 2011, at 11:55 AM, Unidata netCDF Java Support wrote: > > >> > >> John and Ethan, > >> > >> We are at a crux with the handling of GRIB data served via TDS for a high > >> profile project. It's our understanding that the issues we're having are > >> resolved in NetCDF-Java 4.3. What is the status as far as stability of > >> this work? Could we build a TDS 4.3 war or drop in NetCDF-Java 4.3 into a > >> TDS 4.2 install (is NetCDF-Java 4.3 API compatible with 4.2?). We're > >> wondering if standing up a TDS server using the GRIB fixes in NetCDF-Java > >> 4.3 is a viable option. > >> > >> Thanks much, > >> > >> Tom > >> > > > > Hi Tom: > > > > Ive resumed work on 4.3 now that 4.2 is (almost) out the door. Im working > > to stabilize the code asap, but the GRIB libraries have been completely > > rewritten. Can you remind me what issue you are seeing? Also a sample file > > if you havent already sent one. > > > > John > > > > > > > > Ticket Details > > =================== > > Ticket ID: BRU-363674 > > Department: Support netCDF Java > > Priority: Normal > > Status: Open > > > > > Ticket Details =================== Ticket ID: BRU-363674 Department: Support netCDF Java Priority: Normal Status: Open