Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork359
Make LTN cell calculations account for one-way roads#1043
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Some good results, some weird
Maybe it should be defined per entry into the area? If there's a "loop" like this, if you enter as part of the loop, you're forced out. But if you enter from the other side and join the loop, then it forces you out. Those are different cases. And maybe all the shortcutting traffic is trying to enter from one boundary road, and the other isn't a real problem. |
Problem: Sometimes one-ways can effectively block off part of an area:

There's just one large purple cell, though, because the current calculation ignores direction of the roads.
This PR is a start to taking them into account:

But even this example gets confusing. Why is there the tiny blue cell at the bottom? There are "spurious" changes in cells based on the order we happen to floodfill. For example we have both:


and
I think this idea has potential, but there are subtleties. A cell is meant to represent everywhere you can reach without leaving the area. One-ways throw that off.