Data sources

WMS

The workhorse of every spatial data infrastructure: a raster map service, queried on click and explained by a legend the server draws for us.

Try it: click anywhere on the zoning plan to query the service, drag the opacity slider in the layer panel, and switch on the tree register — it only draws from zoom 15, so the panel tells you why nothing appears yet.

What this demo shows

WMS layers requested as tiles in EPSG:3857 (a requirement of MapLibre — see decision D-02)
info turns a layer into a queryable one: clicks become GetFeatureInfo requests
legend: "auto" pulls a GetLegendGraphic image into the legend panel
minZoom keeps a heavy layer off small scales, and the layer panel explains the gap
metadata.url links the layer to its catalogue record — the SDI connection

map0 builds the GetMap URL for you, including the axis-order-safe CRS parameter for WMS 1.3.0, and keeps any vendor parameters your base URL already carries (a MapServer map= path, for example).

Browser-direct, no proxy Capabilities, tiles and GetFeatureInfo are fetched straight from the service, so it has to send CORS headers. The City of Vienna services used here do.

Configuration

This is the actual file the map above is running on:

Embedding

          <script type="module" src="/map0.js"></script>
          <map0-viewer config-src="/configs/wms.map0.json" style="height:520px"></map0-viewer>