4
votes
Accepted
Integer field of CSV file always output as String when processed with ogr2ogr
Read documentation from here https://gdal.org/drivers/vector/csv.html#layer-creation-options
STRING_QUOTING=[IF_NEEDED/IF_AMBIGUOUS/ALWAYS]: Defaults to
IF_AMBIGUOUS. whether to double-quote strings. ...
3
votes
Accepted
Writing Foreign Members to GeoJSON files using ogr2ogr
Will be available in GDAL 3.9 per https://github.com/OSGeo/gdal/pull/8830
ogr2ogr out.json in.whatever -lco "FOREIGN_MEMBERS_FEATURE={\"foreign-key\": \"foreign-value\"}"
3
votes
Integer field of CSV file always output as String when processed with ogr2ogr
Will be fixed in GDAL 3.8.2 per https://github.com/OSGeo/gdal/pull/8813
2
votes
Why doesn't ogr2ogr support the PostgreSQL schema search path?
If the change was due to that commit https://github.com/OSGeo/gdal/pull/2405 then obviously it did not break anything that is tested. The PostGIS Python tests are in https://github.com/OSGeo/gdal/blob/...
2
votes
Integer field of CSV file always output as String when processed with ogr2ogr
Using a VRT file?
https://gdal.org/drivers/vector/vrt.html
there is an example on the CSV page: https://gdal.org/drivers/vector/csv.html#building-point-geometries
I wrote a tutorial some years ago ...
1
vote
ogr2ogr skipping rows when converting from osm.pbf to gpkg
The way that you used as an example is this https://www.openstreetmap.org/way/404851503
It is a closed way that consists of 109 points. It acts in an "outer" role in a relation "Golden ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
ogr2ogr × 1134gdal × 340
shapefile × 199
postgis × 189
geojson × 132
ogr × 112
qgis × 110
postgresql × 104
python × 77
coordinate-system × 63
openstreetmap × 58
sql × 57
kml × 53
sqlite × 46
file-geodatabase × 45
convert × 44
sql-server × 37
spatialite × 37
geopackage × 36
csv × 32
dxf × 29
gml × 28
wfs × 23
osgeo4w × 21
import × 18