Route transfer as a basic function
Planning and then driving a route – child’s play? Far from it. Just marking a few points on a route and transferring that is not enough. After all, you do not plan a route just to then have the navigation system calculate how to get there – without taking into account the factors you so carefully considered in the first place.
Therefore, the route as a whole has to be transferred from a planning software to the navigation solution – which is where standards and the big question of compatibility come into play. If you want to include current, relevant information with the planned routes and therefore in the routing and navigation software, things get even more complicated.
So how do the geodata get into the navigation system? In brief: MapTrip creates the reference route from a CSV file. So when a scheduler uses a logistics solution for planning, the route can be converted into this easy to generate, text-based format and transferred to the corresponding devices. Then MapTrip can access it using the interface command or GUI (“Load reference route”). Logically MapTrip treats this route as a reference route – which is retained even if the driver deviates from the plan. So MapTrip finds the best way back.
So that's the technology (visit the Developer Zone for more information). But what we keep hearing is: That's really easy! Because we solve a logistics problem that has been around for a long time.