OpenStreetMap/Overpass: differenze tra le versioni
| (3 versioni intermedie di uno stesso utente non sono mostrate) | |||
| Riga 9: | Riga 9: | ||
* [https://www.openstreetmap.org/user/SomeoneElse/diary/409111 Setting up an Overpass API server - how hard can it be?] | * [https://www.openstreetmap.org/user/SomeoneElse/diary/409111 Setting up an Overpass API server - how hard can it be?] | ||
* [https://github.com/drolbr/Overpass-API Repo originale drolbr/Overpass-API] | * [https://github.com/drolbr/Overpass-API Repo originale drolbr/Overpass-API] | ||
* [https://github.com/b1tw153/Overpass-API Fork aggiornato b1tw153/Overpass-API] con | * [https://github.com/b1tw153/Overpass-API Fork aggiornato b1tw153/Overpass-API] con istruzioni molto chiare e estensive | ||
* [https://github.com/wiktorn/Overpass-API | ** [https://hub.docker.com/r/b1tw153/overpass-api Immagine Docker b1tw153/overpass-api] | ||
* [https://hub.docker.com/r/wiktorn/overpass-api Immagine Docker wiktorn/overpass-api] | |||
** [https://github.com/wiktorn/Overpass-API Repo wiktorn/Overpass-API] | |||
** [https://community.openstreetmap.org/t/overpass-api-performance-issues/140598/35 Indicazioni sull'utilizzo] | |||
=== Requisiti === | |||
Informazioni dai [https://github.com/b1tw153/Overpass-API/blob/main/README.md#resource-sizing requisiti ufficiali]: | |||
==== Storage ==== | |||
For a full planet import, expect roughly 4-5× expansion from the compressed `.osm.bz` file to the database. Check the current planet file size on [https://planet.openstreetmap.org/planet/ planet.openstreetmap.org] before provisioning storage. | |||
Approximate full planet database sizes by metadata mode as of Q2 2026: | |||
{|class="wikitable"| | |||
! Mode | |||
! Database Size | |||
|- | |||
| attic (full history) | |||
| ~750 GiB | |||
|- | |||
| meta (latest metadata) | |||
| ~365 GiB | |||
|- | |||
| no (base data only) | |||
| ~270 GiB | |||
|- | |||
| --areas=yes (area data) | |||
| ~30 GiB (additional) | |||
|} | |||
For extracts, the database will be proportionally smaller, but the expansion ratio from source to database is similar. Check the size of your chosen extract file and apply a 4-5× multiplier as a planning estimate. Note that most extract sources do not include full history, so `attic` mode is generally not available for extracts; `meta` mode is typical. | |||
==== CPU ==== | |||
The container runs one fcgiwrap worker per CPU core plus one by default (`FCGIWRAP_WORKERS` defaults to `cpu.max`/`nproc` + 1). Each worker handles one concurrent query. Provision CPU cores based on your expected concurrent query load. A single core is sufficient for light personal use; a public-facing instance benefits from more cores to handle concurrent requests without queuing or rate limiting. An optional request queue can be configured in nginx. | |||
==== RAM ==== | |||
* A minimal development instance with a small extract can run with 1-2 GiB | |||
* A lightly loaded personal instance can run with 4-8 GiB | |||
* A moderately loaded instance with complex queries benefits from 16-32 GiB | |||
* A heavily loaded public instance may need 64 GiB or more | |||
Set the container memory limit explicitly — for example, with `docker run --memory=16g`. Without a memory limit, the container can consume all available host memory under heavy query load. | |||
=== Istanza italiana === | === Istanza italiana === | ||
Spazio su Cloud VPS ottenuto in {{phab|T426790}}. Istanza in fase di setup. | Spazio su Cloud VPS ottenuto in {{phab|T426790}} nel progetto <code>osmit</code> ([[Server#Altri_server_in_Wikimedia_Cloud]]). Istanza in fase di setup. | ||
Versione attuale delle 07:19, 10 set 2026
Servizio di query su OpenStreetMap, usato abbondantemente dalla comunità italiana.
Link utili
Overpass API
- osm:Overpass API
- Setting up an Overpass API server - how hard can it be?
- Repo originale drolbr/Overpass-API
- Fork aggiornato b1tw153/Overpass-API con istruzioni molto chiare e estensive
- Immagine Docker wiktorn/overpass-api
Requisiti
Informazioni dai requisiti ufficiali:
Storage
For a full planet import, expect roughly 4-5× expansion from the compressed `.osm.bz` file to the database. Check the current planet file size on planet.openstreetmap.org before provisioning storage.
Approximate full planet database sizes by metadata mode as of Q2 2026:
| Mode | Database Size |
|---|---|
| attic (full history) | ~750 GiB |
| meta (latest metadata) | ~365 GiB |
| no (base data only) | ~270 GiB |
| --areas=yes (area data) | ~30 GiB (additional) |
For extracts, the database will be proportionally smaller, but the expansion ratio from source to database is similar. Check the size of your chosen extract file and apply a 4-5× multiplier as a planning estimate. Note that most extract sources do not include full history, so `attic` mode is generally not available for extracts; `meta` mode is typical.
CPU
The container runs one fcgiwrap worker per CPU core plus one by default (`FCGIWRAP_WORKERS` defaults to `cpu.max`/`nproc` + 1). Each worker handles one concurrent query. Provision CPU cores based on your expected concurrent query load. A single core is sufficient for light personal use; a public-facing instance benefits from more cores to handle concurrent requests without queuing or rate limiting. An optional request queue can be configured in nginx.
RAM
- A minimal development instance with a small extract can run with 1-2 GiB
- A lightly loaded personal instance can run with 4-8 GiB
- A moderately loaded instance with complex queries benefits from 16-32 GiB
- A heavily loaded public instance may need 64 GiB or more
Set the container memory limit explicitly — for example, with `docker run --memory=16g`. Without a memory limit, the container can consume all available host memory under heavy query load.
Istanza italiana
Spazio su Cloud VPS ottenuto in T426790 nel progetto osmit (Server#Altri_server_in_Wikimedia_Cloud). Istanza in fase di setup.