Re: [gdal-dev] Trouble reprojecting feature that crosses antimeridian

Was a bug. Fix queued in https://github.com/OSGeo/gdal/pull/5543 Le 29/03/2022 à 22:30, Robin Wilson a écrit : Hi, I’ve been running into problems creating STAC items for images that cross the antimeridian. The geometries for the images are coming out as spanning the width of the whole world

Re: [gdal-dev] Trouble reprojecting feature that crosses antimeridian

>From what I could tell, you are attempting to re-project a bounding box across the antimeridian. Here is one way to handle that ( https://pyproj4.github.io/pyproj/stable/api/transformer.html#pyproj.transformer.Transformer.transform_bounds ): >>> import shapely.geometry >>> from pyproj import Tran

[gdal-dev] Gitpod workspace with Ubuntu GDAL

Gitpod workspace with Ubuntu GDAL How to open a Gitpod machine with the version of GDAL in the Ubuntu software library. 1. Point browser at https://gitpod.io/#https://github.com/OSGeo/gdal 2. Login with Github credentials 3. In a couple of minutes the gitpod linux mac

[gdal-dev] Trouble reprojecting feature that crosses antimeridian

Hi, I’ve been running into problems creating STAC items for images that cross the antimeridian. The geometries for the images are coming out as spanning the width of the whole world (from -180 to +180 degrees). With the help of the author of the tool I was using to create the STAC items (rio-st

Re: [gdal-dev] Errors when reading large xlsx files

On Tue, 29 Mar 2022, Dirk Vanden Boer wrote: Scanning through the file, it turns out 2 lines actually have a value in the eight column, that's why the column is present, it doesn't have a header for that column however. So I have 2 questions: - does the error impact the returned data? - Is ther

Re: [gdal-dev] Errors when reading large xlsx files

Le 29/03/2022 à 20:29, Dirk Vanden Boer a écrit : > The effect will at least be to ignore any rows for which this message was raised - the function is unconditionally exited after the error is raised, before a new feature is added to the current layer. So do I understand correctly that for fi

Re: [gdal-dev] Errors when reading large xlsx files

> The effect will at least be to ignore any rows for which this message was raised - the function is unconditionally exited after the error is raised, before a new feature is added to the current layer. So do I understand correctly that for files containing roughly more than 10 lines, rows tha

Re: [gdal-dev] Errors when reading large xlsx files

> does the error impact the returned data? The effect will at least be to ignore any rows for which this message was raised - the function is unconditionally exited after the error is raised, before a new feature is added to the current layer. > Is there a way to suppress this error without disab

Re: [gdal-dev] The Not Rocket Science Rule Of Software Engineering

Le 29/03/2022 à 14:45, Andrew C Aitchison a écrit : I have been reading The Not Rocket Science Rule Of Software Engineering https://graydon2.dreamwidth.org/1597.html which is:    automatically maintain a repository of code    that always passes all the tests Does https://github.com/OSG

Re: [gdal-dev] The Not Rocket Science Rule Of Software Engineering

Andrew C Aitchison writes: > I have been reading The Not Rocket Science Rule Of Software Engineering > https://graydon2.dreamwidth.org/1597.html > which is: >automatically maintain a repository of code >that always passes all the tests > > Does https://github.com/OSGeo/gdal have

[gdal-dev] The Not Rocket Science Rule Of Software Engineering

I have been reading The Not Rocket Science Rule Of Software Engineering https://graydon2.dreamwidth.org/1597.html which is: automatically maintain a repository of code that always passes all the tests Does https://github.com/OSGeo/gdal have a branch with this property ? If we do

Re: [gdal-dev] Errors when reading large xlsx files

Scanning through the file, it turns out 2 lines actually have a value in the eight column, that's why the column is present, it doesn't have a header for that column however. So I have 2 questions: - does the error impact the returned data? - Is there a way to suppress this error without disabling

Re: [gdal-dev] Errors when reading large xlsx files

Hi Dirk, > I do notice when I open the file in excel and select everything, the eight column in the file is empty but also gets selected. It looks like that's the key here. The code you identified gets hit if GDAL encounters a row with more populated columns than the previous one, and if the pro

[gdal-dev] Errors when reading large xlsx files

Hi, When reading xlsx files that contains a lot of lines gdal reports the following error multiple times: | Adding too many columns to too many existing features It comes from the the xlsx driver: GIntBig nFeatureCount = poCurLayer->GetFeatureCount(false); if( nFeatureCount > 0 && static_cast