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

Try bundle classification based on the number of major roads #264

Merged
merged 1 commit into from
Apr 5, 2024

Conversation

dabreegster
Copy link
Contributor

#248. I'm looking at a particularly uniform area in California that has a clear pattern of junctions, corridors, and land use blocks. Before this PR, the classes were a mess:
image
With this PR, most cases become correct:
image

Some of the misclassifications will be tricky to remedy. Some more ideas to think about later:

  • does the cumulative length of roads at different angles inside the bundle tell us anything?
  • if we look at the connections between bundles, even if they're misclassified, can we start to put together a simplified graph?

@@ -4,52 +4,3 @@ pub use osm_reader::{NodeID, OsmID, RelationID, WayID};

// This is a commonly used key in the codebase, so worthy of a bit of typo-prevention
pub const HIGHWAY: &str = "highway";

#[derive(PartialEq, Eq, PartialOrd, Ord, Clone, Copy, Debug)]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All unused in this codebase and the list of highway types has become out-of-date with everything now. So removing.

@dabreegster dabreegster merged commit 8fb4efa into main Apr 5, 2024
@dabreegster dabreegster deleted the bundle_classes branch April 5, 2024 21:05
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

Successfully merging this pull request may close these issues.

1 participant