USGS OrthoImage Tif files

[seippg]

I got some good orthoimagery from USGS Earth Explorer and tried loading it into SBuilderX....12 images, 20 Meg each. I tried just uploading 2 of them, without calibration at first, but the images were too tall and just overlayed one another which makes me think SBuilderX couldn't read the image position from the image. The second time I tried calibrating each image....that seemed to give them the right dimensions but they weren't quite lined up...perhaps 200 feet off, or so, which makes me think that SBuilderX and the USGS are using a different projection...or, maybe, I'm just doing something wrong. I'm trying to come up with a strategy to get them usable. I've included the metadata for one below. Any help would be appreciated.

Gregg

=======
Identification_Information:
Citation:
Citation_Information:
Originator: U.S. Geological Survey (USGS)
Publication_Date: 20090508
Title: High Resolution Orthoimagery:1274809_MYR14C104
Geospatial_Data_Presentation_Form: Remote Sensing Image
Publication_Information:
Publication_Place: Sioux Falls, South Dakota
Publisher: USGS Earth Resources Observations and Science Center (EROS)
Online_Linkage: https://lta.cr.usgs.gov/high_res_ortho
Description:
Abstract: High resolution orthorectified images combine the image characteristics of an aerial photograph with the geometric qualities of a map. An orthoimage is a uniform-scale image where corrections have been made for feature displacement such as building tilt and for scale variations caused by terrain relief, sensor geometry, and camera tilt. A mathematical equation based on ground control points, sensor calibration information, and a digital elevation model is applied to each pixel to rectify the image to obtain the geometric qualities of a map.

A digital orthoimage may be created from several photographs mosaicked to form the final image. The source imagery may be black-and-white, natural color, color infrared, or color near infrared (4-band) with a pixel resolution of 1-meter or finer. With orthoimagery, the resolution refers to the distance on the ground represented by each pixel.

Time_Period_of_Content:
Time_Period_Information:

Range_of_Dates/Times:
Beginning_Date: 01-OCT-07
Ending_Date: 01-OCT-07
Currentness_Reference: Ground Condition
Status:
Progress: In Work
Maintenance_and_Update_Frequency: As Needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -77.935541879102402
East_Bounding_Coordinate: -77.918778850312336
North_Bounding_Coordinate: 34.276974902504342
South_Bounding_Coordinate: 34.263058293015824
Data_Set_G-Polygon:
Data_Set_G-Polygon_Outer_G-Ring:

G-Ring_Latitude: 34.276974902504342
G-Ring_Longitude: -77.935051321110237

G-Ring_Latitude: 34.276566463107258
G-Ring_Longitude: -77.918778850312336

G-Ring_Latitude: 34.263058293015824
G-Ring_Longitude: -77.91927200276082

G-Ring_Latitude: 34.263466526730483
G-Ring_Longitude: -77.935541879102402
Keywords:
Theme:

Theme_Keyword_Thesaurus: None
Theme_Keyword: Aerial Photography
Theme_Keyword: Black-and-White
Theme_Keyword: Natural Color
Theme_Keyword: High Resolution Orthoimagery
Theme_Keyword: Color Near-Infrared
Theme_Keyword: Photographs
Theme_Keyword: Orthorectified
Theme_Keyword: Color Infrared
Theme_Keyword: Georeferenced
Place:

Place_Keyword_Thesaurus: U.S. Department of Commerce, 1995, Countries, dependencies, areas of special sovereignty, and their principal administrative divisions, Federal Information Processing Standard 10-4, Washington, D.C., National Institute of Standards and Technology
Place_Keyword: Puerto Rico
Place_Keyword: U.S.
Place_Keyword: Virgin Islands
Place_Keyword: Mexico
Place_Keyword: Canada
Access_Constraints: Any downloading and use of these data signifies a user's agreement to comprehension and compliance of the USGS Standard Disclaimer. Insure all portions of metadata are read and clearly understood before using these data in order to protect both user and USGS interests.
Use_Constraints: There is no guarantee of warranty concerning the accuracy of these data. Users should be aware that temporal changes may have occurred since the data was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of their limitations. Acknowledgement of the originating agencies would be appreciated in products derived from these data. Any user who modifies the data set is obligated to describe the types of modifications they perform. User specifically agrees not to misrepresent the data set, nor to imply that changes made were approved or endorsed by the U.S. Geological Survey. Please refer to http://www.usgs.gov/privacy.html for the USGS disclaimer.
Point_of_Contact:
Contact_Information:

Contact_Person_Primary:
Contact_Person: custserv@usgs.gov
Contact_Organization: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center
Contact_Organization_Primary:
Contact_Organization: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center
Contact_Person: custserv@usgs.gov
Contact_Position: Customer Service Representative
Contact_Address:
Address_Type: Mailing and Physical Address
Address: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center 47914 252nd Street
City: Sioux Falls
State_or_Province: SD
Postal_Code: 57198-0001
Country: USA
Contact_Electronic_Mail_Address: custserv@usgs.gov
Hours_of_Service: 0800 - 1600 CT, M-F, -6 h GMT
Contact_Instructions: custserv@usgs.gov
Browse_Graphic:
Browse_Graphic_File_Name: Browse graphic for: http://earthexplorer.usgs.gov/brows...each_sc_0x5000m_utm_clr/vol008/myr_14c104.jpg
Browse_Graphic_File_Description: This is a compressed and resampled version of the data set of interest to help validate area of interest, data quality, and the impact of cloud cover, if it exists.
Security_Information:
Security_Classification_System: None
Security_Classification: Unclassified
Security_Handling_Description: None
Native_Data_Set_Environment: Oracle
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report: None
Logical_Consistency_Report: None
Completeness_Report: None
Lineage:
Process_Step:
Process_Description: None
Process_Contact:
Contact_Information:

