Introduction to Altitude API
Explore how Altitude by Geotab exposes its underlying data layer through its API, providing the same data that drives the UI so you can combine it with your own data sources.
Altitude by Geotab is designed to help users intuitively understand their roadways. The Altitude platform data layer is serviced in its entirety by the Altitude API, so the same data that drives the Altitude user interface (UI) is available in its basic form through direct requests to the API. This allows our Customers to glean actionable information by combining these insights with other disparate data sources to work towards alleviating inefficient and congested roadways.
The Altitude API suite complements the Altitude platform in its function. The end-user version of Altitude provides a point-and-click experience to deliver insights and support visualizations. You may need to extend your analysis beyond the insights and visualizations presented in the UI for specific use cases, processing needs, or to merge or overlay data with other existing data sets. The Altitude API allows you to get compatible data to support these use cases.
This guide outlines the API requests related to the various applications of the Altitude platform. It describes the business rules for accessing the API and its associated data.
Our Data
Altitude is built on 100% observed commercial vehicle movement, comprised of aggregated Geotab assets’ commercial data. Some modules, such as AADT, apply statistical modelling to that observed base.
The aggregated data is generated based on defined criteria and filtered to respect all relevant privacy legislation and internal standards.
Data Quality
- Expansion Factors
- Alternative third-party data sources
- OSM (OpenStreetMap) updates: recent map edits may not yet be reflected in zone or road segment boundaries used in your analysis.
- Data recency: results reflect the most recent data refresh, so very recent roadway or traffic changes may not yet appear.
- Overlapping zones and trip behavior: overlapping zone definitions can cause the same trip activity to be counted in more than one zone.
- Data that has not passed our privacy restrictions: records excluded for privacy reasons are not included in results, which can affect totals for low-volume areas.
