Views

A view is what you actually share. Projects hold the raw material (the layers, the styles, the tooltips), and a view turns that into a specific, published map you can hand to someone.

The same project can power several views. One might be a wide-open internal version with every layer visible, another a focused public embed with two layers and a single filter control. Each view stores its own choices about what to show, what viewers can interact with, and how the map is delivered.

What a view captures

A view belongs to a project and remembers a presentation of it. That includes:

• Which layers are visible
• How each filter behaves: visible as a control, applied silently, or off
• Whether to override a layer’s style for this particular view
• The basemap theme and which built-in map features (roads, labels, water, and so on) are shown
• The starting camera
• Embed sizing
• An optional 6-digit PIN

Every project starts with a system Default View so you can share something immediately. Custom views are where you make deliberate presentation choices.

Create and switch views

You manage views from the Views list in the project editor. Add a new one with Add View, then rename, duplicate, or delete it from the row’s actions menu.

The view you’re currently editing is the “active” view. The editor uses it for preview, so switching the active view changes what you see in the canvas while you work. This is how you build different versions of the same project without copying anything. Flip between views to make sure each one stands on its own.

The system Default View is treated specially. It always reflects the project’s full set of layers and can’t be renamed or deleted. If you need a narrower presentation, build a custom view.

Map style and basemap

Each view has its own basemap settings, separate from the project’s vector data.

You can pick a basemap theme (currently Dark Matter or OSM OpenMapTiles) and toggle the built-in map features on or off. That includes things like boundaries, buildings, landcover, places, POIs, transportation, water, and their associated labels.

Use this when the basemap is fighting your data. Strip out everything except boundaries and water for a clean choropleth, or keep places and roads visible for a more wayfinding-oriented map.

Visible layers and per-layer overrides

In the Layers tab of the view, every project layer appears in a list. For each one, you can:

• Hide it in this view, or include it.
• Show viewers a toggle so they can turn the layer on and off themselves. This is useful for embeds where you want a little interactivity without exposing the editor.
• Reassign the layer to a different existing project style for this view only.

Reassigning a style here doesn’t touch the style itself; you’re just picking which existing style this view applies. To edit the underlying style definitions, go to Styles.

Filter controls in a view

Filters are configured on the layer (see Filters), but the view decides what happens with them when someone opens the published map.

Underneath each layer in the view’s Layers tab, you’ll see the layer’s active filters indented as their own rows. For each one:

• The power toggle (Turn filter off / Turn filter on) decides whether the filter applies in this view at all.
• Add UI control decides whether viewers can see and adjust the filter themselves. Without it, the filter still applies; they just can’t change it.

This is where the same project can become several different audiences’ maps: hide a filter from the public view, expose it as a control in an internal one.

Starting camera

Each view stores where the map opens.

Leave Auto fit on and the view opens framed to the data’s extent. Turn it off and you can save the editor’s current center, zoom, bearing, and pitch as the starting position. This is useful when the auto-fit zooms out too far, or when you want to draw attention to a specific area.

Share or embed a view

Sharing and embedding both happen from the view, not the project. Each view has its own link at /view/{viewId}, and you can optionally protect it with a 6-digit PIN.

For embeds, the view also stores its sizing: landscape, square, or portrait, plus Fill width and Fill height toggles. If both fill toggles are on, the aspect ratio is ignored. Embeds also need the host page added to your workspace’s allowed hosts before they’ll load.

The dedicated guides have more detail: Sharing and Embedding.