-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
.TIF files
- Thread starter Roel
- Start date
Hi Roel:
It appears that the Geo-referencing for your USGS aerial imagery source file(s)- as stated in the INF submitted to FS SDK Resample- ...is wrong.
This can change Geographic coordinates for placement, the aspect ratio, and the image size displayed in FS at run time, because FS SDK Resample will blindly 'accept' the aerial imagery GeoTIFF source file when submitted if it is formatted in the correct SDK-specified GIS Projection and Datum, even when Geo-referencing info within a GeoTIFF and/or the INF file that references it ...is "wrong".
Would you please post for download somewhere, (1) of the un-edited original aerial imagery GeoTIFF files you acquired from USGS as discussed above ?
BTW: I am going to post a tile of the 30cm aerial imagery I acquired from the USGS so that sometime soon, we can compare the "visual quality" (and for the sake of discussion, initially, not so much the stated "resolution") of the aerial imagery data sets available for you to use for your project area.
After I have one of my tiles cited above uploaded to ex: MediaFire, I'll post a download link here.
GaryGB
It appears that the Geo-referencing for your USGS aerial imagery source file(s)- as stated in the INF submitted to FS SDK Resample- ...is wrong.
This can change Geographic coordinates for placement, the aspect ratio, and the image size displayed in FS at run time, because FS SDK Resample will blindly 'accept' the aerial imagery GeoTIFF source file when submitted if it is formatted in the correct SDK-specified GIS Projection and Datum, even when Geo-referencing info within a GeoTIFF and/or the INF file that references it ...is "wrong".
Would you please post for download somewhere, (1) of the un-edited original aerial imagery GeoTIFF files you acquired from USGS as discussed above ?
BTW: I am going to post a tile of the 30cm aerial imagery I acquired from the USGS so that sometime soon, we can compare the "visual quality" (and for the sake of discussion, initially, not so much the stated "resolution") of the aerial imagery data sets available for you to use for your project area.
After I have one of my tiles cited above uploaded to ex: MediaFire, I'll post a download link here.
GaryGB
Last edited:
- Messages
- 309
- Country
I have the original files that I downloaded here:
https://mega.nz/#!iEBXQI7B!tJafathaJAODC8XDv0DPiDn4WmY9ntN1iFU6tF6lt3c
Nothing has been done to them, not even unzipped.
Good luck!
https://mega.nz/#!iEBXQI7B!tJafathaJAODC8XDv0DPiDn4WmY9ntN1iFU6tF6lt3c
Nothing has been done to them, not even unzipped.
Good luck!
Hi Roel:
Thanks for posting the example file.
I will take a look at this over the weekend, and shall try to see what happens to the Geo-rectification when imported into SBuilderX compared to the original Metadata seen in Global Mapper.
I'll also try running Ollyau's GeoTIFF2INF utility on it to compare the Geo-rectification it writes into a INF file with that written to an INF by SBuilderX after a BGL is compiled via FS SDK Resample.
GaryGB
Thanks for posting the example file.
I will take a look at this over the weekend, and shall try to see what happens to the Geo-rectification when imported into SBuilderX compared to the original Metadata seen in Global Mapper.
I'll also try running Ollyau's GeoTIFF2INF utility on it to compare the Geo-rectification it writes into a INF file with that written to an INF by SBuilderX after a BGL is compiled via FS SDK Resample.
GaryGB
Hi Roel:
Would you also please post for download somewhere, the 'original' aerial imagery GeoTIFF file for the example file you posted and linked to above:
http://www.fsdeveloper.com/forum/threads/tif-files.436404/page-2#post-736063
...which has been re-projected with "OSGeo4W Shell" using your "GDALWARP" command string discussed previously in this thread ?
Also, since the screenshot you posted previously in this thread does not show the entire CMD mode console output text, would you please post in your reply, the entire text for the "GDALWARP" command string you utilized to re-project your aerial imagery in "OSGeo4W Shell" ?
In OSGeo4W, select and copy the entire "GDALWARP" command string you utilized to re-project your aerial imagery for the example screenshots you posted above, then that string can be seen more legibly via the FSDeveloper Forum message composing area at the bottom using the "Insert" icon's sub-menu choice for "Code".
BTW: When I indicated that the file should be 'original' and "un-edited", I meant that it should not have been opened / edited / saved in a graphics application.
What I should properly have indicated at the same time, was that the 'original' and "un-edited" aerial imagery GeoTIFF files you acquired from USGS should be the ones re-projected by "OSGeo4W Shell" using the entire "GDALWARP" command string ...prior to being submitted to SBuilderX; sorry for not having been more clear in my statement.
I shall await your reply with an additional post of the "OSGeo4W Shell" re-projected version of the (same) example aerial imagery GeoTIFF file you acquired from USGS (...and had previously posted a link to in its "non-re-projected" form).
GaryGB
Would you also please post for download somewhere, the 'original' aerial imagery GeoTIFF file for the example file you posted and linked to above:
http://www.fsdeveloper.com/forum/threads/tif-files.436404/page-2#post-736063
...which has been re-projected with "OSGeo4W Shell" using your "GDALWARP" command string discussed previously in this thread ?
Also, since the screenshot you posted previously in this thread does not show the entire CMD mode console output text, would you please post in your reply, the entire text for the "GDALWARP" command string you utilized to re-project your aerial imagery in "OSGeo4W Shell" ?
In OSGeo4W, select and copy the entire "GDALWARP" command string you utilized to re-project your aerial imagery for the example screenshots you posted above, then that string can be seen more legibly via the FSDeveloper Forum message composing area at the bottom using the "Insert" icon's sub-menu choice for "Code".
Code:
This is an example "code" text display; notice that it can be scrolled horizontally to show entire lines without line wrappingBTW: When I indicated that the file should be 'original' and "un-edited", I meant that it should not have been opened / edited / saved in a graphics application.
What I should properly have indicated at the same time, was that the 'original' and "un-edited" aerial imagery GeoTIFF files you acquired from USGS should be the ones re-projected by "OSGeo4W Shell" using the entire "GDALWARP" command string ...prior to being submitted to SBuilderX; sorry for not having been more clear in my statement.
I shall await your reply with an additional post of the "OSGeo4W Shell" re-projected version of the (same) example aerial imagery GeoTIFF file you acquired from USGS (...and had previously posted a link to in its "non-re-projected" form).
GaryGB
Last edited:
Hi Roel:
Here is a "before-and-after" example of what the Metadata looks like in the Global Mapper GIS application, when the example aerial imagery GeoTIFF file you acquired from USGS linked in your latter post above, is re-projected (using Global Mapper ) ...to Geographic / WGS / Arc Degrees, and only the 3-Band RGB 'visual' data is retained for making your FS SDK Resample custom photo-real aerial imagery BGL:
19tcf585795_tif_UTM_Zone_19_NAD83_meters (Original: 4-Band RGB_I)
19tcf585795_Geographic_WGS84_Arc_Degrees (Re-projected; converted to 3-Band RGB)
Hope this helps with sorting out the command strings to use with OSGEO4W.
GaryGB
Here is a "before-and-after" example of what the Metadata looks like in the Global Mapper GIS application, when the example aerial imagery GeoTIFF file you acquired from USGS linked in your latter post above, is re-projected (using Global Mapper ) ...to Geographic / WGS / Arc Degrees, and only the 3-Band RGB 'visual' data is retained for making your FS SDK Resample custom photo-real aerial imagery BGL:
19tcf585795_tif_UTM_Zone_19_NAD83_meters (Original: 4-Band RGB_I)
Code:
FILENAME=[path]\3335805_19TCF585795\MA\2014\201404_massachusetts_state_ma_0x3000m_utm19_cnir\vol002\19tcf585795.tif
DESCRIPTION=19tcf585795.tif
UPPER LEFT X=358500.000
UPPER LEFT Y=4581000.000
LOWER RIGHT X=360000.000
LOWER RIGHT Y=4579500.000
WEST LONGITUDE=70.69190614° W
NORTH LATITUDE=41.36834497° N
EAST LONGITUDE=70.67363196° W
SOUTH LATITUDE=41.35457711° N
UL CORNER LONGITUDE=70.69190614° W
UL CORNER LATITUDE=41.36808272° N
UR CORNER LONGITUDE=70.67397812° W
UR CORNER LATITUDE=41.36834497° N
LR CORNER LONGITUDE=70.67363196° W
LR CORNER LATITUDE=41.35483924° N
LL CORNER LONGITUDE=70.69155628° W
LL CORNER LATITUDE=41.35457711° N
PROJ_DESC=UTM Zone 19 / NAD83 / meters
PROJ_DATUM=NAD83
PROJ_UNITS=meters
EPSG_CODE=EPSG:26919
COVERED AREA=2.25 sq km
LOAD TIME=9.42 s
NUM COLUMNS=5000
NUM ROWS=5000
NUM BANDS=4
COLOR BANDS=0,1,2
PIXEL WIDTH=0.3 meters
PIXEL HEIGHT=0.3 meters
BIT DEPTH=32
SAMPLE TYPE=Unsigned 8-bit Integer
DPI=72
TIME=2014:07:26 16:31:00
PCS_CITATION=UTM Zone 19/NAD 83 (2011)/Meters
PHOTOMETRIC=RGB Full-Color
BIT_DEPTH=32
SAMPLE_FORMAT=Unknown Format (0)
ROWS_PER_STRIP=1
COMPRESSION=None
DPI=72
PIXEL_SCALE=( 0.3, 0.3, 1 )
TIEPOINTS=( 0.00, 0.00, 0.00 ) --> ( 358500.000, 4581000.000, 0.000 )
MODEL_TYPE=Projection Coordinate System
RASTER_TYPE=Pixel is Area19tcf585795_Geographic_WGS84_Arc_Degrees (Re-projected; converted to 3-Band RGB)
Code:
FILENAME=[path]\19tcf585795_Geographic_WGS84_Arc_Degrees.tif
DESCRIPTION=19tcf585795_Geographic_WGS84_Arc_Degrees.tif
UPPER LEFT X=-70.6919061395
UPPER LEFT Y=41.3683449724
LOWER RIGHT X=-70.6736322309
LOWER RIGHT Y=41.3545774032
WEST LONGITUDE=70.69190614° W
NORTH LATITUDE=41.36834497° N
EAST LONGITUDE=70.67363223° W
SOUTH LATITUDE=41.35457740° N
UL CORNER LONGITUDE=70.69190614° W
UL CORNER LATITUDE=41.36834497° N
UR CORNER LONGITUDE=70.67363223° W
UR CORNER LATITUDE=41.36834497° N
LR CORNER LONGITUDE=70.67363223° W
LR CORNER LATITUDE=41.35457740° N
LL CORNER LONGITUDE=70.69190614° W
LL CORNER LATITUDE=41.35457740° N
PROJ_DESC=Geographic (Latitude/Longitude) / WGS84 / arc degrees
PROJ_DATUM=WGS84
PROJ_UNITS=arc degrees
EPSG_CODE=EPSG:4326
COVERED AREA=2.336 sq km
NUM COLUMNS=6764
NUM ROWS=5096
NUM BANDS=3
COLOR BANDS=0,1,2
PIXEL WIDTH=0.0000027 arc degrees
PIXEL HEIGHT=0.0000027 arc degrees
BIT DEPTH=24
SAMPLE TYPE=Unsigned 8-bit Integer
GT_CITATION=GCS_WGS_1984
PHOTOMETRIC=RGB Full-Color
BIT_DEPTH=24
SAMPLE_FORMAT=Unknown Format (0)
ROWS_PER_STRIP=1
COMPRESSION=None
ORIENTATION=row 0 top, col 0 lhs
PIXEL_SCALE=( 0.00000270164232, 0.00000270164232, 1 )
TIEPOINTS=( 0.00, 0.00, 0.00 ) --> ( -70.6919061395, 41.3683449724, 0.0000000000 )
MODEL_TYPE=Geographic lat-long system
RASTER_TYPE=Pixel is AreaHope this helps with sorting out the command strings to use with OSGEO4W.
GaryGB
Last edited:
- Messages
- 6,521
- Country
This works for me using the OSGeo4W Shell:
The gdal_translate gets rid of the alpha channel. The gdalwarp reprojects to geographic and sets the no data pixels to white.
Dick
Code:
gdal_translate -b 1 -b 2 -b 3 19tcf585795.tif No_Alpha.tif
gdalwarp -t_srs EPSG:4326 -dstnodata 255,255,255 No_Alpha.tif Final.tifThe gdal_translate gets rid of the alpha channel. The gdalwarp reprojects to geographic and sets the no data pixels to white.
Dick
- Messages
- 309
- Country
Sorry for the late response, I was away for a couple of days.
I have the link to the, no alpha file I've used in my example above, for you Gary:
https://mega.nz/#!DMJyRQDa!_I5XDbTpMBoREKxqf1LH-qSjQ_4zpYBrNs9uZMiixQY
I hope you can do something with it
I have the link to the, no alpha file I've used in my example above, for you Gary:
https://mega.nz/#!DMJyRQDa!_I5XDbTpMBoREKxqf1LH-qSjQ_4zpYBrNs9uZMiixQY
I hope you can do something with it
Hi Roel:
Here is what the Metadata looks like in the Global Mapper GIS application, when the example aerial imagery GeoTIFF file you acquired from USGS linked in your latter post above, is "Opened" (...without being re-projected) using Global Mapper.
http://www.fsdeveloper.com/forum/threads/tif-files.436404/page-2#post-736806
FYI: This file is in the format which IIUC, you derived from use of the command line parameters values posted by Dick above:
http://www.fsdeveloper.com/forum/threads/tif-files.436404/page-2#post-736347
Note that you have successfully retained the "projection" of: UTM Zone 19 / NAD83 / meters, and only the 3-Band RGB 'visual' data was retained ...for making your FS SDK Resample custom photo-real aerial imagery BGL:
FILENAME=[path]\test_no_alpha.tif
DESCRIPTION=test_no_alpha.tif
UPPER LEFT X=358500.000
UPPER LEFT Y=4579500.000
LOWER RIGHT X=360000.000
LOWER RIGHT Y=4578000.000
WEST LONGITUDE=70° 41' 29.6026" W
NORTH LATITUDE=41° 21' 17.4213" N
EAST LONGITUDE=70° 40' 23.8298" W
SOUTH LATITUDE=41° 20' 27.8573" N
UL CORNER LONGITUDE=70° 41' 29.6026" W
UL CORNER LATITUDE=41° 21' 16.4776" N
UR CORNER LONGITUDE=70° 40' 25.0751" W
UR CORNER LATITUDE=41° 21' 17.4213" N
LR CORNER LONGITUDE=70° 40' 23.8298" W
LR CORNER LATITUDE=41° 20' 28.8005" N
LL CORNER LONGITUDE=70° 41' 28.3440" W
LL CORNER LATITUDE=41° 20' 27.8573" N
PROJ_DESC=UTM Zone 19 / NAD83 / meters
PROJ_DATUM=NAD83
PROJ_UNITS=meters
EPSG_CODE=EPSG:26919
COVERED AREA=2.25 sq km
LOAD TIME=0.30 s
NUM COLUMNS=5000
NUM ROWS=5000
NUM BANDS=3
COLOR BANDS=0,1,2
PIXEL WIDTH=0.3 meters
PIXEL HEIGHT=0.3 meters
BIT DEPTH=24
SAMPLE TYPE=Unsigned 8-bit Integer
DPI=72
TIME=2014:07:26 16:30:50
GT_CITATION=NAD83 / UTM zone 19N
GEOG_CITATION=NAD83
PHOTOMETRIC=RGB Full-Color
BIT_DEPTH=24
SAMPLE_FORMAT=Unsigned Integer
ROWS_PER_STRIP=1
COMPRESSION=None
DPI=72
PIXEL_SCALE=( 0.3, 0.3, 1 )
TIEPOINTS=( 0.00, 0.00, 0.00 ) --> ( 358500.000, 4579500.000, 0.000 )
MODEL_TYPE=Projection Coordinate System
RASTER_TYPE=Pixel is Area
When this aerial imagery tile is viewed in SBuilderX via:
SBuilder Menu > File > Add Map > From Disk
...the SBuilderX import process for GeoTIFFs apparently initially reads / retains the internal calibration of the GeoTIFF if it is already in a format compatible with display as a 'web tile server' type of projection.
Thus, it seems SBuilderX 'may' only automatically re-project the aerial imagery when a final 'selection' of displayed aerial imagery tiles in the SBuilderX work-space is submitted for compilation to FS SDK Resample as a *.BMP file with accompanying Geo-referencing info *.TXT with a matched file name.
My apologies for any confusion arising from my prior description of SBuilderX's work-flow in my post above (now edited), as this is a rather poorly documented feature in the SBuilderX help CHM help file.
[EDITED]
IIUC, the SBuilderX 'Add Map From Disk' process for GeoTIFFs automatically re-projects the aerial imagery from the particular cited UTM Zone 19 / NAD83 / meters projection listed in the above metadata from your downloaded source files:
Projection: UTM Zone: 18 &19
Datum: Nad83 Planar: Meter
Image Info: GeoTiff Radiometry: 3 band RBG, 24 bit
Pixel Size: 0.3 Meter
...to the Geographic / WGS / Arc Degrees type projection when a final group of displayed aerial imagery tiles in the SBuilderX work-space is 'selected', and that composited matrix of aerial imagery tiles added as a 'Map' from disk, is submitted by SBuilderX along with a INF file for compilation into a photo-real scenery BGL by FS SDK Resample via:
SBuilderX Menu > File > BGL Compile...
[END_EDIT]
PS: I am still researching the mis-match of aerial imagery display sizes (and presumably projections) for a Geo-TIFF added to the SBuilderX work-space via:
SBuilderX Menu > File > Add Map > From Disk
...when also viewing downloaded aerial imagery tiles added to the SBuilderX work-space display via:
SBuilderX Menu > View > Show Background
Hope this helps explain the process a bit more clearly for you.
GaryGB
Here is what the Metadata looks like in the Global Mapper GIS application, when the example aerial imagery GeoTIFF file you acquired from USGS linked in your latter post above, is "Opened" (...without being re-projected) using Global Mapper.
http://www.fsdeveloper.com/forum/threads/tif-files.436404/page-2#post-736806
FYI: This file is in the format which IIUC, you derived from use of the command line parameters values posted by Dick above:
http://www.fsdeveloper.com/forum/threads/tif-files.436404/page-2#post-736347
Note that you have successfully retained the "projection" of: UTM Zone 19 / NAD83 / meters, and only the 3-Band RGB 'visual' data was retained ...for making your FS SDK Resample custom photo-real aerial imagery BGL:
FILENAME=[path]\test_no_alpha.tif
DESCRIPTION=test_no_alpha.tif
UPPER LEFT X=358500.000
UPPER LEFT Y=4579500.000
LOWER RIGHT X=360000.000
LOWER RIGHT Y=4578000.000
WEST LONGITUDE=70° 41' 29.6026" W
NORTH LATITUDE=41° 21' 17.4213" N
EAST LONGITUDE=70° 40' 23.8298" W
SOUTH LATITUDE=41° 20' 27.8573" N
UL CORNER LONGITUDE=70° 41' 29.6026" W
UL CORNER LATITUDE=41° 21' 16.4776" N
UR CORNER LONGITUDE=70° 40' 25.0751" W
UR CORNER LATITUDE=41° 21' 17.4213" N
LR CORNER LONGITUDE=70° 40' 23.8298" W
LR CORNER LATITUDE=41° 20' 28.8005" N
LL CORNER LONGITUDE=70° 41' 28.3440" W
LL CORNER LATITUDE=41° 20' 27.8573" N
PROJ_DESC=UTM Zone 19 / NAD83 / meters
PROJ_DATUM=NAD83
PROJ_UNITS=meters
EPSG_CODE=EPSG:26919
COVERED AREA=2.25 sq km
LOAD TIME=0.30 s
NUM COLUMNS=5000
NUM ROWS=5000
NUM BANDS=3
COLOR BANDS=0,1,2
PIXEL WIDTH=0.3 meters
PIXEL HEIGHT=0.3 meters
BIT DEPTH=24
SAMPLE TYPE=Unsigned 8-bit Integer
DPI=72
TIME=2014:07:26 16:30:50
GT_CITATION=NAD83 / UTM zone 19N
GEOG_CITATION=NAD83
PHOTOMETRIC=RGB Full-Color
BIT_DEPTH=24
SAMPLE_FORMAT=Unsigned Integer
ROWS_PER_STRIP=1
COMPRESSION=None
DPI=72
PIXEL_SCALE=( 0.3, 0.3, 1 )
TIEPOINTS=( 0.00, 0.00, 0.00 ) --> ( 358500.000, 4579500.000, 0.000 )
MODEL_TYPE=Projection Coordinate System
RASTER_TYPE=Pixel is Area
When this aerial imagery tile is viewed in SBuilderX via:
SBuilder Menu > File > Add Map > From Disk
...the SBuilderX import process for GeoTIFFs apparently initially reads / retains the internal calibration of the GeoTIFF if it is already in a format compatible with display as a 'web tile server' type of projection.
Thus, it seems SBuilderX 'may' only automatically re-project the aerial imagery when a final 'selection' of displayed aerial imagery tiles in the SBuilderX work-space is submitted for compilation to FS SDK Resample as a *.BMP file with accompanying Geo-referencing info *.TXT with a matched file name.
My apologies for any confusion arising from my prior description of SBuilderX's work-flow in my post above (now edited), as this is a rather poorly documented feature in the SBuilderX help CHM help file.
[EDITED]
IIUC, the SBuilderX 'Add Map From Disk' process for GeoTIFFs automatically re-projects the aerial imagery from the particular cited UTM Zone 19 / NAD83 / meters projection listed in the above metadata from your downloaded source files:
Projection: UTM Zone: 18 &19
Datum: Nad83 Planar: Meter
Image Info: GeoTiff Radiometry: 3 band RBG, 24 bit
Pixel Size: 0.3 Meter
...to the Geographic / WGS / Arc Degrees type projection when a final group of displayed aerial imagery tiles in the SBuilderX work-space is 'selected', and that composited matrix of aerial imagery tiles added as a 'Map' from disk, is submitted by SBuilderX along with a INF file for compilation into a photo-real scenery BGL by FS SDK Resample via:
SBuilderX Menu > File > BGL Compile...
[END_EDIT]
PS: I am still researching the mis-match of aerial imagery display sizes (and presumably projections) for a Geo-TIFF added to the SBuilderX work-space via:
SBuilderX Menu > File > Add Map > From Disk
...when also viewing downloaded aerial imagery tiles added to the SBuilderX work-space display via:
SBuilderX Menu > View > Show Background
Hope this helps explain the process a bit more clearly for you.
GaryGB
Last edited:
"Bumped" for edits to my post immediately above. 
Roel:
You may wish to review this online tutorial for use of SBuilderX to make photo-real scenery with the GeoTIFFS you now know how to convert from the USGS source files.
http://www.flightsim.com/vbfs/showthread.php?250762-How-to-create-photoreal-scenery-for-FSX
BTW: I would not attempt to combine mis-matched aerial imagery display sizes (and presumably projections) for your Geo-TIFFs added to the SBuilderX work-space via:
SBuilderX Menu > File > Add Map > From Disk
...when also viewing downloaded aerial imagery tiles added to the SBuilderX work-space display via:
SBuilderX Menu > View > Show Background
I would suggest that instead, you make the work performed with those 2 sets of aerial imagery each a separate project in SBuilderX.
GaryGB
Roel:
You may wish to review this online tutorial for use of SBuilderX to make photo-real scenery with the GeoTIFFS you now know how to convert from the USGS source files.
http://www.flightsim.com/vbfs/showthread.php?250762-How-to-create-photoreal-scenery-for-FSX
BTW: I would not attempt to combine mis-matched aerial imagery display sizes (and presumably projections) for your Geo-TIFFs added to the SBuilderX work-space via:
SBuilderX Menu > File > Add Map > From Disk
...when also viewing downloaded aerial imagery tiles added to the SBuilderX work-space display via:
SBuilderX Menu > View > Show Background
I would suggest that instead, you make the work performed with those 2 sets of aerial imagery each a separate project in SBuilderX.
GaryGB
Last edited: