<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear Jeff,<div><br></div><div>I want to import it -- probably tiled and pyramid-ed -- into a PostGIS 2.0 raster, to be published with GeoServer. I can use wgrib2 to create a CSV file without trouble, so one option would be to use gdal_grid to re-create the raster in, say, a GeoTIFF from the CSV. That seems rather clunky, and I'm a little concerned about re-interpolating already interpolated data. But if the files won't go into the PostGIS raster import utility as is, they won't go in.<div><br></div><div>Roger, I will try hacking the four trailing bytes off the file and see whether the result is usable.</div><div><br></div><div>Thanks to you both!</div><div><br></div><div>rw</div><div><br></div><div><div><div>On Oct 23, 2012, at 3:35 PM, Jeff Lake wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> <div bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">That's a common print out from the GRIB driver<br> what are you wanting to do w/ the GRIB file ..<br> I might have some better solutions than using GDAL<br> <font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="white-space: pre;"><br></span></font> </div></div></blockquote></div><br></div></div><div>Roger wrote:</div><div><br></div><div></div><blockquote type="cite"><div>I had the same problem, but with two trailing bytes. [...]</div><div>I solved the problem by removing the bytes using:<br><br>dd if=gribFileNameWithTrailingBytes<br>of=gribFileNameWithoutTrailingBytes bs=1 skip=0 count=219886<br><br>Where count is the original grib file size minus the trailing bytes<br>(four, in your case).</div></blockquote></body></html>