Geospatial / IntelligenceDefence and situational awareness, Bangladesh

GlobalView

Client: Internal / personal R&D

Geospatial situational-awareness platform on a 3D globe. Aviation, maritime, satellite, and ground feeds correlated on one operational picture.

Definition

What is the GlobalView case study?

GlobalView is an internal LoneSock R&D platform for geospatial situational awareness. It correlates aviation (ADS-B), maritime (AIS), satellite, and ground-sensor feeds onto a single CesiumJS 3D globe. It is not a paying client engagement and is published as a case study of the platform pattern rather than a customer deployment.

The Challenge

What we were solving for.

Situational awareness in defence contexts is fragmented across single-domain tools. Aviation tracking sits in one system, maritime in another, satellite imagery in a third, and ground sensors elsewhere. There is no consolidated operational picture.

The data is heavy and latency-critical. Operators need to see events when they happen, not minutes later, and they need to be able to correlate across domains rather than context-switch between tools.

Visualisation matters. 2D map views lose altitude, satellite-pass geometry, and terrain context. A 3D globe with proper terrain handles those naturally.

What We Built

Technical architecture.

An eight-service Go microservice architecture in which each service owns a domain: ADS-B ingestion, AIS maritime tracking, satellite pass prediction, sensor fusion, alerting, historical replay, user management, and the API gateway.

A CesiumJS 3D globe front-end rendering live positions of aircraft, vessels, and ground assets with terrain awareness. Operators can rotate, zoom, and query any tracked entity for detailed metadata, historical track, and cross-feed correlations.

A Kafka-based event streaming layer carrying the firehose of position updates, with PostGIS spatial queries driving geofencing alerts and proximity calculations.

A historical replay capability that lets operators rewind and replay any time window with all feeds overlaid for after-action reconstruction.

Key Numbers

Attributed, honest figures.

We publish numbers that the engagement supports. Unverifiable marketing metrics are not on this page.

8 services
Go Microservice Set
ADS-B + AIS
Air + Sea Feeds
PostGIS
Spatial Backbone
CesiumJS
3D Globe

Technology Stack

What we built it with.

GoNext.js 16CesiumJSPostgreSQL + PostGISKafkaRedisWebSocket

Outcome

What the engagement delivered.

GlobalView functions as a single operational picture combining air, sea, space, and ground feeds, which is the core capability the pattern is designed to demonstrate.

Position updates surface with low latency on the live feeds, and the geofencing alert path supports proactive monitoring of defined areas.

Historical replay supports after-action review with full cross-domain fidelity, rather than reconstructing events from per-domain logs.

Questions

FAQ for the GlobalView engagement.

What is GlobalView?

GlobalView is an internal LoneSock R&D platform for geospatial situational awareness, correlating aviation, maritime, satellite, and ground feeds onto a 3D globe. It is not currently a paying client engagement.

Why is it published as a case study?

The pattern (multi-feed correlation, 3D globe visualisation, historical replay) is reusable across defence, infrastructure monitoring, and large-area logistics. The case study describes the pattern and the engineering choices behind it.

What tech stack was used?

Go for the eight-service backend, Next.js 16 plus CesiumJS for the 3D globe front-end, PostgreSQL with PostGIS for spatial state, Kafka for event streaming, Redis for hot caches, and WebSockets for live UI updates.

Can LoneSock build this kind of system for a customer?

Yes. The GlobalView pattern is directly applicable to defence, civil aviation, port and maritime authorities, and other domains that need a consolidated operational picture across multiple real-time feeds. A customer engagement would scope feeds, access model, and deployment to the customer's requirements.

Is the platform externally deployed?

Not as an external customer deployment. It runs internally as R&D and as a reference implementation of the multi-feed correlation pattern.

Working on something similar

We have shipped this class of system before. Tell us what you are dealing with.

$20/hr time and materials, fixed-price milestones, or retainer. Source code is yours.