Contact_Person_Primary:
Contact_Person: custserv@usgs.gov
Contact_Organization: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center
Contact_Organization_Primary:
Contact_Organization: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center
Contact_Person: custserv@usgs.gov
Contact_Position: Customer Service Representative
Contact_Address:
Address_Type: Mailing and Physical Address
Address: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center 47914 252nd Street
City: Sioux Falls
State_or_Province: SD
Postal_Code: 57198-0001
Country: USA
Contact_Electronic_Mail_Address: custserv@usgs.gov
Hours_of_Service: 0800 - 1600 CT, M-F, -6 h GMT
Contact_Instructions: custserv@usgs.gov
Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Raster
Distribution_Information:

Distributor:
Contact_Information:

Contact_Person_Primary:
Contact_Person: custserv@usgs.gov
Contact_Organization: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center
Contact_Organization_Primary:
Contact_Organization: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center
Contact_Person: custserv@usgs.gov
Contact_Position: Customer Service Representative
Contact_Address:
Address_Type: Mailing and Physical Address
Address: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center 47914 252nd Street
City: Sioux Falls
State_or_Province: SD
Postal_Code: 57198-0001
Country: USA
Contact_Electronic_Mail_Address: custserv@usgs.gov
Hours_of_Service: 0800 - 1600 CT, M-F, -6 h GMT
Contact_Instructions: custserv@usgs.gov
Distribution_Liability: Although these data have been processed successfully on a computer system at the U.S. Geological Survey, no warranty expressed or implied is made by the USGS regarding the use of the data on any other system, nor does the act of distribution constitute any such warranty.
Standard_Order_Process:

Digital_Form:
Digital_Transfer_Information:
Format_Name: Geographical-Tagged Image File Format (GeoTIFF)
Digital_Transfer_Option:

Online_Option:
Computer_Contact_Information:

Network_Address:
Network_Resource_Name: http://earthexplorer.usgs.gov
Offline_Option:
Recording_Format: Varies
Fees: Typically, all data available from USGS/EROS are downloadable at no cost to the user. There are some cases when a service fee is required to convert the analog film record to a digital file. This non-refundable fee is $30 per scene/frame.
Turnaround: A majority of the data are available for immediate downloading.
Technical_Prerequisites: Adequate computer capability is the only technical prerequisite for viewing data in digital form.
Metadata_Reference_Information:

Metadata_Review_Date: As Needed
Metadata_Contact:
Contact_Information:

Contact_Person_Primary:
Contact_Person: custserv@usgs.gov
Contact_Organization: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center
Contact_Organization_Primary:
Contact_Organization: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center
Contact_Person: custserv@usgs.gov
Contact_Position: Customer Service Representative
Contact_Address:
Address_Type: Mailing and Physical Address
Address: U.S. Geological Survey (USGS) Earth Resources Observation and Science (EROS) Center 47914 252nd Street
City: Sioux Falls
State_or_Province: South Dakota
Postal_Code: 57198-0001
Country: USA
Contact_Electronic_Mail_Address: custserv@usgs.gov
Hours_of_Service: 0800 - 1600 CT, M-F, -6 h GMT
Contact_Instructions: custserv@usgs.gov
Metadata_Standard_Name: Content Standard for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998, Version 2
Metadata_Time_Convention: Local Time
Metadata_Access_Constraints: None
Metadata_Use_Constraints: None
Metadata_Security_Information:
Metadata_Security_Classification_System: None
Metadata_Security_Classification: Unclassified
Metadata_Security_Handling_Description: None

 

[bob5568]

Usgs uses Transverse Mercator projection. FSX and P3D expect images to be in Geographic projection, datum of WSG84.

I thought SBX could do that reprojection, but I'm not sure. In my time of building terrain for fsx..we had to do that work with GIS applications like Global Mapper.

 

[GaryGB]

Hello:

In my experience, different USGS data sets for aerial imagery may vary as to actual GIS projection used.


The 'example image' cited in the Metadata posted by the OP above:

http://earthexplorer.usgs.gov/brows...each_sc_0x5000m_utm_clr/vol008/myr_14c104.jpg

...is in Universal Transverse Mercator (aka "UTM") suggesting that the GeoTIFF download may also be in UTM projection.

https://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system


However, one must always refer to the actual metadata packaged with GeoTIFF files from a particular USGS data set to confirm what the projection and datum parameters are.

If the GeoTIFF does not come with a separate ex: XML or HTML Metadata file, one must open that file in a GIS application to read the Metadata from inside the header of the GeoTIFF file itself and/or the [filename].TFW "world" file, which typically accompanies such that [filename].TIF GeoTIFF file, and also contains the Geo-referencing information with projection and datum.

One can then re-project to the GIS file format that SBuilderX requires for creation of a "background map" that can subsequently be used and processed within the SBuilderX work-space ...prior to output in the correct format required for use with FS SDK Resample.



