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

Matching Behaviour is incorrect #164

Open
NitinSingh1812 opened this issue Aug 11, 2023 · 0 comments
Open

Matching Behaviour is incorrect #164

NitinSingh1812 opened this issue Aug 11, 2023 · 0 comments

Comments

@NitinSingh1812
Copy link

Hi Team,

I am trying to use barefoot with my custom map network & a set of GPS points.
I am following the steps mentioned for distributed processing by Spark.

I am mapping BaseRoad(long id, long source, long target, long refid, boolean oneway, short type, float priority, float maxspeedForward, float maxspeedBackward, float length, Polyline geometry) to my Map edges, source vertex, target vertex, oneway and have set default values for type, priority, maxspeedForward and maxspeedBackward. I am creating the Polyline and computing the length by Polyline.calculateLengthIn2D.

I have created a custom implementation of RoadReader. I am creating MatcherSample list using a set of GPS Points.

The output in MatcherKState is completely off track and I am trying to understand what could be the problem since the Map co-ordinates are passed correctly.

image

As you can see from the above image, a small part of matching where dotted line represents GPS points & the solid lines show matched edges.

Is there something I should keep in mind before using a custom map network?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant