[gdal-dev] CSV driver inconsistent separator dealing to failures

Hello everyone, I'm trying to use ogr2ogr with a CSV file that uses semicolons as separator, but there is a field that contain one comma. The issue that I'm facing is that as it contains a comma, it originally takes the comma as separator, so it's not parsed correctly. However, when trying to

Re: [gdal-dev] Ogr2ogr CSV driver not handling correctly line breaks inside columns

ote: > >> Hi, >> >> >> >> Have you considered to output GeoJSONseq >> https://gdal.org/drivers/vector/geojsonseq.html instead of CSV, that for >> my mind is a workaround as a geodata format. Maybe JSON could handle your >> newlines by the same. >&g

Re: [gdal-dev] Ogr2ogr CSV driver not handling correctly line breaks inside columns

decoupling the layer GEOMETRY_NAME creation option with > CREATE_CSVT=YES > > Even > Le 04/05/2023 à 13:58, Moises Calzado via gdal-dev a écrit : > > Hi Robert! > > I think that we're losing a bit the main issue that we reported, as in > fact the problem is related with line breaks

Re: [gdal-dev] Ogr2ogr CSV driver not handling correctly line breaks inside columns

ose to, then more layer creations options are needed >> to handle the SRID/CRS >> >> CREATE_PRJ=YES/NO >> or -t_srs and/or -s_srs triggers the dot-prj file being created. >> >> Just saying . >> >> In the meantime would a short python script help parse the one fil

Re: [gdal-dev] Ogr2ogr CSV driver not handling correctly line breaks inside columns

ay 3, 2023 at 8:57 AM Moises Calzado via gdal-dev < > gdal-dev@lists.osgeo.org> wrote: > >> We're also specifying the GEOM_POSSIBLE_NAMES, so it would be great if >> with that option we could use the GEOMETRY_NAME without using the >> CREATE_CSVT=YES option. >>

Re: [gdal-dev] Ogr2ogr CSV driver not handling correctly line breaks inside columns

T > Integer, Integer,WKT > > CSV > line_id,point_id,geom > 1,1,"POINT(1000 1000)" > > PRJ > EPSG:26910 > > > > > On Wed, May 3, 2023, 05:23 Moises Calzado via gdal-dev < > gdal-dev@lists.osgeo.org> wrote: > >> Hi Even, >> >

Re: [gdal-dev] Ogr2ogr CSV driver not handling correctly line breaks inside columns

yer name: out >> Geometry: None >> Feature Count: 3 >> Layer SRS WKT: >> (unknown) >> id: String (0.0) >> descriptio: String (0.0) >> OGRFeature(out):1 >> id (String) = 1 >> descriptio (String) = This is my third row >> >> OGRFeatu

[gdal-dev] Ogr2ogr CSV driver not handling correctly line breaks inside columns

Hello! We're trying to convert a Shapefile into a CSV using ogr2ogr and we're having some issues while dealing with some columns that contain line breaks inside their values. If we have a line with the following string, ogr2ogr detects that the line break is a new line and it returns two lines.

[gdal-dev] Latest GDAL version not transforming lat/lng into geom column

Hello everyone, We've just updated to the latest GDAL version (v3.6.0) and it seems that something is not working correctly when trying to obtain a geom column from a CSV containing latitudes and longitudes. This is the command that is being used: ogr2ogr -f CSV -skipfailures -makevalid

[gdal-dev] ogr2ogr error: ERROR 1: Maximum number of characters allowed reached.

Hello everyone, We're facing some issues working with ogr2ogr in the 3.5.1 version, as we've found a dataset that provokes the following error during the execution of the following command: ogr2ogr -f CSV -skipfailures -makevalid /vsistdout/ > CSV:munic_s_anonymized.csv -simplify 0.1 -dim XY

[gdal-dev] (no subject)

Hello everyone, We're performing some tests with ogrinfo trying to read GPKG files, and we're facing some issues executing the command with remote GPKG files in WAL mode. As can be checked in the following command output, ogr fails while reading the file content: ERROR: Error: Command failed:

[gdal-dev] Ogr2ogr taking too much time to process a MapInfo TAB file

Hi everyone! We're using ogr2ogr to convert MapInfo TAB files into CSV format using the following command: ogr2ogr -f CSV -skipfailures -makevalid /vsistdout/ /vsizip/onLDU.zip -oo > AUTODETECT_TYPE=YES -lco CREATE_CSVT=YES > test_2.csv The file weights ≈200 MB and the process is taking too

[gdal-dev] Ogr2ogr issue with big integers

test.csv Hello everyone! I'm dealing with some issues with ogr2ogr trying to convert my data to a CSV file guessing the data types. I'm using the following command: ogr2ogr -f CSV -skipfailures -makevalid