Changelog

​

Introducing the /cube endpoint

We all know about distance matrices (our /table endpoint), but Route Optimization systems require multiple slices throughout the day. Ideally one for every 5 minutes in the day in order to get the travel time as granular and accurately as possible. However, if you would want to solve a 1000-jobs VRP request, you would need 288 matrices of 1000x1000 elements. That would be quite cumbersome to first calculate and then secondly hold in memory during the solve.

That is why we are introducing a /cube endpoint to fetch the entire 3-D matrix or what we call cube. 288 slices is too much but what if we can approximate it with a function? A polynomial that reduces the necessary slices. Read more in the /cube introduction

​

Predictive traffic integration

Thanks to our partnership with TomTom, we can now provide predictive traffic information to our routing engine.

​

Publicly launching Solvice Maps

Solvice Maps is now publicly available since December 2024. We believe that it is one of the most powerful and fastest routing engines available. We’re launching on OpenStreetMap data initially and will soon expand to other map data providers such as TomTom.

Next to the routing engine, we also provide a tile server that can integrate with any map application and framework such as Leaflet, Mapbox GL JS, OpenLayers, etc.