Understand what the map shows
The Lexoh site map brings device locations and configured zone boundaries into one geographic view. Operators can use it to find equipment and relate it to entrances, exits and other areas of a site. The available layers, controls and device details depend on the installed version, site configuration and your permissions.
A stored location is a reference for finding equipment. It does not establish live GPS tracking, position accuracy or the current operating state of a barrier, reader or camera. Confirm the device record and current feedback before making an operational decision.
Use this guide for reading and checking the map. Use zone management to edit zone records and device management to inspect equipment or perform authorized actions.
Open the correct site and map view
- Sign in with the account assigned to your role and select the intended organization or site where that selection is available.
- Open Map in the application navigation. If it is unavailable, ask the administrator to check your access and the functions enabled for the site.
- Check the displayed site name, recognizable surroundings and selected filters. A default or automatically centered view does not prove that every expected device has loaded.
- Wait for loading to finish and note any error. Check the background map, devices and zones separately: one layer can be visible while another is missing.
- Compare an expected device with its device-management record. Confirm its site assignment and saved location before investigating a missing marker.
Read the layers separately
The geographic background gives orientation; device markers and zone shapes represent application records. Their data sources and refresh behavior may differ. A visible background cannot confirm that the equipment data is current.
The examples below show how to interpret an observation. They describe investigation steps, not recorded Lexoh incidents or a guarantee of a particular interface.
| What you see | What to verify |
|---|---|
| Roads are visible, but no device markers appear. | Check site scope, filters, permissions, saved coordinates and device-data loading. Do not infer that all equipment is offline. |
| Device markers appear over a blank background. | Check background-map loading and connectivity separately from the device records. |
| A marker appears at the expected entrance. | Match its reference and name to the installed device, then inspect current status and feedback. |
| A zone shape surrounds a reader. | Check the reader’s actual zone assignment and access rules. Visual containment alone does not establish either. |
| Several devices appear as one numbered group. | Expand the group or use the device list to identify its members. A group is not a single physical device. |
Identify the device behind a marker
Select a marker to inspect the information available in your version. Match the device reference, descriptive name, location and type with the installation record. An icon can help distinguish equipment categories, but similar icons or nearby positions are not enough to identify a device.
Separate the saved position from communication status, reported equipment state and physical operation. When a timestamp is available, check its time zone and age. A marker that remains visible may represent an old position or an outdated status.
Before using any available control, confirm the exact device and follow the site’s operating procedure. Opening a detail panel is different from sending a command. A command acknowledgement does not by itself confirm that a barrier moved or that a passage occurred.
Check coordinate meaning
Use the coordinate format and field order required by the actual form or import. Do not interchange latitude and longitude or copy values from an incompatible format. A valid geographic point can still be wrong for this installation; compare it with a known site location.
Handle missing and default positions
Check whether a value is absent, a placeholder or a surveyed position before changing it. Zero values are not inherently invalid geographic coordinates. A point at 0,0 is inappropriate for a Québec installation, but this does not establish how the application filters that point. Preserve the original record when correcting it.
Interpret zone boundaries and the legend
Use each zone’s name and saved boundary to identify the area it represents. Read the legend and record details rather than relying on color alone. If shapes overlap, select the intended zone or open its record to distinguish them.
A drawn boundary provides map context. It does not automatically assign readers, change access permissions, establish parking capacity or count vehicles. Check those settings and their associated devices in zone management.
If a zone is missing, check its site assignment, configured boundary, status, filters and your access. The conditions for display can vary by version. A short legend or a hidden layer is not proof that the zone was deleted.
Confirm boundaries against the installation plan and the site’s intended operating areas. Treat this map as an operational reference; do not use the apparent edge of a shape as a surveyed property boundary.
Find devices inside a marker group
Where marker grouping is enabled, nearby markers can combine at a wider view to keep the map readable. Zoom in or select the group using the controls available in your version, then identify individual records. Devices saved at the same coordinates can remain visually stacked.
A group’s number describes the records represented by that group under the current view and filters. It does not establish healthy-device count, lane capacity, redundancy or the site’s total inventory. Use the device list or statistics report for the appropriate count and definition.
For example, three separately named readers saved at one entrance may appear together. Match all three references in the list before concluding that a reader is missing or that only one reader is installed. This is an illustrative checking method, not a site result.
Investigate missing or incorrect map content
When reporting a problem, include the application version if available, relevant record references, expected result, observed result and steps to reproduce it. Share a screenshot through the approved support channel and omit unrelated personal or credential information.
Blank or partially loaded map
Record the error, time, site and affected layer. Check whether device and zone lists still load. If the problem affects only the geographic background, have the administrator check access to the configured map service. Preserve useful error details before reloading; do not reset site configuration to fix a display problem.
Missing or misplaced device
Find the exact record in device management. Compare its site, coordinates, filters and visible group membership. Check a suspected position against the installation record before editing. A missing marker alone does not diagnose a hardware fault.
Missing or incorrect zone shape
Compare the zone record, point order and intended boundary. Check whether the correct layer and site are selected. Keep a copy of the previous boundary before an authorized correction, then verify the resulting shape at more than one zoom level.
Slow or unresponsive display
Note the browser, device, site scope and action that causes the delay. Compare a smaller supported view or device list to isolate the problem. Share these observations with support; an arbitrary zoom range or marker limit is not a verified performance requirement.
Maintain reliable location records
- Use stable device references and descriptive site, entrance and lane names so an operator can match the map to the physical installation.
- Verify positions against installation records and on-site identification. More decimal places in a coordinate do not prove a more accurate measurement.
- Update the location record when equipment is moved or replaced, and confirm the linked device identity and zone assignments separately.
- After an authorized change, reopen the map and the underlying record. Confirm the saved position, intended boundary and site scope; check for overlapping markers.
- Record who made the change, why it was needed and how it was checked. Keep unresolved display or status discrepancies in the service record.