Le 25/04/2024 à 00:39, Andrew C Aitchison via gdal-dev a écrit :
On Wed, 24 Apr 2024, Even Rouault via gdal-dev wrote:
A future TileDB version will remove various deprecated API that the
GDAL TileDB driver currently uses.
https://github.com/OSGeo/gdal/pull/9725 migrates away from those
depr
On Wed, 24 Apr 2024, Even Rouault via gdal-dev wrote:
A future TileDB version will remove various deprecated API that the GDAL
TileDB driver currently uses. https://github.com/OSGeo/gdal/pull/9725
migrates away from those deprecated APIs, but that causes the minimum
requirement from TileDB t
Not knowing any detail about TileDB, I find good this bump in GDAL 3.9.0,
that is already changing many other dependency minimum versions.
On Wed, 24 Apr 2024 at 20:45, Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Hi,
>
> A future TileDB version will remove various deprecated AP
Hi,
A future TileDB version will remove various deprecated API that the GDAL
TileDB driver currently uses. https://github.com/OSGeo/gdal/pull/9725
migrates away from those deprecated APIs, but that causes the minimum
requirement from TileDB to go from 2.7 to 2.15. It would probably be
wise to
Le 24/04/2024 à 15:00, Michael Sumner a écrit :
Or a grouping function that returned the cell index for neighbours and
weighting that are involved in whatever calculation summary is wanted.
That doesn't seem super user friendly, as users would still be left to
do the raster value extraction and
Or a grouping function that returned the cell index for neighbours and
weighting that are involved in whatever calculation summary is wanted.
Maybe the warper could return this as a starting point rather than doing
the "task at hand". ?
On Wed, Apr 24, 2024 at 8:51 PM Even Rouault via gdal-dev
Hi,
I guess this discussion, and past similar ones, calls for an
enhancement. A new API function, like CPLErr
GDALRasterInterpolateAtPoint(GDALRasterBandH, double dfPixel, double
dfLocation, GDALRIOResampleAlg eInterpolation, double *pdfValue), that
could be used by a new mode of gdallocation
Hi Javier
I regularly use PROJ for that. It’s a bit of a hack but it works. Here’s a
demonstration using the DVR90_2023 geoid. The lower left grid point is at
(7,53.5) and the horizontal grid spacing is 0.1 degree. Below I first get the
actual grid values at two adjacent grid points and then la
Hi,
How about making a VRT file with doubled pixel size by applying your favourite
resampling method and then making a query from the VRT file with
gdallocationinfo?
-Jukka Rahkonen-
Lähettäjä: gdal-dev Puolesta Javier Jimenez
Shaw via gdal-dev
Lähetetty: keskiviikko 24. huhtikuuta 2024 11.3
I think it is not QGIS 3 compatible. It is very old (yes, I tried to
install from the zip,.. and failed)
On Wed, 24 Apr 2024 at 10:51, Paul Harwood wrote:
> If you want to do it in QGIS ...
>
> https://plugins.qgis.org/plugins/rasterinterpolation/
>
> On Wed, 24 Apr 2024, 09:33 Javier Jimenez Sh
If you want to do it in QGIS ...
https://plugins.qgis.org/plugins/rasterinterpolation/
On Wed, 24 Apr 2024, 09:33 Javier Jimenez Shaw via gdal-dev, <
gdal-dev@lists.osgeo.org> wrote:
> Hi
>
> I would like to read in QGIS or GDAL an interpolated value in a DSM (well,
> actually it is a geoid mode
Hi
I would like to read in QGIS or GDAL an interpolated value in a DSM (well,
actually it is a geoid model, but it is the same behaviour). See that I do
not want the pixel value, but the linear interpolation among the neighbour
pixels, assuming that the pixel value is in the center of the pixel.
F
12 matches
Mail list logo
