-
Notifications
You must be signed in to change notification settings - Fork 13
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
Comments
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. |
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? |
The matched data are now available for beta testing, the information is posted to the MQTT topic You can try it with Before this is a part of the mainstream version, we need:
|
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. |
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:

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.
The text was updated successfully, but these errors were encountered: