Re: [gdal-dev] Quete_string_fields creation option for CSV

On mercredi 18 avril 2018 20:48:12 CEST Rahkonen Jukka (MML) wrote: > Hi, > > See this > https://gis.stackexchange.com/questions/279960/ogr2ogr-create-csv-with-stri > ngs-wrapped-in-double-quotes > > The GDAL CSV driver supports quoted string fields in reading but I suppose > that data can't be

Re: [gdal-dev] ogr2ogr JSON -> Shapefile Failing

Great, that worked. Now to figure out how to solve the "Warning 1: Feature id not preserved" error. I suspect if I dig long enough in google I'll find the key, but am hoping someone will see this and make my life easy. Matt .

Re: [gdal-dev] ogr2ogr JSON -> Shapefile Failing

On mercredi 18 avril 2018 20:41:05 CEST Cechini, Matthew F. (GSFC-423.0) [Science Systems & Applications, Inc.] wrote: > Great, that worked. Now to figure out how to solve the "Warning 1: Feature > id not preserved" error. I suspect if I dig long enough in google I'll > find the key, but am

[gdal-dev] Quete_string_fields creation option for CSV

Hi, See this https://gis.stackexchange.com/questions/279960/ogr2ogr-create-csv-with-strings-wrapped-in-double-quotes The GDAL CSV driver supports quoted string fields in reading but I suppose that data can't be written like that. -Jukka Rahkonen-

Re: [gdal-dev] ogr2ogr JSON -> Shapefile Failing

On mercredi 18 avril 2018 20:00:40 CEST Cechini, Matthew F. (GSFC-423.0) [Science Systems & Applications, Inc.] wrote: > All, > Once upon a time (GDAL 1.x) I was able to convert the following JSON to > Shapefile without errors. However with GDAL 2.x I am not. Any assistance > you can provide

[gdal-dev] ogr2ogr JSON -> Shapefile Failing

All, Once upon a time (GDAL 1.x) I was able to convert the following JSON to Shapefile without errors. However with GDAL 2.x I am not. Any assistance you can provide is welcome. I’m running a simple ` ogr2ogr -f "ESRI Shapefile" -preserve_fid ` command. { "crs": { "type":

Re: [gdal-dev] GDAL 2.3.0 planning

Hi, So a reminder that 2.3.0beta1 is planned for this friday (unspecified time) I've updated https://github.com/OSGeo/gdal/blob/master/gdal/NEWS There were literarily tens of thousand of lines of commit logs to parse, so it is not unlikely I may have forgotten things. I'd appreciate reviews

Re: [gdal-dev] (no subject)

On 18 April 2018 at 13:57, Gane R wrote: > Hi all, > > Is there any way to disable one or all OGR formats when building on Linux. > i.e., > when using ./configure > > Is there any way to disable certain raster formats when building on Linux

[gdal-dev] (no subject)

Hi all, Is there any way to disable one or all OGR formats when building on Linux. i.e., when using ./configure Is there any way to disable certain raster formats when building on Linux Thanks Ganesan ___ gdal-dev mailing list gdal-dev@lists.osgeo.org

Re: [gdal-dev] hardcoded paths in the testsuite

Ben, > > I noticed that the testsuite does things like this: > > sys.path.append('../pymod') > and: > sys.path.append('../gcore') > > Using hard-coded relative paths makes things fragile. It means you must > be in the specific test directory for the tests to run -- it can't be > run from

[gdal-dev] hardcoded paths in the testsuite

Hi Even I noticed that the testsuite does things like this: sys.path.append('../pymod') and: sys.path.append('../gcore') Using hard-coded relative paths makes things fragile. It means you must be in the specific test directory for the tests to run -- it can't be run from anywhere. I think it