Hi Bjorn:
Many thanks for that further clarification of the workflow which turned up this anomalous result when:
* Aerial Imagery displayed in Global Mapper (aka "GM") is Exported via:
GM Menu > File > Export Raster / Image Format > BMP
...
or:
* Aerial Imagery displayed in Global Mapper is Exported via:
GM Menu > File > Export Raster / Image Format > GeoTIFF
...with accompanying *.PRJ and *.TFW files
One might wonder whether info written into a *.TFW world file might be at fault, depending on the options set in Global Mapper's export parameters:
GM Menu > Help > Online Help > 3.) TOOLBAR AND MENUBAR > File Menu > Export Raster/Imagery Format:
*
Export GeoTIFF command
...
or:
*
Export BMP command
Settings in either of the above export configurations would affect the meta data in the "world file" accompanying a BMP or GeoTIFF such that SBuilderX may not be able to Append / "import" / display / process it correctly.
As described, when you converted the GeoTIFF into a BMP with MS Paint you
lost the GeoTIFF tags / data within the GeoTIFF header file when written into the BMP file format.
When the BMP file was then 'geo-rectified' manually in SBuilderX using the top left (NW) corner and the bottom right (SE) corners using the known geographic coordinates from the GM metadata for the source aerial imagery in the GM Overlay Control Center, the correct alignment was achieved.
However, I am still somewhat intrigued as to what other factors may be at play in the occurrence of "
black and
red" texture anomalies at several locations around the aerial imagery.
I'm wondering if this may be more due to factors other than alignment,
ex: how / when to (...or when
not to) combine masks with a "NullValue" parameter.
I am not certain about this, but I would be concerned that retaining a 'empty' "
NullValue =" in your example *.INF file [Source1], [Source2], [Source3], and [Source4] entries as shown above at:
http://www.fsdeveloper.com/forum/showpost.php?p=626386&postcount=7
...
without also declaring a full and explicit numeric parameter sequence ...may invoke automatic substitution of an internal default value by FSX SDK Resample (
ex: 255,255,255)
http://www.fsdeveloper.com/forum/showthread.php?t=16443&highlight=auto
http://www.ptsim.com/forum/viewtopic.php?f=22&t=2147
[
EDITED]
...
Also see:
http://www.ptsim.com/forum/viewtopic.php?f=22&t=1060
http://www.ptsim.com/forum/viewtopic.php?f=22&t=1060&start=15
http://www.ptsim.com/forum/viewtopic.php?f=22&t=1060&start=30
[
END_EDIT]
Hope this leads to more insights on this curious scenario, and how to avoid such anomalies !
GaryGB