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

GUI improvements #78

Open
kodonnell opened this issue Nov 14, 2016 · 1 comment
Open

GUI improvements #78

kodonnell opened this issue Nov 14, 2016 · 1 comment

Comments

@kodonnell
Copy link
Contributor

There are some flaws:

  • it displays an entire edge even if only part of the edge is travelled on (this is at start/end of route, and in the middle, e.g. when U-turning partway down edge)

It could be enhanced to help debugging:

  • add candidate locations on for each gpx entry (and display emission/transition probabilities?)
  • animate to see step-by-step
  • more inputs (e.g. sigma/beta probabilities)
  • add some leaflet controls e.g. distance measurement and displaying location of click (both helpful while debugging).

UI improved:

  • rerun routing without having to reload file ... maybe even on change of parameters.

Other stuff ...

@karussell
Copy link
Member

karussell commented Nov 15, 2016

Would be really nice additions :) !

it displays an entire edge even if only part of the edge is travelled on

Here it is not the UI. It is more the API (even the Java API is wrong in this regard) which removes virtual edges as they do not make sense outside of the calculation without the appropriate QueryGraph and we calculate the wrong geometry as we only have real edges.

What we would need are three three informations: the correct geometry, the list of edges and a notation that some of those edges are partial. Or some other solution, this is the same as requested in #50 and partially implemented in #51

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