TravelTime Snowflake Native App
Bring accurate, multimodal travel times to Snowflake — with Enterprise-level performance, scale and security. No ETL, no data export, no separate infrastructure.
Partner
- /time-map/fast
- /h3/fast
- /time-filter/fast
- /geocoding/search
- /geocoding/reverse
TravelTime location intelligence native to Snowflake
The TravelTime Snowflake Native App brings the TravelTime API directly into Snowflake, so customers can run accurate travel time and catchment area calculations natively against data in their own account, without ever leaving Snowflake.
TravelTime's Snowflake App puts the functionality of the TravelTime API - isochrones, travel time matrices, H3 catchments, and geocoding - inside of Snowflake.
Customers can calculate accurate, multimodal travel times at massive scale, with no ETL or bulk data export, under a fixed-cost, unlimited-usage licence.
//Why teams use it
Harness the power of TravelTime in Snowflake
TravelTime combines accuracy, performance, and a commercial model that is built for scaling applications.
Native to Snowflake
Requests are simple to run with no separate infrastructure, no ETL pipeline and no bulk data export, with results landing straight back in Snowflake.
Privacy by design
TravelTime stores no data from API requests other than metrics for performance monitoring. Requests are processed in memory and then wiped, with nothing written to disk.
Global data coverage
TravelTime calculations available across 200+ countries and territories for every transport mode, including multimodal public transit.
Accurate transit models
Real-world routing (driving, public transport, walking, cycling) that stands alongside the accuracy of leading A to B routing providers.
High performance at huge scale
Use Snowflake compute to enable users to calculate tens of millions of travel times per minute, even on a small warehouse.
Fixed cost, unlimited usage
Build freely with no per-call cost or volume caps, and no overage charges. Unlock high volume use cases that are not viable under usage-based pricing.
//Resources
Using TravelTime in Snowflake
Snowflake Marketplace is a centralised hub within Snowflake's Data Cloud that offers an array of data-driven applications and services. Native apps on the Snowflake Marketplace leverage Snowflake's cloud-based data platform, allowing seamless integration and enhanced functionality.
Here’s how you can use the TravelTime app in Snowflake.
//Data flow
TravelTime app architecture
Data analyst
or application
Consumer data
Coordinates, addresses
Virtual warehouse
Consumer compute
≈ one worker per vCore (8 on X-Small, doubling per size up)
Snowflake partitions the input data and distributes it across workers.
Each worker runs TravelTime Native App's UDTFs and processes the data row-by-row.
TravelTime Native App
TIME_FILTER_FAST
TIME_MAP_FAST
H3_FAST
GEOCODING_SEARCH
GEOCODING_REVERSE
TravelTime API key
Provided at install.
External access integration
Allows access to api.traveltimeapp.com.
Enabled at install.
TravelTime API
Data flow
- ❯1Query — Calls a UDTF function via a SQL LATERAL join.
- ❯2Feed flows — Consumer tables supply the input rows.
- ❯3Execute — Warehouse runs the UDTFs.
- ❯4Call TravelTime API — One request per row through the EAI.
- ❯5Respond — JSON parsed into success / error rows.
- ❯6Return — Results stream back to the caller.
Better together
Built for the Enterprise
Together, TravelTime and Snowflake support the largest Enterprise applications with the highest performance requirements.
Even on a small warehouse, users can run tens of millions of travel time calculations per minute — no complex setup, configuration, or hosting.
For Snowflake’s AI Data Cloud, real-world travel times become a core part of the models customers build in Snowflake, powering matching, propensity, demand-forecasting, site-selection, and more through Snowpark ML and Cortex.
And because TravelTime is fixed-cost with unlimited usage, customers can build at scale — without compromise.
TravelTime & Snowflake FAQs
TravelTime is a Snowflake Native App. It is external distribution, running entirely in the consumer’s account.
A set of Python table functions — GEOCODING_SEARCH, GEOCODING_REVERSE, H3_FAST, TIME_MAP_FAST and TIME_FILTER_FAST — plus an external access integration scoped to api.traveltimeapp.com and a TravelTime API key provisioned at install. You call the functions from SQL like any other UDTF.
An API. Each call is calculated live by TravelTime’s API and streamed back as rows, so there’s no static dataset to refresh and no risk of working from stale road or timetable data.
No. The functions are implemented in Python but called as SQL table functions, so anyone comfortable writing a SELECT can use them.
Only the parameters needed to run the calculation — coordinates, transport mode, travel time — are sent to the TravelTime API. Results stream straight back into your account, and nothing is written to disk. The app README contains examples of all the functions that can be copy and pasted.
Nothing is written to disk on the TravelTime side. Requests are processed in memory and then wiped.
Driving, public transport, walking and cycling across 200+ countries and territories, with public transport modelled from published timetables and driving from our proprietary congestion model — not just estimated from road speeds.
Rows are processed in parallel by your warehouse, so even a small warehouse can run tens of millions of travel time calculations per minute. Scaling up your warehouse increases throughput without any change to your SQL.
Performance, scale and security
with TravelTime & Snowflake
Let’s discuss your Search and Match, Spatial Analysis, and Routing needs.