Routing you integrate, not routing you run

Distances, routes and geocoding over a web API. Triona runs the environment, maintains the configuration, and keeps the underlying network data current. Part of Triona's Infra Data Management Solution.

Why

One integration, no engine to run

Plenty of systems need a distance or a route, and very few of them want to be in the routing business. Running an engine means hosting it, configuring it, and keeping the road network data current, and none of that work shows up in your own product. Distance Service is the routing part without the machinery around it. Your system asks and gets an answer, and the work of keeping that answer correct stays on our side.

  • Nothing to host - Triona runs the environment
  • Current data - maintained as part of the service
  • Routing, optimization and geocoding in one place - one integration to build and one to maintain

Features

Routes, optimization and geocoding

  • Route calculation

    From A to B, with via points along the way, and up to three route alternatives per request so you can compare them.

  • Routing on vehicle parameters

    A route a car can drive is not always a route a loaded truck can drive. Give the vehicle its height, weight, length, axle load and bogie weight, and the road network is adjusted before the route is calculated.

  • Barriers and areas to avoid

    Areas you do not want to drive through go in with the request, and the route is calculated around them.

  • Multi-stop optimization

    Optimization of multi-stop requests with multiple vehicles, answering both the order of visits and the split of orders between vehicles. Opening hours and capacities are taken into account.

  • Geocoding

    An address turned into a position, and a position turned back into an address, without a second service to integrate.

  • What comes back

    Distance and drive time, route geometry and driving instructions, restrictions found along the route, toll statistics and route properties, and CO2 output.

Who is it for?

Built for systems where routing is one input among many

  • TRANSPORT

    Transport and logistics systems

    Where a distance or a drive time is an input to planning, pricing or follow-up, and has to be the one the vehicle will actually drive

  • PLANNING

    Systems that plan multi-stop work

    Deliveries, collections and service rounds, where the order of the visits is the difference between a good day and an expensive one

  • ADDRESSES

    Applications that work with addresses

    Turning what somebody typed into a position, or a position back into something a person can read

  • PARTNERS

    Software vendors and solution providers

    Building routing into their own product, and would rather integrate an interface than take on the engine and its data

Contact

Discover how Distance Service fits your system

Contact us for more information, or to discuss how Distance Service would fit into the system you are building.

Related links

You may also be interested in