You can compare the meaning of this parameter with the xRoute1 ExceptionPath:values [0,100] in percent of cost per segment of the original route to influence the attraction to this route.
So 0 is very attractive, while 100 restores the regular behaviour without attraction
First we compute a base route.
Then we use the base route as exception path for the continuous re-routings considering the REROUTEATTRACTIONFACTOR.
Update 26.7.2021:
With the SDK you can set the native value of the attraction parameter as mentioned above.
But: in the Navigator application's BCR file itself you can only set some meta values:
- -1 : do not consider
- 0 : strong
- 1 : normal
- 2 : weak