Thanks Even, I didn't realize that.
On Thu, Sep 19, 2024 at 5:26 PM Even Rouault
wrote:
>
> Le 20/09/2024 à 00:25, Norman Barker via gdal-dev a écrit :
>
> +1 The old RFCs were useful but as you can get them from the wayback
> machine that is fine.
>
> They are all at https://gdal.org/en/latest
Le 20/09/2024 à 00:25, Norman Barker via gdal-dev a écrit :
+1 The old RFCs were useful but as you can get them from the wayback
machine that is fine.
They are all at https://gdal.org/en/latest/development/rfc/index.html
too, aren't they?
--
http://www.spatialys.com
My software is free, but
+1 The old RFCs were useful but as you can get them from the wayback
machine that is fine.
On Thu, Sep 19, 2024 at 4:35 PM Daniel Baston via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> +1
>
> Dan
>
> On Thu, Sep 19, 2024 at 3:34 PM Javier Jimenez Shaw via gdal-dev
> wrote:
> >
> > I agree
> >
+1
Dan
On Thu, Sep 19, 2024 at 3:34 PM Javier Jimenez Shaw via gdal-dev
wrote:
>
> I agree
>
> On Thu, 19 Sept 2024, 20:35 Even Rouault via gdal-dev,
> wrote:
>>
>> Hi,
>>
>> I suggest we complete remove the content from
>> https://trac.osgeo.org/gdal/wiki. At this point, it is totally outdate
Motion passed with +1 from PSC members KurtS, JukkaR, JavierJS and me.
Le 11/09/2024 à 21:26, Even Rouault via gdal-dev a écrit :
Hi,
I move to approve RFC 101 "Raster dataset read-only thread-safety":
https://github.com/OSGeo/gdal/pull/10676
Starting with my +1,
The candidate implementatio
I agree
On Thu, 19 Sept 2024, 20:35 Even Rouault via gdal-dev, <
gdal-dev@lists.osgeo.org> wrote:
> Hi,
>
> I suggest we complete remove the content from
> https://trac.osgeo.org/gdal/wiki. At this point, it is totally outdated
> compared to gdal.org and useless for most people, and potentially
>
Hi,
I suggest we complete remove the content from
https://trac.osgeo.org/gdal/wiki. At this point, it is totally outdated
compared to gdal.org and useless for most people, and potentially
causing confusion if someone reaches it. People who would need to access
those outdated docs for their ou
Le 19/09/2024 à 15:59, Michał Kowalczuk via gdal-dev a écrit :
Hi,
After re-thinking this topic, I also came to conclusion that using
BoundingBox tags will not be a satisfactory solution for GDAL users.
Maybe it will better than current, but still poor...
In my opinion the most flexible soluti
Hi,
After re-thinking this topic, I also came to conclusion that using
BoundingBox tags will not be a satisfactory solution for GDAL users. Maybe
it will better than current, but still poor...
In my opinion the most flexible solution is to provide a list of supported
SRSs by a server, just like in
If your program uses threads, and you don't make sure to wait for their
termination before calling GDALDestroy, this could explain memory
corruption if they use GDAL TLS, while GDALDestroy() is cleaning the TLS
structures. I'll stop random guessing here.
And you can just get rid of the GDALDes
10 matches
Mail list logo
