Travel time H3 using Protocol Buffers
Copy link

Overview
Copy link

The Travel Time H3 (Fast) endpoint is available with even higher performance through a version using Protocol Buffers (Protobuf). This version of the API is built to create large catchment areas with extremely low response times.

The endpoint takes as inputs a single origin location, a mode of transport, a maximum travel time, a resolution, and requested properties.

The endpoint returns a series of H3 cell IDs with accompanying requested properties. The returned cells cover the area up to the maximum travel time.

Performance
Copy link

Protocol Buffers are used to reduce latency in comparison to the JSON version of the Travel Time H3 (Fast) endpoint. Performance is also optimised by having minimal configurable parameters - if you require the ability to configure things like specific arrival/departure times then you should use the Travel Time H3 JSON endpoint.

The maximum travel time depends on the resolution you request. Some resolution and travel time limitations apply.

Use cases
Copy link

The Protobuf endpoint is most appropriate for use cases that involve large response messages and where performance is a high priority. For example:

  • Big data applications
  • B2C applications that require a travel time search functionality with minimised impact on page loading times

Access
Copy link

The Protobuf endpoint is accessible using the same API credentials as other TravelTime API endpoints, and is available on all licence plans.

Integration
Copy link

There are 2 ways in which the H3 Protobuf endpoint can be accessed:

  • SDKs
  • Direct integration

SDKs
Copy link

These SDKs support the H3 Protobuf endpoint:

If you have a particular requirement for one of our other SDKs to support the H3 Protobuf endpoint, please get in touch at support@traveltime.com

Direct integration
Copy link

While we would recommend using the SDKs above, the H3 Protobuf endpoint can also be accessed in other languages through building your own direct integration.

When building your own integration it is important to note that we do not use gRPC, we use Protobuf for serialization only.

Supported countries
Copy link

Protobuf is not supported in every country that we cover, but is currently available in 38 of the largest countries that we support, including most of Europe and North America.

A full list of supported countries can be found at the bottom of this page.