Cut my life into pieces - this is my last HPR
Posted: Wed Oct 25, 2023 7:41 am
Just for fun I've been discussing with a partner about how to structure his system of HPRs (HIghPerformanceRoutingNetworks) in a story that is build upon a set of disjunct planning areas (several depots, each with a more or less static amount of assigned customers) within a meta area (e.g. ZZ-EUR or Germany). I could imagine different technical approaches of how to model this. For the moment let's assume that we are dealing with s single vehicle profile (though in reality such a user story quickly turns into a "multi vehicle types").
Before I start with the comparison let's define some terms:
Before I start with the comparison let's define some terms:
- Meta Area : the smalles area where all future actions such as routings (1:!) and tour optimizations (N:N) are supposed to take place - over all depots and all customers. Some players may simply use the given pre-defined continental codes such as ZZ-EUR. Or they specify a set of country codes such as ["DE","AT","CH"] to describe a business market area. In both cases the GeographicRestrictions based on allowedCountries apply.
- Depot Area : This approach is based on the depot's coodinates and it's assigned location's coordinates. We first compute the bounding rectangle around the involved locations and then add some buffered space around it. For this approach custom search space bounds are required. .
- Sidenote: An alternative to the bounding rectangle could be a computed, route base geometry such as an isochrone:
Label | Description | Pro's | Con's |
---|---|---|---|
1 graph per meta area |
|
| |
1 graph per depot area |
|
|