On Wednesday, 29 September 2021 9:37:57 AM AEST Chastain, Raymond Lee (MU-
Student) wrote:
> Process is very simple
>
> 1. Take our tiles and build a virtual raster:
> gdalbuildvrt -r lanczos -resolution HIGHEST output.vrt -input_file_list
> input_file_list.txt 2. Convert our virtual raster to
Process is very simple
1. Take our tiles and build a virtual raster:
gdalbuildvrt -r lanczos -resolution HIGHEST output.vrt -input_file_list
input_file_list.txt
2. Convert our virtual raster to a GeoTIFF:
3. gdal_translate -of GTIFF ./output.vrt ./output.tif
The artifacts occur with all
I changed the Dockerfile following the same steps as the author of this
post (https://github.com/OSGeo/gdal/issues/4467) did to install GDAL (but
using version 2.2.3) and it worked fine. Still don't know why the way I did
previously is not working anymore but now everything is ok. Thank you!
Em se
Le 28/09/2021 à 09:04, Rahkonen Jukka (MML) a écrit :
Hi,
Even Rouault wrote:
> One option to avoid both issues would be for the service to publish
> DescribedBy links at the collection level that would point to a XML
> schema (using a GML Simple Feature schema profile, such as the one
> u
Hi,
Even Rouault wrote:
> One option to avoid both issues would be for the service to publish
> DescribedBy links at the collection level that would point to a XML
> schema (using a GML Simple Feature schema profile, such as the one
> understood by the GML driver) or a JSON schema (not "too" comp
