Even,
Thanks for having a look at the data, I see what you mean about the NODATA
value in the COGs. They are *supposed* to have an internal NODATA value set
on the band, but they actually do not. I set NODATA with gdal_edit and the
resampling method no longer affects overview usage.
For us, this
Even,
On Wed, Nov 4, 2020 at 3:40 AM Even Rouault
wrote:
> Sean,
>
> What GDN stands for: GDAL Dataset Name ?
>
Yes. I just made that up on the spot. Think of it as a GDAL or FOSS4G
specific namespace. Until now, GDAL has been using symbols like WFS: and
HDF5: in the global namespace, which cau
> > Another particularity we have in GDAL is that the dataset name might be
> > almost
> > anything. Most of the time, it is a regular file path, or some /vsi path.
> > But
> > sometimes, it can be JSON content (the GeoJSON driver accepts the content
> > to
> > be directly provided as the dataset n
Angus,
The difference of behaviour between my test case and yours is that yours has a
set on the VRTRasterBand, and the source COGs don't have that
value. In this situation a key optimization used by the VRT driver is
disabled, and there's a fallback to code that won't make use of the source
Sean,
What GDN stands for: GDAL Dataset Name ?
> The URN or GDN version might look something like the thing below, using ?+
> and ?= [3] to identify vsi and driver option sections
>
> gdn:curl:csv:
> example.com/foo.csv?a=1&b=2?+max_retry=5?=autodetect_type=yes&keep_geom_colu
> mns=no
The http
Hello,
I am using gdal version 2.4.4 in my c# app.
As a part of my project I am creating pdf with gdal_translate command. GDAL
translate command is
"gdal_translate --config SHAPE_ENCODING "utf-8" -of PDF -tr 0.001 0.001 -a_srs
EPSG:3765 Granice.tif Sisacko_moslavacka_zupanija3.pdf -co
OGR_DATA
