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

Core edge filters not properly initialized for certain profiles #785

Closed
aoles opened this issue Aug 11, 2020 · 0 comments · Fixed by #787
Closed

Core edge filters not properly initialized for certain profiles #785

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

Comments

@aoles
Copy link
Member

aoles commented Aug 11, 2020

The matching of core edge filters to routing profiles fails because of a mismatch between the flag encoder names in FlagEncoderNames and the names used by the method RoutingProfileCategory.getFromEncoder.
@aoles aoles added bug 🐞 Erroneous behavior of the backend core-alt :atom: labels Aug 11, 2020
@aoles aoles self-assigned this Aug 11, 2020
@aoles aoles mentioned this issue Aug 11, 2020
Merged
12 tasks
@takb takb closed this as completed in #787 Aug 12, 2020
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.

Use constants defined in FlagEncoderNames rather than hard coded names GIScience/openrouteservice
1 participant
@aoles