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.
Hi Ajit, > My problem is that most of our access into the NetCDF library in > ArcGIS is via the C++ libraries. Because of the compile errors I'm > getting with the new C++ code, I tried using the old (3.x) files > viz., netcdf.cpp, netcdfcpp.h etc, but that produces several runtime > problems with the file ids etc. and the data file access is > incorrect. > > Is there any chance of error-free C++ files for 4.x being available > in the immediate future? There is a good chance we will have up-to-date C++ sources soon for 4.x, as an external developer is currently working on this. He has not been constrained by backward compatibility with the 3.x C++ API. He started with the current experimental code, but says his implementation has an improved API. The latest news we have from him is that he hopes "to have it completed very soon". To give you an idea of what's coming, he says: > I have spent quite a bit of time playing around with ideas. In the end I > have elected not to use the blitz array library and stick with what the > STL can offer. I have also moved away from the original C++ API quite a > bit. Hopefully the result is simpler and more transparent. One of my > rationals is to store as little data in each object as possible and rely > on the C API calls to deliver everything else. This minimizes the > possibility that objects may not be holding the most current information . --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: CYF-313110 Department: Support netCDF Priority: High Status: Closed