On vendredi 25 janvier 2019 11:59:55 CET Sean Gillies wrote:
> Hi Even,
>
> What will the impact be on spatial referencing stored in new datasets? For
> example, will users with GDAL 2.5 run gdal_translate and write WKT2 into a
> GeoTIFF, thereby creating data that can't be opened using GDAL 2.4?
On vendredi 25 janvier 2019 14:36:23 CET Christoph Paulik wrote:
> Hi,
>
> We have a VRT file in which some regions overlap. As far as I can tell
> a gdal_translate of the VRT into a GTIFF just takes the value of the
> first file it encounters for a given target pixel.
Actually, this will be the
Hi,
you need to know your data spatial resolution and the pixel coordinates
corresponding to (Easting,Northing).
If GDAL cannot read the .emf file, try using ImageMagick:
convert image.emf my_raster.png
Then, you might try to create a worldfile my_raster.wld (See [0]).
The attached example is
Hi,
We have a VRT file in which some regions overlap. As far as I can tell
a gdal_translate of the VRT into a GTIFF just takes the value of the
first file it encounters for a given target pixel.
Is there a way to specify an averaging method for such cases e.g. take
the mean, max, min etc.?
If not
Thanks for the clarification.
On Jan 25, 2019, at 1:05 AM, Craig de Stigter
mailto:craig.destig...@koordinates.com>> wrote:
I didnt write it but I had to fiddle with the build scripts quite a bit for the
pytest refactor. Travis only supports Trusty (recently added Xenial, though I
don't think
