Configuration#
Settings are read from environment variables with the OWRT_ prefix or from an ignored
.env file in the working directory (.env.example lists them). The same settings apply to
the service, the CLI, the Python loader and dataset generation.
Setting |
Default |
Purpose |
|---|---|---|
|
|
Bind address of the service |
|
|
Port of the service |
|
|
Search provider |
|
|
Lifetime of in-memory provider responses |
|
|
Building limit for simulations and scene compilation |
|
|
Building limit for browsing |
|
|
Sources eligible for automatic routing |
|
unset |
Local Boston catalog for offline or historical releases |
|
|
Overture surface features per theme |
|
|
Provider HTTP timeout |
|
|
Overture connect timeout |
|
|
Overture request timeout |
|
project string |
Sent to public providers |
|
public Overpass |
Overpass endpoint; deploy a private instance for sustained use |
|
public Nominatim |
Search endpoint |
|
|
Output root for datasets |
|
|
Cache root for loader scenes, relative to the checkout |
|
|
Cached Overture STAC index per release |
Script-level variables that are not settings: OWRT_RELOAD=1 enables auto-reload in
scripts/run.sh; OWRT_BIND_ADDRESS changes the host interface in Compose;
OWRT_EXAMPLE_* configure examples/generate_dataset.py; OWRT_LOCAL_BUILDINGS is read
by the example building-source plugin.
Public Overture and OSM access is remote and best effort. Nominatim allows one request per second and results must be cached; the OSM tile service is for interactive use only; Overpass is best effort. Production deployments should configure suitable provider capacity and keep attribution visible.