An Overpass-API compatible engine on SQL Databases.
Underpass-API aim to be a Overpass-API compatible engine built upon overpass_parser_rust to parse Overpass Query an converto to SQL.
Alternatively WASM version, without requering backend is also available in underpass-wasm.
Follow the instruction of one of the backends:
- Postgres+PostGIS / Osmosis, Osmosis schema
- DuckDB+Spatial / QuackOSM, Quackosm schema
It is possible to setup Underpass-API without Docker. Looks at specific backend directory, and use Dockerfile content as installation guide.
Start the server with
BACKEND="DuckdbQuackosm" DB="data/database.parquet" cargo runBACKEND="PostgresOsmosis" DB="postgresql://user:pw@host:5432/database" cargo run
The API as available at http://localhost:9292/interpreter
Test with the Gironde, France extract (94MB). Test with generic index, running localy, 8 CPU, 8 GB RAM.
Test Query 1
[out:json][timeout:25];
(
nwr[highway=bus_stop][name];
nwr[public_transport=platform];
);
out center meta;
time curl 'http://localhost:9292/interpreter' -X POST -H 'Content-Type: application/x-www-form-urlencoded; charset=UTF-8' --data-raw 'data=%5Bout%3Ajson%5D%5Btimeout%3A25%5D%3B%0A(%0A++nwr%5Bhighway%3Dbus_stop%5D%5Bname%5D%3B%0A++nwr%5Bpublic_transport%3Dplatform%5D%3B%0A)%3B%0Aout+center+meta%3B'
| Backend | Setup | Query 1 |
|---|---|---|
| Postgres+PostGIS / Osmosis | 10m11s | 5,7s |
| DuckDB+Spatial / QuackOSM (1) | 2m00s | 2,4s |
| DuckDB+Spatial / QuackOSM / WASM (1, 2) | 2m00s | 8,0s |
| Overpass API (3) | 8m49s | 3,1s |
| Overpass API overpass-api.de (4) | - | 5,9s |
(1) Without metadata. (2) With local Parquet file (3) Required converion from PBF to XML included (). (4) Query with polygon to limit the spatial extent.