ANDROID iGO Avicsync 9.35.2.227616

iGO AVICSYNC – HERE/TRUCK routing issue. Could an automatic HERE map converter be developed?

Thank you for your replies.

I would like to clarify two additional points.

1. Does the same problem occur in iGO Israel and PAL?

Has anyone tested whether iGO Israel and iGO PAL calculate truck routes correctly with HERE maps when toll road avoidance is enabled?

I am particularly interested in whether these versions correctly distinguish roads covered by mandatory electronic truck toll systems, such as e-TOLL in Poland and Toll Collect in Germany, from motorway sections with additional toll charges.

Does this problem also occur in Israel and PAL, or is it specific to AVICSYNC 9.35.2?

2. Would it be possible to develop an automatic converter for HERE maps?

Since AVICSYNC calculates truck routes correctly with TomTom maps, but incorrectly interprets toll roads with HERE maps, I wonder whether a tool could be developed to automatically correct the relevant data in HERE maps.

The objective would be to make AVICSYNC interpret HERE toll road information in the same way it successfully handles TomTom map data.

I am not suggesting removing all toll road information or disabling truck restrictions.

All restrictions concerning vehicle weight, dimensions, truck access prohibitions and ADR should remain fully functional. Only the interpretation of electronic truck tolls would need to be corrected.

Has anyone involved in iGO modifications investigated this possibility?

Is the problem related to the structure or attributes of HERE map files (.fbl, .ftr), or is it caused by the AVICSYNC routing algorithm itself?

I understand that HERE and TomTom map formats may differ and that direct conversion may not be possible. I am asking whether the relevant toll attributes could be corrected automatically, rather than converting entire maps.

Perhaps there is a way to solve the underlying issue without abandoning AVICSYNC.

Best regards.