We intend to use the map mathcing API for getting the type and surface for our MountainBike GPX tracks.
However when a segment is not present on OSM the map matching algorithm seems to force a detour with known routes, hence introducing unwanted behavior for our usage as inexact statistics would be returned.
Would there be a way to avoid this behavior, ie force the map matching “to not match” when no segment is available in OSM ?
Which reprensents a change of 18% of the itinerary becaus eht Mountain bikeer decided to follow nonexisting OSM transportation artefacts.
And ends up with 8 additonnal ‘unwanted’ kilometers after map matching.
Do you see an option to lower this type of behavior, knowing our main interest here is to collect data of surfaces and type of trasportation (roads versus tracks) ?