Skip to content
This repository has been archived by the owner on Feb 18, 2021. It is now read-only.

shortest / short_fastest weightings #7

Open
develar opened this issue Mar 29, 2020 · 1 comment
Open

shortest / short_fastest weightings #7

develar opened this issue Mar 29, 2020 · 1 comment
Assignees

Comments

@develar
Copy link
Contributor

develar commented Mar 29, 2020

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?

@menion
Copy link
Member

menion commented Apr 7, 2020

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.

@menion menion self-assigned this Apr 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants