You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 1, 2021. It is now read-only.
During the matching algorithm, the software can do an extra check to remove spurious errors. The program may check the edge of the point, and check one (two-customizable) points backwards and one (two-customizable) points forwards to see if their edge is in a street that's on the same class. If the point before (x-1) and after (x+1) are on a highway, and x is not on a motorway, you can do an extra check if the point is near a motorway, and ignore it if it so. Could this be a right idea?
The text was updated successfully, but these errors were encountered:
This should be taken care automatically from the used algorithm based on a simple routing. Also the tag information is currently not available after import (but this is rather easy to fix)
I'll close this for now, as currently there are no real world examples which make the map-matching failing for this scenario. Please reopen if you encounter such issues!
During the matching algorithm, the software can do an extra check to remove spurious errors. The program may check the edge of the point, and check one (two-customizable) points backwards and one (two-customizable) points forwards to see if their edge is in a street that's on the same class. If the point before (x-1) and after (x+1) are on a highway, and x is not on a motorway, you can do an extra check if the point is near a motorway, and ignore it if it so. Could this be a right idea?
The text was updated successfully, but these errors were encountered: