A lightweight Node.js server for generating isochrone maps using OSRM routing data.
Galton is a lightweight Node.js server that generates isochrone maps—visualizations of areas reachable within specified travel times from a starting point. It uses OSRM for routing calculations and provides an HTTP API to compute these polygons for applications like urban planning, logistics, and accessibility analysis.
Developers and organizations building mapping, logistics, or urban planning tools that require travel time analysis, such as ride-sharing apps, delivery services, or city planners.
Galton offers a simple, self-hosted alternative to commercial isochrone services, with full control over data and parameters, and integrates seamlessly with OpenStreetMap and OSRM for accurate, customizable travel time visualizations.
Lightweight Node.js isochrone map server
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Galton is designed as a minimal Node.js server with low overhead, focusing on performance for isochrone generation without unnecessary bloat, as highlighted in its philosophy.
It supports multiple input methods including OSRM files, OSM extracts, and geocoding via Overpass API, offering versatility in sourcing routing data without being locked into one format.
Users can tune parameters like intervals, buffer radius, cell size, and units via command-line options or API calls, allowing precise control over isochrone polygon generation.
With built-in Docker support and examples, Galton simplifies containerization and integration into existing workflows, making deployment straightforward across environments.
Setting up requires downloading and processing OSM data with OSRM tools—extracting and contracting—which is time-consuming and assumes familiarity with geospatial command-line workflows.
Relies on pre-computed OSRM graphs, so isochrones do not account for real-time factors like traffic or road closures, limiting accuracy for dynamic applications.
The tool assumes knowledge of OSRM, geospatial concepts, and Unix commands, making it less accessible for developers without mapping or backend server experience.
Docker examples tie to specific OSRM versions (e.g., v5.18.0), which could lead to compatibility issues or require manual updates when underlying dependencies change.