From style to image, without a browser in your product¶
WMS-VT is for workflows that need a finished map image rather than an interactive map. It renders a MapLibre-compatible style for an exact bounding box, width, height, and DPI on the server.
1
Choose the map¶
Supply a MapLibre style URL and a projected bounding box. The style continues to control sources, layers, labels, glyphs, and sprites.
2
Describe the output¶
Set the pixel dimensions and DPI for the document, export, or downstream image workflow that will consume the result.
3
Receive an image¶
WMS-VT renders the requested area on the server and returns a PNG image. No WebGL-capable client is required.
Built for output workflows¶
Print and PDF¶
Generate map artwork at explicit dimensions and DPI for reports, layouts, and print production.
Thin clients¶
Give clients a finished image when embedding a full interactive renderer is impractical or unnecessary.
Consistent styling¶
Use the same MapLibre style language for an interactive map and its server-rendered exports.
A request looks like this¶
curl --get 'https://api.wmsvt.com/api/v1.0.2/queued-wms' \
--data-urlencode "key=$WMSVT_API_KEY" \
--data-urlencode 'bbox=238138.090518,6238073.596726,264358.090923,6264293.626065' \
--data-urlencode 'width=1600' \
--data-urlencode 'height=1600' \
--data-urlencode 'dpi=300' \
--data-urlencode 'styleurl=https://maps.example.com/style.json' \
--output map.png
Understand every parameter See the sample output
Access and upstream data
The public endpoint requires an issued WMS-VT API key. Style and tile-provider credentials remain the customer's responsibility, as do the attribution and licensing requirements of the underlying map data.
Bring us the awkward map export¶
Tell us the desired output size, request volume, coordinate system, style provider, and where the image will be used. We will help determine whether WMS-VT fits the workflow.