Problem Solved.
Mr. G Watson provided the solution. Specifically, I had specified "w" in my
call to VSIFOpen. The carriage returns rightfully disappeared
after changing the mode to "wb".
What threw me off was the fact that the problem did not occur when using
Int16 output. Ugh, another beginner m
Thank you - interesting theory but none of the carriage returns occur after
a null, and I'm using gdalwarp to test the driver, so I see no reason for
character io to occur on the output.
Another useful bit of info: the problem does not occur if I specify -ot
Int16. I get random carriage returns on
0x0d is a carriage return. Someone is using character I/O somewhere. It’s
possible they are appearing after ‘nul’ characters 0x00 bytes or some such.
George Watson
Principal, Sierra Computing
wat...@sierracmp.com
> On Dec 14, 2015, at 10:52 AM, Jerry Tol wrote:
>
> Hello,
> I'm implementing
Hello,
I'm implementing a gdal raster driver for an internal file format and am
getting results I do not understand. The output is a binary raster of
32-bit floating point data, but the resulting file contains single bytes of
value 0x0D at seemingly random intervals throughout the data.
Within my
