Re: [gdal-dev] Participating on gdal2tiles

2017-01-22 Thread Grégory Bataille
ok thanks :) --- Gregory Bataille On Sun, Jan 22, 2017 at 11:47 AM, Even Rouault wrote: > On dimanche 22 janvier 2017 11:21:06 CET Grégory Bataille wrote: > > > Yes it is. There was a commit on the test_gdal2tiles.py changing the > > > checksum values for test 1 :) > > > > Well, that's the li

Re: [gdal-dev] Participating on gdal2tiles

2017-01-22 Thread Even Rouault
On dimanche 22 janvier 2017 11:21:06 CET Grégory Bataille wrote: > Yes it is. There was a commit on the test_gdal2tiles.py changing the > checksum values for test 1 :) Well, that's the life of a project that test results might change because of other changes. Not sure to understand if that's you

Re: [gdal-dev] Participating on gdal2tiles

2017-01-22 Thread Grégory Bataille
Yes it is. There was a commit on the test_gdal2tiles.py changing the checksum values for test 1 :) that's odd, it's pyflakes that is throwing me those warnings... well flake8 actually that is pyflakes + pep8. I'll have a look anyway. And yes, the style commits need to be separate, no worries. I d

Re: [gdal-dev] Participating on gdal2tiles

2017-01-22 Thread Even Rouault
On dimanche 22 janvier 2017 09:00:59 CET Grégory Bataille wrote: > Hey all, > > 2 questions: > seeing that it's complex to build trunk on mac (and that some recent > changes have an impact on gdal2tiles output), is it ? You can have a look at the scripts in ci/travis/osx used for the OsX target

Re: [gdal-dev] Participating on gdal2tiles

2017-01-22 Thread Grégory Bataille
Hey all, 2 questions: seeing that it's complex to build trunk on mac (and that some recent changes have an impact on gdal2tiles output), I wanted to setup the vagrant box, but I get this error. Any clue? > shell provisioner: > * `path` for shell provisioner does not exist on the host system: > /U

Re: [gdal-dev] Participating on gdal2tiles

2017-01-20 Thread Mark Johnson
You might also consider incorporating the mbtiles implementation of a fork of gdal2tiles that can be found here: https://github.com/mj10777/gdal2mbtiles Here the goal was to also offer mbtiles as the output-format - instead of a tiles-directory It also offered options to use mbtiles as a source

Re: [gdal-dev] Participating on gdal2tiles

2017-01-20 Thread Grégory Bataille
yes indeed, that would be one of the things I'd like to try and do... A few bug fix before though and then I'll see Thanks --- Gregory Bataille On Fri, Jan 20, 2017 at 10:34 AM, Sean Gillies wrote: > Hi Grégory, > > On Fri, Jan 20, 2017 at 8:59 AM, Even Rouault > wrote: > >> On vendredi 20 j

Re: [gdal-dev] Participating on gdal2tiles

2017-01-20 Thread Sean Gillies
Hi Grégory, On Fri, Jan 20, 2017 at 8:59 AM, Even Rouault wrote: > On vendredi 20 janvier 2017 05:45:28 CET Grégory Bataille wrote: > > > Hi everyone, > > > > > > I just subscribed to this list. Due to current interest, driven by my > > > current job, I'd like to participate on gdal2tiles. > > >

Re: [gdal-dev] Participating on gdal2tiles

2017-01-20 Thread Grégory Bataille
youhou... :) ok, I'll see what I can do then --- Gregory Bataille On Fri, Jan 20, 2017 at 8:59 AM, Even Rouault wrote: > On vendredi 20 janvier 2017 05:45:28 CET Grégory Bataille wrote: > > > Hi everyone, > > > > > > I just subscribed to this list. Due to current interest, driven by my > > > c

Re: [gdal-dev] Participating on gdal2tiles

2017-01-20 Thread Even Rouault
On vendredi 20 janvier 2017 05:45:28 CET Grégory Bataille wrote: > Hi everyone, > > I just subscribed to this list. Due to current interest, driven by my > current job, I'd like to participate on gdal2tiles. > However I'm not sure how to go about it and how active the development > still is. > I,

[gdal-dev] Participating on gdal2tiles

2017-01-19 Thread Grégory Bataille
Hi everyone, I just subscribed to this list. Due to current interest, driven by my current job, I'd like to participate on gdal2tiles. However I'm not sure how to go about it and how active the development still is. I, for example, encountered an issue, that after investigation led me there https: