The Map Matcher pipeline template can be used to perform two types of map matching on probe data:
It supports map-matching on the following two input data formats:
The Map Matcher publishes results to an Index layer in parquet format. The output Index layer has indices of timewindow of 1 hour and HERETile zoom level of 12. If Path Matcher is used, additional routing information such as messageId, route, hourKey, idx_time and idx_tileId publishes to a different layer in parquet format with the same indices.
resultsBoundingBox.southLatitude=-90 resultsBoundingBox.northLatitude=90 resultsBoundingBox.westLongitude=-180 resultsBoundingBox.eastLongitude=180
In order to deploy and run this pipeline template, you will need the Wizard Deployer. The Wizard executes interactively, asking questions about the application, and expects the user to provide needed answers. Assuming you followed the Wizard's documentation instructions and set up the needed parameters beforehand, follow these steps:
You can use your existing output layer or let the Wizard script create a new catalog/layer for you. If using existing catalog, make sure it is shared with GROUP_ID which will be used for this deployment.
If you do not use the Wizard to create the output catalog then refer to the file config/output-catalog.json to find the structure of the output layers needed in the output catalog to publish results of the pipeline.
The output catalog of the pipeline consists of 2 layers:
- layer_1: - stores map-matched information as parquet format - index layer - timewindow (1 hour), HERE Tiles (zoom level 12) - layer_2 - stores routing information as parquet format - index layer - timewindow (1 hour), HERE Tiles (zoom level 12)
For input data type SDII Data stored in a Versioned or Index layer, the output Layer 1 contains the map matched information with the following columns:
For input data type Generic/CSV stored as parquet format in an Index layer, the output Layer 1 contains the map matched information with the following new columns added to the existing input data:
When path matching is performed on any supported input data format, the output Layer 2 contains the routing information with the following columns:
The route column will contain an empty sequence, when a route is not found for a message while map matching.
The values in the columns mmLat, mmLon, fraction, distInMeters, vertexTileId, vertexIndex, hmcTileId, segmentId are set to -999 and segmentDir is set to NA, when the map matcher does not return any results for a probe while map matching.
In Platform Portal select the Pipelines tab where you should be able to see your Pipeline deployed and running. After your Pipeline finishes and your data is published, you can find your output catalog under the Data tab and inspect your data visually or query/retrieve your data programmatically using one of the following options:
Executing this pipeline template will incur the following costs:
Cost will depend on the amount of data that will be published to a Versioned layer as an output from execution.
Will depend on:
Will depend on the amount and size of partitions (metadata) stored in the Versioned layer.
Depends on the number of workers you specify in the Wizard questions
To minimize this cost log level is set to WARN.
If you need support with this pipeline template, please contact us.