Map Route Reference
Understand the site map’s filters, popup actions, and spatial handoffs into sites, scheduler, inspections, work orders, and defects.
Before you start
- You need location-first triage rather than a list-first desk.
Expected outcome
You can use the map as a launcher into operational records without confusing it for the owning data surface.
What this route is for
Map shows the site portfolio spatially so the office can triage geographically and jump into the right site, planner slice, inspection, work-order, or defect desk from one marker.
Visibility and capability notes
| Item | Details |
|---|---|
| Route id | map |
| Visibility | Customer-facing core route. |
| Capability notes | Map visibility is broad, but some popup actions still open capability-gated desks such as Work Orders. |
| Direct inbound | Shell nav, dashboard site coverage, and route-level spatial review. |
Main regions, popups, and controls
| Surface | What it does |
|---|---|
| Map canvas | Plots sites with location data. |
| Filter toolbar | Narrows the plotted estate by search, latest result, and inspection-state signals. |
| Marker popup | Launches the main site-scoped desks directly from one site. |
| Results slice | Keeps the current search or status slice coherent while you move around the map. |
Key actions
- Search for a site or location.
- Filter by latest inspection result or inspection presence.
- Open the site record.
- Open the scheduler scoped to the site.
- Create an inspection for the site.
- Create a work order for the site.
- Open the site-scoped defect backlog.
Filters and URL state
| Param | What it controls |
|---|---|
q | Search |
result | Latest result filter such as pass, pass_with_advisories, fail, or no_inspections |
inspection | with_inspections or without_inspections |
- The map does not use dialog-heavy workflow state.
- Route state is intentionally light so the map stays focused on launching other desks.
Outputs and side effects
- The map mostly causes navigation side effects.
- Popup actions can open create mode in Inspections or Work Orders.
- No site or inspection data is edited directly on the map.
Inbound links
- Shell
Mapnavigation. - Dashboard site coverage drill-ins.
Outbound links
#/scheduling?siteId=...#/sites?siteId=...#/inspections?siteId=...&create=1#/work-orders?siteId=...&create=1#/defects?siteId=...&status=open
Indirect handoffs
- Site address quality controls whether a site is even visible here.
- Latest-result filtering depends on inspection completion and report state elsewhere.
- The map is often the fastest bridge between the estate register and the operational queues.
Troubleshooting
| Symptom | What to check |
|---|---|
| A site is missing from the map | Confirm the site has usable coordinates. Sites without plotted location data do not render as markers. |
| The defect or work-order action opens an empty queue | Check whether the site id carried over and whether the downstream desk is capability-gated. |
| A result filter seems wrong | Re-check the latest inspection result on the underlying site or inspection record. |
Sites Route Reference
Understand the site register, site dialogs, import entry points, and the way site-level rules affect scheduler and field workflows.
Scheduling Route Reference
Understand the planner’s board, timeline, map, selection actions, quick-view tools, and dynamic handoffs into sites, inspections, work orders, and AI context.