Live data & the Globe
Real-world feeds on one map
Nexma renders the real world's live data feeds on one map. Flights, ships, weather, threats, sensors, fleets, and your own telemetry surface on the Globe alongside your project — pull what is relevant, leave what is not, and ask Jax to reason over any of it. Live data is first-class project content, not a separate layer to learn.
The path is consistent for every feed: ingestion writes data into the world model, and the Globe renders it reactively. There is no per-feed UI code and no separate data layer — if you can work with your own designs, you can work with live data.
Core concepts
- The Globe. Nexma's map-native canvas — a 3D-capable basemap with live project layers on top. The map is the primary surface; dashboards, inspectors, and Jax slide in around it.
- Live feed. A real-world source — aviation, maritime, weather, earth observation, cyber, mobility — enabled per project and rendered automatically.
- Spatial pin. Any feature you right-click to attach as context to a Jax conversation, so the agent can read its state and reason over it.
- Reactivity. One write to the DataStore, and every surface updates — Globe layers, tables, and the agent all read the same truth.
Sources are enabled per project. Ones you do not enable never touch your project, and they cost you nothing.
How it works
Feeds flow from ingestion into the world model, and the Globe renders any spatial layer it finds there. No feed writes to the map directly.
1SyncEngine / Event Broker --> Nexma DataStore --> the Globe
2 (connect & stream) (world model) (reactive render)
3 |
4 v
5 Jax (reads & reasons)SyncEngine connects the breadth of sources; the Event Broker streams high-frequency telemetry. Both write into the DataStore. A reactive layer renders any spatial feature on the Globe automatically — adding a feed requires no map code, only a connector and the source.
What you can do with it
- Bring real-world context into a design. Overlay weather, traffic, vessel positions, or threat data to see which assets are exposed and where.
- Pin features into a Jax conversation. Right-click any flight, vessel, or weather cell to pin it; the agent now has structured information about that entity and can reason over it.
- Build dashboards next to the map. Tables, charts, and trend lines render alongside the Globe for any source you opt in to.
- Search, filter, and export. Live data participates in the same workflows as your own content.
The feed catalog
A non-exhaustive list of categories shipped today. The catalog grows monthly, and customer-requested sources — industry-specific data, your own APIs, on-prem sensor streams — are typically added within a release cycle.
| Category | Examples |
|---|---|
| Aviation | Live flights, airport status |
| Maritime | Vessel positions, port congestion |
| Weather | Radar, severe-weather alerts, forecast surfaces |
| Threat and cyber | Exposure scanners, network intel feeds |
| Earth observation | Wildfire detection, vegetation indices |
| Mobility | Traffic, transit, freight flows |
| Environment | Deforestation, emissions, climate anomalies |
| Markets | Commodity prices for relevant verticals |
| Custom | Internal systems, equipment telemetry, partner APIs |
Spatial pins and Jax
Right-clicking a feature on the Globe pins it to the current Jax conversation. Pinned features become spatial context chips that travel with your next message, carrying the feature's structured state. The agent reads that state through the eight generic primitives and reasons over it — comparing a pinned vessel against a drawn zone, checking a sensor reading against a threshold, or correlating several pinned features at once.
Pinning works on any feature with geometry — a live feed, one of your own entities, or a result Jax just produced. There is no special pinning mode and no maximum.
Click is read, edit is write
The Globe is map-native, not a dashboard bolted onto a GIS engine. That inverts how interaction works:
- Click any feature to see its full record. The map is a window onto the DataStore, so what you click is the live record.
- Right-click to pin the feature as Jax context.
- Edit on the map — drag a vertex and the record updates; drop a polygon and a new selection is saved. The write flows back to the world model, and every other surface reacts.
Seeing the world through time
Live feeds carry a timeline. The Globe's temporal slider re-renders all time-aware layers at the chosen instant, drawing on the DataBase for position history. Slide back to reconstruct an incident after the fact, or forward to render against future-dated forecast feeds. Because the same store holds the present moment and everything that led to it, replay feels as responsive as the live map.
Where it fits
Live data is one expression of the world model. It renders on the Globe, it is visible to Jax, and it participates in search, filter, pin, and export like any other content. The same data appears in mobile field apps with no extra sync, and automations read and write it through the same project.
The Globe is observational — it shows the world and your project together, but it is not a control-authority system for actuating field equipment.
Where to go next
- Nexma SyncEngine — connect and ingest live feeds.
- Nexma Event Broker — stream real-time telemetry.
- Nexma DataBase — the time-aware store behind the temporal slider.
- Connecting data — enable feeds in a project.