Interesting results, George !
IMHO this raises questions as to what is different about the
TIF file format output by GIMP in LZW compressed and uncompressed mode versus the
TIF file format output by another graphics application such as Photoshop / Corel PhotoPaint or PaintShop Pro etc..
BTW: Could everyone tell us
which version numbers of GIMP were used in this thread please ?
Alternatively, perhaps FS SDK Resample works different if INF file parameters "
NullValue" or "
Variation" are used ?
http://www.fsdeveloper.com/forum/threads/photoreal-blend-mask-issue.426688/
http://www.fsdeveloper.com/forum/th...ring-and-summer-seasons-are-solid-red.123533/
NOTE: The OP has a "
Variation" but no "
NullValue" INF file parameter:
http://www.fsdeveloper.com/forum/threads/problem-to-create-blend-mask.433852/
Regarding the "
Variation" parameter, I assume FSX / P3D 1.x SDK Resample retro-compatibly honors substitution by the
legacy FS2004 SDK Resample syntax of "
BuildSeasons" ...in your own example INF posted above ?
Also, I assume FSX / P3D 1.x SDK Resample retro-compatibly honors substitution of
ex:
nCols
nRows
ulxMap
ulyMap
xDim
yDim
...in "
current" FSX SDK Resample INF parameter syntax, as shown at:
https://msdn.microsoft.com/en-us/library/cc707102.aspx#TheResampleTool:
...by use of legacy syntax "
Lat", "
Lon" and "
Cell" in your own example INF posted above,
ex:
http://www.fsdeveloper.com/forum/threads/problem-to-create-blend-mask.433852/#post-708550
NumOfCellsPerLine = 15889 ;Pixel is not used in FSX
NumOfLines = 8447 ;Pixel is not used in FSX
Lon = 8.28059434890747 ;for top left and bottom right is: 8.33741784095764
Lat = 51.9372010231018 ;for top left and bottom right is: 51.914544403553
CellXdimensionDeg = 3.57627868652344E-06
CellYdimensionDeg = 2.68220901489258E-06
FYI: A previous discussion of TIF LZW compression versus performance with FS SDK Resample compilation:
http://www.fsdeveloper.com/forum/threads/resample-exe-performance-question.433597/
PS: An interesting side note from reading the FS2004 SDK document "
Custom Terrain Textures.Doc" which AFAIK was not included in the FSX SDK docs (perhaps ACES assumed GeoTIFFs would be used more often instead of BMPs ?
):
"
Correcting Images that Contain Black Borders
Some of the images may contain a black border. This happens when the image source doesn’t fully cover a terrain cell. Each terrain cell falls on a multiple of 360/32768 degrees latitude, which is 0.010986328125 decimal degrees and 480/32768 degrees longitude, which is 0.0146484375 decimal degrees. To prevent this from happening, use the [Destination] directives NorthLat, SouthLat, EastLon, and WestLon to define the exact area to fall on a cell boundary within the source image."
http://www.fsdeveloper.com/forum/resources/terrain-sdk.40/
[
EDITED]
NOTE: A discussion of options and linked threads related to dealing with this sub-topic of determining and specifying required and/or desired quad extents in a INF file for one's source imagery submitted to FS SDK Resample is here:
http://www.fsdeveloper.com/forum/threads/photoscenery-how-much-overlap.425814/
[
END_EDIT]
GaryGB