Even Rouault

> With muparser "sum(X, Y)" we get `X[1] + Y[1], X[2] + Y[2]`, but with builtin "sum" we are getting `X[1] + Y[1], Y[2]` any suggestion on what we should...

> I implemented the muparser behavior intentionally to match what numpy would do in this situation. That's why the inputs must have the same number or bands, or a single...

> Because the gpkg_spatial_ref_sys has a single row for each srs_id (primary key) in a GeoPackage, the definition of Epoch for a GeoPackage is limited to one Epoch date per...

> Is there any particular reason why it's not supported by XLS/XLSX driver? Such built-in logic needs to be implemented in each driver and thus has a initial and long...

> While CSV supports geography type. what makes you think so ? OGR itself (the abstraction) doesn't kow about PostGIS geography vs geometry, only the PostGIS driver does. The CSV...

@geographika Yes definitely a good idea! There is so much jargon that can be explained

instead of listing all dependent libraries, the use of the --only-deps flag might help. Something like: "conda install -c conda-forge --only-deps libgdal libgdal-hdf4 libgdal-hdf5 libgdal-netcdf libgdal-pdf libgdal-openjpeg"

> I've come across this issue working with EUMETSAT's FCI (MTG) files can you provide a link to it ?

Changing the output data type might invalidate metadata. When you just do direct NITF -> NITF without options (but driver creation options), the NITF driver is able to retrieve information...

This was discussed in https://github.com/OSGeo/gdal/issues/8440#issuecomment-1731195918 . There are pros & cons, and this would be a change with breaking potential