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

Turn-by-turn instructions #6

Open
xivk opened this issue Jun 4, 2020 · 2 comments
Open

Turn-by-turn instructions #6

xivk opened this issue Jun 4, 2020 · 2 comments
Assignees
@pietervdvn
Milestone
Itinero - Itinero...

Comments

@xivk
Copy link
Contributor

xivk commented Jun 4, 2020

No description provided.

@pietervdvn pietervdvn self-assigned this Jun 4, 2020
@pietervdvn
Copy link
Contributor

  1. How done in itinero1 (architecturally)? How in other engines?
  2. Instruction generation is inefficient due to lua calls. How to do more efficiently?
  3. What about translations? Server side or client side? Sending an abstract version to the client?
  4. Totally different package?

Note: in the route object, branches are included
Setup a small project in itinero2, make something simple that works.

Future work:

Network: 'follow along network Groene Wandeling', 'go to Westtoer node 12'

@pietervdvn
Copy link
Contributor

Current itinero uses rewrite rules to group commands

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pietervdvn pietervdvn

Labels
None yet
Projects
None yet
Milestone
Itinero - Itinero1 feature parity.
Development

No branches or pull requests
2 participants
@xivk @pietervdvn