Thanks for trying out accessing FlatGeobuf via http.
For the record I've been slightly aware of this particular efficiency
problem and I aim to improve it when I can get to it, because this is a use
case I definitely want FlatGeobuf to grab the first place. :)
/Björn
Den tors 24 okt. 2019 kl 20:
Nick,
That's lots of info and questions. Just from a quick overview, it looks
like you need to set your ground control points to the correct lat/lon
coordinates (or whatever coordinate system you want to use) and you also
need to set your image's projection. You can do both of these with the
I included as much detail as I could. I put links to all images because I
wasn't sure they would embed in the email list. Experienced programmer but
brand new to gdal.
Overview: My drone is taking multiple high resolution images that slightly
overlap each other in order to view 1 large high resolu
Hi,
I want to use gdal_contour to generate shapefile contours which is
pretty straight forward except I'm working with coastal relief data that
has both elevation and bathymetry. I only want contours for the bathymetry.
I tried setting the -off -5 and -i -5 with the idea that this would
star
Hi Marco,
Am 30.10.2019 um 09:46 schrieb Marco:
>
> Indeed Buffer 0 won't do any good on self intersections. Thats just not
> the way to repair them.
But many users act like this:
1. Get a warning about invalid geometry,
2. run Buffer 0,
3. Warning about invalid geometry is gone.
Again, this is
I've, unsuccessfully, tried to reproduce your issue with the following script:
-
from osgeo import gdal
import concurrent.futures
def worker(in_f, out_f):
gdal.Unlink(out_f)
gdal.Warp(out_f, in_f, options = '-co COMPRESS=DEFLATE -co TILED=YES -ts
2048 2048')
jobs = []
for i in ran
On mercredi 30 octobre 2019 12:05:01 CET Patrick Young wrote:
> Hi all,
>
> I've been experiencing some behavior using the GDAL python bindings where I
> am occasionally seeing what appears to be random blocks of the tiff being
> unwritten in geotiffs I've pushed to S3. a small block(s) in one of
Hi all,
I've been experiencing some behavior using the GDAL python bindings where I
am occasionally seeing what appears to be random blocks of the tiff being
unwritten in geotiffs I've pushed to S3. a small block(s) in one of the
bands will be all zeros while everywhere else is good.
My setup is
On mercredi 30 octobre 2019 15:52:54 CET Jose Gomez-Dans wrote:
> Hi,
>
> I'm mosaicking a large number of small tiles using the GDAL python bindings
> (python 3.7, gdal 3.0.1, but also tested on 2.4.2). Code is something like
>
> ```
>
> *output_fname = "/something/or/other.vrt"*
> *fnames = ["
Hi,
I'm mosaicking a large number of small tiles using the GDAL python bindings
(python 3.7, gdal 3.0.1, but also tested on 2.4.2). Code is something like
```
*output_fname = "/something/or/other.vrt"*
*fnames = ["file1.tif", ..., "fileN.tif"]*
*dst_ds = gdal.BuildVRT(output_fnam
Tobias,
Indeed Buffer 0 won't do any good on self intersections. Thats just not
the way to repair them.
Hence I wrote "Buffer 0 on INVALID geometries IMHO can lead to good
results depending on the /nature of the invalidity/. To my experience
/repeating points,//wrong coordinate ordering and
On mercredi 30 octobre 2019 00:49:24 CET TUELLER, SHAYNE R CIV USAF AFMC 519
SMXS/MXDEC wrote:
> All,
>
> We're currently using GDAL 2.3.1 on Windows to develop a shapefile editor
> for our application.
>
> We're seeing a crash in our application when we call GDALClose() on a
> dataset/layer tha
12 matches
Mail list logo
