Zum Hauptinhalt springen
Virtik

Mapping

How maps work in Virtik: the main map provider, where its token comes from, the basemaps and controls, what you see when a map cannot load, and the mobile map.

Version
0.2
Zuletzt aktualisiert
Verfügbarkeit
Teilweise verfügbar

Dieses Dokument wird derzeit nur auf Englisch veröffentlicht. Englische Originalfassung lesen

Maps in Virtik show sites, cameras, people and incidents in Command Center, Live Operations, Detection and Virtual Sites. They are drawn by a map provider, and this page covers what an organisation needs to know about that provider and what it can and cannot configure.

One provider

The web application's main map is drawn with Mapbox. Some satellite imagery and map styles come from other providers, which this page does not cover, and an organisation cannot choose a provider.

Where the token comes from

A map provider needs an access token. In this release the application carries a built-in public token, and a deployment can override it for the main map when it is built. Routing, address search and the mobile application use the built-in token directly. The application has no setting where an organisation administrator enters a map token, so mapping is not something an organisation configures for itself. The token is a public, browser-side token, which map providers intend to be restricted to the sites that may use it; whether it is restricted for a given deployment has not been verified.

If a map cannot render, it shows "Map unavailable", and the rest of the screen keeps working. Because of the built-in token, a missing token is rarely the cause.

Basemaps and controls

The Map controls panel offers five basemaps: Tactical Dark, Street / Navigation, Satellite Intelligence, Terrain / Topographic and Strategic Globe. It also has a 2D or 3D toggle, a North control that resets the heading, and, on screens that supply it, an icon-only Fit operational area control (Detection has its own Fit all command). Operational layers are listed only where the product has wired a data source for them, which does not mean your organisation has data in them. A layer with no data source is not shown.

Virtual Sites opens on the satellite basemap the first time, unless you changed basemap earlier in the session.

Routes

Responder routes use the map provider's directions service. When routing fails, Command Center's responder panel says "Road route unavailable" or "Routing error", and the Response map says "Route unavailable" and shows the straight-line distance. An incident can still be worked without a route.

The mobile map

The mobile application offers two basemaps, Dark and Satellite. On a physical device build the map is not drawn: positions are shown without a basemap and the application points to the web application for the map. When a map cannot be shown, the mobile application says why in words such as "The map isn't set up", "The map service refused access" or "You're offline".

What to plan for

Provider access
Every deployment depends on a map provider account and its terms. Virtik does not state those terms here.
Network
Browsers need to reach the map provider and its tile services. The Studio map may use other providers' tile hosts, so a firewall allow-list built from one screen may be incomplete. The exact hosts are confirmed for each deployment; see Requirements.
Locations
A site with no coordinates does not appear on the map. Command Center and Virtual Sites list it under "Location not configured", and Detection says "This site has no coordinates". Coordinates can be added when you create the site or edited later on the Sites page under Admin → Organization.

Current availability