Thanks for the reply. I've included the input file information below.
I understand that I should see skewing. What's the best method for
correction of the skew?
I misspoke a bit about the tiles. I had a few sets of 100 tiles each. on
each 100 tile set, the output size was 30gb. The total siz
Le vendredi 13 février 2015 19:43:17, Alan Stewart a écrit :
> I'm assuming any "*WIN32*" define should be used when building for Windows.
> I'll certainly try without that one. Is there documentation I have not
> found for GDAL defines? I certainly don't understand the practical
> significance of
Le vendredi 13 février 2015 18:08:39, Alan Stewart a écrit :
> I'm building 1.11.0 as a DLL on Windows with CPL_MULTIPROC_WIN32 and
> USE_WIN32_MUTEX defined. Everything builds fine, but in my workflow a debug
> build always fails while the release build succeeds. I'm using a modified
> version of
I'm building 1.11.0 as a DLL on Windows with CPL_MULTIPROC_WIN32 and
USE_WIN32_MUTEX defined. Everything builds fine, but in my workflow a debug
build always fails while the release build succeeds. I'm using a modified
version of gdalwarp.cpp as a function linked into the DLL instead of as a
standa
Le vendredi 13 février 2015 15:01:39, Nick Ves a écrit :
> I agree with the significance gdal2tiles. I've used on numerous
> occasions and it would a shame to lose it.
Note: my proposal 3) was not about to remove the command line interface. It
was about to move the script from one package to anot
I agree with the significance gdal2tiles. I've used on numerous
occasions and it would a shame to lose it.
On a side note the multitreaded patch [0] was submitted 3 years ago,
and stilll wasn't merged in official channel.
[0] http://trac.osgeo.org/gdal/ticket/4379
On Fri, Feb 13, 2015 at 2:54 P
1) Merge maptiler's gdal2tiles enhancements into GDAL version, and make
maptiler just a GUI over it
2) Merge maptiler's gdal2tiles enhancements into GDAL version, and
also import
the GUI (I think it is lightweight) if there's no too strong build
complications involved for GDAL. Would have to
On 13 February 2015 at 14:18, Dmitriy Baryshnikov wrote:
> I agreed with Angelos.
> My +1
>
I also agree with Angelos, +1 for option 1
> Best regards,
> Dmitry
>
--
ciao
Luca
http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
___
gdal-dev mailin
I agreed with Angelos.
My +1
Best regards,
Dmitry
13.02.2015 15:54, Angelos Tzotsos пишет:
Hi Even,
On 02/13/2015 02:05 PM, Even Rouault wrote:
Hi,
(adding gdal-dev in CC as it is of interest)
As far as I understand (but I may be wrong as I haven't looked deeply
at the
code), maptile
Hi Even,
On 02/13/2015 02:05 PM, Even Rouault wrote:
Hi,
(adding gdal-dev in CC as it is of interest)
As far as I understand (but I may be wrong as I haven't looked deeply at the
code), maptiler (the open source project) consists of an improved
gdal2tiles.py + a python gui.
The duplication be
Le vendredi 13 février 2015 03:30:48, Kurt Schwehr a écrit :
> I'll have to look into this more.
>
> gdal_grid --debug on -txe 440720.0 441920.0 -tye 3751320.0 3750120.0 \
>
> > -outsize 20 20 -ot Float64 -l grid \
> >
> > -a
>
> invdist:power=2
Hi,
(adding gdal-dev in CC as it is of interest)
As far as I understand (but I may be wrong as I haven't looked deeply at the
code), maptiler (the open source project) consists of an improved
gdal2tiles.py + a python gui.
The duplication between gdal2tiles.py in maptiler and GDAL isn't somethin
Le mercredi 11 février 2015 10:29:16, vous avez écrit :
> Hi,
>
> As no points have been raised,
>
> Motion : I move to adopt RFC 53: OGR not-null constraints and default
> values
>
> http://trac.osgeo.org/gdal/wiki/rfc53_ogr_notnull_default
>
> Starting with my +1
I declare this motion passed
There is some interesting discussion about an issue with a VRT file that
combines very many small images within the comments of this ticket
http://trac.osgeo.org/gdal/ticket/5828
For my mind mailing lists suit usually better for discussions than
Trac/Jira/Github bug trackers and at least by now se
14 matches
Mail list logo
