Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail less often for intersection geometry #243

Open
2 tasks
dabreegster opened this issue Mar 17, 2024 · 4 comments
Open
2 tasks

Fail less often for intersection geometry #243

dabreegster opened this issue Mar 17, 2024 · 4 comments

Comments

@dabreegster
Copy link
Contributor

Especially when we use raw OSM footways, we break on so many intersection geometry cases (the circles):
image

I'll start looking into these, but I've also been looking at how https://github.com/StrandedKitty/streets-gl handles things. It's much more robust.

TODO:

  • Can we have an optional mode where we don't trim back road center-lines at all and have empty intersection polygons, just to debug and see how it looks?
  • Investigate what streets-gl does and see if we can adapt ideas from it

CC @BudgieInWA in case you're interested or have ideas. osm2streets has revived thanks to the Muv work. I'm kind of interested in getting footways and crossings all showing up exactly as they're in OSM, and generally getting rid of the old inferred sidewalks mode.

@dabreegster
Copy link
Contributor Author

Many of the problems are happening at degenerate intersections, with exactly 2 edges. There's a hardcoded length we demand to trim roads back. The Aurora example fails because the footways are split into tiny pieces to show curb cuts, so I tried reducing this distance a bunch. Doing better, but looking carefully at the polygons shows overlapping bits, so I'll keep looking at it.
image

@dabreegster
Copy link
Contributor Author

Ah actually much of the noise was the sidewalk-corner markings being applied when they shouldn't. But still a few "bow-tie" cases with the degenerate intersection geometry that could be improved,
image

@dabreegster
Copy link
Contributor Author

... but also regressions with fixed 0.1 meter, by https://www.openstreetmap.org/node/2918402990. Maybe the relative thickness/angle of the two roads needs to matter. Do we need this hardcoded param at all? Can we just make a triangle or quadrilateral generically?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant