Re: [gdal-dev] clipping with an irregular polygon with gdal.VectorTranslate

2021-03-07 Thread Brad Hards
Perhaps ogr2ogr -clipsrc polygon.shp -f MVT If that doesn't do what you want, you might need to provide more info, including a full description of the source data, the clipping polygon you want to use, what you expect to happen, and what happens instead. Brad _

[gdal-dev] clipping with an irregular polygon with gdal.VectorTranslate

2021-03-07 Thread MRRAJESH
Developers, I am trying to set the "-clipsrc" with bbox, it is working as expected. ogr2ogr -clipsrc -9943695.99544 5321548.895035 -9943537.149741 5321390.049336 -f MVT But how can I set a "-clipsrc" with an irregular polygon? Any other ways? Regards, Rajesh -- Sent from: http://osgeo-

Re: [gdal-dev] Is it possible to switch warnings off?

2021-03-07 Thread Joaquim Manuel Freire Luís
Thanks Even e Mateusz It is the same gdal lib in both cases. The only other one I have is sheltered in OSCeo4W. And I had found where the messages are coming from but it's weird that they are printed in one case and not the other. I guess some internal setting that doesn't get set when called v

Re: [gdal-dev] Is it possible to switch warnings off?

2021-03-07 Thread Even Rouault
Joaquim, I suspect you are not testing with the same GDAL version with your gdalinfo shell invokation or within julia. With the C API, you can shut down warnings and errors with CPLPushErrorHandler(CPLQuietErrorHandler); ... CPLPopErrorHandler(); You can install a custom error handler that

Re: [gdal-dev] Is it possible to switch warnings off?

2021-03-07 Thread Mateusz Loskot
On Sun, 7 Mar 2021 at 21:42, Joaquim Manuel Freire Luís wrote: > > I have this strange case where some warnings come from don’t know where. > [...] > Warning 1: The dataset has several variables that could be identified as > vector fields, but not all share the same primary dimension. Consequentl

[gdal-dev] Is it possible to switch warnings off?

2021-03-07 Thread Joaquim Manuel Freire Luís
Hi, I have this strange case where some warnings come from don't know where. >From a shell command (cmd but it doesn't matter) all fine gdalinfo AQUA_MODIS.20020717T135006.L2.SST.nc Driver: netCDF/Network Common Data Format Files: AQUA_MODIS.20020717T135006.L2.SST.nc Size is 512, 512 Metadata:

Re: [gdal-dev] building gdal-3.3.0-dev with proj free(): invalid pointer

2021-03-07 Thread Even Rouault
Chris, two version of libproj are involved: chris@jacie:~$ ldd /usr/local/bin/gdalinfo | grep libproj libproj.so.22 => /usr/local/lib/libproj.so.22 (0x7f3a6cecc000) libproj.so.19 => /usr/local/lib/libproj.so.19 (0x7f3a659da000) That's definitely the cause of the crash. It is illegal

[gdal-dev] building gdal-3.3.0-dev with proj free(): invalid pointer

2021-03-07 Thread chris english
Hi. Been building and rebuilding gdal-3.3.0-dev and arrive at this output: chris@jacie:~$ gdalinfo --version GDAL 3.3.0dev-96fab634a5, released 2021/03/02 free(): invalid pointer Aborted two version of libproj are involved: chris@jacie:~$ ldd /usr/local/bin/gdalinfo | grep libproj libproj.so.22