Start modelling movements at intersections #93
Conversation
…movement at a time.
they occur in the debug mode.
|
What am I looking at here... 🤔 I initially assumed that the red arrows are illegal moves and the blue one is legal, but that doesn't seem correct. I'd expect there would need to be at least 1 way to either enter or exit each segment. Or maybe I am reading it correctly, and we just haven't fleshed out all the legal turns from the available restrictions yet? |
| to = Some(*w); | ||
| } else { | ||
| // Some other case, bail out | ||
| return; |
There was a problem hiding this comment.
I'm not very familiar with this logic yet, but should these be continue?
| let angle = angle_of_line(line); | ||
| Polygon::new( | ||
| LineString::new(vec
Part of #30 (with some TODOs there) and also necessary for #41. This adds a debug mode (from the "pick neighbourhood" page) to understand movements at each intersection. They're generated by looking at one-way directions and the simplest OSM turn restriction cases. Only used in this debug mode right now, not yet for routing.
It's going to be much easier to flesh this out with a better unit testing story. I'm thinking of manually drawing / clipping some test cases in JOSM, checking those in here. For movements, maybe the output can be expressed in the code as a list of movements between named roads, or maybe some GeoJSON / SVG output would be faster to understand.