Define routes, zones and points of interest
Indoor mapping for conference venues and exhibition halls means producing a structured data model of the building that a navigation system can use to calculate routes and position a visitor on screen. It is not simply a decorative floor plan. The map must contain geometries for rooms and corridors, coordinates for points of interest, level information for multi-storey venues, and attributes that distinguish walkable areas from walls, columns and fixed obstacles.
Conference venues and exhibition halls present distinct mapping challenges compared to retail units or museums. The footprints are large, often exceeding several thousand square metres on a single level. Ceiling heights vary considerably between main halls and ancillary spaces, which affects how positioning signals propagate. Layouts change between events: an exhibition hall configured for a trade show one week may be divided into parallel conference tracks the next. Any mapping approach must account for this reconfigurability rather than treating the floor plan as a permanent fixture.
The map data sits between two layers. Below it is the positioning infrastructure — beacons, Wi-Fi access points or other signal sources that estimate where a device is. Above it is the application that renders routes, shows the visitor's dot and displays contextual information. If the map geometry is inaccurate or incomplete, even a well-calibrated positioning system will place visitors in the wrong location or route them through walls. The map is the reference frame everything else depends on.
Most venue mapping projects start from existing architectural drawings or CAD files. These are useful but rarely sufficient on their own. Architectural plans show structural elements but often omit temporary fixtures, furniture layouts, stand positions and the operational details visitors actually need — registration desks, catering points, accessible routes and emergency exits. Converting a CAD file into a navigation-ready map typically involves simplification, coordinate transformation, attribute assignment and validation against the physical space.
Routing, positioning and interface choices
Defining the navigable network
Before drawing anything, decide what the map needs to support. A visitor trying to find a specific exhibition stand has different requirements from one looking for the nearest accessible toilet or an emergency exit. Each use case implies different points of interest and different routing priorities. List the categories your system must handle: stands, session rooms, registration, catering, first aid, toilets, lifts, stairs and exits. Then decide which of these need to appear on the visitor-facing map and which are primarily for routing logic.
The navigable network is the set of paths a visitor can realistically walk. In an exhibition hall, this is not the entire floor area. Stands, staging, AV rigs and cabling runs all reduce the walkable space. Mapping the network means defining corridors and aisles as polylines or polygons with appropriate width, not simply outlining the hall boundary. If your map assumes visitors can walk through a stand to reach an aisle, the routing engine will produce impossible directions.
Multi-level venues and transitions
Many conference centres span two or more levels, with plenary halls on one floor and breakout rooms or exhibition space on another. Each level needs its own map layer with a shared coordinate system so that vertical transitions — stairs, lifts and escalators — connect correctly. The vertical transition points must be modelled explicitly. A lift, for instance, is not a single point; it has doors on each level that need to align with the corridor network on that floor. Misalignment here causes routes that jump between floors without a logical connection.
Handling temporary and reconfigurable layouts
Exhibition halls are rarely static. Stands move, session rooms are re-partitioned and entrance points shift between events. There are two broad approaches to handling this. The first is to maintain a base map of the permanent structure and overlay event-specific layers for each configuration. The second is to treat each event layout as a separate map version. The overlay approach reduces duplication but requires the navigation system to merge layers correctly at runtime. Separate versions are simpler to test but create a version-control burden.
Whichever approach you choose, establish a clear handover process with the event organiser or venue operations team. They need to supply finalised layout plans far enough in advance for the map to be built, validated and deployed. Last-minute stand changes are common in the events industry, so build in a cut-off point beyond which alterations will not appear on the digital map and communicate that deadline clearly.
Accessibility routing
Accessible routes are not an optional extra to add later. They require specific attributes on the navigable network: ramps rather than steps, lifts with sufficient dimensions, door widths and surface types. If the map data does not distinguish a staircase from a ramp, the routing engine cannot offer an accessible path. Tag each vertical transition and each potential obstacle with accessibility attributes from the start. This also supports compliance with the Equality Act 2010, though specific legal guidance should be sought independently.
Coordinate systems and scale
Indoor maps typically use a local Cartesian coordinate system in metres, with an origin point tied to a real-world reference such as a surveyed corner of the building. The scale must be consistent across all levels. A common error is importing floor plans that were drawn at slightly different scales, causing misalignment between levels that only becomes apparent when a visitor's position appears to jump sideways when moving between floors. Verify scale by measuring a few known distances in the physical space and comparing them to the map.
Evidence, accessibility and review triggers
Treating the map as finished after initial creation
The most frequent mistake is assuming the map is complete once the first version is built. In a conference or exhibition environment, the map is a living asset that needs updating for each event configuration, each structural change and each seasonal reorganisation. Without a maintenance process, the map gradually diverges from reality. Assign ownership of the map data to a specific role or team and schedule review points around the event calendar.
Confusing visual fidelity with positional accuracy
A map can look highly detailed — showing every column, stand and piece of furniture — yet be misaligned with the positioning system by a metre or more. Visual detail and positional accuracy are separate qualities. A visitor following a blue dot that is consistently offset from their actual position will trust the system less than one following a simpler map where the dot tracks correctly. Prioritise geometric accuracy over decorative detail, and validate the map against the positioning layer before going live.
Ignoring ceiling-height and structural variations
Large exhibition halls often have different ceiling heights in different zones — lower under gantries and rigging, higher in open areas. These structures affect Bluetooth and Wi-Fi signal propagation, which in turn affects positioning accuracy. If the map does not reflect where these obstructions are, it becomes harder to diagnose accuracy problems later. At minimum, annotate the map with the locations of major overhead structures so that positioning performance can be correlated with the physical environment.
Over-detailing areas visitors do not need
It is tempting to model every room, cupboard and service corridor. Unnecessary detail inflates the map file size, complicates the routing graph and can confuse the navigation engine if service corridors are accidentally marked as walkable. Model what visitors need to navigate and nothing more. Back-of-house areas should generally be excluded unless staff navigation is a specific requirement, in which case they belong on a separate layer.
Key checks before going live
- Scale verification: Measure at least three known distances in the venue and compare them to the map. Discrepancies of more than a few centimetres per metre indicate a scale or transformation error.
- Level alignment: Stand at a lift or stairwell that spans multiple floors and check that the corresponding points on each map layer align when overlaid.
- Walkable-area validation: Physically walk the main visitor routes and confirm that the map's navigable network matches what is actually accessible. Check for missing barriers, one-way corridors and areas blocked by event infrastructure.
- Point-of-interest placement: Visit a sample of tagged points of interest — registration, toilets, session rooms — and confirm their positions on the map correspond to their real locations.
- Routing sanity test: Request routes between several origin-destination pairs that you know the correct path for, including at least one accessible route and one cross-level route. If the system suggests walking through a wall or taking an implausible detour, the navigable network has a gap or incorrect connection.
- Positioning overlay: With the positioning system active, walk a known path and observe where the blue dot tracks relative to the map. Consistent offset in one direction suggests a coordinate transformation error; erratic movement suggests a signal or calibration issue that may be compounded by the map geometry.
Mapping a conference venue or exhibition hall is a preparatory discipline that underpins every other part of the indoor navigation system. Getting the geometry, attributes and update process right does not guarantee a flawless visitor experience on its own, but getting them wrong makes every downstream component harder to debug and less reliable in operation.
