<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I saw a <a
href="https://lists.osgeo.org/pipermail/gdal-dev/2016-July/044761.html">posting
from July</a> about work towards deciphering the Arc File
Geodatabase Raster format.<br>
<br>
Inspired, I did some work today and successfully extracted a raster
from a geodatabase.<br>
<br>
Using Even Rouault's <i>dump_gdbtable</i> as a starting point, I
decompressed the raster blobs using zlib, as suggested in the
posting.<br>
<br>
For my raster, this gave 128x128 big-endian 32-bit floating-point
values with a trailer of about 512 bytes.<br>
<br>
Assembling these 128x128 tiles using the col_nbr and row_nbr fields
resulted in the raster coming out.<br>
<br>
I've uploaded my fork, along with appropriate input data and a
command to run it all (see README.md) to <a
href="https://github.com/r-barnes/dump_gdbtable">https://github.com/r-barnes/dump_gdbtable</a>.<br>
<br>
What remains is to link metadata (block size, band_width,
band_height) to the raster so the output can be sized appropriately,
the data type deduced automatically, and projections saved. This is
probably just a matter of linking the appropriate rows from some of
the lower-numbered gdbtables with the files containing the raster
data. It might also be nice to determine whether zlib is always
being used, but I assume an error could be thrown if an unexpected
compression format is encountered.<br>
<br>
I'm interested in seeing GDAL include the ability to translate Arc
File Geodatabase Rasters into other (less proprietary) formats.<br>
What is a good way to move forward with that?<br>
<br>
Best regards,<br>
Richard Barnes<br>
</body>
</html>