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
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
/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
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
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
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