Re: [gdal-dev] Problem reading Sentinel-1 GeoTIFFs

2021-12-10 Thread Even Rouault
Those files use a invalid GeogEllipsoidGeoKey=4326 for the WGS 84 ellipsoid. The correct code should be 7030. Sometimes should report that to the data producer. Warning silenced in https://github.com/OSGeo/gdal/pull/4975 Le 11/12/2021 à 00:05, Simon Eves a écrit : After also finding this thre

Re: [gdal-dev] Problem reading Sentinel-1 GeoTIFFs

2021-12-10 Thread Simon Eves
After also finding this thread... https://github.com/OSGeo/gdal/issues/2321 ...I installed geotiff-bin and ran listgeo on the file. It also spits the same message (three times). The output is attached. S On Fri, Dec 10, 2021 at 2:56 PM Simon Eves wrote: > Further to my earlier post about

[gdal-dev] Problem reading Sentinel-1 GeoTIFFs

2021-12-10 Thread Simon Eves
Further to my earlier post about GCP Transforms, I now have that code written, and it seems to be functioning fine, although whether it's generating the right values is as yet unclear. The problem is that I am having trouble creating the secondary transformation from whatever the output space of t

Re: [gdal-dev] Transforming Raster Points from GeoTIFF with GCPs

2021-12-10 Thread Simon Eves
Thanks. The code to which I was referring in my original mail was that used by gdaltransform. I just hadn't found the API part. On Fri, Dec 10, 2021 at 12:45 PM wrote: > and https://gdal.org/programs/gdaltransform.html > > > > -Matt > > > > *From:* gdal-dev *On Behalf Of *Simon > Eves > *Sent:*

Re: [gdal-dev] Transforming Raster Points from GeoTIFF with GCPs

2021-12-10 Thread Matt.Wilkie
and https://gdal.org/programs/gdaltransform.html -Matt From: gdal-dev On Behalf Of Simon Eves Sent: December 10, 2021 12:21 PM To: Yann-Sebastien Tremblay-Johnston Cc: gdal dev Subject: Re: [gdal-dev] Transforming Raster Points from GeoTIFF with GCPs *** External email: Do not click on links

Re: [gdal-dev] Transforming Raster Points from GeoTIFF with GCPs

2021-12-10 Thread Simon Eves
Aha! That's the bit I hadn't found. Thank you! :) On Fri, Dec 10, 2021 at 10:38 AM Yann-Sebastien Tremblay-Johnston < yanns.tremb...@gmail.com> wrote: > Simon, > > See the Transformer API, in particular > https://gdal.org/api/gdal_alg.html?highlight=transformer#_CPPv419GDALTransformerFunc > (or g

Re: [gdal-dev] Transforming Raster Points from GeoTIFF with GCPs

2021-12-10 Thread Yann-Sebastien Tremblay-Johnston
Simon, See the Transformer API, in particular https://gdal.org/api/gdal_alg.html?highlight=transformer#_CPPv419GDALTransformerFunc (or gdal.Transformer in Python). Sebastien On Fri, Dec 10, 2021 at 10:24 AM Simon Eves wrote: > So we have a GeoTiFF of Sentinel-1 imagery which `gdalinfo` reports

[gdal-dev] Transforming Raster Points from GeoTIFF with GCPs

2021-12-10 Thread Simon Eves
So we have a GeoTiFF of Sentinel-1 imagery which `gdalinfo` reports as having a GCP projection with 210 points, which we'd (perhaps naively?!) like to import directly, transforming to WGS84 on the fly. Obviously a simple OGRSpatialReference/OGRCoordinateTransformation transform isn't going to do a

Re: [gdal-dev] Problems compiling GDAL in ARM + NEON + libpng

2021-12-10 Thread Javier Jimenez Shaw
Thanks! .___ ._ ..._ .. . ._. .___ .. __ . _. . __.. ... ._ .__ Entre dos pensamientos racionales hay infinitos pensamientos irracionales. On Fri, 10 Dec 2021 at 12:52, Even Rouault wrote: > Was fixed in > https://github.com/OSGeo/gdal/commit/1c719a864232daf58b799fbb2da785f3f9b2d579 > L

Re: [gdal-dev] Problems compiling GDAL in ARM + NEON + libpng

2021-12-10 Thread Even Rouault
Was fixed in https://github.com/OSGeo/gdal/commit/1c719a864232daf58b799fbb2da785f3f9b2d579 Le 10/12/2021 à 12:29, Javier Jimenez Shaw a écrit : Hi I am trying to compile GDAL 3.3.2 for ARM (apple M1), and I have problems with the included libpng. There is a missing "arm" folder in libpng. Is

[gdal-dev] Problems compiling GDAL in ARM + NEON + libpng

2021-12-10 Thread Javier Jimenez Shaw
Hi I am trying to compile GDAL 3.3.2 for ARM (apple M1), and I have problems with the included libpng. There is a missing "arm" folder in libpng. Is that intentional? How can I build it? NEON support is detected, so libpng try to use NEON optimized functions, but the implementation of those is mi