City planners and transport authorities are flying blind. Ground-loop counters, manual surveys and operator-reported ridership give fragmented, delayed snapshots of a network that changes hour by hour. The result is infrastructure spend driven by politics and gut instinct rather than evidence, chronic congestion on corridors that satellite data could have flagged years earlier, and zero ability to model the ripple effects of a road closure or a new metro line before the concrete is poured.
A sovereign GNSS-augmented satellite stack closes that gap. A LEO nanosatellite constellation carrying GNSS-reflectometry and RF survey payloads generates city-wide signal-of-opportunity measurements every 15–30 minutes, feeding ground-truth into a positioning correction service accurate to sub-metre in urban canyons where commercial GPS degrades to 5–15 m. Fused with anonymised probe-vehicle feeds and transit smart-card timestamps, the platform produces a living origin-destination matrix updated in near-real-time—something no single commercial data vendor can or will provide to a government without carving out their most valuable commercial slices first.
The operational output is concrete: dynamic signal-timing on arterials, optimised bus-frequency schedules, freight-window enforcement backed by satellite-time-stamped entry logs, and model inputs for billion-dollar capital decisions. Cities that rent this capability from a foreign platform hand over the most granular possible record of how their population moves—a dataset with obvious intelligence value that should never leave the national boundary.
Frequently asked
Why does a city or nation need a satellite layer for mobility analytics — can't ground sensors do the job?
Ground sensors (inductive loops, cameras, Bluetooth beacons) provide dense point data but no coherent city-wide or cross-border picture. Satellite positioning and imagery supply a consistent, infrastructure-independent reference frame that works even where road sensors have not been deployed — which is most of the road network in most countries. The two layers are complementary, not substitutable.
What kind of satellite system actually underpins urban mobility analytics?
Three distinct satellite capabilities are typically fused: GNSS constellations (GPS, Galileo, GLONASS, BeiDou) for positioning; LEO small-sat constellations carrying AIS, ADS-B or custom IoT payloads for fleet tracking; and high-revisit Earth-observation satellites (optical or SAR) for macro traffic-pattern monitoring. A sovereign programme ideally owns at least one of these layers outright and contracts augmentation for the rest.
How accurate is satellite-based positioning for buses and trams in city centres?
With raw multi-constellation GNSS the typical urban accuracy is 3–10 m, degraded further by multipath in dense canyons. Adding a satellite-based augmentation system (SBAS such as EGNOS in Europe) or a commercial precise-point positioning (PPP) correction service brings this to 0.5–1 m, which is sufficient for lane-level fleet management. A sovereign CORS network of ground reference stations can deliver sub-metre performance without relying on a foreign correction provider.
What is the minimum constellation size a nation needs to support this application?
For a dedicated fleet-tracking IoT payload mission, a constellation of 6–12 microsatellites in a sun-synchronous LEO orbit (~550 km) can achieve 30–60 minute revisit over a national territory, meeting the latency requirements for operational fleet management rather than just planning analytics. Optical monitoring at useful resolution requires procuring imagery from a commercial provider such as Planet or BlackSky, or commissioning a shared national observation satellite.
Who owns the mobility data generated by a commercially procured satellite analytics service, and why does it matter?
Under most commercial data-as-a-service contracts (e.g., those offered by Spire, Iridium or Viasat-linked platforms), processed analytics are licensed to the city but raw positioning and trajectory data remain on the vendor's servers, often in a foreign jurisdiction. This means a government cannot independently audit the data, cannot guarantee service continuity in a diplomatic dispute, and may not be able to share the data with other agencies under its own privacy laws. Sovereign ownership eliminates this ambiguity.
Can satellite analytics help with freight and logistics, not just passenger transport?
Absolutely — and often this is where the financial case is strongest. Satellite-tracked freight vehicles generate last-mile delivery efficiency data, enable dynamic kerbside management, and can feed port-landside corridor models. The World Bank estimates that poor urban freight management costs developing-country cities 1–3% of GDP annually; satellite-derived origin-destination matrices are a cost-effective tool to quantify and address this.
How does this application relate to autonomous vehicle navigation?
Urban mobility analytics provides the aggregate, population-level data layer (where vehicles travel, when, at what density) while autonomous vehicle navigation requires centimetre-level, real-time positioning for individual vehicles. The two are complementary: HD maps used by autonomous vehicles are partially derived from aggregated mobility analytics, and sovereign ownership of both layers ensures that the mapping data feeding autonomous vehicles is not controlled by a private foreign operator.
What is a realistic build-vs-buy decision timeline for a mid-income country?
A sovereign programme covering a 6-satellite IoT-payload LEO constellation with ground segment and analytics platform typically takes 4–6 years from programme approval to operational capability, at a cost of $80–150M. Buying analytics-as-a-service from a commercial provider can start in under 12 months for $2–5M per year, but the sovereign option delivers indefinite capability and data ownership after the payback period of roughly 8–10 years. The right sequencing is usually: buy commercially while building sovereign, then transition.