# Map view

> The network on a map - filter-scoped vector tiles, condition coloring, Esri overlays, and click-through to any feature.

Source: https://app.assetlab.ca/docs/infrastructure/map

For linear assets the map isn't a visualization nicety - it's the primary interface. "Which segment is this?" is a map question, and so is "where are we weakest?".

## What renders

In the **Features** tier the map renders once at least one filter narrows it: network, feature class, zone, material, condition band, risk level, or feature type. Until then a placeholder asks you to pick a filter - an unfiltered map would stream every tile in the tenant, so the filters are what scope the vector tiles. There are no per-layer checkboxes; set the filter bar to "just watermains" or "one zone" and the tiles follow. The only on-map layer control is the Esri overlay switchboard (below).

A zone filter clips the tiles to that zone's boundary - the boundary itself doesn't draw.

The other two [tiers](/docs/infrastructure/zones-routes-corridors) scope themselves, so they answer the same question differently:

| Tier | What draws | What scopes it |
|---|---|---|
| Features | Segments and nodes, coloured by condition | At least one filter |
| Routes | The same segments, with the selected route's members highlighted | At least one filter |
| Corridors | Every active corridor as a line, coloured by urgency band | Nothing - the layer is one line per street |

Clicking works the same in all three, but selects the thing the tier is about. In Routes, clicking a segment selects the **route** it belongs to - the whole route lights up and the map fits to it. A segment that belongs to no route opens as a feature instead. Where a segment sits on two routes (a shared intersection, a multi-named street) the click resolves to the same one every time.

### Coloring

Features paint by **condition** - the triage view; red segments cluster where programs should go. Two other paint modes exist on other surfaces: the [replacement planner](/docs/projects/replacement-planner)'s map mode paints by forecast replacement year, and the corridors view paints [corridor](/docs/infrastructure/zones-routes-corridors) urgency bands. The legend follows whichever mode the surface uses; there is no symbology switcher on the Infrastructure page itself.

The forecast-year ramp bands a feature by how far its replacement year is from today, and reserves red for work you are already carrying:

| Band | Replacement year | Colour |
|---|---|---|
| Past due | before this year | red |
| Urgent | this year through 2 years out | orange |
| Soon | 3-5 years | amber |
| Mid-term | 6-10 years | lime |
| Long-term | more than 10 years | green |
| Unknown | no install date or service life | grey |

A feature's replacement year is its in-service date plus its service life, and that service life is [inherited](/docs/infrastructure/networks-and-classes) from the material or feature class when the feature carries none of its own.

## Esri overlays

When you have [Esri sources](/docs/infrastructure/esri-sync) configured, the on-map switchboard toggles each active source on as a read-only overlay - the live GIS layer drawn over your AssetLab features, with warnings when you're zoomed too far out or the overlay was truncated. Click an overlay feature to open a bind dialog that links it to an AssetLab feature - useful for reconciling what GIS has against what you manage.

## The basemap

The built-in basemap comes in three variants - **Dark**, **Streets** and **3D buildings** - all drawn from OpenStreetMap data as vector maps, so they stay sharp at any zoom and label text renders crisply rather than being baked into the image. The layers button at the top right of the map switches between the built-in variants and any basemaps your organization has added, and your choice is remembered per user on that device.

**3D buildings** is the Dark cartography with building massing extruded to its real height, and picking it tilts the camera so the massing reads. Buildings only appear from zoom 14 in - at a city-wide view there are no footprints to extrude, so the map stays flat until you zoom into a block. Heights come from OpenStreetMap, so coverage follows what has been surveyed in your area: a downtown core is usually well mapped, an industrial edge often is not. Switching back to Dark or Streets levels the camera again. Use it to read a corridor in context - which segments run beside a built frontage and which cross open ground - rather than as a survey of the buildings themselves.

When you are viewing one of your organization's own basemaps, a tone slider appears at the bottom left of the map - slide it down to mute the imagery so condition colors carry the story. That setting is remembered per user as well.

Administrators can add custom raster basemap sources (XYZ, WMS, or WMTS) under **Settings → Infrastructure → GIS & basemaps** (the old **Infrastructure → Basemap** address redirects there). A source marked as the organization default is what new users see first. For ArcGIS servers, paste the MapServer link directly - AssetLab converts it to the tile endpoint. Tiled ArcGIS caches must be published in Web Mercator to display; if your GIS server offers a **_WM** variant of a service, that is the one to use - a cache in a local projection (such as UTM) serves tiles the map cannot place. Secured ArcGIS services are supported with the **ArcGIS token** access option: enter the GIS sign-in username and password once and AssetLab generates and refreshes the short-lived tokens itself; credentials are stored encrypted and are never sent to the browser.

## Working from the map

Hover syncs between map and table, and a view switcher toggles table, split, and full-map layouts - whichever you last used is remembered per user on that device, so leaving on the map means coming back to the map. Clicking a feature selects its row in split view; in full-map view (or when the row isn't on the current page) it opens the feature detail sheet instead. In the Routes tier a click resolves to the route the segment belongs to and opens that route's panel in every layout, split included. All three layouts work in every tier, so a route or a corridor can be read side by side with its table row.

Panning away from what you selected is easy, so a **focus** button sits beside the layers button at the top right. It returns the camera to whatever the map is currently about: the selected feature, route or corridor in that tier, or - with nothing selected - your organization's whole extent. It's the same fit the map performs when you select the row, so focusing never lands somewhere new.

The detail sheet carries the feature's quick stats, attributes, financials and custom fields, and three actions: **Close**, **Create Work Order**, and **Open full page**. Create Work Order opens the [work order](/docs/cmms/work-orders) form with the feature already attached - Staff and above see it. Common flows:

- **Dispatch** - resident reports a break at an address; find the segment on the map, open it, raise the [work order](/docs/cmms/work-orders) right from the sheet
- **Windshield triage** - reviewing an area before budget season, clicking through the segments in question
- **Data QA** - after any [sync](/docs/infrastructure/esri-sync) or import: missing geometry, zero-length segments, and misclassified features are visually obvious

> [!tip] Screenshot condition-colored map extracts straight into board reports. A red-and-green map of the ward communicates a deficit better than any table.

## Scale

Tiles stream per filter, so the map stays responsive on networks of tens of thousands of segments - as long as you keep the filter meaningful. If a view feels heavy, narrow to the network or class in question.