Urban freight is invisible to most city governments. Delivery vans, cargo bikes and micro-fulfilment shuttles generate a significant share of urban congestion and kerbside conflict, yet municipal authorities typically learn about this load only through carrier self-reporting — data that is incomplete, delayed and commercially curated. Without an independent ground-truth, planners cannot price loading zones correctly, enforce time-windows, or quantify the carbon footprint of the last mile.
A constellation of sub-metre optical microsatellites combined with an RF survey payload gives a city an independent, continuous read on delivery activity. Repeated passes over commercial corridors detect vehicle accumulation at kerbsides, dwell times, double-parking events and the emergence of new informal staging areas near fulfilment hubs. Optical detections are cross-correlated with RF signatures from fleet telematics bands (433 MHz, 868 MHz, 915 MHz LoRa/Sigfox, and cellular LTE-M) to distinguish delivery vehicles from private cars and to attribute detections to vehicle class.
The operational outcome is a dynamic freight heat-map that city logistics teams update daily without touching a single carrier API. Planners can identify which streets absorb disproportionate dwell load across morning and afternoon windows, target enforcement resources, and model the effect of kerbside pricing changes before implementation. Aggregate emissions estimates — derived from vehicle class, dwell duration and engine-state inference — feed directly into national urban air quality reporting obligations.
Frequently asked
What exactly can a satellite see that a city's own CCTV network cannot?
Satellite imagery provides a consistent, city-wide spatial layer that no ground-based camera network can replicate without prohibitive cost. It captures the full arterial and neighbourhood network simultaneously — revealing, for instance, that delivery pressure has migrated from a managed zone in the city centre to an unmonitored residential street. CCTV covers fixed points; satellites cover the whole urban fabric and can be retasked within hours.
How frequently does a satellite constellation need to revisit a city to be useful for delivery pattern analysis?
For strategic planning — identifying chronic double-parking hotspots, mapping micro-fulfilment demand — daily or twice-daily revisit is sufficient, achievable today with a 16–30 satellite LEO constellation. For dynamic kerb-space management, sub-hourly revisit is desirable, requiring either a larger constellation (50+ satellites) or fusion with AIS/ADS-B-style IoT tracking on delivery fleets. Most sovereign programmes should plan for daily optical plus continuous RF monitoring as a baseline.
Why shouldn't a city just buy this data from Planet, BlackSky, or Spire as a commercial service?
Commercial subscriptions transfer data sovereignty to the vendor: pricing, access terms, and data-sharing policies can change at contract renewal, and the vendor may sell the same analytics to competing cities or private logistics operators. A sovereign constellation means the city or nation controls data retention, resolution, revisit tasking priorities, and who else — if anyone — sees the output. For cities negotiating freight access with large e-commerce platforms, that information asymmetry is a genuine governance risk.
What satellite technologies are used — optical cameras, SAR, or RF sensors?
All three have roles. High-resolution optical (30–50 cm) identifies vehicle types and counts stops in daylight. SAR (Synthetic Aperture Radar) from operators like ICEYE or Capella provides all-weather, day-night imaging but requires more complex classification algorithms. RF/AIS monitoring (Spire, HawkEye 360) detects fleet transponders on larger commercial vehicles. A mature sovereign programme fuses all three layers, with optical as the primary analytical input.
How does this connect to urban freight regulation and loading-zone policy?
Satellite-derived dwell-time and stop-density maps directly inform the evidence base for loading-zone placement, time-of-day access restrictions, and low-emission zone boundaries — decisions increasingly required under EU SUMPs (Sustainable Urban Mobility Plans) and equivalent national frameworks. Without objective spatial data, cities must rely on lobbying from logistics operators or sparse manual surveys; satellite analytics shifts that negotiation onto a factual footing the city controls.
Can nanosatellites and microsatellites deliver the resolution needed, or does this require large bus platforms?
Sub-50 cm optical resolution has historically required 100–300 kg platforms, but advances in telescope miniaturisation (e.g. Planet's Pelican series) are pushing 50 cm imagery into the 30–50 kg microsatellite range. For a sovereign programme, a constellation of 8–12 microsatellites in a sun-synchronous LEO orbit at ~500 km can deliver 50 cm resolution with twice-daily city revisit — a realistic procurement target within a mid-income nation's space budget over a 5–7 year development cycle.
What ground infrastructure is needed to make satellite data operationally useful for city planners?
At minimum: a national ground station for downlink and tasking, a cloud-based image processing pipeline capable of automated vehicle detection and classification (typically using convolutional neural network models), and an API layer that feeds outputs into the city's traffic management and GIS systems in OGC-compliant formats. Integration with existing city data platforms — such as digital twins or SUMP dashboards — is where most implementation effort concentrates, not the satellite hardware itself.
Is there a risk that logistics companies will simply avoid satellite-monitored streets?
Behavioural displacement is a real effect: if enforcement is known to be satellite-informed, operators may shift to unmonitored streets or off-peak hours. This is actually a policy feature as much as a bug — displacing deliveries to off-peak windows reduces peak congestion. Whole-city coverage (not just monitored corridors) closes the displacement loophole, and nations operating their own constellation can retask imagery dynamically to follow emerging hotspots rather than being constrained by a vendor's fixed tasking schedule.