[gdal-dev] error reading AIG blocks

2017-05-11 Thread Gregory, Matthew
Hi all, I think this is a bug, but wanted to make sure I wasn't doing something stupid before I posted it as such. At r32878 (git 1eb605a), Even added new logic for dealing with raw 32-bit AIG blocks. I've got an AIG raster that has a few blocks where valid data is getting set to the min Int3

[gdal-dev] Issue getting correct GeoTransform

2017-05-11 Thread Janelle Archer
I am creating a data set in virtual memory and then copying over to a DTED driver. I have verified that when I setGeoTransform, I am able to get the same values back. (*i).tempMemDS = tempMemDriver->Create ("", (int) xSize, (int) ySize, 1, GDT_Float32, NULL (*i).dtedDS = dtedDriver->CreateCopy (sz

Re: [gdal-dev] GDAL Linking issues VS2015 64-bit

2017-05-11 Thread Damian Dixon
We also do the following: FOR /R gdal %%F IN (*.res) DO DEL /F /S "%%F" > nul FOR /R gdal %%F IN (*.obj) DO DEL /F /S "%%F" > nul FOR /R gdal %%F IN (*.pdb) DO DEL /F /S "%%F" > nul FOR /R gdal %%F IN (*.dll) DO DEL /F /S "%%F" > nul FOR /R gdal %%F IN (*.lib) DO DEL /F /S "%%F" > nul FOR /R gdal

Re: [gdal-dev] GDAL Linking issues VS2015 64-bit

2017-05-11 Thread Even Rouault
Liam, > > SYM_PREFIX= --> You don't need to touch that one. Correct behaviour is determined by WIN64 setting > > LINK : error LNK2001: unresolved external symbol OSRValidate > LINK : error LNK2001: unresolved external symbol OPTGetProjectionMethods > LINK : error LNK2001: unresolved external s

[gdal-dev] GDAL Linking issues VS2015 64-bit

2017-05-11 Thread Candy, Liam
Hi all, I managed to get the GDAL library with ECW support to compile and link for 32-bit, but realized I need to get the 64-bit library working. I'm having linking issues with this. I'm running Windows 10, VS2015 command line tools, and trying to build GDAL 2.1.3 with support for ERDAS ECW 5.

[gdal-dev] KML : some vectors are not seen by GDAL

2017-05-11 Thread Bugbuster
Dear all, When I try to export some vector data in KML, I sometimes "lose" some vectors. It depends on the way layers are created : case #1 : no tags are created. All vectors are considered "at the top level". Everything is fine case #2 : vectors all belong to a specific layer, using one or several

[gdal-dev] KML : some vectors are not seen by GDAL

2017-05-11 Thread Bugbuster
Dear all,When I try to export some vector data in KML, I sometimes "lose" some vectors.It depends on the way layers are created :case #1 : no tags are created. All vectors are considered "at the top level". Everything is finecase #2 : vectors all belong to a specific layer, using one or several t