Mapping
Mapping gives live users a shared picture of the site. It can show base maps, show maps, imported planning layers, overlays, and Event Control log markers.
Read the map
The map opens on the event's configured view. Use the layer panel to switch layers on or off. Some layers are base layers; others are design or operational overlays.
Use layers to answer practical questions:
- Where is this incident?
- Which gate, zone, or route is nearby?
- Which planned overlay should the team use for this phase of the show?
- Does a log already exist at the same place?
Work with log locations
When logs have locations, they appear as markers. Selecting a marker opens or routes you towards the matching Event Control log. This is useful when an operator starts from the map rather than the stack.
You can also pick a map location and carry it into Event Control where the workflow allows it. This helps keep map references and log records tied together.
Find a What3Words reference
Where the environment is configured with What3Words, use the search box to resolve a three-word address. If What3Words is not configured, Nexus shows a safe message instead of pretending the lookup worked.
What3Words is helpful for field reports, but it should not replace clear operational wording. Include the gate, zone, route, or landmark when you know it.
Why configure maps properly
A well-prepared map lets the control room move faster. Operators can locate an issue, choose the right route, and attach a log to a place without opening another system.
The best setup is boring on purpose: one clear base map, only the overlays the live team needs, and imported planning maps that have been checked before show day.