19
edits
Howto:Use TerraGear without wanting to kill yourself: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Use TerraGear without wanting to kill yourself (view source)
Revision as of 16:17, 14 October 2021
, 14 October 2021some clarification+ce
IskenderWang (talk | contribs) (Created page with "My aim was to go through this whole process successfully with as little manual labour (don’t have the knowledge to go fine tuning in QGIS? no problem! neither did I) as poss...") |
IskenderWang (talk | contribs) m (some clarification+ce) |
||
| Line 131: | Line 131: | ||
[[File:QGIS example for TG 1.png|thumb|right|Obviously we'd never need all this, that's why we had further split up these shapefiles]] | [[File:QGIS example for TG 1.png|thumb|right|Obviously we'd never need all this, that's why we had further split up these shapefiles]] | ||
'''BRO TIP''': I didn’t | '''BRO TIP''': I didn’t realise this myself at first as a n00b to the toolkit, but I was advised by legoboyvdlp that osm_unclassified actually includes numerous roads and isn’t as irrelevant as the name would suggest, in fact it’s better to include this and PRUNE osm_residential for improved performance. | ||
[[File:QGIS example for TG 2.png|thumb|left|Here you can see a big difference, not to mention I also ended up pruning the selected osm_residential landclass]] | [[File:QGIS example for TG 2.png|thumb|left|Here you can see a big difference, not to mention I also ended up pruning the selected osm_residential landclass]] | ||
| Line 168: | Line 168: | ||
And have patience, because this could take a while! '''Seriously!!''' | And have patience, because this could take a while! '''Seriously!!''' | ||
For legoboyvdlp, Ireland took a whole week (nonstop!!) to generate! And even for a relatively small scale such as Hong Kong and some of the surrounding area, because the Pearl River Delta is rather dense and data-rich, it took me 24 hours on my 2017 Macbook Pro just for it to reach stage 2 (the second stage out of three, the last of which generates the BTG files), at which point it inexplicably killed the process! So I had to pull out the big guns, and on my heavier rig (8 core CPU, running at 14 threads) at last I was able to complete the whole process in just about three hours (wow!) with Ubuntu in WSL, compiled from source using the download_and_compile script, followed by adding ''install/terragear/bin'' to my <code>$PATH</code> – this way, all the terragear tools can be called normally. | For legoboyvdlp, Ireland took a whole week (nonstop!!) to generate! And even for a relatively small scale such as Hong Kong and some of the surrounding area, because the Pearl River Delta is rather dense and data-rich, it took me 24 hours on my 2017 Macbook Pro just for it to reach stage 2 (the second stage out of three, the last of which generates the BTG files), at which point it inexplicably killed the process! So I had to pull out the big guns, and on my heavier rig (8 core CPU, running at 14 threads) at last I was able to complete the whole process in just about three hours (wow!) with Ubuntu in WSL, compiled from source using the download_and_compile script, followed by adding ''install/terragear/bin'' to my user <code>$PATH</code> (in .zshrc, for me) – this way, all the terragear tools can be called normally. | ||
So you see, the quickness of this step will depend entirely on a) the processing power at your disposal and b) the size and richness of the scenery you aim to generate. It may fail along the way for reasons you don’t understand – that’s OK, as long as you know you followed the process correctly just try again and most likely, it should work after some time. | So you see, the quickness of this step will depend entirely on a) the processing power at your disposal and b) the size and richness of the scenery you aim to generate. It may fail along the way for reasons you don’t understand – that’s OK, as long as you know you followed the process correctly just try again and most likely, it should work after some time. | ||