I also forgot to mention that I see 1000 instances of this error... I'm not
sure if it's related.
ERROR 1: String buffer too small
I tried setting CPL_DEBUG to "OSM" and didn't see obvious errors. The output
looks like this:
OSM: OGR_INTERLEAVED_READING = 1
OSM: For layer points, new max size
I'm trying to extract water vectors from OSM using my own local Overpass API
server and OGR. It works for the most part, but there are some water features
missing in my output. One particularly large omission is Lake Huron.
I put an example OSM file here:
https://s3.amazonaws.com/gdal-osm-data/
On mercredi 12 juillet 2017 17:24:44 CEST Dmitry Baryshnikov wrote:
> Hi Johan,
>
> Just use CPL_VSIL_ZIP_ALLOWED_EXTENSIONS to add new extension and enjoy.
>
> CPLSetConfigOption(CPL_VSIL_ZIP_ALLOWED_EXTENSIONS, "sg-grd-z");
>
> Or in ogrinfo use option -config CPL_VSIL_ZIP_ALLOWED_EXTENSIONS s
Hi,
I have tried to use GDAL 2.2 in OTB. I have some issues with
output images in the ENVI format. Some of the images I use have :
A geotransform with an origin, for instance : geotransform =
{10, 1, 0, 10, 0, 1}
No map projection (the image c
Hi Johan,
Just use CPL_VSIL_ZIP_ALLOWED_EXTENSIONS to add new extension and enjoy.
CPLSetConfigOption(CPL_VSIL_ZIP_ALLOWED_EXTENSIONS, "sg-grd-z");
Or in ogrinfo use option -config CPL_VSIL_ZIP_ALLOWED_EXTENSIONS sg-grd-z
Best regards,
Dmitry
12.07.17 17:18, Johan Van de Wauw пишет:
Hi a
Hi all,
Saga GIS introduced a new file format .sg-grd-z [1] which actually is
a zipfile containing the normal files encountered in saga gis (*.sgrd
; *.sdat; and optionally *.mgrd ).
In fact, if you rename the .sg-grd-z file you can already open it using vsizip
eg
cp Landgebruik_def_watem.sg-grd-
Hi Maning,
There was a 2016 summer of code proposal to implement GeoJSON text
sequences but it didn't pan out. The Fiona package (for Python) is the only
thing in the GDAL ecosystem that does this right now, as far as I know.
See https://toblerity.org/fiona/cli.html#load and disregard the outdate
