#4565 closed defect (fixed)
GDALOpen failed on GRC grid
Reported by: | mladen | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | GDAL_Raster | Version: | 1.9.0 |
Severity: | major | Keywords: | gdalopen, grc, vertical mapper, northwood, gdal_translate |
Cc: | Kyle Shannon |
Description (last modified by )
There is an error when trying to open a GRC grid (Northwood VerticalMapper Classified Grid) with gdal_translate. The command and error is:
C:\>gdal_translate -of vrt "C:\temp\ClassficationGrid-UK-Technologies_1.grc" "C:\temp\ClassficationGrid-UK-Technologies_1.vrt" ERROR 4: `C:\temp\ClassficationGrid-UK-Technologies_1.grc' not recognised as a supported file format. GDALOpen failed - 4
This seems like it could be a problem with the file, but I can open it in MapInfo, as well as Global Mapper 13, so I think the file is OK. I put the .grc/.tab file pair in a zip (~5.3 Mb) at http://dl.dropbox.com/u/53500018/GdalOpenFailedGrid.zip if it helps.
I did some more research, and compared a working grid against the one that fails to open. Here is the working grid, which is almost exactly the same as the failing one (~50K difference in file sizes): http://dl.dropbox.com/u/53500018/WorkingGdalOpen.zip Comparing the two in a binary editor, I see differences in bytes 10 and 26 of the header... not sure exactly what that means without the GRC spec. However, as noted above, the failing grid does open correctly in other software (MapInfo and Global Mapper 13), so I suspect that there may be a bug in the GDAL GRC driver.
Attachments (1)
Change History (10)
comment:1 by , 12 years ago
Description: | modified (diff) |
---|
comment:2 by , 12 years ago
comment:3 by , 12 years ago
Component: | default → GDAL_Raster |
---|
comment:4 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:5 by , 12 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
The fix broke my build on win32 msvc10. I don't think MSVC supports struct::member syntax. I looked around and found this:
http://stackoverflow.com/questions/3864583/sizeof-a-struct-member
and tested on win32 (compilation, I don't have autotest on win32) and it compiled. gdalinfo works on the test dataset on both win and linux. Other option would just be #define the size in the header.
comment:6 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
comment:7 by , 12 years ago
Cc: | added |
---|
+kyle, let me know if the build problem persists after the last change.
comment:8 by , 12 years ago
Frank, Built in both trunk and 1.9, gdalinfo on the test data worked for the trunk. Thanks.
kss
comment:9 by , 12 years ago
I tested this today on my dataset, it worked for all the files I tried. Thanks, guys.
I confirmed the problem this morning. I don't know that I have a current email address for Perry Casson - I'll try to look at this tonight if Even doesn't get to it first.