Removal of the hard-coded Mapbox access token (that just 401'd for me anyway).
If the access token was meant to be there (and I just happened to try it while the free quota was done with), it can be defaulted back in.

Yup, my old token seems to have gotten revoked suddenly - I fixed that with a quick hotfix today.
Just wanted to point that out real quick, I'm still feeling a bit sick but I'll do a code review asap! :)

@louis-e Get well soon! I can rebase this on top of the new stuff tomorrow or so, and make the CLI default to the hard-coded default token 👍

⏱️ Benchmark run finished in 0m 43s
🧠 Peak memory usage: 1614 MB

📈 Compared against baseline: 42s
🧮 Delta: 1s
🔢 Commit: e95a6ff

🟢 Generation time is unchanged.

You can retrigger the benchmark by commenting retrigger-benchmark.

Hi there, thanks a lot for the great contribution! Especially the tile caching is amazing. I was already thinking about doing that via a proxy server, but turns out that is not allowed according to the Mapbox guidelines. So client side caching is a good idea.

I have to test it more thoroughly but one thing I saw is that you missed out returning the ground in pub fn generate_ground_data(args: &Args) -> Ground {

That might explain this :)

The generated map with this data is just flat :(

retrigger-benchmark

Sorry for the delay, I was on a business trip and got sicker afterwards - I pushed a fix for the last error I mentioned and will merge the PR now! :)

Good catch on the return! I, too, was AFK for about 3 weeks (in Japan 🗻). Thanks!