AFAIK, SBuilderX accepts any image manually Geo-referenced / calibrated by the end user with Geographic (Lat-Lon) coordinates.


CAVEAT: GeoTIFF or other imagery Geo-referenced / calibrated by the end user in SBuilderX will be 'automatically re-projected' to the Geographic (Lat-Lon) WGS84 projection required by FS SDK resample only if it is already in a 'web tile server-type' projection (aka "Spherical Web Mercator") also referred to as "EPSG:3857"

https://en.wikipedia.org/wiki/Web_Mercator


One must use an external GIS application such as Global Mapper, ArcGIS / ArcMap (payware) or QGIS (freeware) etc. to manually re-project such downloaded GeoTIFF files from UTM to Geographic (Lat-Lon) projection / WGS84 datum (...which is required by FS SDK resample).

Once that has been done, one can import the imagery into SBuilderX via:

SBuilderX Menu > File > Add Map > From Disk...


NOTE: FS SDK Resample has a 2-GB output BGL file size limit, and the size of the total working file set (before any optional compression to be applied to the output BGL during compilation) may be limited within a SBuilderX windows task session by the amount of "User Virtual Address Space" (aka "USERVA") that is available; typically this is less than:

* 2-GB for 32-Bit SBuilderX (aka SBuilderX version 3.13)

...and:

* 4-GB for 64-Bit SBuilderX (aka SBuilderX version 3.14)


BTW: After re-projection, you may be able to load more than 12 of your cited "20 MB" source files within a SBuilderX task session:

(12 x 20 MB = 240 MB working set size).


Hope this helps !

GaryGB

 

[seippg]

I wish I could format this. It did come with this XML file...

I do have QGIS (barely any idea how to use it.) I found the properties of the layer and, while it did have some data in it, nothing that specified what the format of the file was other than GEOtiff and no data that looked like coordinates.

