Moises,
In my humble opinion it makes sense to follow this approach if the separator is not clear, but in this case the first CSV line contains like 10 semicolons (the real separator) and just one comma. I believe that the actual behaviour could be improved adding some way of checking the most repeated separator. What do you think?
That seems reasonable. You may file an enhancement ticket about that, with the header of the CSV file on which you hit the issue as an illustration. We should also probably emit a CE_Warning visible even in production builds when such ambiguous situation arises.
Even
-- *Moises Calzado* Support Engineer +34671264286 | mcalz...@carto.com | CARTO <https://www.carto.com/> <https://spatial-data-science-conference.com/2023/london/> _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
-- http://www.spatialys.com My software is free, but my time generally not.
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
