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

Failing assertion with CoreALT routing #1047

Closed
aoles opened this issue Aug 30, 2021 · 0 comments · Fixed by #1053
Closed

Failing assertion with CoreALT routing #1047

aoles opened this issue Aug 30, 2021 · 0 comments · Fixed by #1053
Assignees
@aoles
Labels
bug 🐞 Erroneous behavior of the backend core-alt :atom:

Comments

@aoles
Copy link
Member

aoles commented Aug 30, 2021 •
edited
Loading

CALT routing might fail throwing the following error when run-time assertions are enabled by the -ea flag . The problem seems to originate from an attempt of checking whether a virtual node is a core node.

Caused by: java.lang.AssertionError: node 11067 is invalid. Not in [0,11066)
	at com.graphhopper.storage.CHGraphImpl.checkNodeId(CHGraphImpl.java:120) ~[graphhopper-core-v0.13.15.jar:?]
	at com.graphhopper.storage.CHGraphImpl.getLevel(CHGraphImpl.java:115) ~[graphhopper-core-v0.13.15.jar:?]
	at org.heigit.ors.routing.graphhopper.extensions.core.AbstractCoreRoutingAlgorithm.isCoreNode(AbstractCoreRoutingAlgorithm.java:203) ~[classes/:?]
	at org.heigit.ors.routing.graphhopper.extensions.core.CoreALT.fillEdgesFrom(CoreALT.java:131) ~[classes/:?]
...
@aoles aoles added bug 🐞 Erroneous behavior of the backend core-alt :atom: labels Aug 30, 2021
@aoles aoles self-assigned this Aug 30, 2021
@aoles aoles mentioned this issue Aug 30, 2021
Merged
12 tasks
@takb takb closed this as completed in #1053 Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aoles aoles

Labels
bug 🐞 Erroneous behavior of the backend core-alt :atom:
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check for virtual node before querying node's level GIScience/openrouteservice
1 participant
@aoles