Map Matching API
A service that snaps GPS coordinates to the road network, providing accurate route reconstruction from noisy GPS data.
Overview
The Map Matching API takes a series of GPS coordinates and matches them to the most likely path on the road network. This is particularly useful for cleaning up GPS traces that may have inaccuracies due to signal interference or device limitations.
Key Features
- GPS Trace Correction: Automatically corrects GPS drift and inaccuracies
- Road Network Snapping: Matches coordinates to actual road segments
- Route Reconstruction: Rebuilds the most probable path taken
- Configurable Radius: Adjust the search radius for matching
Use Cases
GPS Trace Correction
Clean up GPS tracking data from mobile devices to remove drift and inaccuracies.
Route Reconstruction
Reconstruct delivery or service routes from GPS logs for accurate analysis.
Movement Analysis
Analyze vehicle movement patterns on road networks for optimization insights.
Location Analytics
Improve accuracy of location-based analytics by snapping coordinates to actual roads.
Usage
Request Parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
path | array | Array of coordinate objects in format [{lat,lng},{lat,lng}] | yes |
apiKey | string | Your API key for accessing Gebeta Maps | yes |
radius | number | Search radius in meters for matching coordinates to roads (default: 1) | yes |
Response Codes
| Status Code | Message | Description |
|---|---|---|
200 | OK | The request was successful. The system matched the path and returned the corrected route. |
404 | NoRoute | No matching route found for the provided coordinates. |
401 | Not Authorized - No Token | Authentication failed. No valid token was provided. |
401 | Not Authorized - Invalid Token | The authentication token provided is either invalid or expired. |
422 | InvalidInput | The request parameters are incorrect. Review the input values and adjust as needed. |