EDK / ROUTES

Route on your terms.

Directions, travel times, and distance matrices from an open API that works at global scale.

const result = await e2.routes.directions({ origin, destination })
// structured result + geography

OUTCOME

Treat a route as part of your geographic workflow, not the end of it.

HOW IT FITS

01

Resolve origins, destinations, or candidate features

02

Calculate route, matrix, or reachable area

03

Use the output for corridor search, maps, and decisions

BUILT FOR THE NEXT ACTION

A product primitive should keep working after the first response.

●

Routes and matrices

Move from a single journey to many-to-many travel-time comparisons when the problem needs it.

●

Reachability in the product

Bring isochrones and travel-time constraints into location search and site-selection flows.

●

Geometry you can use

Keep the route and its metrics available to map, inspect, or analyze in the next operation.

EVALUATING OPTIONS?

See how EDK approaches routes workflows.

Explore the alternative