I know that either deleting the extra data point, or moving the turn instruction up to the first of the two data points, would correct the problem. But what about situations where I don't know that MapsOnUs has fed me this kind of data and it's in the player and it's now too late?

If they're literally the same I can probably make a quick patch to simply drop one. However, the Python should be fixed to really drop it, if it isn't.

Also, this brings up the point of what happens if you see e.g.

2774 -1955
2812 -1963
2813 -1964
2821 -1927

where you in fact have a quick "left" before a hard "right". It would be nice to assume it doesn't happen, or it's accurate when it does. Is it? I don't know.