Do you think maps inaccuracy or devices cause the issue?
It's devices issue for sure
Maybe you can add some business cases when this feature can be useful.
While you track vehicles and set some geofences as check points (like when you track buses and check points are stations) devices inaccuracy cause considering some check points missed while vehicle touched them. You may say draw geofences bigger, but proble is that sometimes vehicles goes inside 2-way streets and only on one side of street we have check points or stations. in these cases you have to draw geofences as small as you can and use high accuracy devices, snap to roads will help in this case. Another case is when you draw a linear geofence to control vehicles path, devices inaccuracy will cause mistakes in reports and reports says vehicles went out of geofence while it has never happened.
"Snap to road" feature will increase the time of building a track
I'm not sure if Gurtam maps has snap to road function or not, but I have to say, what we asked is not about Tracks only, we asked for a function in Wialon that if user applied it, then Wialon save more data in it's DB about units. Which data? It should check each point that device sends to Wialon and do correction on each points and save both point (the point is received from device and corrected point with snapp to road). Then, can use each sort of data (received or corrected) in whole system (reports, Notifications, Tracks). As I understand Google charge customers per each query, a way to decrease costs is to do these corrections each 6 hours or one time per day.