Re: [gdal-dev] Allocate large memory space with CPLMalloc(). Bug or not?

2015-10-01 Thread fazotron
Thanks for reply, I'll try VSIMalloc(). But can you explain the goal of check if( long(nSize) < 0 ) {...} in CPLMalloc()? Cast size_t to long leads to implicit result. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Allocate-large-memory-space-with-CPLMalloc-Bug-or-not-tp52

Re: [gdal-dev] Allocate large memory space with CPLMalloc(). Bug or not?

2015-10-01 Thread fazotron
Thanks for reply, I'll try VSIMalloc(). But can you explain the goal of check *if( long(nSize) < 0 ) {...}* in CPLMalloc()? Cast size_t to long leads to implicit result. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Allocate-large-memory-space-with-CPLMalloc-Bug-or-not-tp

Re: [gdal-dev] Allocate large memory space with CPLMalloc(). Bug or not?

2015-10-01 Thread Even Rouault
Le jeudi 01 octobre 2015 21:18:33, fazotron a écrit : > Hello! > > Take a look on the following code: > > *... > size_t w = 1, h = 5000, d = 150; > size_t sz = w * h * d * sizeof(float); // ~27.94 Gb > > float *volume = (float*)CPLMalloc(sz); > ...* > > In this case GDAL throws error in run

Re: [gdal-dev] Allocate large memory space with CPLMalloc(). Bug or not?

2015-10-01 Thread Kyle Shannon
On Thu, Oct 1, 2015 at 1:18 PM, fazotron wrote: > > Hello! > > Take a look on the following code: > > *... > size_t w = 1, h = 5000, d = 150; > size_t sz = w * h * d * sizeof(float); // ~27.94 Gb > > float *volume = (float*)CPLMalloc(sz); > ...* > > In this case GDAL throws error in runtime: "

[gdal-dev] Allocate large memory space with CPLMalloc(). Bug or not?

2015-10-01 Thread fazotron
Hello! Take a look on the following code: *... size_t w = 1, h = 5000, d = 150; size_t sz = w * h * d * sizeof(float); // ~27.94 Gb float *volume = (float*)CPLMalloc(sz); ...* In this case GDAL throws error in runtime: "ERROR 1: CPLMalloc(-664771072): Silly size requested." But I think that

Re: [gdal-dev] (no subject)

2015-10-01 Thread Dmitry Baryshnikov
Hi Konstantin, Can you explain your case. For example for WMS driver (TMS) GDAL_HTTP_PROXY config option works for me. Best regards, Dmitry 01.10.2015 14:39, Константин Лапин пишет: Hi, CPLSetConfigOption( "GDAL_HTTP_PROXY",proxy.toLocal8Bit().data()); CPLSetConfigOption( "GDAL_PROXY_A

[gdal-dev] (no subject)

2015-10-01 Thread Константин Лапин
Hi, CPLSetConfigOption( "GDAL_HTTP_PROXY",proxy.toLocal8Bit().data()); CPLSetConfigOption( "GDAL_PROXY_AUTH", "NTLM" ); CPLSetConfigOption( "GDAL_HTTP_PROXYUSERPWD", " : " ); how to make "bypass proxi for local adresses" ? С уважением, Константин Лапин lk...@mail.ru

Re: [gdal-dev] Motion: Adopt RFC 59.1: GDAL/OGR utilities as a library

2015-10-01 Thread Even Rouault
Le mardi 29 septembre 2015 12:45:43, Even Rouault a écrit : > Hi, > > Since no remarks have been done on the latest proposal, I move to adopt RFC > 59.1: GDAL/OGR utilities as a library > > https://trac.osgeo.org/gdal/wiki/rfc59.1_utilities_as_a_library > > Starting with my +1, Hi, This motion

Re: [gdal-dev] gdalwarp fails to warp for this GeoPDF

2015-10-01 Thread Jean-Claude Repetto
Le 01/10/2015 10:42, Even Rouault a écrit : > > I don't think so. Looks like an issue with your GDAL and/or proj.4 install. > The proj.4 string for EPSG:3857 reported above is wrong. It should be (as > reported by gdalsrsinfo "EPSG:3857"): > > +proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=

Re: [gdal-dev] gdalwarp fails to warp for this GeoPDF

2015-10-01 Thread Even Rouault
Le jeudi 01 octobre 2015 09:31:33, Gane R a écrit : > Hi, > > https://drive.google.com/file/d/0B4shTM1bPS5TZ3psWTFpU1ZuV2c/view?usp=shari > ng > > gdalwarp -t_srs EPSG:3857 "file04.pdf" "file04.tif" > > ERROR 6: Failed to initialize PROJ.4 with `+proj=merc +lon_0=0 +k=0 +x_0=0 > +y_0= > 0 +ellps

[gdal-dev] gdalwarp fails to warp for this GeoPDF

2015-10-01 Thread Gane R
Hi, https://drive.google.com/file/d/0B4shTM1bPS5TZ3psWTFpU1ZuV2c/view?usp=sharing gdalwarp -t_srs EPSG:3857 "file04.pdf" "file04.tif" ERROR 6: Failed to initialize PROJ.4 with `+proj=merc +lon_0=0 +k=0 +x_0=0 +y_0= 0 +ellps=WGS84 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs '. k <= 0 Is this due to