Re: [gdal-dev] GEOTIFF with RAT - transformation unsuccessful (and related warning)

Il 20/12/24 12:59, Rahkonen Jukka via gdal-dev ha scritto: Hi, All GeoTIFF creation options are documented in https://gdal.org/en/stable/drivers/raster/gtiff.html. There is no creation option "CREATE_RAT=YES". There is also no configuration option --config RAT_PATH. Either the name of your f

[gdal-dev] Motion: adopt RFC 103 - OGR_SCHEMA open option

Hi, Motion: Adopt RFC 103: OGR_SCHEMA open option[1] I have updated the RFC [1] with: - updated JSON schema with field rename support - removed GDAL_DMD_OGR_SCHEMA_OPEN_OPTION_FLAGS (after talking to Even about using DMD_OPEN_OPTION_LIST instead) There is also a complete candidate impleme

[gdal-dev] Call for review on RFC 103: OGR_SCHEMA open option

evelopment/rfc/rfc103_schema_open_option.html [2] https://github.com/OSGeo/gdal/pull/11071 [3] see last commits: https://github.com/elpaso/gdal/commits/enhancement-gh10943-fields-schema-override/ -- Alessandro Pasotti w3: www.itopen.it ___ gdal-d

Re: [gdal-dev] Proposed RFC 8 amendment regarding (prohibited use of) generative AI tools

Il 09/10/24 00:55, Greg Troxel via gdal-dev ha scritto: ElPaso via gdal-dev writes: I have read the discussion on lwn and I must say that I am more in line with the debian position. My view is that code that comes out of generative AI should be viewed as an improper derived work, and lacking

Re: [gdal-dev] Proposed RFC 8 amendment regarding (prohibited use of) generative AI tools

Il 07/10/24 18:38, Even Rouault via gdal-dev ha scritto: Hi, I propose we update RFC 8 with the following changes: https://github.com/OSGeo/gdal/pull/10958 Can we enforce that? No (similarly we can't prevent someone from stealing copyrighted material from source code of proprietary software

Re: [gdal-dev] Formalizing GDAL "file name" syntax in an RFC?

Il 14/09/23 17:14, Sean Gillies ha scritto: Hi all, In https://github.com/OSGeo/gdal/pull/8155#issuecomment-1704923263 I think I see (for the first time?) the beginning of a specification of the syntax for GDAL "file names". I think it would be helpful if there was an RFC for this. I'm sure

[gdal-dev] Motion: adopt RFC 94: Numeric fields width/precision metadata

Hi, Motion: adopt RFC 94:  Numeric fields width/precision metadata  https://github.com/OSGeo/gdal/pull/7264 Rendered text view: https://github.com/OSGeo/gdal/blob/e19eda1db023abdaf2d24036aa2e167e99e35029/doc/source/development/rfc/rfc94_field_precision_width_metadata.rst Regards. -- Ales

[gdal-dev] Motion: adopt RFC89: SQL query logging callback

/elpaso/gdal/tree/rfc89_sql_logging_callback_implementation [3] https://github.com/elpaso/QGIS/tree/ogrprovider-sql-logging -- Alessandro Pasotti w3: www.itopen.it ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo

[gdal-dev] RFC89: sql logging callback

ine, we can now see which SQL is generated from the OGR/GDAL data providers. [1] https://github.com/elpaso/gdal/tree/rfc89_sql_logging_callback_implementation [2]  https://github.com/OSGeo/gdal/pull/6837 -- Alessandro Pasotti w3: www.itopen.it

Re: [gdal-dev] SortIncludes was Re: Motion: adopt RFC69 C/C++ Code Formatting

Il 24/11/22 10:55, Andrew C Aitchison ha scritto: On Thu, 24 Nov 2022, ElPaso wrote: Hi, Motion: Adopt RFC88: RFC69 C/C++ Code Formatting [1] I have updated the RFC [1] to use pre-commit and I have created a draft implementation of the pre-commit hook and the CI integration with a GH

[gdal-dev] Motion: adopt RFC69 C/C++ Code Formatting

I used a clang-format file I've found under gdal/scripts), but the biggest decision is wether proceed with an initial "Big Reformat" or an incremental one, my draft implementation supports both. Kind regards. [1] https://github.com/elpaso/gdal/blob/rfc69_cplusplus_formattin