Re: [gdal-dev] Assert due to stack corruption in FlatGeoBuf export

Our emails crossed. I am indeed testing with the latest flatbuffers now too. Agreed on the rest. On Fri, Feb 23, 2024 at 3:42 PM Even Rouault wrote: > Simon, > > did you try to update to the latest > https://github.com/google/flatbuffers/releases to see if that would solve > the issue ? If that

Re: [gdal-dev] Assert due to stack corruption in FlatGeoBuf export

Simon, did you try to update to the latest https://github.com/google/flatbuffers/releases to see if that would solve the issue ? If that worked, that would be the best way forward... Otherwise if the issue persists with the latest flatbuffers release, a (admitedly rather tedious) option woul

Re: [gdal-dev] Assert due to stack corruption in FlatGeoBuf export

I'm also testing a build that uses the latest *flatbuffers* 23.5.26, which is a drop-in replacement and does not require the *VerifyField* change, just in case the issue has been fixed since 2.0.6. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https:

Re: [gdal-dev] Assert due to stack corruption in FlatGeoBuf export

I was able to create a fork of 3.7.3 with just the *flatbuffers* replaced with the pre-3.6.x version (2.0.0). This seemed to only require changes to the version asserts and adding an *align* parameter to *Table::VerifyField()* to match the newer API. https://github.com/heavyai/gdal/tree/simon.eve

Re: [gdal-dev] gdalinfo and WMS: is there a way to pass credentials via CLI?

Thank you, it works great On Fri, 23 Feb 2024 at 18:27, Even Rouault wrote: > Hi, > > I haven't tested but you should be able to use any of the env variable > listed for CPLHTTPFetch() at > https://gdal.org/api/cpl.html#_CPPv412CPLHTTPFetchPKc12CSLConstList > > so here GDAL_HTTP_USERPWD > > gdal

Re: [gdal-dev] gdalinfo and WMS: is there a way to pass credentials via CLI?

Hi, I haven't tested but you should be able to use any of the env variable listed for CPLHTTPFetch() at https://gdal.org/api/cpl.html#_CPPv412CPLHTTPFetchPKc12CSLConstList so here GDAL_HTTP_USERPWD gdalinfo "WMS:http://wms.geobase.ca/wms-bin/cubeserv.cgi"; --config GDAL_HTTP_USERPWD user:pa

[gdal-dev] gdalinfo and WMS: is there a way to pass credentials via CLI?

Hi, is there a way to pass UserPwd parameter via a gdalinfo command? Is there a way to pass it, without creating an XML file? Something like this gdalinfo "WMS:http://wms.geobase.ca/wms-bin/cubeserv.cgi"; -UserPwd user:password Thank you -- ___ Andrea Borruso website: https://

Re: [gdal-dev] Reading PMTiles With Missing Tiles

Thanks Even! I got a much smaller reproduce case with data ready at https://github.com/OSGeo/gdal/issues/9288 I created the test case with `pmtiles extract --maxzoom 7 ...`, interestingly enough using a coarser zoom didn't surface the issue! Patrick On Fri, Feb 23, 2024 at 1:37 AM Even Rouault

Re: [gdal-dev] the /vsistdout mistery and the Update question

Hi Even, thanks for your answer. ok with /vsistdout/ I’m sure trying to finish the job. I’ve been documenting that, going through actions errors. But I’m not trying to incorporate anything new but only trying to let it clean from doubts I have from the beginning and I left for later. Now is th

Re: [gdal-dev] the /vsistdout mistery and the Update question

Abel, Le 23/02/2024 à 10:34, Abel Pau via gdal-dev a écrit : Hi, after reading https://gdal.org/user/virtual_file_systems.html#vsistdout-standard-output-streaming I have to say I don’t understand what it me

[gdal-dev] the /vsistdout mistery and the Update question

Hi, after reading https://gdal.org/user/virtual_file_systems.html#vsistdout-standard-output-streaming I have to say I don't understand what it means. I which cases it's used? Some example to consider? In the driver I have to do something with that? I have, copied from other, if (!STARTS_WITH(ps

Re: [gdal-dev] Reading PMTiles With Missing Tiles

Hi, this is likely a bug. I would need access to the file to investigate, ideally through /vsicurl, /vsis3, etc. . I don't have storage to host 300 GB. And possibly try to reduce the file size by removing upper zoom levels Even Le 23/02/2024 à 06:54, Patrick Young via gdal-dev a écrit : He