[gdal-dev] S-57 driver Generic attribute DSNM

Hello, After reading this documentation concerning the S-57 driver : https://gdal.org/drivers/vector/s57.html I thought the attribute DSNM ( Dataset name) should be defined on all features, no ? But on the source code, the method S57GenerateStandardAttributes (s57featuredefns.cpp) always a

[gdal-dev] Gdal and large tile sets

Hi, I'm using gdal to reproject a set of web-mercator tiles to Quadralateralized-Spherified-Cube (QSC) for displaying data like LandSat on a 3D globe. With some difficulty, I got this working. My work flow is: 1 - georeference the tiles using translate 2 - build a vrt from the georeferenced tiles

Re: [gdal-dev] Motion: promote GDAL 3.1.0 RC2

On 2020-04-30 05:34, Even Rouault wrote: Hi, Having adressed the few issues raised about RC1, I believe RC2 is good to go. Motion: promote GDAL 3.1.0 RC2 to final 3.1.0 +1 Daniel -- Daniel Morissette Mapgears Inc T: +1 418-696-5056 #201 ___ gda

Re: [gdal-dev] Motion: promote GDAL 3.1.0 RC2

On Thu, 30 Apr 2020 at 11:34, Even Rouault wrote: > > Having adressed the few issues raised about RC1, I believe RC2 is good to go. > Motion: promote GDAL 3.1.0 RC2 to final 3.1.0 > Starting with my +1 > Even +1 Mateusz ___ gdal-dev mailing list gdal-de

Re: [gdal-dev] Motion: promote GDAL 3.1.0 RC2

On Thu, Apr 30, 2020 at 4:35 AM Even Rouault wrote: > Hi, > > > > Having adressed the few issues raised about RC1, I believe RC2 is good to > go. > > > > Motion: promote GDAL 3.1.0 RC2 to final 3.1.0 > > > > Starting with my +1 > > > > > +1 Norman ___ g

Re: [gdal-dev] Motion: promote GDAL 3.1.0 RC2

> On Apr 30, 2020, at 4:34 AM, Even Rouault wrote: > > Hi, > > Having adressed the few issues raised about RC1, I believe RC2 is good to go. > > Motion: promote GDAL 3.1.0 RC2 to final 3.1.0 > > Starting with my +1 +1 Howard ___ gdal-dev maili

Re: [gdal-dev] GDAL memory management

Thanks for your answer, Even. I would want that, yes, but I was prepared for the answer being no :(. I also though computational complexity would be the problem, but I checked with VTune and it points the other way (malloc, free, realloc). Moreover, performance is worse each time I execute the sa

Re: [gdal-dev] Motion: promote GDAL 3.1.0 RC2

On 2020-04-30 6:34 a.m., Even Rouault wrote: Motion: promote GDAL 3.1.0 RC2 to final 3.1.0 +1 jeff -- Jeff McKenna MapServer Consulting and Training Services https://gatewaygeo.com/ ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists

Re: [gdal-dev] VRT file and CSV source with strange name: "Failed to open datasource"

My error, I had a carriage return. I had CSV:/vsicurl_streaming/https://docs.google.com/spreadsheets/d/e/2PACX-1vTwuYdMYS7vKJnTETwycLEGPFG2pwhxIlPMeChXuluRLjApQwhzEy_gUgsw_9lVRrAmGhAHWEj9LDV7/pub?gid=0&single=true&output=csv and not CSV:/vsicurl_streaming/https://docs.google.com/spreadsheets/d/

[gdal-dev] Motion: promote GDAL 3.1.0 RC2

Hi, Having adressed the few issues raised about RC1, I believe RC2 is good to go. Motion: promote GDAL 3.1.0 RC2 to final 3.1.0 Starting with my +1 Even -- Spatialys - Geospatial professional services http://www.spatialys.com ___ gdal-dev mailing l

Re: [gdal-dev] VRT file and CSV source with strange name: "Failed to open datasource"

> and run "ogrinfo --debug ON input.vrt", I have Works for me. On 2.4, I've had to add -ro to prevent the driver from trying first update mode and emitted warning/errors, but even without it, it managed to open the datasource Tip: with the VRT you can actually put a nice layer name. Put the la

Re: [gdal-dev] GDAL memory management

Jesús, > > I have been working with C/C++ and GDAL with GEOS for some time now and I > have a question about GDAL memory management. > > I wonder if there are any memory management options or tips to control > allocations and deallocations in the library since we are noticing > performance probl