[gdal-dev] Doubts to Convert TopoJson to SHP File

Hi, I am newbie to use the GDAL and passing the problem in convert TopoJSON to SHP FIle. I executed the command below and some files were created (.dbf, .shp, .shx) but the file .prj is not created. Is there any parameters that I need to pass to create this .prj file? ogr2ogr -

[gdal-dev] Call for discussion on RFC 78: gdal-utils package

Hi All, I would like to call for discussion on RFC 78: gdal-utils package Please give your feedback on this PR. Summary This RFC

Re: [gdal-dev] Duplicate pixels in VRT

Hi, Check what are the extents of two adjacert images reported by GDAL 2 and 3, as well as the sizes in pixels, and if images are of type "pixel is area" or "pixel is point". DEM kind of images are sometimes intentionally produced to have overlap. -Jukka Rahkonen- Jon Morris wrote > Hello all,

Re: [gdal-dev] Visual C++ 2015: compiling error with GDAL 3.2

This works perfectly. Thanks It is just an ugly patch before I can witch to a more modern compiler -- Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailm

Re: [gdal-dev] Visual C++ 2015: compiling error with GDAL 3.2

On Tue, 22 Dec 2020 at 12:47, Bugbuster wrote: > > You may be right about the update of VS2015. > My version is 19.00.23026 (to be compared to yours : 19.00.23506) > > An I do have the error with the small test you sent. > > Do you have any idea declare/initialize the NaN attribute in another way

[gdal-dev] Duplicate pixels in VRT

Hello all, I've come across a weird edge case and I'm wondering if anyone has seen something similar. I'm updating our application from GDAL v2.2 to v3.2 and have a failing test where there is a 1 pixel shift in the output. We're building a VRT from a DTM and a flood depth raster and when you

Re: [gdal-dev] Exporting triggers/constraints from PG to GPKG

Hi, You are right, ogr2ogr converts just the data from the table/view/query and metadata that defines the coordinate system. I believe it would be very hard to handle the creation of triggers and constraints and insert data in the right order into SQLite, Oracle, MSSQL etc. it's perfectly und

Re: [gdal-dev] Exporting triggers/constraints from PG to GPKG

Hi, You are right, ogr2ogr converts just the data from the table/view/query and metadata that defines the coordinate system. I believe it would be very hard to handle the creation of triggers and constraints and insert data in the right order into SQLite, Oracle, MSSQL etc. -Jukka Rahkonen- gh

Re: [gdal-dev] Visual C++ 2015: compiling error with GDAL 3.2

You may be right about the update of VS2015. My version is 19.00.23026 (to be compared to yours : 19.00.23506) An I do have the error with the small test you sent. Do you have any idea declare/initialize the NaN attribute in another way ? I do not any easy way to update my compiler :-( -- S

[gdal-dev] Exporting triggers/constraints from PG to GPKG

Hi all (and sorry for the flood of these days), the question is very simple: if I have triggers and/or constraint in a PG database, is ogr2ogr exporting them to the GPKG? At a first view it seems not (I looked in the exported GPKG and I cannot find the triggers and constraints). I also couldn

Re: [gdal-dev] Visual C++ 2015: compiling error with GDAL 3.2

On Tue, 22 Dec 2020 at 11:11, Bugbuster wrote: > > When compiling GDAL 3.2, I get an error in gcore/tilematrixset.hpp > tilematrixset.hpp(47): error C2131: expression did not evaluate to a > constant > failure was caused by non-constant arguments or reference to a non-constant > symbol > note: see

[gdal-dev] Visual C++ 2015: compiling error with GDAL 3.2

My environnement is : * Windows 10 * Visual C++ 2015 64 bits When compiling GDAL 3.2, I get an error in gcore/tilematrixset.hpp tilematrixset.hpp(47): error C2131: expression did not evaluate to a constant failure was caused by non-constant arguments or reference to a non-constant symbol note: see

Re: [gdal-dev] ogr2ogr question

Hi Jukka, thanks for the clarifications. On 12/22/20 8:36 AM, jratike80 wrote: No, -overwrite does not truncate but it drops the table. However, with the PostgreSQL driver it is also possible to truncate the table by using this documented method https://gdal.org/drivers/vector/pg.html#vector-