geophil wrote:
From not a very good hotel WiFi:
Yes, you can run the UTM tile exporter several times. It will only create new tiles and skip any existing one. If you do 3D tiles keep in mind that they will consume quite a bit of disk space.
Gosh, my tilemaps are whats killing me, I have used 27gigs of ram with more to go, the disk space is easy to come by.
When trans dem uses that much ram its downloader slows to a crawl, why does it need to keep the map tile in ram after it has already downloaded it?
Using the tile downloader AND having the tiles loaded in trans dem is counter productive, but this is currently done while the tile downloader is doing its download, which is whats causing the tile downloader slowdown when downloading 400+ tiles at 2048 res from google ortho imagery with a api private key.
But it still keeps chugging along even with 27 gigs of ram use.. It does finish the 1,000+ tile download, just takes 2 days.
I am doing this work on a 6 core 4ghz 6850k with 32gigs of ram clocked at 3ghz. When dealing with so much ram, transdem cpu use for its single thread is 100% almost the entire time. It never uses more than 100% of a single cpu, like many programs.
When running the UTM exporter transdem launches multiple copies making that process as efficient as possible, so nice.
So this thread was started because of two problems I was doing.
Problem 1: using a DEM file that was not much bigger than my selection area.
Answer: redownload and use a much larger dem file for your area:
https://gdex.cr.usgs.gov/gdex/ I used 1arc data.
Problem 2. selecting too big an export area when doing utm exports.
Answer. the max size limit you should select when doing utm export should be experimented with to determine what works for you, for me its about the size of a mid to large city in America.