search

nakijun / tilers-tools

Automatically exported from code.google.com/p/tilers-tools
1 stars 0 forks source link

Too much RAM used while trying to tile a map #15

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. python gdal_tiler.py -z 0:18 --tps -q -r -s -p xyz 2107001.KAP -t outputdir

What is the expected output? What do you see instead?

I am seeing an usage of 10+ GB of RAM and still don't have any generated file.
Can't keep running it since have only 12 GB of RAM.
Maybe related with issue 3?

The file is attached.

What version of the product are you using?

cloned 004501593734

What was the operating system?

Linux

Original issue reported on code.google.com by nao...@gmail.com on 11 Jul 2014 at 9:39

Attachments:

GoogleCodeExporter commented 9 years ago 
You simply asking too much from the source you are trying to process:

If you'd try to process it without -z 0:18 you'll get max zoom at 10, which is 
quite close the the rasters native resolution. 

So when you're asking for max zoom 18 then GDAL is upscaling your source to 
something quite enormous (you'll calculate it yourself;). This is quite 
meaningless as your source cannot provide such a detail.

If you need some more control over automatic zoom range calculation you'd try 
something like -z :+1, which in this case will give you max zoom of 11.

Original comment by vadp.d...@gmail.com on 16 Jul 2014 at 3:51

GoogleCodeExporter commented 9 years ago 
Right. I didn't know about :+1
Thanks

Original comment by nao...@gmail.com on 16 Jul 2014 at 4:08

GoogleCodeExporter commented 9 years ago 
BTW you can also try something like --zoom=-1:+1 or --zoom=+2:-1

Undocumented, sorry, but you can call it an Easter Egg ;)

Original comment by vadp.d...@gmail.com on 17 Jul 2014 at 7:38