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.

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

Implement route matching #36

Closed
roata opened this issue Oct 4, 2019 · 4 comments
Closed

Implement route matching #36

roata opened this issue Oct 4, 2019 · 4 comments
Labels
enhancement New feature or request help wanted Extra attention is needed
Milestone

Comments

@roata
Copy link
Member

roata commented Oct 4, 2019

Due to the fact that raw GPS telemetry data is a bit noisy and inaccurate, the vehicle markers are slightly off the actual route. While this is not critical, i.e. the site still serves its function and makes peoples' lives better, a polished product should look better.

This is what I mean:
image

Instead of showing the raw position, we should project the marker onto the line segment where it ought to be, creating the illusion that it really moves on the route.

@roata roata added enhancement New feature or request help wanted Extra attention is needed labels Oct 4, 2019
@roata roata added this to the 2.0.0 milestone Oct 4, 2019
@leanu
Copy link

leanu commented Nov 1, 2019

If you have 'segments', need to find closest segment, and 'project' transport to it. But as I see, segments are pretty raw, from osm, sometimes they cross the road, and are in both direction the same. I mean, it would be nice to have position not in the mid of the road, but on the right half, depending on the dirrection.

@roata
Copy link
Member Author

roata commented Nov 1, 2019

It would definitely be nicer, but this would require an additional effort - either to make OSM data more detailed, or to post-process it after we retrieve it. I don't know of a way to do that easily. Have you got any ideas?

@roata
Copy link
Member Author

roata commented Dec 27, 2019

The matched data are now available for beta testing, the information is posted to the MQTT topic telemetry/transport/chiK8n/1/1/+ (the last element is the tracker ID).

You can try it with mosquitto_sub -h opendata.dekart.com -p 1945 -t telemetry/transport/chiK8n/1/1/+.

Before this is a part of the mainstream version, we need:

  1. A debugging aid for visualizing map data, to see how well the matching works and tune the algorithm's parameters. It could be an HTML page that one can open locally and see live data. @iamandrewluca, do you have any suggestions about the easiest way to test this?
  2. Eventually, the switch to MQTT transport must be accomplished Switch to the MQTT-backed transport #81, because redirecting the data between the legacy (AMQP) and new (MQTT-based) systems will result in infinite loops.

@roata
Copy link
Member Author

roata commented Dec 31, 2019

This was resolved by applying changes to the backend, hence there is no specific commit to link to.

The map will now snap the marker to the nearest road, found within a radius of 10m. There will be false positives, of course. However, this change brings the UI to a "good enough" level that balances aesthetics and practicality.

This can be improved, when more people join the project and more time can be dedicated to this issue.

@roata roata closed this as completed Dec 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants