Files
CartoLite-Server/docs/data-sources.md
T

16 lines
984 B
Markdown

# Data sources
## Operator MQTT broker
All topology and activity originate from the operator-configured MeshCore MQTT feed. The server sends no traffic to a shared CartoLite service. MQTT credentials stay inside the server container environment and are never returned by an endpoint.
## CARTO vector basemap
The browser uses a minimal CARTO vector style for land, water, boundaries, roads, and place labels. Each operator supplies a CARTO Basemaps API key during the image build. The client makes normal TileJSON, vector PBF, and glyph requests directly to CARTO. There is no raster basemap fallback.
## Optional terrain
Topography and 3D use Mapterhorn's public TileJSON endpoint at `https://tiles.mapterhorn.com/tilejson.json`. MapLibre reads its Terrarium elevation tiles only after a visitor enables Topography or 3D. No MQTT data or visitor identifier is added to those requests.
No country, regional-boundary, geocoding, weather, analytics, or history source is bundled.