Re: [gdal-dev] ogr2ogr PG->SHP lacks EPSG code

Martin Landa wrote > Hi, > > 2016-11-11 18:56 GMT+01:00 Even Rouault > even.rouault@ > : >> The WKT variant of ESRI Shapefile .prj doesn't have EPSG codes (nor >> TOWGS84 >> node by the way). At least that was how it was historically and GDAL >> "morphs" >> OGC WKT to ESRI WKT this way (there

Re: [gdal-dev] ogr2ogr PG->SHP lacks EPSG code

Hi, 2016-11-11 18:56 GMT+01:00 Even Rouault : > The WKT variant of ESRI Shapefile .prj doesn't have EPSG codes (nor TOWGS84 > node by the way). At least that was how it was historically and GDAL "morphs" > OGC WKT to ESRI WKT this way (there are other variations in

Re: [gdal-dev] How to replace an osm key?

Thank you for the reply Jukka. Neither "building:levels" nor "height" fields were located in osmconf.ini under the "[multipolygons]". I have just added them as you suggested, and now the previously mentioned command creates the .shp file without raising an error.I tried the initial: -dialect

Re: [gdal-dev] How to replace an osm key?

Hi, Related to your previous question, you can use SQL select only for fields which are included in osmconf.ini. Perhaps "height" is not. 'building:levels' may make a surprise for you, if ogr2ogr follows SQL specification it will select a fixed string. You should use double quotes instead and