Where a rendered map is the useful product¶
Interactive maps are excellent for exploration. They are less convenient when the deliverable is a PDF, a scheduled report, an email attachment, a thumbnail, or an input to another image-processing step.
Print and PDF production¶
Create a map at the pixel dimensions and DPI required by a document layout. The style remains expressed in the MapLibre style specification, while the output is a conventional image that reporting and publishing systems already understand.
Typical flow:
- A document service determines the map frame's geographic extent and physical size.
- It converts those requirements into BBOX, width, height, and DPI parameters.
- WMS-VT returns a rendered image for placement into the document.
Scheduled and generated reports¶
Render the same operational area at regular intervals while changing the style or its source data upstream. The report generator receives a file instead of needing to coordinate a browser, animation state, and screenshot timing itself.
Thin clients¶
Some clients can display an image but should not load an interactive map engine and all of its data sources. WMS-VT moves rendering to the service boundary and gives the client one predictable image response.
Preview and export services¶
Create map previews, attachment images, or download exports from the same family of styles used in an interactive application. This helps keep colours, labels, and cartographic hierarchy consistent between the application and its exports.
Image-analysis inputs¶
When a downstream system expects pixels, WMS-VT can produce a deterministic geographic frame with explicit dimensions. Suitability depends on the analysis: rendered cartography is not a replacement for source geospatial data when exact feature geometry or measurements are required.
Not every map task should become an image
Use vector tiles or source geospatial data when the consumer needs feature interaction, querying, editing, or precise geometry. Use WMS-VT when the required result is the styled visual representation.
Have a different output workflow?¶
Describe the consumer, map size, coordinate system, volume, and latency target. Those details matter more than a generic feature checklist.