Re: [gdal-dev] "Very" long path name support under windows

2016-11-23 Thread Damian Dixon
Hi Even, Philippe, Windows has two types of paths. The first is essentially the codepage and is about 260 characters. The second is the unicode pathname which is probably around 32k characters. I can't remember the actual limit. The cmd line and explorer only use the 260 character limit. So a

Re: [gdal-dev] "Very" long path name support under windows

2016-11-23 Thread Bugbuster
Hi Even, thanks for your long and detailed answer. I have plenty of information I can play around with. In fact, I managed to "cd" to the desired directory within a *Cygwin Mintty* windows. In this window, I do not have the "8.3 Windows renaming". In that way, I mimicked what I get with a system

[gdal-dev] ElasticSearch and native geometry

2016-11-23 Thread Rahkonen Jukka (MML)
Hi, What if somebody would like to use ElasticSearch for queries but still somehow get the native geometries included in the output? The geometry must be re-projected into EPSG:4326 for creating either geo_point or geo_shape, but can anybody suggest a clever way for saving the native

Re: [gdal-dev] cppcheck

2016-11-23 Thread Kurt Schwehr
I definitely want to add some checks to that script! A lot of what I'm doing is just reading through the code. I have been taking notes in hopes that I can convert some of the grep's that I do into the script. Right now, most of them are super high on the false positive side of things. e.g.

Re: [gdal-dev] cppcheck

2016-11-23 Thread Even Rouault
On mercredi 23 novembre 2016 05:43:44 CET Kurt Schwehr wrote: > Even, > > Thank you for your work with getting cppcheck setup and fixing a huge > number of warnings (and suppressing a large number of false positives)!!! I encourage you as well to extend the tooling so as to check that all the

[gdal-dev] cppcheck

2016-11-23 Thread Kurt Schwehr
Even, Thank you for your work with getting cppcheck setup and fixing a huge number of warnings (and suppressing a large number of false positives)!!! -kurt ___ gdal-dev mailing list gdal-dev@lists.osgeo.org

Re: [gdal-dev] Question about how GDAL makes an ElasticSearch index

2016-11-23 Thread Even Rouault
On mercredi 23 novembre 2016 12:58:56 CET Rahkonen Jukka (MML) wrote: > Hi, > > It seems that all examples about how to query ElasticSearch with GDAL in > http://www.gdal.org/drv_elasticsearch.html are failing with ElasticSearch > versions 2.x. That's likely. They were writte against 1.X. I

[gdal-dev] Question about how GDAL makes an ElasticSearch index

2016-11-23 Thread Rahkonen Jukka (MML)
Hi, It seems that all examples about how to query ElasticSearch with GDAL in http://www.gdal.org/drv_elasticsearch.html are failing with ElasticSearch versions 2.x. Reason is the breaking change "A field can no longer be referenced using its short name. Instead, the full path to the field is

Re: [gdal-dev] "Very" long path name support under windows

2016-11-23 Thread Even Rouault
Philippe, > I bumped into a problem under windows (Win7 or Win8 64 bits). I try to > manage an image which directory name is "very long" (more than 260 chars) : > >cd C:\VeryLongDirectoryPath >gdalinfo Image.tif I experimented a bit, and the truth is that Windows itself poorly supports

[gdal-dev] "Very" long path name support under windows

2016-11-23 Thread Bugbuster
Dear all, I have already posted this question a while ago, but I just noticed it has never been accepted by the mailing list. And I don't know how to make it accepted today. I do feel sorry for this double-posting. I bumped into a problem under windows (Win7 or Win8 64 bits). I try to manage an