Sequence is broken for submitted track about map-matching

[braito4]

you should clean the gpx before do the matchmaking.

[andrew-hardin]

Thank you for the suggestion. I've pruned the track down to just 8 points that cause the error. Here's the new track file and the updated error message: bus_minimal_example.txt

java.lang.IllegalArgumentException: Sequence is broken for submitted track at time step 3 (8 points).
observation:Observation{point=35.06498,-106.5506,0.0},
3 candidates: [
        distance: 14.46840573628661 to 35.06509572413032,-106.55052732416677,NaN,
        distance: 6.387625781247086 to 35.0649789919093,-106.55052982726808,NaN,
        distance: 6.387625781247086 to 35.0649789919093,-106.55052982726808,NaN].
If a match is expected consider increasing max_visited_nodes.

The updated track is plotted above. The vehicle is traveling from north to south along a road that splits temporarily into a pair of one-way streets at a security checkpoint. Any idea how to troubleshoot this?

[braito4]

The problem is that open streetmap doesn't have mapped that road:

I added:

Try now
yo can edit it here: https://www.openstreetmap.org/edit#map=20/35.06568/-106.55061

Be careful with the behavior of the gates/ford

Also, wait a day to download the new pbf; that's normally the time they need to update the map in the servers

[andrew-hardin]

I've downloaded the new pbf from OSM and the vehicle is being routed along the service road. That map edit resolves the initial problem, but I dug a little deeper because I wanted to understand why it wasn't routing along the one-way road.

The root cause ended up being the behavior of the gate on the south-bound lane. There was a GPS snap-point that was just south of the gate along the one-way road that couldn't be reached. This broke the Viterbi path.

I'll go ahead and close the issue - the broken sequence was caused by a problem with the OSM data and not the library. Thank you for your help, @braito4.