You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2021. It is now read-only.
I want to add a new weightings — shortest and short_fastest. At least, to try it. Because I experienced the problem that Graphhopper generates not good route for MTB (too easy and "fastest" in terms of time). Komot generates better route (also uses GH, as far I know: https://github.com/komoot/graphhopper).
But I cannot find values in GeoDataExtra.
Is it ok if I will use custom int values?
private const val MTB_SHORTEST = 40
private const val MTB_SHORT_FASTEST = 41
private const val HIKE_SHORTEST = 42
private const val HIKE_SHORT_FASTEST = 43
or change in Locus API is required?
The text was updated successfully, but these errors were encountered:
Hi,
this is a little more complicated and adding extra types needs extra work not just in the API, but also in the app. As I see, the current system is really not flexible and extending is very cumbersome :/.
Anyway, trackTypes field returns the list of supported types and in computeTrack is then specific setup for every value.
So it is very simple for you to play with it and set certain flags & weighting here. If there will really be a need for some extra types, let me know and I'll add them into API.
I want to add a new weightings —
shortest
andshort_fastest
. At least, to try it. Because I experienced the problem that Graphhopper generates not good route for MTB (too easy and "fastest" in terms of time). Komot generates better route (also uses GH, as far I know: https://github.com/komoot/graphhopper).But I cannot find values in
GeoDataExtra
.Is it ok if I will use custom int values?
or change in Locus API is required?
The text was updated successfully, but these errors were encountered: