Documentation¶
WMS-VT accepts a geographic extent and render settings, resolves a MapLibre-compatible style and its assets, and returns a finished map image.
Start here¶
- Quickstart: make a complete request with safe credential placeholders.
- API request: understand the route, request lifecycle, and response.
- Parameters: see required values, formats, and source-level limits.
- Styles and assets: prepare styles, tiles, glyphs, and sprites for server-side use.
- Projections and BBOX: form the extent expected by the public renderer.
- Output formats: distinguish the production PNG path from experimental Rust output.
- Limits and errors: handle validation, rendering, and upstream failures.
- Attribution and licensing: understand responsibilities for the style and source data.
Two implementations exist in this repository¶
| Implementation | Role in this documentation |
|---|---|
TypeScript/Express renderer in maplibre/ |
Basis for the currently reachable public API route and examples. |
Rust/Axum renderer in wms-vt-rust/ |
Newer experimental implementation with EPSG and SVG-related work; not presented as the production contract. |
The distinction matters. Parameters supported in one implementation do not automatically apply to the other.
Service status
The public health endpoint responds at https://api.wmsvt.com/api/v1/health. A healthy process does not itself guarantee that a particular style, provider, extent, or output size will render successfully.