Express transformations to run better about osm2streets HOT 4 CLOSED

I started this -- apologies for not waiting on a PR, I keep stomping on myself with all the open branches, and I'm starting to feel time pressure from SotM. Feel free to review at your leisure. I can also help rebase your open PR against any changes.

No worries. It was a surprise to see the merge conflict updating from main, but the level of documentation within the commit messages and how they're tied back to the GH issues is more than enough. Let's adopt a "merge first, then ask for forgiveness" attitude for this repo, where it unblocks subsequent changes. (e.g. I am a fan of immediately merged PRs as a place for discussion after the fact, and simply commenting on commits on GH too.)

from osm2streets.

Sounds good. Speciality transformations too, for speciality uses like routing a racing line or something.

It will be useful to run a list of transformations as part of creating a new StreetNetwork to get it into a valid state. (That way we can get the benefits of stepwise debugging and a clear way of expressing the order of steps.) Classifying intersections feels like part of new, but isolating it in its own transformation is nice.

from osm2streets.

I started this -- apologies for not waiting on a PR, I keep stomping on myself with all the open branches, and I'm starting to feel time pressure from SotM. Feel free to review at your leisure. I can also help rebase your open PR against any changes.

from osm2streets.

I'm happy enough to call this issue closed:

The web app exposes some settings to enable optional steps. We could go crazy with that interface and let people drag-and-drop all possible steps and make up their own list, but that feels overkill at this point

from osm2streets.