-
Notifications
You must be signed in to change notification settings - Fork 179
HDF5 readHeapString error #1204
Comments
Yes, we will probably need to see the file. But first, can you find out what library |
Ok, I looked at the file you sent and it was created using netcdf-c library. |
I notice that the superblock version is 2, which is pretty uncommon. It is possible |
@DennisHeimbigner, This problem may be something in IDL itself. The user who provided the sample HDF5 file reported Wednesday that:
I take it that "Harris" = Harris Geospatial. |
That would explain the problem except as near as I can tell, there is no |
@DennisHeimbigner, Well, we'll see if she comes back with another problem HDF5 file after updating to the "fixed" version of IDL. |
Any word back? If not, I'll close out this particular issue. Thanks! |
I have heard nothing. Give a day or two to see if we get a response to your comment. |
@lesserwhirls, @DennisHeimbigner, Haven't heard a peep from the user who originally queried about this. |
I'm having trouble using NJ to open an HDF dataset, as the
HDheader
class is throwing an exception "Cant find Heap Object,heapId= nelems=0 heapAddress=0 index=0". Can someone explain what this might mean? The file in question was, I'm told, created using IDL. There's no trouble opening it up using HDFView.I've queried the person who provided the file to see it's okay to share with NJ developers, in case it's needed in order to figure out the issue.
The text was updated successfully, but these errors were encountered: