With the TravelTime Geohash API you can:
- Calculate travel times to every geohash cell reachable within a time limit
- Return the minimum, maximum and mean travel time for each cell
- Choose a resolution from 4 (regional) to 9 (street level)
- Combine catchments with unions and intersections in a single request
- Run unlimited requests on a fixed annual price, with no per-call charge
What the Geohash API returns
The TravelTime Geohash API returns every geohash cell reachable from, or to, a location within a set travel time and transport mode. Each cell comes with its geohash ID and the minimum, maximum and mean travel time across that cell. Large water bodies are removed by default.
Try TravelTime Geohash API
API lite demo
Geohash API at a glance
Quick overview of TravelTime Geohash API specifications.
| Transport modes | Driving, public transport, bus, coach, train, cycling, walking, ferry and multi-modal combinations |
|---|---|
| Resolutions | 4–9 (Geohash); 4–7 (Geohash Fast) |
| Returned properties | Min, max and mean travel time per cell |
| Maximum travel time | Up to 10 hours (resolution 4), decreasing at higher resolutions |
| Searches per request | Up to 10 departure and 10 arrival searches |
| Combine catchments | Up to 10 unions and 10 intersections per request |
| Time settings | Specific departure or arrival time, plus departure windows for public transport (Geohash); weekday morning (Geohash Fast) |
| Coverage | Global |
Why use geohash cells for travel times?
Join to any geohash-indexed data
Travel time statistics per cell
Choose your level of detail
Join travel times to your data
Enrich POIs and listings
Score and rank locations
Aggregate at scale
Reproducible geohash results
Re-run analysis
Plan for any time
No live traffic anomalies
Which Geohash endpoint should I use?
Use Geohash Fast for speed and volume. Use the standard Geohash endpoint for higher resolutions, longer travel times and specific departure times.
| Geohash | Geohash Fast | |
|---|---|---|
| Resolutions | 4–9 | 4–7 |
| Maximum travel time | 10 hours | 3 hours (1 hour at resolution 7) |
| Time settings | Any departure or arrival time | Weekday morning |
| Departure windows | Yes (public transport) | No |
| Configurability | Extensive parameters | Transport mode |
| Performance | Standard | Higher |
| Coverage | Wider | More limited |
Geohash, H3 or isochrone?
All three describe where's reachable. The right choice depends on how you'll use the result.
| Geohash API | H3 API | Isochrone API | |
|---|---|---|---|
| Output | Rectangular geohash cells | Hexagonal H3 cells | Polygon shape |
| Travel time per cell | Min, max, mean | Min, max, mean | No (inside or outside) |
| Best for | Systems already indexed by geohash | Even spatial analysis and aggregation | Drawing reachable areas on a map |
| Joins to data by | Geohash string | H3 index | Spatial query |
| Read more | Learn more | Learn more |
Pricing
How we price the TravelTime APIs
Get unlimited geohash calculations for a fixed annual subscription based on your capacity, support and caching needs. Not a bill for every API call.
Chat to our teamGeohash API FAQs
A geohash is a short alphanumeric string that represents a rectangular area on the Earth's surface. Each extra character makes the cell smaller, so a 4-character geohash covers a region and a 9-character geohash covers a few metres. Geohashes are widely used to index and group location data.
Geohash divides the world into a grid and encodes each cell as a base-32 string by alternately splitting longitude and latitude in half. It's a kind of spatial indexing that lets databases store, search and group locations using simple text, without complex geometry. Each extra character splits a cell into 32 smaller ones, which makes geohash hierarchical, from regions down to a few metres.
Geohash uses rectangular cells identified by text strings, while H3 uses hexagonal cells identified by 64-bit indexes. Geohash suits systems already indexed by geohash, such as many databases and search engines. H3's hexagons have more uniform neighbours, which suits spatial analysis. TravelTime returns travel times for both.
Yes. The TravelTime Geohash API calculates travel times to every geohash cell within a catchment area, by driving, public transport, cycling or walking. Each cell is returned with its geohash ID and min, max and mean travel time.
A geohash cell covers an area, not a single point, so travel times vary across it. The min, max and mean show the fastest, slowest and average journey times within each cell, which is more useful for analysis than a single reachable or unreachable result.
Yes. Public transport travel times in the TravelTime Geohash API are built from published timetables, including walking, waiting and interchanges. The standard endpoint also supports departure windows to capture service frequency.
Yes. The TravelTime Geohash API supports up to 10 unions and 10 intersections per request. Unions return cells reachable from any of your locations, and intersections return cells reachable from all of them.
Yes. There's no requirement to use TravelTime's map libraries or SDKs, and you can show geohash cells on any map with TravelTime attribution.
The TravelTime Geohash API is priced as a fixed annual subscription with unlimited requests, rather than per call. Cost is known before you build and doesn't grow with usage.