+1 Frank
On Wed, Oct 11, 2023 at 12:39 PM Rahkonen Jukka via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> +1
>
> -Jukka Rahkonen-
>
> -Alkuperäinen viesti-
> Lähettäjä: gdal-dev Puolesta Howard
> Butler via gdal-dev
> Lähetetty: keskiviikko 11. lokakuuta 2023 19.14
> Vastaanottaja: gdal
Carsten,
The gdal_rasterize command allows you to "burn in" polygons from an OGR
supported datasource into an existing raster. If your raster is a 3 band
RGB file, you could use --burn 100 150 200 to burn in the RGB value
(100,150,200). This will only work if the raster format you are using
sup
Carsten,
gdal_rasterize definitely supports burning into existing files.
I'm not sure about the configuration of your raster -- some formats are not
updatable-in-place, but the limitation isn't in gdal_rasterize.
Best regards,
Frank
On Tue, Mar 19, 2024 at 8:42 AM Carsten Lockenkötter <
carsten
Even,
I'm actually surprised that it is considered impractical to make some/most
drivers thread safe (read-only) natively and I thought key ones already
were mostly there in the past though I'm not so confident in my memory.
Looking through the GTiff code I find myself not able to work out where
On Fri, Sep 6, 2024 at 6:35 PM Even Rouault
wrote:
> Looking through the GTiff code I find myself not able to work out where
> locking is done and how we are managing the directory loading/switching as
> block reads are done.
>
> No locking is done. To be noted that the logic of TIFF directory
>
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
+1 Frank
On Mon, Dec 9, 2024 at 9:35 AM Howard Butler via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> An emphatic +1!
>
> Howard
>
> > On Dec 9, 2024, at 8:26 AM, Rahkonen Jukka via gdal-dev <
> gdal-dev@lists.osgeo.org> wrote:
> >
> > +1
> >
> > -Jukka Rahkonen-
> >
> > -Alkuperäinen vies
+1 Frank
On Mon, Dec 9, 2024 at 9:35 AM Howard Butler via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> +1 Howard
>
> On Dec 9, 2024, at 6:09 AM, Javier Jimenez Shaw via gdal-dev <
> gdal-dev@lists.osgeo.org> wrote:
>
> +1 Javier
>
> On Mon, 9 Dec 2024 at 13:05, Rahkonen Jukka via gdal-dev <
> gd
+1 Frank
On Thu, Jan 2, 2025 at 1:00 PM Sean Gillies via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> +1 and a happy new year to all!.
>
> On Thu, Jan 2, 2025 at 7:54 AM Even Rouault via gdal-dev <
> gdal-dev@lists.osgeo.org> wrote:
>
>> Hi,
>>
>> Happy New Year to everyone!
>>
>> PSC,
>>
>> GDA
Even,
I have no objection. FWIW, Seth who wrote this is actively working on CUDA
image warping work these days!
Best regards,
Frank
On Thu, Mar 6, 2025 at 1:08 PM Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> ==> https://github.com/OSGeo/gdal/pull/11929
>
> --
> http://www.sp
+1 Frank
On Mon, Mar 3, 2025 at 11:33 AM Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> +1 Even
>
> Le 03/03/2025 à 17:30, Daniel Morissette via gdal-dev a écrit :
> > Hi PSC members,
> >
> > I would like to nominate Michael Smith to become a member of the GDAL
> > Project Steerin
Patrik,
I have no objection to such a proposal, but in my experience with specific
NITF based product profiles it is often not worth trying to support
completely based on write support built into the GDAL drivers themselves.
For producing NCDRD compliant NITF files our approach at Planet has been
Michael,
If you were depending on -rpc to force use of the RPC method instead of
geotransforms for instance, it might be sufficient to pass -to METHOD=RPC
to things that take transformer options.
Best regards,
Frank
On Fri, Jul 18, 2025 at 11:39 AM Scott via gdal-dev <
gdal-dev@lists.osgeo.org>
13 matches
Mail list logo
