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.

Sign up for GitHub

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

Jump to bottom

Figure out a way to better detect islands and route under all conditions. #104

Closed
xivk opened this issue Jun 13, 2017 · 2 comments
Closed

Figure out a way to better detect islands and route under all conditions. #104

xivk opened this issue Jun 13, 2017 · 2 comments
Assignees
@xivk
Labels
bug
Milestone
Itinero 2.0

Comments

@xivk
Copy link
Contributor

xivk commented Jun 13, 2017

See issue #85

Something else needs to be figured out here, probably marking ways that are part of a routing island per profile to make things really rock solid. I'm going to open a new issue for this.
@xivk xivk added the bug label Jun 13, 2017
@xivk xivk added this to the Itinero 2.0 milestone Jun 13, 2017
@xivk xivk self-assigned this Jun 13, 2017
@xivk
Copy link
Contributor Author

xivk commented Jun 30, 2017

A possible solution could be once #112 is finished to detect islands (optionally) during preprocessing and store them in the routerdb.

@xivk
Copy link
Contributor Author

xivk commented Nov 16, 2017

This has been implemented too, available in 1.4, should become default from 2.0 on.

@xivk xivk closed this as completed Nov 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xivk xivk

Labels
bug
Projects
None yet
Milestone
Itinero 2.0
Development

No branches or pull requests
1 participant
@xivk