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.
Rob, > Let's ignore the count[] array. I only wanted to know how NetCDF-4 > deals with the start[] array when trying to address data along a 64 > bit dimenson, and it sounds like the answer is "netcdf-4 complains and > says 'do that on a 64 bit platform', right? If I understand your question, the answer for the start array is the same as for the count array. As an array of size_t values, it is either 32 bits of 64 bits, depending on the platform it's compiled on. But the netCDF-3 format only allows 32-bit dimensions on either kind of platform, because that's all there is space for in the format. I wish the error message you got was always informative enough to give useful guidance, but in the case of specifying a start index that's too large, all the user gets is: NetCDF: Index exceeds dimension bound --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: FFY-177157 Department: Support netCDF Priority: Normal Status: Closed