A belated +1!
On Thu, Sep 12, 2024 at 9:19 PM Howard Butler via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Declaring this motion passed with +1s from Sean, Jukka, Daniel, Javier,
> Kurt, and Howard. We technically needed the contract active to pay Even's
> previous invoice so I am fast-tracki
Declaring this motion passed with +1s from Sean, Jukka, Daniel, Javier, Kurt,
and Howard. We technically needed the contract active to pay Even's previous
invoice so I am fast-tracking the vote as it appears non-controversial ;)
> On Sep 11, 2024, at 10:50 PM, Scott via gdal-dev
> wrote:
>
>
Thanks Even!
The NETCDF file(s) I'm working with have hundreds of sub data sets.
Initially, I was breaking out all of them to .vrt's as you suggested,
but it got a bit messy. Counting the sub-datasets with gdalinfo
iteratively then using gdal_create -bands N was a lot cleaner.
Passing dozens
Scott,
# add another tif to band 2 and add meta data for it:
gdalwarp -q -srcband 1 -dstband 2 -t_srs EPSG:4326 src2.tif result.tif
BAND1 is lost at that stage. gdalwarp must override the metadata of the
output dataset with the one of src2.tif.
Presumably it should instead merge them, using
Greetings,
I need some help with gdal_edit. If I add meta data each time I add a
band to a raster, only the last meta edit is present. Here's the
scenario GDAL 3.9.1, gdal_edit.py is 3.6.2, Debian 12:
# create empty 2-band raster with existing prototype:
gdal_create -if src1.tif -bands 2 resu
+100
On Thu, Sep 12, 2024 at 6:15 AM Sean Gillies via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Absolutely yes +1
>
> On Wed, Sep 11, 2024, 8:24 PM Howard Butler via gdal-dev <
> gdal-dev@lists.osgeo.org> wrote:
>
>> PSC,
>>
>> I am motioning to renew Even's maintainer contract through the GD
+1 Javier
On Thu, 12 Sept 2024 at 08:27, Rahkonen Jukka via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> +1
>
> -Jukka Rahkonen-
>
> -Alkuperäinen viesti-
> Lähettäjä: gdal-dev Puolesta Even
> Rouault via gdal-dev
> Lähetetty: keskiviikko 11. syyskuuta 2024 22.27
> Vastaanottaja: gdal-d
Mika,
Le 12/09/2024 à 09:22, Heiskanen Mika (FMI) via gdal-dev a écrit :
*
Ah, and one thing I realized is that OGRSpatialReference isn't
thread-safe, so I've also added an optional SetThreadSafe() on it,
to also use a per-instance mutex in multi-threaded scenarios (cf
commit
Absolutely yes +1
On Wed, Sep 11, 2024, 8:24 PM Howard Butler via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> PSC,
>
> I am motioning to renew Even's maintainer contract through the GDAL
> Sponsorship Program that is hosted by NumFOCUS for another year.
>
> /me starts with a +1
>
> Howard
> ___
Hi,
Your suggestion to utilize the additional layer BBOXes if they exist feels good
to me, and better than to use the first advertised SRS from the root level.
Beyond that what can be done with parsing the GetCapabilities is limited in my
mind, because all projections which are supported may no
So we remain at the point that there is no good method that, using only
GDAL, will allow to fully use the WMS service without additional work
related to XML parsing...?
Best,
Michał Kowalczuk
wt., 10 wrz 2024 o 17:06 Michał Kowalczuk
napisał(a):
> A sample from your link:
>
>
>
>
>
>
>
>
>
>
>
*
Ah, and one thing I realized is that OGRSpatialReference isn't thread-safe, so
I've also added an optional SetThreadSafe() on it, to also use a per-instance
mutex in multi-threaded scenarios (cf commit
https://github.com/OSGeo/gdal/pull/10746/commits/c7e1862273dd018e58a01f25b21fdff6dbfdd1cd)
12 matches
Mail list logo
