-
A new data type has been added: Movement path data. This data type enables the representation and analysis of trips following road networks. It allows for detailed street analysis, traffic flow analysis, origin-destination analysis much like the already existing Movement data.
Movement path data consists of (map-matched) trips defined by a series of road segments. While movement data consists of trips defined by a series of GPS coordinates. The former is often a more natural data representation for analysing road traffic.
To work with movement path data, you first need a geometry data set consisting of road segments, ideally with a property that defines the Road class for multi-scale road network handling. Next you need data files (in CSV or Parquet) that represent the sequence of road segments traveled by all trips. Each entry in the data files represents a part of a trip, referencing the trip by its ID and referencing the road segment by its ID. Next, you can also add metadata for the trips (as CSV or Parquet) files, where each entry in those files references a trip by its ID. The data files typically contain time-varying properties such as speed. The metadata files typically contain constant properties such as vehicle type.
Figure 1. Example movement path data set from INRIX consisting of trips along a road network.
A prominent example of movement path data in the traffic/mobility industry is INRIX Trip Paths data.
-
Time series, Geometry, and Movement path data now use a multi-scale approach when handling road segment data. If your data set has a property with special meaning Priority Level with values (starting with) a number from 1 to 9 where 1 corresponds to the most important road type (e.g., highways), an automatic multi-scale representation will be generated. The approach favors larger roads (i.e., priority level 1) when zoomed out and smaller roads (e.g., priority level 6 or more) when zoomed in. This enables you to use country-wide road networks in your analysis.
Figure 2. Multi-scale handling of road network data. Left; Only showing the motorways when zoomed out. Right: also showing the smaller roads when zooming in.
-
Time series, Geometry, and Movement path data now enable the analysis of two-way roads. If your data set has a property with special meaning Reverse ID, the platform automatically understands that the road is a two-way road. For instance, if the identifier of a road segment is 2014921_0, then the reverse identifier might be -2014921_0. When configuring the reverse identifier, the platform understands that the road segment needs to be handled (and visualized) as a two-way road.
Your temporal data (for time series sets) and movement data (for movement data sets) can then represent data for both sides of the road by using either of the two IDs (2014921_0 or -2014921_0 in the example above).
Figure 3. Handling of two-way roads, with indication of driving direction.
-
Road networks defined in Time series, Geometry, and Movement path data sets now display an arrow pointing in the driving direction when the road is visualized sufficiently widely. This benefits analysis of traffic on bi-directional roads. You can change the width of the visualized road segments using the Size scale slider.
-
Time series and geometry data sets now use the 'Style by' value as label instead of the shape’s name. This enables faster insight generation and more informative visualization. For instance, when displaying speed on a road segment, the label will now show the (average/min/max/…) speed in the label. Additional information is now also shown when hovering with the mouse.
-
Time series and geometry data sets now do not expose the shapes as areas of interest shapes by default. You now have to explicitly configure this. When disabled, you cannot select the shapes as areas on the different analytics pages, for instance to display multiple trends on the Trend Analytics page. If enabled, you can use the shapes in the data set as before as areas of interest shapes.
-
Labels for Time series, Geometry, and Movement path data sets are now deconflicted (decluttered) for a better visual representation.
-
Some of the default styling options have changed. Styling by a numeric property now selects the Rainbow colormap by default. Accumulation styling is now also disabled by default. The latter can be enabled to apply a density effect based on the number of records or assets, in addition to the colormap used for styling.