https://www.fsdeveloper.com/forum/threads/about-wgs84-images.445708/post-828104
I'm not sure I understand why the log indicated "/" slash either, this isn't something I entered manually ... it's all UI based so no command line.
Apparently the QGIS programmers have not implemented a code option to display paths using the Backslash character to maintain explicit compatibility with a growing number of applications written in Windows-based programming languages, even though there may already be an option in the QGIS QT / Python coding used to create QGIS itself.
https://stackoverflow.com/questions...ward-slash-issue-in-path-on-windows-in-python
Apparently this coding preference is to maintain cross-OS-platform compatibility for QGIS plugins coded as Python-related scripts.
https://issues.qgis.org/issues/12084
https://gis.stackexchange.com/questions/170797/running-pyqgis-script-in-windows
https://www.howtogeek.com/181774/wh...hes-and-everything-else-uses-forward-slashes/
Although Windows reportedly can support either a Slash
or Backslash delimited path format, IMHO with the rapidly growing number of custom applications being created for use in
Windows,
use of a 'Slash' (/) Folder and File path delimiter character is asking for trouble.
https://blogs.msdn.microsoft.com/ie/2006/12/06/file-uris-in-windows/
https://stackoverflow.com/questions...ween-forward-slash-and-backslash-in-file-path
https://www.fsdeveloper.com/forum/threads/about-wgs84-images.445708/post-828104
One other question, where are you getting center lat/lon values from per
this document? Will they be contained in the Metadata from .TIF output?
Cheers, Rob.
I would first try Arno's MCX Coordinate Converter:
Coordinate converter
https://www.fsdeveloper.com/wiki/index.php?title=ModelConverterX#Coordinate_converter
...using the workflow mentioned in the above cited wiki:
Align background image in 3D editor - Calculating position
https://www.fsdeveloper.com/wiki/in...round_image_in_3D_editor#Calculating_position
Compare MCX' Metadata with that from a
Global Mapper demo (...
since QGIS can't get out of its own way in being consistently obscure 
).
FYI: Since the current Global Mapper demo and trial mechanism is reportedly intrusive and draconian, I'd suggest using an earlier demo.
You can download / install this feature-limited (no exports) USGS
viewer called DLGV32 Pro (aka Global Mapper 13 demo - non-expiring):
https://www.mediafire.com/file/ug44dpiy27jnfqf/dlgv32_pro_usgs_setup_exe.zip/file
For a historical reference on
USGS Digital Data Viewer: DLGV32 Pro:
https://www.bluemarblegeo.com/products/global-mapper-dlgv32.php
DLGV32 Pro was distributed free for all to use until a couple of years ago by USGS, and the installer is
still legal to use (
old URL is offline).
It is safe to use, and is a legal copy I downloaded directly from USGS years ago.
Global Mapper v13 (aka "GM-13") demo was intended only to "view" imagery and identify coordinates, as well as perform measurements etc. ...in a particular GIS "projection" format.
It allows viewing of (
4) data files at a time, and will impose other limitations until purchased.
A e-mailed Registration key is entered after one purchases a license for use of all features.
https://www.bluemarblegeo.com/knowl.../Using_Global_Mapper_with_a_Trial_License.htm
I do
not recommend using the Global Mapper demo
currently available online, until having learned how Global Mapper works, to avoid being blocked from re-installing it in the future.
Doing initial learning in a non-expiring GM-13 demo may allow one to more '
successfully' use the fully functioning Global Mapper demo
currently available online for period of 2 weeks.
Currently one must otherwise use a demo of the latest Global Mapper which expires after 2-weeks, so this older version is still useful.
You can Open your GeoTIFF output by GDALWARP in
DLGV32 Pro (aka:
Global Mapper v13 demo aka: "
GM-13") via:
GM-13 Menu > File > Open
Metadata for a loaded GIS file can be viewed / copied via:
GM-13 Menu > Tools > Control Center >
select: your GDALWARP GeoTIFF 'layer' >
click: [Metadata] button.
PS: Theoretically, if working in a true non-warped aka "Flat Earth" GIS projection using numeric (Cartesian) coordinates, one should be able to compute the Center Pixel coordinate position by subtracting the smallest coordinate value from the largest coordinate value for each of the Latitudinal and Longitudinal coordinate axes.
Pixel is Point vs.
Pixel is Area parameter value may also be considered depending on the type of data set values and projections used.
https://gis.stackexchange.com/quest...oordinates-of-pixels-in-georeferenced-rasters
https://trac.osgeo.org/gdal/ticket/3837
https://gis.stackexchange.com/questions/262726/does-qgis-handle-area-or-point-metadata-tag
https://www.prepar3d.com/SDKv4/sdk/world/terrain/terrain_overview.html#The Resample Tool
CAVEAT: Geographic (and Cartesian ?) coordinates 'may' change when GIS "Projection" and/or "Datum" format changes
Hope this helps a bit more.
GaryGB