Loading Space Optimization API : How to visualize the bin packing results in 3D

The PTV Developer Loading Space Optimization API allows to optimize the way to arrange goods into one or several bins, in order to spare some loading meters, or to facilitate the unloading of items at stops. 

Our new tutorial illustrates how simple it is, by mean of the three.js library, to display the results of the bin packing operations so as to easily visualize in 3D the suggested packing for each bin, as well as detailed or global KPIs like the number of used bins or the number of packed items.

Please also have a look at our technical concept pages if you want to know more information about bins and items , orientation and stackability, or sequencing constraints. Moreover, our multiple code samples can also help you on advanced features : defining allowed orientation per item, setting stacking restrictions between different types of items and much more. 

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.

Changing vehicle parameters at waypoints

When calculating a route with more than 2 waypoints, it often happens that logistic events occur at intermediate stops, which can modify some routing-relevant characteristics of the selected vehicle.

The most common use-case is obviously unloading or loading some goods at a stop, which implies a change of the weight of the vehicle. The nature of the transported goods can also be important, for instance when it relates to hazardous materials : some roads should then be either preferred or avoided. Last but not least, adding or removing a trailer will definitely modify the dimensions of the vehicle itself.

Such vehicle adaptions can sometimes have a sensitive impact on the path of the optimal route, or even on toll costs. And more commonly, they also directly affect the quantity of emitted pollutants and the energy consumption for a given route.

While it is of course possible to split a route request in several requests with different input vehicle configurations, it is much more performant and user-friendly to be able to consider these changes in a single request.     

This is why the version V1.14.0 of the PTV Developer Routing API now offers you to (re-)define some of the vehicle parameters directly in your on-road or off-road waypoints, with the POST method : calculateRoutePost.

Our new code sample provides you a fast-and-easy way to evaluate the influence of the change of load weight at waypoints. As shown on the screenshot below, it is preconfigured to test a route where unloading the goods at the second waypoint influences the course of the route. 

Please have a look on our technical concept to get more information about waypoints handling.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.

Fastest, shortest … and now cheapest routes

Usually the ‘FAST’ routing mode tends to reduce the driver cost of your calculated transport routes due to shorter driving times, while ‘SHORT’ routing mode rather optimizes fuel consumption costs due to a shorter travel distance.

Multiple factors should indeed be considered in order to spare money : toll costs, energy costs, vehicle cost per kilometer, or even working-time cost per hour. Therefore, a new ‘MONETARY’ routing mode has been added in version V1.13.0 of the PTV Developer Routing API, to directly evaluate these factors within the objective function, in order to calculate the cheapest route according to our monetary cost model. Since V1.14.0 it is also possible to define costs per kWh for electric or hybrid vehicles.

In addition, you can now request detailed monetary cost reports even for routes calculated using the ‘FAST’ or the ‘SHORT’ mode, and then easily compare the resulting price for each mode in the desired currency.

The above example illustrates the result difference between the ‘FAST’ (in orange) and the ‘MONETARY’ (in blue) routing modes for a given start and destination.  

Please refer to our technical concept to get more information about when and how to use Monetary Costs routing, as well as the current limitations of this new mode. You can also try our new code sample to test it.  

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.

Release of Loading Space Optimization API V1.0.0

A new version of the PTV Developer Loading Space Optimization API is now available!

You can check the new features in the list below or use the API Changes webpage for more details.

Loading Space Optimization API V1.0.0

  • Feature: Three-dimensional packing of multiple cuboid items in multiple cuboid bins.

You can test PTV Developer for free by registering a MyPTV account and activating the product on the website.
By doing this you will gain 100k transaction per month for free to directly start testing.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.

Release of Matrix Routing API V1.1.0

A new version of the PTV Developer Matrix Routing API is now available!

You can check the new features in the list below or use the API Changes webpage for more details.

Matrix Routing API V1.1.0

  • Feature:  The toll costs can be calculated in a specified currency by using the result type ‘TOLL_COSTS’ and the request parameter ‘currency’.

Matrix Routing API V1.0.0

  • Feature: Calculation of the distances and travel times between a set of origins and destinations.

You can test PTV Developer for free by registering a MyPTV account and activating the product on the website.
By doing this you will gain 100k transaction per month for free to directly start testing.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.