[gdal-dev] georeference and project a jpeg

Hello, I am attempting to georeference and project a jpeg image using only gdal tool.I have georeferenced the jpeg using the following command: gdal_translate -a_srs EPSG:102719-of HFA -gcp 0.0 0.0 -82.5586187839508 35.59414007259327 -gcp 0.0 410.0 -82.55858659744263 35.5937998255945 -gcp 52

Re: [gdal-dev] memory leak in GRIB reader (with Python bindings)

Le jeudi 24 mai 2012 23:47:14, Chris Barker a écrit : > On Thu, May 24, 2012 at 2:40 PM, Even Rouault > > wrote: > > Ok, see http://trac.osgeo.org/gdal/ticket/4682 for a fix. Basically, the > > current caching strategy is maintained (cache all bands that have been > > accessed), until a threshold

Re: [gdal-dev] memory leak in GRIB reader (with Python bindings)

On Thu, May 24, 2012 at 2:40 PM, Even Rouault wrote: > Ok, see http://trac.osgeo.org/gdal/ticket/4682 for a fix. Basically, the > current caching strategy is maintained (cache all bands that have been > accessed), until a threshold is reached (arbitrarly set to 100 MB by default). seems reasonabl

Re: [gdal-dev] memory leak in GRIB reader (with Python bindings)

Ok, see http://trac.osgeo.org/gdal/ticket/4682 for a fix. Basically, the current caching strategy is maintained (cache all bands that have been accessed), until a threshold is reached (arbitrarly set to 100 MB by default). When the threshold is reached, then we only cache one band at a time. Tha

Re: [gdal-dev] memory leak in GRIB reader (with Python bindings)

Even, Thanks so much! > ok I reproduce your issue. > > The GRIB driver actually caches all the raster data from a band the first type > you access it, and never releases it. I just tested reading only a subset of teh band (because I don't need the whole thing), and it used exactly the same amoun

Re: [gdal-dev] memory leak in GRIB reader (with Python bindings)

Chris, ok I reproduce your issue. The GRIB driver actually caches all the raster data from a band the first type you access it, and never releases it. This is to speed-up successive RasterIO operations on a band, which is a nice feature generally. But if you iterate over all the bands, it mean

[gdal-dev] memory leak in GRIB reader (with Python bindings)

Hi folks, I"m finding what appears to be a memory leak, using the GRIB reader, with the python bindings. What I'm trying to do is read the data one band at a time, then throw it away and read the next band -- there are 1129 bands in the file at hand, and I can't hold it all in memory (32 bit stil

Re: [gdal-dev] ogr2ogr shapefile to mapinfo tab: no SRS.

Hi Frans, Il giorno gio, 24/05/2012 alle 14.42 +0200, Frans Knibbe | Geodan ha scritto: > The SRS that I am using is a projection (EPSG:28992, to be precise), > so I think geographic (unprojected) mode is not applicable. I will try > to update ticket 481. I checked in my c:\program files\Mapinfo

Re: [gdal-dev] libKml driver in 64 bit

I'll do that. It will have to wait till next week. Sent from my mobile - From: "Jeff McKenna" Subject: Re: [gdal-dev] libKml driver in 64 bit Date: 24 מאי 2012 17:51 On 12-05-24 11:40 AM, Livneh Yehiyam wrote: > Thanks everyone, > I did manage to compile everything.

Re: [gdal-dev] libKml driver in 64 bit

On 12-05-24 11:40 AM, Livneh Yehiyam wrote: > Thanks everyone, > I did manage to compile everything. Now it works You might want to add your x64 hints to the wiki now (gives you good karma): http://trac.osgeo.org/gdal/wiki/LibKML -jeff -- Jeff McKenna MapServer Consulting and Training Servic

Re: [gdal-dev] libKml driver in 64 bit

Thanks everyone, I did manage to compile everything. Now it works Sent from my mobile - From: "Piotr Tracz" Subject: Re: [gdal-dev] libKml driver in 64 bit Date: 24 מאי 2012 17:36 W dniu 2012-05-24 13:28, Livneh Yehiyam pisze: Has anyone managed to build the libKM

Re: [gdal-dev] libKml driver in 64 bit

W dniu 2012-05-24 13:28, Livneh Yehiyam pisze: Has anyone managed to build the libKML driver win 64 bit for windows 7? I'm having problems getting all of the third-parties compiled. // I did. It compiles fine on VS2005 (GDAL 1.9.0 but no problem with previous version either) /Piotr

Re: [gdal-dev] libKml driver in 64 bit

On 12-05-24 8:28 AM, Livneh Yehiyam wrote: > Hi > > Has anyone managed to build the libKML driver win 64 bit for windows 7? I skipped over that driver when compiling x64. -jeff -- Jeff McKenna MapServer Consulting and Training Services http://www.gatewaygeomatics.com/ __

Re: [gdal-dev] ogr2ogr shapefile to mapinfo tab: no SRS.

Hi Chaitanya, The SRS that I am using is a projection (EPSG:28992, to be precise), so I think geographic (unprojected) mode is not applicable. I will try to update ticket 481. Regards, Frans On 2012-05-24 13:31, Chaitanya kumar CH wrote: Frans, Add the option "-a_srs WGS84" to ogr2ogr comm

Re: [gdal-dev] libKml driver in 64 bit

On 24 May 2012 12:28, Livneh Yehiyam wrote: > Hi > > Has anyone managed to build the libKML driver win 64 bit for windows 7? > I haven't. > > > I'm having problems getting all of the third-parties compiled. > > ** > OK. Cheers, -- Mateusz Loskot, http://mateusz.loskot.net

[gdal-dev] libKml driver in 64 bit

Hi Has anyone managed to build the libKML driver win 64 bit for windows 7? I'm having problems getting all of the third-parties compiled. Thanks Yehiyam Livneh ** This message (including any attachments)

Re: [gdal-dev] ogr2ogr shapefile to mapinfo tab: no SRS.

Frans, Add the option "-a_srs WGS84" to ogr2ogr command. It should force geographic mode. If that doesn't solve your issue, please go through the discussion on this topic at ticket 481. http://trac.osgeo.org/gdal/ticket/481 On Thu, May 24, 2012 at 4:35 PM, Frans Knibbe | Geodan < frans.kni...@ge

[gdal-dev] ogr2ogr shapefile to mapinfo tab: no SRS.

Hello, I wonder if someone can help me with a nasty problem with using ogr2ogr to convert shapefile to Mapinfo tab format. Whatever I try, I can not get the output to have a correct definition of the SRS. Ogrinfo always reports the output having a NonEarth SRS. The input shapefile has a *.pr