Re: [gdal-dev] gdal_clip

Hi Zack, Your function sounds great. We've tried to implement something similar last summer but couldn't get it to work properly. I have no authority to say if this should be implemented in GDAL or not, but you've got my vote ;) Thanks, Paul *Paul Meems * Release manager, configuration manager

Re: [gdal-dev] Ogr2ogr does not support file name with non-ASCII character

Hi, You shouldn't know that file name is UTF. It maybe not in UTF (e.g. in you system encoding - in Linux usually UTF-8, in Windows - CP1252, CP1251 etc.). But you command line shell (bash, cmd, etc.) should encode the input to the UTF8, or you have to set the environment variable GDAL_FILEN

Re: [gdal-dev] Ogr2ogr does not support file name with non-ASCII character

Hi: Thanks for your reply. But I wonder how do I know if the file name is utf8? Since not all of the filename contain no-asci characters. Thanks 2014/1/8 Dmitriy Baryshnikov > Hi, > > The GDAL utilities expected all input paths in UTF-8 encoding. If you want > to use system native encoding

[gdal-dev] gdal_clip

Dear developers, I would like to contribute some code to the project. I have a utility I call gdal_clip I wrote wrote in C++, which I used to compile against the FWTools gdal .lib file and later Mr. Szekeres .lib files, which will "clip" an image. It uses an input image and an input poly

Re: [gdal-dev] What is readlink used for?

Allen Kempe http://acksoft.dyndns.biz/PictureGallery 298 W. Audubon Drive Shepherdsville, KY 40165 +1 502 543-3438 On 01/06/2014 01:35 PM, Kurt Schwehr wrote: Hi all, I ran into trouble with readlink as can be seen in http://trac.osgeo.org/gdal/ticket/5340. I'm working with a system wher

Re: [gdal-dev] GeoRSS and TestCapability("CreateField")

Le mercredi 08 janvier 2014 21:23:50, Jared Erickson a écrit : > Hi all, > > I am working with the GeoTools developers on their OGR module in order to > add OGR support for GeoScript and I have a question about what exactly > Layer.TestCapability means. In GeoTools (which is written in Java), whe

[gdal-dev] GeoRSS and TestCapability("CreateField")

Hi all, I am working with the GeoTools developers on their OGR module in order to add OGR support for GeoScript and I have a question about what exactly Layer.TestCapability means. In GeoTools (which is written in Java), when creating a new Layer we call Layer.TestCapability("CreateField") to see

[gdal-dev] Update on RFC 45 - GDAL datasets and raster bands as virtual memory mappings

Hi, I've investigated memory file mapping mechanisms and added that to the RFC. You'll find the diffs w.r.t the version I submitted 3 few weeks ago : * http://trac.osgeo.org/gdal/wiki/rfc45_virtualmem?action=diff&version=6 * http://trac.osgeo.org/gdal/wiki/rfc45_virtualmem?action=diff&version=7 *

Re: [gdal-dev] Ogr2ogr does not support file name with non-ASCII character

Hi, The GDAL utilities expected all input paths in UTF-8 encoding. If you want to use system native encoding you have to set GDAL_FILENAME_IS_UTF8 environment variable to NO. http://trac.osgeo.org/gdal/wiki/ConfigOptions#GDAL_FILENAME_IS_UTF8 Best regards, Dmitry 08.01.2014 4:03, maven a

Re: [gdal-dev] Convert GeoPDF with gdal_translate

On 01/07/2014 11:19 PM, Ari Jolma wrote: On 01/07/2014 11:02 PM, Even Rouault wrote: I assume your GDAL build has only write support for geospatial PDF (which doesn't require any third-party library), but not read support that requires linking to a third-party library, like Poppler or Podofo.

Re: [gdal-dev] Regarding to the memory management in the SWIG API

On 01/08/2014 12:27 PM, Even Rouault wrote: Le mercredi 08 janvier 2014 11:10:58, Tamas Szekeres a écrit : Hi Devs, Is that intentional that we don't call ReleaseResultset within the destructor of the OGR Layer object? The OGR Layer object has generally no pointer to the datasource from which

Re: [gdal-dev] Convert GeoPDF with gdal_translate

Le mercredi 08 janvier 2014 06:41:49, Pekka Sarkola a écrit : > Thanks Even! > > And also Jukka and Ari. Jukka: Is there still Windows machines in Finland? > Interesting, Land of Linux ;-) Well, even I have few. > > Ok, I try GDAL versions with 3rd party librariries > > I agree with Ari: gdalinf

Re: [gdal-dev] Regarding to the memory management in the SWIG API

Le mercredi 08 janvier 2014 11:10:58, Tamas Szekeres a écrit : > Hi Devs, > > Is that intentional that we don't call ReleaseResultset within the > destructor of the OGR Layer object? The OGR Layer object has generally no pointer to the datasource from which it originates (well, at the swig level

[gdal-dev] Regarding to the memory management in the SWIG API

Hi Devs, Is that intentional that we don't call ReleaseResultset within the destructor of the OGR Layer object? Actually the destructor is not even generated (at least for the C# API) which seems to be an improper solution and leads to memory leaks, definitely. However ReleaseResultset is exposed

[gdal-dev] Modifying gdal_retile.py to incorporate resume support

Hello I am trying to add resume functionality to gdal_retile.py. If, whilst creating tiles, gdal_retile.py fails because of a bad base tile, I want to be able to simply remove that bad base tile and restart gdal_retile.py to generate the remaining possible tiles rather than starting from scratch.