Version 2.4

Version 2.4 contains lots of improvements and new functionality for Xtreme Route, with the focus on improved fleet routing. Some of the changes are:

• ISOChrones and closest center areas can now have a Weight which affects the relative size of the areas
• Fixed a bug which made ISOChrones with many coordinates to have lots of 0,0 coordinates at the end
• Various fixes and improvements for fleet routing with time window
• New option QuickResult to fleet routing with the Router.RouteFleetArgs and RouteFleet method. Use it for very large problems to get a result faster
• A bug fix in OSMImporter for illegal attribute values
• New properties in NodePath, NodePaths and FleetPaths: DriveTime, WaitTime and AverageSpeed
• New property OptionalStartTime for use with time windows. It tells the latest time a vehicle can start and still drive within time windows
• Change of property Time and TimeSpan: that value always includes the full route time, including wait times for time windows
• Fixed a bug in RouteDescription that gave wrong coordinates, also removed duplicate coordinates for connected intersections
• New RouteSetting property ForceLinkBased, use when linkbased routing is needed but cant be detected by engine, like when using turn restriction check in cost delegate
• Renamed UseReferenceRouting to ForceOneDirectionRouting, since it can be needed outside testing scenarios
• Added SoftTimeWindows to RouteFleetArgs, which will allow router to be returned even if one or more nodes are outside time windows
• Added property RouteFleetArgs to FleetPaths which is a reference to the arguments used when calculating the fleet route
• Added property DistanceTable to FleetPaths which is the internally calculated distance table
• Some refacturing in FleetRoute, which only affects customers that don't use the Router.RouteFleet helper method (use this!!!)
• Changed so RouteStartTime and RouteEndTime are always set, even if time windows are not used
• Fleet route can now have dynamic departure times, which optimizes fleet routes where driver can start later than the specified departure time
• Fleet routes now has support for pickups and deliveries (RouteNode.Pickup and RouteNode.Delivery)
• Support for driver breaks, set with RouteSettings.DriverBreaks. When fleet routing with time windows, driver breaks are optimized to reuse wait times
• Improved support for time windows in NodePath and NodePaths (wait time properties, etc)
• Added driver breaks and total time/distance to route descriptions
• Added presets for driver breaks for EU, USA, Canada and some more countries
• Added support for driver breaks in NodePath (DriverBreaks property)
• Improved support for explicit vehicles in fleet routes
• Constraint callback available from fleet routing, letting the application determine exactly what service stations can be passed by which vehicle
• Increased performance for very large fleet routes
• Reduced memory consumption for ISO calculations and 1-to-many calculations
• Lots of updates and new sections in the Getting Started guide
• Improvements to explicit vehicles (speed modification, maximum route time)
• Fixed a bug in isochrone calcultion, which created wrong outerrings

Beside these changes, a lot of bug fixes and smaller performance improvements has been made. See the Getting Started guide (installed when installing Xtreme Route) for explanations and samples.