> On Dec 4, 2023, at 4:51 PM, Daniel Evans via gdal-dev
> wrote:
>
> Agree with Kurt - it's always struck me as a little surprising that it was
> optional.
GDALs bindings predate Numpy. We spanned over the Numeric/Numarray transition
IIRC too. __
Hi Greg,
I'd like to better understand your concerns, so I have a couple of questions
and remarks:
1. do the platforms you care about package Firefox, librsvg, or any other
popular software that's using Rust?
2. do you have any reasons to believe that numpy will require Rust in the
future? I s
Hi,
I declare this motion passed with +1 from PSC members JavierJS, KurstS,
HowardB, JukkaR and me.
Even
Le 01/12/2023 à 16:32, Even Rouault via gdal-dev a écrit :
Hi,
Motion: adopt RFC 98: Build requirements for GDAL 3.9
https://github.com/OSGeo/gdal/pull/8802
Starting with my +1,
Even
Thomas Knudsen writes:
> Den tirs. 5. dec. 2023 kl. 02.15 skrev Greg Troxel via gdal-dev <
> gdal-dev@lists.osgeo.org>:
>> Building the
>> rust compiler requires the *immediately preceding* compiler, which seems
>> unprecented, and I don't understand how people can think that's ok
>
> I don't th
You can use the -spat + (-clipsrc or -clipdst) switches of ogr2ogr
Le 05/12/2023 à 14:57, Jan Wolski via gdal-dev a écrit :
Hi,
I'm creating MVT tilesets for the ETRS-TM35FIN tiling scheme using
GDAL/OGR. I'm prototyping with ogr2ogr but later I will be using
Python bindings to create the pro
Hi,
I'm creating MVT tilesets for the ETRS-TM35FIN tiling scheme using
GDAL/OGR. I'm prototyping with ogr2ogr but later I will be using Python
bindings to create the production workflow.
Is there a way to limit the geographic extent of where the MVT driver
creates tiles? By default it seems to cr
