This forum deals with any kind of routing computation whether it is simple A:B-routing, calculation of isochrones, simple matrix computation or nearest search.
we maintain our own geo locations for ferry ports and railway stations. Thus we are not relying on the combinedTransportIDs within PTV. What would be the best-practice scenario when calculating a route from A to B with a ferry or rail in between, without using combinedTransportIDs?
Currently we would implement it like that (for ferries):
calculateRoute call for the 1st segment from A to port of departure
calculateRoute call for the 2nd segment from port of arrival to B
draw the polyline for the ferry on your own on the map, to connect the two points (departure and arrival of the ferry)
well, if you have the (x,y) of pickup and delivery ports why not just use them?
START-->Enter Ferry-->Exit Ferry-->DESTINATION
But assure that the usage of ferries is allowed on the leg Enter Ferry-->Exit Ferry.
You might now now but: you can change the routing options at each waypoint...
Best regards,
Bernd
Bernd Welter Technical Partner Manager Developer Components
PTV Logistics - Germany
Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning...
thanks for the answer. How would it be possible to specify a routing optoin that's actually only a line between Start Ferry --> Exit Ferry?
We do not need any distance calculation between those 2 points (x,y) and only expect calculateRoute to draw a simple line between them ("Luftlinie"), not taking into account the distance in meters or kilometers. I was not able to find any setting in the routing options to specify that.
Currently we would split up our calculateRoute request into 2 requests and draw the line between Start Ferry --> Exit Ferry on our own. Same for railways..
Bernd Welter Technical Partner Manager Developer Components
PTV Logistics - Germany
Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning...