You are viewing Nextmv legacy docs. ⚡️ Go to latest docs ⚡️



You will learn the basics of measures for Nextmv Cloud.


Measures determine the cost of connecting two things together. This may mean assigning one item to another, clustering two points together, or routing a vehicle from one location to another. These cost computations are generically referred to as "measures". Measures are used as part of the value function to make decisions in Nextmv Cloud.


Haversine is the default measure used by Nextmv Cloud to calculate the distance between two locations.

The haversine formula provides the shortest distance between two points on the surface of a sphere and is often referred to as 'as-the-crow-flies' distance. Haversine distance is fast to compute and sufficient for finding the best routes in the run time allotted.

When using the haversine measure, vehicle speed is required to calculate duration (duration = distance / speed). If vehicle speed is not specified (as default or for individual vehicles), then an error will be returned.

No changes to the input file are required to utilize the haversine measure for distance and duration in Nextmv Cloud. If no measure is specified, haversine will be set as default.


Streets is an integration for extending Nextmv measures using real-road networks when calculating the distance between two points. See the Streets integration guide for more information.


HERE is an integration for extending Nextmv measures using HERE's matrix routing service to make routing decisions informed by accurate street routes and real-time or projected traffic conditions. See the HERE integration guide for more information.

Page last updated

Go to on-page nav menu