Mapping configuration
Mapping configuration prepares the map that live users see during the show.
General mapping
General mapping sets the event's base map, opening zoom, event boundary, and scrollable area.
Use the boundary to describe the event footprint. Use the scrollable area to stop operators drifting too far from the site.
Set a generous scrollable area around the event, but keep the opening view tight. Operators should land where the show is, then pan out only when they need context.
Base maps
OpenStreetMap is available as a general base. OS Maps can be selected when the environment has the required OS Data Hub key.
If OS Maps is selected without a configured key, Nexus shows an unavailable warning and keeps the save action safe. Configure the OS key before relying on OS Maps for a live show.
Show maps and layers
Show maps are operational map sets for the event. Each show map can have layers:
- base layers;
- design layers;
- overlays;
- imported planning map layers.
Use layers to separate what operators may need at different moments. Too many default-visible layers can make the map slower to read.
Imports and georeferencing
Upload planning PDFs in Imports. Nexus prepares each page, then keeps manual referencing, alignment feedback, overlay review, and reusable calibrations together in one workspace.
The import steps are:
- Upload PDF adds the source PDF and prepares page previews.
- Select pages lets you include useful pages and ignore covers, legends, or other non-map pages.
- Reference and review is the main workspace. Click the same recognisable place on the PDF and reference map, then save the pair. Saved points remain numbered and visible on both maps.
- Prepare and publish explicitly renders the final tiles and turns the checked page into a show-map layer.
In Side by Side mode, choose well-spread locations that are easy to identify on both maps, such as building corners, path junctions, gates, or survey marks. Nexus checks alignment immediately after the fourth enabled pair is saved. Four pairs are the minimum because the extra observation can expose a mistake; add a fifth pair whenever possible to make that check more useful. You do not need to start or wait for a separate alignment job.
Every saved pair has the same number and symbol on the PDF, the reference map, and the point list. Use the list to focus or edit a pair, or temporarily exclude it from the alignment. Do not rely on colour alone when comparing points.
Switch to Overlay Preview without leaving the workspace to compare the solved PDF against roads, gates, paths, and building outlines. Accuracy and spread messages update after any point is saved, edited, included, or excluded. Rendering does not start automatically: move to Prepare and publish and choose Render Final Layer only after the alignment looks correct.
Reusing a viewport calibration
A viewport calibration saves the complete set of point pairs for a particular PDF map frame and crop. It is useful when several PDFs use the identical viewport but differ in visible content—for example a gridded copy, a copy with extra annotations, or an export where the base map is omitted.
Save a named viewport calibration after the source page is production ready. On another page, Nexus compares PDF page size, crop box, rotation, and aspect ratio and labels the calibration Compatible, Needs confirmation, or Not compatible. Content similarity and PDF fingerprints are not used as a gate. Before reuse, you must confirm that the visible map frame and crop are identical. Nexus then scales the saved PDF positions to the target preview, copies every matched pair, and checks the alignment again.
To replace a saved calibration after refining its points, choose Replace with current points, review its name and sharing scope, then choose Update viewport calibration. Nexus prevents accidental duplicate names within the same scope.
Do not reuse a calibration when the map frame has shifted, the crop differs, or only part of the original viewport is shown. Match fresh points instead.
Once a page is production eligible and tiles are generated, it can become a map layer.
Do not publish an imported planning map on show day without checking it against known points. A badly georeferenced plan is worse than no plan because it looks authoritative.
What to rehearse
Before the event starts:
- open the live map;
- check the base map loads;
- switch each important layer on and off;
- open each imported planning map in Reference and review, compare at least four well-spread point pairs, and add a fifth where possible;
- click a known log marker if logs already exist;
- search a What3Words reference if the event relies on it.