Weekend project (do not look at the source): https://sat9.land/x/swath/#0,25500
Forgot to add the warning: this is intended for, and only tested on, desktop browsers.
Various fixes. It now uses fourth-order Runge–Kutta integration to place the labels, which is objectively overkill and also I probably put many bugs in it, but I had fun and that’s the important thing.
I say objectively overkill because Euler was computationally faster, even though it took a few more steps.
Also, there’s a really wide range of h parameters that are tied for optimality. Taken together, this makes me think that it’s the lumpiness of the topography that’s the main limit here. But I’m in way over my head mathematically, so I could easily be misimplementing or misinterpreting.
Anyway, this is easily the silliest thing I’ve ever done with ground control points.
Should I finish a devlog about this even though it’s getting a bit out of hand and probably makes errors about the math I had to learn?
Okay, here we are: https://gist.github.com/celoyd/f163e6e582d87a50a6d37743e840dcb8
Posted while running out the door to carve pumpkins. There are probably a few TKs and such, and I didn’t spellcheck it. (Visual Studio Code doesn’t do that, apparently, at least on Ubuntu?)
@vruba amazingly not built-in, but this spellcheck plugin is popular: https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker (but I use Vale)