"failed to read anything" about libgeotiff

[rouault]

This must have been fixed per 0dba341 , that has been delivered in libgeotiff 1.4.3
This was just an error message, not something affecting geotifcp output.

[rw2]

I suppose I should have added, if I then do a listgeo on the output file, the changes have not been applied.

[rouault]

Please provide a fully procedure (input data + exact commands issued) so that we can reproduce

[rw2]

I'm on Ubuntu 18.04.1 and geotiff-bin V1.4.2 so let me figure out how to get a more recent build since you thought there might have been a change...

[rouault]

I'm on Ubuntu 18.04.1 and geotiff-bin V1.4.2 so let me figure out how to get a more recent build since you thought there might have been a change...

The change should only remove the warning, and not affect the output. So you can provide what you observe with your current version

[rw2]

WI_RichlandCenter_503502_1905_125000_geo.tif.zip

unzip the attached tiff

listgeo WI_Richland\ Center_503502_1905_125000_geo.tif > t.geo

Modify t.geo. I've just been changing the last digit of one of the coordinates.

applygeo t.geo WI_Richland\ Center_503502_1905_125000_geo.tiff

listgeo WI_Richland\ Center_503502_1905_125000_geo.tif

Changes aren't evident in the file, though the timestamp does get updated.

[rouault]

Did you modify the coordinates in the "Corner Coordinates" section ? If so, that explains things. Everything that is after "End_Of_Geotiff" is informative only and ignored by geotifcp. So if you want to modify the coordinates you have to modify the ModelTiepointTag and/or ModelPixelScaleTag values

[rw2]

You nailed it. I just looked at the file and thought it was obvious. But now you've pointed me in the right direction. Go ahead and close this one. Now I have to figure out what looks to be a far more complicated standard than I expected!