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

NearestEdgeFinder not finding edges when using geodetic coordinate systems #2

Open
aschengen opened this issue Jul 25, 2019 · 0 comments

Comments

@aschengen
Copy link
Collaborator

aschengen commented Jul 25, 2019

Geodetic CS are usually interpeted as decimal degrees. Due to float viewDist = 10; (Line 92), the predicate viewDist < Math.max(net.size.x, net.size.y) will almost always falsify unless your network is larger than ~1110km (@ the equator :) ).
As of now one can bypass this issue by just using a projected CS in meters and reproject the result into the desired coordinate system afterwards.

@dkrajzew dkrajzew added enhancement New feature or request usability and removed enhancement New feature or request labels Mar 25, 2020
@dkrajzew dkrajzew added this to the post0.6 milestone Feb 10, 2023
@dkrajzew dkrajzew removed this from the post0.6 milestone Jun 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants