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.