<?xml version="1.0"?>
<!--<!DOCTYPE metadata SYSTEM "http://www.esri.com/metadata/esriprof80.dtd">-->
<metadata xml:lang="en"><Esri><MetaID>{12945094-16F4-4CBF-993B-C194A5187085}</MetaID><CreaDate>20080922</CreaDate><CreaTime>20053000</CreaTime><SyncOnce>FALSE</SyncOnce><SyncDate>20080922</SyncDate><SyncTime>20055200</SyncTime><ModDate>20080923</ModDate><ModTime>19112400</ModTime><DataProperties><lineage><Process ToolSource="C:\Program Files\ArcGIS\ArcToolbox\Toolboxes\Data Management Tools.tbx\DefineProjection" Date="20080922" Time="200546">DefineProjection \\Cprodserver5\I\!USGS\MyrtleBeach2007\!IndexGrid\MyrtleBeach2007_Index.shp PROJCS['NAD_1983_UTM_Zone_17N',GEOGCS['GCS_North_American_1983',DATUM['D_North_American_1983',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Transverse_Mercator'],PARAMETER['False_Easting',500000.0],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-81.0],PARAMETER['Scale_Factor',0.9996],PARAMETER['Latitude_Of_Origin',0.0],UNIT['Meter',1.0]] \\Cprodserver5\I\!USGS\MyrtleBeach2007\!IndexGrid\MyrtleBeach2007_Index.shp</Process></lineage></DataProperties></Esri><idinfo><native Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.3.0.1770</native><descript><langdata Sync="TRUE">en</langdata><abstract>Aerials imagery is critical geospatial data component in identifying, planning and preparing for the protection of the US and its people. This dataset includes imagery for 13 areas in continental US. The dataset covers several major urban areas as well as secondary urban areas. Obtaining as much coverage as possible gives all government entities an interoperable common operating picture during a critical event or in pre or post planning</abstract><purpose>Aerials imagery is critical geospatial data component in identifying, planning and preparing for the protection of the US and its people. This dataset includes imagery for 13 areas in continental US. The dataset covers several major urban areas as well as secondary urban areas. Obtaining as much coverage as possible gives all government entities an interoperable common operating picture during a critical event or in pre or post planning</purpose></descript><citation><citeinfo><origin>REQUIRED: The name of an organization or individual that developed the data set.</origin><pubdate>REQUIRED: The date when the data set is published or otherwise made available for release.</pubdate><title Sync="TRUE">MyrtleBeach2007_Index</title><ftname Sync="TRUE">MyrtleBeach2007_Index</ftname><geoform Sync="TRUE">vector digital data</geoform><onlink Sync="TRUE">\\Cprodserver5\I\!USGS\MyrtleBeach2007\!IndexGrid\MyrtleBeach2007_Index.shp</onlink></citeinfo></citation><timeperd><current>ground condition</current><timeinfo><sngdate><caldate>2007 October</caldate></sngdate></timeinfo></timeperd><status><progress>Complete</progress><update>Irregular</update></status><spdom><bounding><westbc Sync="TRUE">-79.595095</westbc><eastbc Sync="TRUE">-77.521089</eastbc><northbc Sync="TRUE">34.482901</northbc><southbc Sync="TRUE">33.347834</southbc></bounding><lboundng><leftbc Sync="TRUE">630669.000000</leftbc><rightbc Sync="TRUE">819669.000000</rightbc><bottombc Sync="TRUE">3695120.000000</bottombc><topbc Sync="TRUE">3816620.000000</topbc></lboundng></spdom><keywords><theme/></keywords><accconst>The licensing shall allow distribution to Federal (Civil and Defense) State/Local government agencies for Homeland Security purposes and contain a no cost uplift to a fully Public Domain license twelve months from date of purchase of the data. USGS may place the data on the National Map servers prior to the uplift to public domain if the data is limited to view only (no download).</accconst><useconst>Same as access constraints</useconst><natvform Sync="TRUE">Shapefile</natvform><ptcontac><cntinfo><cntperp><cntper>Skyla Petersen</cntper><cntorg>Aerials Express</cntorg></cntperp><cntpos>Sales</cntpos><cntaddr><addrtype>mailing and physical address</addrtype><address>7855 South River Parkway Suite 205</address><city>Tempe</city><state>AZ</state><postal>85284</postal><country>USA</country></cntaddr><cntvoice>480-777-9909</cntvoice><cntfax>480-777-9966</cntfax><cntemail>spetersen@aerials-express.com</cntemail></cntinfo></ptcontac><browse><browsen>None </browsen><browsed>Imagery</browsed><browset>TIFF</browset></browse><datacred>Luke Pritchard, Skyla Petersen, Bradley Mattison, Aaron Kimble</datacred></idinfo><dataIdInfo><envirDesc Sync="TRUE">Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.3.0.1770</envirDesc><dataLang><languageCode Sync="TRUE" value="en"></languageCode></dataLang><idCitation><resTitle Sync="TRUE">MyrtleBeach2007_Index</resTitle><presForm><PresFormCd Sync="TRUE" value="005"></PresFormCd></presForm></idCitation><spatRpType><SpatRepTypCd Sync="TRUE" value="001"></SpatRepTypCd></spatRpType><dataExt><geoEle><GeoBndBox esriExtentType="native"><westBL Sync="TRUE">630669</westBL><eastBL Sync="TRUE">819669</eastBL><northBL Sync="TRUE">3816620</northBL><southBL Sync="TRUE">3695120</southBL><exTypeCode Sync="TRUE">1</exTypeCode></GeoBndBox></geoEle></dataExt><geoBox esriExtentType="decdegrees"><westBL Sync="TRUE">-79.595095</westBL><eastBL Sync="TRUE">-77.521089</eastBL><northBL Sync="TRUE">34.482901</northBL><southBL Sync="TRUE">33.347834</southBL><exTypeCode Sync="TRUE">1</exTypeCode></geoBox></dataIdInfo><metainfo><langmeta Sync="TRUE">en</langmeta><metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn><metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv><mettc Sync="TRUE">local time</mettc><metc><cntinfo><cntaddr><addrtype>mailing and physical address</addrtype><city>Tempe</city><state>AZ</state><postal>85284</postal><address>7855 South River Parkway Suite 205</address><country>USA</country></cntaddr><cntvoice>480-240-3873</cntvoice><cntperp><cntper>Bradley Mattison</cntper><cntorg>Aerials Express</cntorg></cntperp><cntpos>Production Director</cntpos><cntfax>480-777-9966</cntfax><cntemail>bmattison@aerials-express.com</cntemail></cntinfo></metc><metd Sync="TRUE">20080923</metd><metextns><onlink Sync="TRUE">http://www.esri.com/metadata/esriprof80.html</onlink><metprof Sync="TRUE">ESRI Metadata Profile</metprof></metextns></metainfo><mdLang><languageCode Sync="TRUE" value="en"></languageCode></mdLang><mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName><mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer><mdChar><CharSetCd Sync="TRUE" value="004"></CharSetCd></mdChar><mdHrLv><ScopeCd Sync="TRUE" value="005"></ScopeCd></mdHrLv><mdHrLvName Sync="TRUE">dataset</mdHrLvName><distinfo><resdesc Sync="TRUE">Downloadable Data</resdesc><stdorder><digform><digtinfo><transize Sync="TRUE">0.795</transize><dssize Sync="TRUE">0.795</dssize></digtinfo></digform></stdorder><distrib><cntinfo><cntorgp><cntorg>Aerials Express</cntorg></cntorgp><cntaddr><addrtype>mailing and physical address</addrtype><address>7855 South River Parkway Suite 205</address><city>Tempe</city><state>AZ</state><postal>85284</postal><country>USA</country></cntaddr><cntvoice>480-777-9909</cntvoice><cntfax>480-777-9966</cntfax></cntinfo></distrib><distliab>Please see the Aerials Express, LLC END-USER LICENSE AGREEMENT</distliab><availabl><timeinfo><sngdate><caldate>2007 October</caldate></sngdate></timeinfo></availabl></distinfo><distInfo><distributor><distorTran><onLineSrc><orDesc Sync="TRUE">002</orDesc><linkage Sync="TRUE">file://\\Cprodserver5\I\!USGS\MyrtleBeach2007\!IndexGrid\MyrtleBeach2007_Index.shp</linkage><protocol Sync="TRUE">Local Area Network</protocol></onLineSrc><transSize Sync="TRUE">0.795</transSize></distorTran><distorFormat><formatName Sync="TRUE">Shapefile</formatName></distorFormat></distributor></distInfo><spdoinfo><direct Sync="TRUE">Vector</direct><ptvctinf><esriterm Name="MyrtleBeach2007_Index"><efeatyp Sync="TRUE">Simple</efeatyp><efeageom Sync="TRUE">Polygon</efeageom><esritopo Sync="TRUE">FALSE</esritopo><efeacnt Sync="TRUE">6125</efeacnt><spindex Sync="TRUE">FALSE</spindex><linrefer Sync="TRUE">FALSE</linrefer></esriterm><sdtsterm Name="MyrtleBeach2007_Index"><sdtstype Sync="TRUE">G-polygon</sdtstype><ptvctcnt Sync="TRUE">6125</ptvctcnt></sdtsterm></ptvctinf></spdoinfo><spatRepInfo><VectSpatRep><topLvl><TopoLevCd Sync="TRUE" value="001"></TopoLevCd></topLvl><geometObjs Name="MyrtleBeach2007_Index"><geoObjTyp><GeoObjTypCd Sync="TRUE" value="001"></GeoObjTypCd></geoObjTyp><geoObjCnt Sync="TRUE">6125</geoObjCnt></geometObjs></VectSpatRep></spatRepInfo><eainfo><detailed Name="MyrtleBeach2007_Index"><enttyp><enttypl Sync="TRUE">MyrtleBeach2007_Index</enttypl><enttypt Sync="TRUE">Feature Class</enttypt><enttypc Sync="TRUE">6125</enttypc></enttyp><attr><attrlabl Sync="TRUE">FID</attrlabl><attalias Sync="TRUE">FID</attalias><attrtype Sync="TRUE">OID</attrtype><attwidth Sync="TRUE">4</attwidth><atprecis Sync="TRUE">0</atprecis><attscale Sync="TRUE">0</attscale><attrdef Sync="TRUE">Internal feature number.</attrdef><attrdefs Sync="TRUE">ESRI</attrdefs><attrdomv><udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom></attrdomv></attr><attr><attrlabl Sync="TRUE">Shape</attrlabl><attalias Sync="TRUE">Shape</attalias><attrtype Sync="TRUE">Geometry</attrtype><attwidth Sync="TRUE">0</attwidth><atprecis Sync="TRUE">0</atprecis><attscale Sync="TRUE">0</attscale><attrdef Sync="TRUE">Feature geometry.</attrdef><attrdefs Sync="TRUE">ESRI</attrdefs><attrdomv><udom Sync="TRUE">Coordinates defining the features.</udom></attrdomv></attr><attr><attrlabl Sync="TRUE">location</attrlabl><attalias Sync="TRUE">location</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">255</attwidth></attr></detailed><overview><eaover>Geotiff images 1500 meters by 1500 meters</eaover><eadetcit>none</eadetcit></overview></eainfo><mdDateSt Sync="TRUE">20080923</mdDateSt><spref><horizsys><cordsysn><geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn><projcsn Sync="TRUE">NAD_1983_UTM_Zone_17N</projcsn></cordsysn><planar><planci><plance Sync="TRUE">coordinate pair</plance><plandu Sync="TRUE">meters</plandu><coordrep><absres>0.5</absres><ordres>0.5</ordres></coordrep></planci><gridsys><gridsysn Sync="TRUE">Universal Transverse Mercator</gridsysn><utm><utmzone Sync="TRUE">17</utmzone><transmer><sfctrmer Sync="TRUE">0.999600</sfctrmer><longcm Sync="TRUE">-81.000000</longcm><latprjo Sync="TRUE">0.000000</latprjo><feast Sync="TRUE">500000.000000</feast><fnorth Sync="TRUE">0.000000</fnorth></transmer></utm></gridsys></planar><geodetic><horizdn Sync="TRUE">North American Datum of 1983</horizdn><ellips Sync="TRUE">Geodetic Reference System 80</ellips><semiaxis Sync="TRUE">6378137.000000</semiaxis><denflat Sync="TRUE">298.257222</denflat></geodetic></horizsys></spref><refSysInfo><RefSystem><refSysID><identCode Sync="TRUE">NAD_1983_UTM_Zone_17N</identCode></refSysID></RefSystem></refSysInfo><dataqual><logic>The Photography was flown using an ADS40 Camera</logic><complete>Imagery is seamless and nearly cloud free. Ocean water has been colorized to mask out most light reflections and color issues</complete><posacc><horizpa><horizpar>The horizontal positional accuracy and the assurance of that accuracy depend, in part, on the accuracy of the data inputs to the rectification process. The positions of existing USGS photoidentifiable ground control were evaluated on the Geotiff image and compared with their ground values in order to determine an overall accuracy for the final Urban Area. After image coordinate measurement was completed, a radial RMSE was calculated for the entire block. This value is an estimate of the horizontal accuracy of the tile expressed in meters. Aerials Express does not warrant horizontal accuracy to exceed that of 5.0 meters at 90% (NMAS for 1:12000-scale products)</horizpar><qhorizpa><horizpav>5</horizpav><horizpae>Federal Geographic Data Committee, 1998, Geospatial Positioning Accuracy Standard, Part 3, National Standard for Spatial Data Accuracy, FGDC-STD-007.3-1998</horizpae></qhorizpa></horizpa></posacc><lineage><srcinfo><srctime><timeinfo><sngdate><caldate>2007 October</caldate></sngdate></timeinfo><srccurr>ground condition</srccurr></srctime></srcinfo><procstep><procdesc>The production process starts when the film is received from the processing lab. The process is broken into four phases: scanning, Automatic-Triangulation, Color Balancing, Seamlines, and quality control. Scanning Much is determined in the first step of scanning. It is important that this step is done correctly in order for the remaining steps to run smoothly. It is for this reason that a ZEISS Photo Scan photogrammetric scanner is used to perform all scanning in-house. This provides complete control for both resolution and color balance at the start of the process. Automatic Triangulation and Rectification We use Intergraph's Image Station Auto-Triangulaton (ISAT) system that works hand-in-hand with IMU/ABGPS data to match photos together. It is an automated process to create automatic tie points between photos. The process uses a bundle adjustment to tighten the accuracy of the tie points. Upon good AT results, we then use a DEM to rectify the photos with Intergraph's Image Station Ortho Pro (ISOP) software. Color Balancing and Seamline Generation After rectification an overall tone balancing using ER MAPPER Software is applied to the aerial photo project. Seamlines or a stitching process are then assigned between each image to ensure a more seamless mosaic. The mosaic is then tiled into tiff images. Quality Control Aerials Express takes great care in the tone and color balance of the imagery. The ER Mapper software provides the automatic color correction of the imagery in batch mode. As a final review, Adobe Photoshop is used to correct color and image density where stitching is not able to fully disguise the match lines. The final step in this process is to color balance the entire image file to the best color, which gives the photography a completely natural look. Production Process for ADS40 LEICA DIGITAL IMAGERY Data processing of ADS40 imagery and metadata is a streamlined digital workflow process utilizing commercial softcopy photogrammetric software including Applanix POSPAC, Leica GPro, ORIMA, SOCET SET and Orthovista. The ADS40 sensor GPS/IMU position and attitude data is directly processed through three separate but continuous steps: Applanix POSPAC for data extracting, POSGPS for data orientation, and POSProc for creating a Smoothed Best Estimate of Trajectory (SBET) for each flight lift. The post-processed GPS data output is displayed onto the flight profile plot, which clearly shows the RMS values of the combined forward and reverse run separations, C/A Code and Carrier Phase. The output IMU data is also verified by a PDOP plot and its value compared to an acceptable threshold range. The processing of ADS40 images is run on Leica GPRO and ORIMA for bundle adjustment. The image is linked to the local coordinate system through the corresponding GPS/IMU SBET data with correct position and orientation. The residual of the tie-points are displayed instantly to reflect the accuracy of the processed data. After the bundle adjustment, ORIMA automatically displays the unit weight standard deviation, the RMS of tie points and the accuracy of the sensor position and orientation. The iteration process on the bundle adjustment is based on the selected parameters to ensure the data integrity and accuracy is within the project specification. The software also provides the measurement of reliability for variance and co-variance component analysis. This ensures the processed data is statistically satisfied on the application demand. The triangulation process involves automatic measurement of tie points. All operations are performed using the graphical working environment of ORIMA. For automatic tie point measurement, the Auto Point Measurement (APM) from Orima, using a very dense point measuring algorithm adapted for the ADS40, is called directly. Highest quality orientation results are obtained by a combined bundle adjustment. The Combined Adjustment Program CAP-A has been extended to handle all types of observations required for ADS40. The observations are image coordinates, and position and attitude values from GPS and IMU computed by the IMU/GPS post-processing software. The post-processing includes the transformation of the raw data into the reference image frame used for the aerial triangulation. The resultant values of this transformation are the same as orientation elements of standard photogrammetry procedures and results. "The use of the high precision GPS/IMU data combined with these traditional triangulation techniques gives rise to a very robust and flexible system. The adjustment process can determine calibration, datum deficiencies, errors in GPS and more precisely register the imagery to ground control. It should be noted that very little ground control is required. Owing to the GPS/IMU data, ground control is essentially unnecessary." Hinsken, et al, Program author of Orima. Raw imagery is checked and radiometric balanced in a parallel process that utilizes custom gradient correction software and the Leica GPRO Tonal Transfer Curve (TTC) application. While operators are refining a good AT result, others are carefully reviewing the imagery for good color band balance, contrast and tone. Once both processes have passed rigid AT and QC milestones, the imagery bands, red, green and blue or NIR, red, and green are rectified to an RGB or CIR product. These orthos are passed to the mosaic team for QC, seam line placement and tiling using the vigorous interactive capabilities of Orthovista software. For this project, the latest available National Elevation Dataset NED surface model is used for rectification</procdesc><procdate>2007 October</procdate></procstep></lineage></dataqual></metadata>

 

[seippg]

Hmmm. I just imported all 12 pictures into QGIS and it put them right in place straightaway, all aligned perfectly. What's the next step with it?

 

[GaryGB]

Yup, your GeoTIFF in question is in UTM projection / NAD83 datum.

PROJCS['NAD_1983_UTM_Zone_17N',GEOGCS['GCS_North_American_1983',DATUM['D_North_American_1983',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Transverse_Mercator'],PARAMETER['False_Easting',500000.0],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-81.0],PARAMETER['Scale_Factor',0.9996],PARAMETER['Latitude_Of_Origin',0.0],UNIT['Meter',1.0]] \



Open a COPY of the GeoTIFF file(s) in QGIS and re-project to "Spherical Web Mercator" aka "EPSG:3857" ...if you wish to perform all further processing inside SBuilderX.


Then, import the imagery into SBuilderX via:

SBuilderX Menu > File > Add Map > From Disk...


FYI: It is, of course possible to instead manually process the copied GeoTIFF source files to output a custom aerial imagery BGL via FS SDK Resample after re-projecting to Geographic (Lat-Lon) projection / WGS84 datum, but that might be done only by learning considerably more about how to work with the FS SDK compilers after preparing source files using 3rd party software.


BTW: You may wish to download / install / use NotePad++
(freeware) to view / edit XML files for use with FS Development:

https://notepad-plus-plus.org/download/v7.3.3.html


Hope this helps a bit more.

GaryGB

 

[GaryGB]

http://www.fsdeveloper.com/forum/threads/usgs-orthoimage-tif-files.439980/#post-770895

Hmmm. I just imported all 12 pictures into QGIS and it put them right in place straightaway, all aligned perfectly. What's the next step with it?

A thread I found on the QGIS re-projection process:

https://gis.stackexchange.com/questions/73686/how-can-i-change-the-projection-of-shapefile-in-qgis


PS: Some Google links:

https://www.google.com/#q=QGIS+"EPSG:3857"


I do not personally use QGIS, but I hope this helps get you farther.

GaryGB

 

[seippg]

Hmmm...I did the projection and they look aligned but I got black borders...

Maybe there's some adjustment I can make.

 

[GaryGB]

What application work-space is the screenshot from: QGIS, SBuilderX ...etc ?


PS: Is this a historical reconstruction project ?

(...Just curious about the older B+W imagery.)

GaryGB

 

[seippg]

Heh, well, it came out black and white because I was remoted to a windows 7 machine and my capture program recorded it that way. SBuilderX doesn't work on Windows 10. The screenshot is from SBuilderX running on that machine. The uncaptured photos have vibrant colors.

Reading some of those Google entries, there seem to be plugins to tile the images so there may be a way to fix them. Failing that, I'm wondering if I just joined the images together into a big image and worked with that if it would work.

 

[GaryGB]

If you once again open new un-altered copies of the USGS GeoTIFFS in QGIS (in their original projection as UTM / NAD83), you should then be able to 'select' them either as a group of tiles or as a polygon-framed area, then export a 1-piece GeoTIFF in UTM / NAD83.

Once that is done, in a new QGIS task session, open the 1-piece GeoTIFF in UTM / NAD83 with QGIS, and re-project that image to "Spherical Web Mercator" aka "EPSG:3857".

When finished, import the imagery into SBuilderX via:

SBuilderX Menu > File > Add Map > From Disk...


PS: AFAIK, one can run 32-Bit SBuilderX version 3.13 under Windows 10:

http://www.fsdeveloper.com/forum/threads/sbx314-and-windows-10.434998/

http://www.ptsim.com/forum/viewtopic.php?p=8116&sid=c8f6b0eabd7aec1fe8ba53fe5bd0e8de

GaryGB

 

[seippg]

Thanks Gary. Sounds like a plan. I've Raster->Miscellaneous->Merged the pics together and then Raster->Projection->Warp (Reprojected)'ed the EPSG:3857. It has a black border but I'll make a blend mask to take it out. I guess I should use the upper left coordinate of the upper left image for the North/West coordinates and the same for the bottom right image for East/South.

Gregg

 

[GaryGB]

http://www.fsdeveloper.com/forum/threads/usgs-orthoimage-tif-files.439980/#post-770915

Thanks Gary. Sounds like a plan. I've Merged the pics together and applied the EPSG:3857. It has a black border but I'll make a blend mask to take it out. I guess I should use the upper left coordinate of the upper left image for the North/West coordinates and the same for the bottom right image for East/South.

Gregg

[EDITED]

Indeed, you can examine in QGIS, the metadata for the 1-piece GeoTIFF (re-projected to EPSG:3857) to determine Geo-referencing coordinates to use in SBuilderX when manually 'calibrating' a ex: BMP that has precisely the same number of Rows and Columns as the 1-piece GeoTIFF aerial imagery file, and which is also projected in the same EPSG:3857 format.



FYI: You can also use an additional method to compare what Geo-referencing SBuilderX has derived from a sample tile of aerial imagery when you "Add from disk"

To do this, you may use Ollyau's "GeoTIFF to INF" utility to read the GeoTIFF projected in EPSG:3857 that has been imported into the SBuilderX work-space, then use "GeoTIFF to INF" to write out a INF (otherwise intended for use with FS SDK Resample via the 'manual' compilation method).

The resulting INF includes the Geo-referencing info for the NW and SE corners derived from the [filename].TIF 'GeoTIFF file header' and the accompanying [filename].TFW 'world' file for that GeoTIFF image ...as imported to SBuilderX in EPSG:3857 projection.


BTW: FS SDK Resample "INF" files can be opened / viewed /edited as 'text' in Windows NotePad:

http://www.fsdeveloper.com/forum/resources/geotiff-to-inf.119/


CAVEAT: The above process is separate and distinct from the use of Ollyau's "GeoTIFF to INF" utility during 'final' output of files projected in Geographic (Lat-Lon) projection / WGS84 datum GIS format ...for processing by FS SDK Resample.

[END_EDIT]

GaryGB

 

[seippg]

To do this, you may use Ollyau's "GeoTIFF to INF" utility to write out a separate INF (otherwise intended for use with FS SDK Resample via the 'manual' compilation method) that includes the Geo-referencing info derived from the [filename].TIF GeoTIFF file header and the accompanying [filename].TFW 'world' file; that INF file can be opened / viewed in Windows NotePad:

I downloaded GeoTIFF to INF and tried it out on both one of my original files as well as the combined files but the latitude/longitude were both wrong. The Pixel scale was right.

 

[GaryGB]

http://www.fsdeveloper.com/forum/threads/usgs-orthoimage-tif-files.439980/#post-770923

I downloaded GeoTIFF to INF and tried it out on both one of my original files as well as the combined files but the latitude/longitude were both wrong. The Pixel scale was right.

To clarify the general work-flow:

Imagery within the SBuilderX work-space is to be 'non-warped' in a "Spherical Web Mercator" aka "EPSG:3857" projection.

When SBuilderX outputs the "final" 1-piece image for submission to FS SDK Resample along with a INF file for compilation to a custom aerial imagery BGL, it will once more 'internally and automatically' re-project that background image from its work-space into Geographic (Lat-Lon) projection / WGS84 datum GIS format required by FS SDK Resample.


FYI: It is from copies of that "final" 1-piece visible background RGB image output by SBuilderX that all Blend Masks and Land / Water Masks should be derived by creation of Alpha Channels (..after which, the original 'source' visible background RGB channel(s) are deleted from the Mask file(s).

That "final" intact 1-piece visible background RGB channel file is the image on which one would run GeoTIFF-to-INF to verify Geo-referencing coordinates for a "multi-source" INF file for use with multiple visible images and/or Mask files.


BTW: I simply mentioned an additional option in my latter post above, to clarify that one could add a Blend Mask from disk back into the SBuilderX work-space for ex: verification of alignment and/or creation / derivation of other scenery content ...prior to "final" output and compilation.

That latter described process involves re-projecting a final 1-piece aerial image back into "Spherical Web Mercator" aka "EPSG:3857" projection, running GeoTIFF-to-INF on it, then using those resulting "adjusted" Geo-referencing coordinates to re-calibrate any such Blend Mask or Land / Water Mask for use within the SBuilderX. work-space (again).


I have edited my latter post above in an effort to minimize mis-interpretation.

http://www.fsdeveloper.com/forum/threads/usgs-orthoimage-tif-files.439980/#post-770916

GaryGB

 

[seippg]

Thanks again, Gary. I'm buried in work today but I'll have some time tomorrow to run it through SBuilderX, make the masks and process it all through Resample.

Gregg

 

[seippg]

I loaded the combined TIF into SBuilderX, selected it (has green border with red dots). Then I click the compile button but it says I haven't selected anything. Tried searching for an answer but no answer so far. Help?

 

[GaryGB]

Hi:

I'm away from a real computer with SBuilderX on it, and will have check this somewhere in the next hour or so upon my return.

IIRC, you can try zooming out so the background map image area added from disk does not overlap the edge of the work-space, then draw a selection frame around the image area so it is selected properly.

Then see if the request to compile will work.

Let us know how that worked, and I'll check on this a little later tonight.

GaryGB

 

[seippg]

IIRC, you can try zooming out so the background map image area added from disk does not overlap the edge of the work-space, then draw a selection frame around the image area so it is selected properly.

Hi Gary,

Tried that already. Same problem. Tried Ctrl-A and, also, just clicking a corner. My .tif file is 329 MB.

Gregg

EDIT: In another thread I found someone saying to convert it to a BMP. That didn't work and someone else said to change the properties name of the image to something beginning with "PHOTO". The combination of those two things together, though, made it recognize that I was trying to compile the image. I pressed compile and (rats!) it failed but, when I checked, it had created an INF file. I decided to try to run resample with that INF and got very lucky for a first-timer. Success!

If I look carefully at the image, I can see places where it doesn't quite line up with the roads. Not sure how picky I can be.

Gregg

 

[GaryGB]

Back at a real computer with SBuilderX installed.


IIRC, when one adds a GeoTIFF as a 'map from a disk' via:

SBuilderX Menu > File > Add Map > From Disk...

...that GeoTIFF needs to be loaded from:

[SBuilderX install path]\Tools\Work subfolder.


One will be prompted to "Calibrate" the image, and if it is a GeoTIFF in the proper GIS projection, one can simply approve the coordinates submitted to finish the import.


Also, please clarify that the message at the bottom of the "SBuilderX - BGL Compile" dialog box is:

"There is nothing to compile because no items have been selected" ?


If you are unable to get this to work, feel free to ZIP the file and post or PM a link to it on a external download site such as DropBox, MediaFire, MS-OneDrive etc.

Alternatively, please post or PM the ICAO of the airport in question.

[EDITED]

Just saw your updated edit above.

If you have saved out the Geo-referencing info for the final 1-piece GeoTIFF re-projected in QGIS from Geographic (Lat-Lon) / WGS84 projection to "Spherical Web Mercator" aka "EPSG:3857" projection format via use of ex: GeoTIFF-to-INF and have not changed the Row or Column size of the image when converted / edited as a BMP, that should also work.

[END_EDIT]

GaryGB