All JSON-based application runs now have an automatic tabular view into the data. For a run result, the solution is extracted and presented in a tabular view; for the input view the full input data is used for the tabular view.

How the data is presented (code and table) can be toggled with a new control at the bottom of the page as well, so you can easily switch between JSON and tabular views of the data. The code view displays the input or output for a run like it did before, there is no change there, so at any point you can view the exact input or output for the run.

This update has been applied to new and past runs. Also, the view control will remember your last selection for the app, so each app can have its own default view into the data for each individual user.

The routing run visualization in Console has been updated to use vector-based tiles, render more efficiently, and offer more display flexibility.

Vector tiles

The map on which routes and stops are displayed is now rendered with vector tiles rather than raster tiles. This reduces the amount of processing needed to display the map and offers a crisp, clear background for your routing visuals.

Efficient rendering

A number of improvements were made to the code that prepares and processes the data for the routing visuals. And, when possible, items on the map are now rendered with the canvas element rather than rendered as SVGs. In addition to these enhancements, a clustering engine (supercluster) was added to be able to handle efficiently rendering many points on a map.

The size limit for rendering runs in Console with the routing visual has now been increased to 4.5 MB (prior the limit was 350 kb).

Example rendering of 1000s of stops and multiple routes

Display flexibility

If you click on a feature (point or route) in the map a popup appears that displays extra information for that feature. Before, the routing visualization would extract a few specific metrics for display in the popup, but you had no control over which items were displayed.

This has been changed to where now the popup will display any information that is included in a feature’s metadata property. So now you’re in control of the information displayed in the feature popups.

More

The routing visual is available to any app that meets the minimum schema requirements. You can view this minimum schema and learn more about the routing visual in the routing run visualization section.

You can now add custom visuals to your application runs. Add custom charts using the Plotly or Chart.js rendering library, or add custom interactive maps based on GeoJSON data. Visuals can be added to any custom application by following the required schema outlined in the Custom visualizations documentation.

Sample of a Chart.js render for an application run.

The run ID is now included as an analysis option in the scenario test pivot table (id). This is useful if your want to categorize data by runs, or further segment scenario analysis with a per run delineation.

When viewing a run in Nextmv Console, there is a size limit for rendering the input and output for the run. If an input or output file is above this threshold, rather than rendering a visual or the contents of the JSON file, an interface for downloading the file is displayed.

However, sometimes an input’s large file size is because of “machine” data included in the file, and the amount of information that is of interest to an operator or developer is within Console’s file display threshold.

To accommodate this scenario, a new feature has been added to Nextmv Console that trims machine-oriented properties from the input file when viewing a run. After the properties have been trimmed, if the run’s updated input file size is within the display thresholds then the input will be re-rendered with the appropriate display (e.g. a mapping visual if it’s a routing app).

At the moment there are two properties that are trimmed from the input file:

• distance_matrix
• duration_matrix

If these input properties do not exist no action is taken. Also, if one or more of these properties are trimmed, but the input file size still remains above the rendering threshold, the download input interface will remain as is.

App’s that use the Statistics convention in their run output can record time series data with the series_data property and then view this collected data in the Analysis tab of the run details view in Console.

The ability to view the series data used to be only available if your run output file size was below 300kb. Now this feature is available for run outputs of any size as long as the format is JSON. However, do note that if your files are very large it may take a moment for the series data to be extracted and displayed.

Also, the charts that display the progression values of the series_data sets have been updated to be more performant. And if the dataset is larger than 50, a sample of the points are extracted for inspection using the Largest-Triangle-Three-Buckets (LTTB) algorithm.

A new feature has been added to the create scenario test interface that allows you to select individual inputs to use for a scenario. Prior to this you would need to create an input set from the inputs first, and then select that input set for your scenario.

Now you specify which inputs to use directly without having to create an input set first. You can select any combination of existing inputs to use for each scenario in your scenario test.