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

skipped connections between nodes with sufficient mvMax #18

Open
chrisnatali opened this issue Feb 9, 2015 · 1 comment
Open

skipped connections between nodes with sufficient mvMax #18

chrisnatali opened this issue Feb 9, 2015 · 1 comment

Comments

@chrisnatali
Copy link
Contributor

In the following grid

1--/--2

With
1.mvMax: 100
2.mvMax: 100
Edge(1, 2): 50

Where the /\ represents a subnetwork with insufficient mvMax to connect to either 1 or 2

1 and 2 will NOT be connected because we interpret the edge(1,2) as creating a cycle (it intersects a subnetwork in more than 1 point). This is true in NetworkPlanner and in this code, but it doesn't seem right.

A more appropriate method of handling this needs to be thought through, but might be to find the closest projected point on the intervening subnetwork and connect nodes 1 and 2 to those points.

@chrisnatali
Copy link
Contributor Author

A more elegant solution would be to lookup nearest geometry as opposed to nearest point and if it's a segment, project a candidate edge onto it.

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