<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Even,<div><br><div><blockquote type="cite"><div><div>
<blockquote type="cite" cite="mid:4D532919-B2ED-4AEA-BDA8-6DF25A77F151@flighttactics.com">
<pre class="moz-quote-pre" wrap=""> But I also noticed the WKS seems to be different in the two as well. Is there a configuration or something else I might be missing that would cause these to be off? </pre>
</blockquote><p>gdalinfo uses WKT_2:2019, and GetProjectionRef() uses WKT1. You
can use GetSpatialRef()->exportToWKT(apszOptions) with
apsOptions = { "FORMAT=WKT2_2019", nulptr } to get the same result</p></div></div></blockquote><div><br></div>Ah, that makes sense!<br><br><blockquote type="cite"><div><div><span style="white-space: pre-wrap"></span></div></div></blockquote><blockquote type="cite"><blockquote type="cite">Sorry for the bother again - I noticed that when I use gdalinfo to query a document (in this case, a GeoPDF) the geotransform coordinates are slightly different than when I can GetGeoTransform using the API on the same document with GDALOpen + GDALGetGeoTransform.</blockquote></blockquote><blockquote type="cite"><p>Presumably due to a difference in number of significant digits displayed in both cases.</p></blockquote></div>For the GeoTransform, I’m pushing them out to the same significant digits:</div><div><br></div><div>Gdalinfo:</div><div><div>-8800981.741226587, 1.534954250051887, 0.7153177546590841</div><div>4288851.899958452, 0.7158702972076904, -1.534439284842128</div></div><div><br></div><div>API:</div><div>-8800981.488120455, 1.5351602235290571, 0.7144694099544626, </div><div>4288852.103036083, 0.7156171000026056, -1.5347947295515767</div><div><br></div><div>From what I can see, they seem to be kind of far apart to be just significant digits. It’s calculating different pixel sizes and rotations which in turn is causing the lat/lon conversion to be off. The only other thing I can think of is that I compiled the API with PDFium and I believe the homebrew install uses Poppler. I just want to make sure I’m not misunderstanding something with how I’m using this.</div><div><br></div><div>Thanks!</div><div><br></div><div>Cory</div></body></html>