Hi Dear Bernd and Sebastian!
One of our clients came up with an interesting problem.
Let me try to explain it with and example:
1. Lets say we have a freight order from Wien to Stuttgart.
2. The order has been set in our TMS system, and it has already been sent out to the driver, who is already on route to Stuttgart, let's say his already around München.
3. The freight controller realises, he has forget to create an exact route for the driver, he only just sent out the order, and the addresses, but not the guided route. So he creates a route and send it out using a .BCR file to the driver.
4. The driver opens the .BCR with his PTV Navigator.
What happens is now the Navigator would create a route, from his current position, to the upload station in Stuttgart.
Is there any way to somehow direct the driver to the closest point of the already ongoing route (somewhere near München) and use the guided navigation from there?
Thank you,
Peter
Guided navigation for ongoing transports
-
- Posts: 18
- Joined: Tue May 28, 2019 10:45 am
Re: Guided navigation for ongoing transports
Hi Peter,
depending on what you have set the value:
REROUTEATTRACTIONFACTOR the navigator will in any ways reroute to the closest point to the destination.
My recommendation is here to do the following:
- Set the first destination to visited
- Set the RouteReattracionfactor to max 70
So independent of where the driver is then starting his tour, it will normally lead to the closest point on the route direction destination.
This is how a BCR header will look like:
[CLIENT]
REQUEST=true
ROUTENAME=Vienna - Stuttgart
STATION1=Standort,999999999
STATION2=Standort,999999999
TIME=34572
REROUTEATTRACTIONFACTOR=70
[COORDINATES]
STATION1=1820084,6133758
STATION2=1019882,6228574
[DESCRIPTION]
STATION1=A 1*** Vienna
STATION2=D 70*** Stuttgart
[VISITED]
STATION1=1
STATION2=0
depending on what you have set the value:
REROUTEATTRACTIONFACTOR the navigator will in any ways reroute to the closest point to the destination.
My recommendation is here to do the following:
- Set the first destination to visited
- Set the RouteReattracionfactor to max 70
So independent of where the driver is then starting his tour, it will normally lead to the closest point on the route direction destination.
This is how a BCR header will look like:
[CLIENT]
REQUEST=true
ROUTENAME=Vienna - Stuttgart
STATION1=Standort,999999999
STATION2=Standort,999999999
TIME=34572
REROUTEATTRACTIONFACTOR=70
[COORDINATES]
STATION1=1820084,6133758
STATION2=1019882,6228574
[DESCRIPTION]
STATION1=A 1*** Vienna
STATION2=D 70*** Stuttgart
[VISITED]
STATION1=1
STATION2=0
Re: Guided navigation for ongoing transports
Hi Sebastian,
That's a great solution!
We'll start to implement this one in the next few weeks.
Thank you!
Best regards,
Peter
That's a great solution!
We'll start to implement this one in the next few weeks.
Thank you!
Best regards,
Peter
Re: Guided navigation for ongoing transports
Dear Sebastian,
We attempted to implement the REROUTEATTRACTIONFACTOR parameter into the .BCR file, but encountered a new problem we cannot resolve.
When we load the .BCR into the Navigator, the app fails to generate a route from the driver's position.
In our example, this position corresponds to an address in Szeged (46.261436, 20.128069).
We adjusted the REROUTEATTRACTIONFACTOR to various values (e.g., 100 and 40), but there was no change.
The header of the .BCR looks like this:
[CLIENT]
REQUEST=true
STATION1=POI,999999999
STATION2=POI,999999999
STATION3=POI,999999999
TIME=32262
ROUTENAME=2023/1809 jarat Bekescsaba - Siofok
FORGETWEAKLORRYRESTRICTIONS=1
REROUTEATTRACTIONFACTOR=70
[COORDINATES]
STATION1=2346229,5883744
STATION2=2107358,5802289
STATION3=2007627,5920267
[DESCRIPTION]
STATION1=Bekescsaba 2023-08-21 08:00
STATION2=HU Baja 2023-08-21 12:00
STATION3=Siofok 2023-08-21 14:00
[VISITED]
STATION1=1
STATION2=0
STATION3=0
Do you have any insights or suggestions on what might need modification to resolve this?
Interestingly, when the [Station2Segmentcenters] section is removed from the .BCR, the Navigator generates a route to the second station.
I have attached a screenshot for your reference.
Thank you in advance!
Best regards,
Peter
We attempted to implement the REROUTEATTRACTIONFACTOR parameter into the .BCR file, but encountered a new problem we cannot resolve.
When we load the .BCR into the Navigator, the app fails to generate a route from the driver's position.
In our example, this position corresponds to an address in Szeged (46.261436, 20.128069).
We adjusted the REROUTEATTRACTIONFACTOR to various values (e.g., 100 and 40), but there was no change.
The header of the .BCR looks like this:
[CLIENT]
REQUEST=true
STATION1=POI,999999999
STATION2=POI,999999999
STATION3=POI,999999999
TIME=32262
ROUTENAME=2023/1809 jarat Bekescsaba - Siofok
FORGETWEAKLORRYRESTRICTIONS=1
REROUTEATTRACTIONFACTOR=70
[COORDINATES]
STATION1=2346229,5883744
STATION2=2107358,5802289
STATION3=2007627,5920267
[DESCRIPTION]
STATION1=Bekescsaba 2023-08-21 08:00
STATION2=HU Baja 2023-08-21 12:00
STATION3=Siofok 2023-08-21 14:00
[VISITED]
STATION1=1
STATION2=0
STATION3=0
Do you have any insights or suggestions on what might need modification to resolve this?
Interestingly, when the [Station2Segmentcenters] section is removed from the .BCR, the Navigator generates a route to the second station.
I have attached a screenshot for your reference.
Thank you in advance!
Best regards,
Peter