Nextmv marketplace beta release

• The Nextmv Routing app based on nextroute is now available in beta as part of the marketplace on Nextmv console.
• Acceptance testing is now available in beta as part of experiments.

Nextmv SDK v0.25.0

• Bug fixes and performance improvements for the nextroute vehicle routing engine.

Nextmv CLI v0.25.0

• Enable ability to subscribe to marketplace (beta) applications, starting with the Nextmv Routing app.
• Enable ability to create an application with a subscription.

Upgrade to v0.25.0

Open up a terminal and run the following command:

nextmv update

Alternatively, you can specify the version.

nextmv update v0.25.0

Nextmv SDK v0.25.0 upgrade guide

To update and tidy your Go project and reference SDK v0.25.0, stand at the location of the go.mod and run:

go get github.com/nextmv-io/sdk@v0.25.0
go mod tidy

Migration guide to nextroute and Nextmv Routing app

For users who have previously run one of the Nextmv SDK routing templates, or the Nextmv Routing app (v0 schema), below are guidelines on how to migrate to the nextroute routing engine. We recommend upgrading to benefit from improved performance and flexibility.

nextroute is the recommended vehicle routing engine now available as part of the Nextmv platform. For existing users, this guide provides instructions on how to migrate from other templates and apps to the nextroute template and Nextmv Routing app (v1 schema).

Migrate from v0 to v1 Nextmv Routing app schema or the cloud-routing template to nextroute

After creating a nextroute template, the next step will be to migrate your existing schema to that of nextroute. Below is a list of schema changes. For any questions on migrating custom models please contact support.

Schema changes in Nextmv Routing app (from v0 to nextroute v1 schema)

Below is a complete list of features between the v0 and nextroute v1 schema routing apps. Take note of indicated changes to naming and/or API.

input

Vehicle

Stop

initialStop

location (Nextroute) / position (v0 schema)

defaults

vehicleDefaults

stopDefaults

options

solverOptions

diagram

expansion

limits

Migrate from SDK routing templates to nextroute

import (
	"github.com/nextmv-io/sdk/route"
)

All router templates (except for cloud-routing) use set-based inputs. With set-based inputs, all the elements of a set are represented under a single key. An example of this can be seen with vehicle shifts start times.

"shifts": [
  {
    "start": "2020-10-17T09:00:00-06:00",
    "end": "2020-10-17T17:00:00-06:00"
  },
  {
    "start": "2020-10-17T09:00:00-06:00",
    "end": "2020-10-17T17:00:00-06:00"
  }
],

The nextroute template, however, is based on entity-based inputs. The elements of a feature are contained in the entities. Instead of having start_times with a vector of start times, the start_time is represented in each vehicle.

"vehicles": [
  {
    "id": "v2",
    "start_location": {
      "lon": 135.772695,
      "lat": 34.967146
    },
    "start_time": "2023-01-01T12:00:00Z"
  },
  {
    "id": "v3",
    "end_location": {
      "lon": 135.762057,
      "lat": 35.025431
    },
    "start_time": "2023-01-01T12:00:00Z",
    "end_time": "2023-01-01T12:20:00Z"
  },
]

To migrate a model based off a router template, you will need to create a nextroute template.

Then, because nextroute is entity-based, to migrate from an existing routing template, the code has to be completely removed and replaced with nextroute code. It's not enough to create a schema change as referenced in the cloud-routing migration steps, though the naming conventions previously described would still apply. For any questions on migrating your model please contact support.