Skip to content
Nexus Observatory

/

Cities

/

Use cases
Cities: where it is deployed.

Deployment scenarios from the sector research and the use-case library, each with the kit, the data products and the proof a buyer asks for. 4 in all.

Plan a deploymentSolutionsOpen the explainer
  1. Cities · Use cases

    The city, measured block by block

    Street-level flood depth, air quality and heat, mobility and noise, carried on a municipal sensing and connectivity layer, with twins of the streets they sit in and open data residents can read. Needs: street flooding, air quality and urban heat, structural condition of public assets, connectivity for municipal sensors and open data for residents.

  2. Use case

    Street flood observatory

    Ultrasonic depth sensors on poles report street-level water depth as open data and alerts. For cities, emergency management agencies and universities. Data products: street-level water depth time series and open data feed and alerts to emergency management and 311. Drawn against OGC SensorThings API 1.1 and Municipal open-data terms.

    Standards
    OGC SensorThings API 1.1 · Municipal open-data terms
  3. Use case

    Hybrid air-quality observatory

    A few reference analysers and many low-cost nodes, with co-location calibration and an open-data feed. For cities, public-health units, school districts. Data products: air-quality index and hyperlocal maps, labelled supplementary, calibrated time series with quality flags and publication route to an open air-quality aggregator.

    Standards
    EU Directive 2024/2881 (ambient air quality) · CEN/TS 17660 (sensor systems) · US EPA FEM/FRM reference methods
  4. Trust

    Every node proves what it is

    A node joins only after its hardware root of trust answers an attestation challenge. Keys stay in secure hardware, software arrives signed, and every reading carries a signature, so its origin can be checked by anyone downstream without asking us.

  5. Time and place

    Every reading carries when and where

    Readings are stamped against a disciplined clock, from satellite time or a PTP grandmaster, together with the station position and its siting record. When time or position is degraded, the record says so instead of hiding it, and every analyst downstream sees the same warning.

  6. How it scales

    One base unit, repeated

    A programme starts with one base node and the instruments it reads. A station adds power and radio, a site adds a relay, a fleet repeats the proven site across many places, and a network federates fleets through edge and core. Capacity grows by adding units, never by replacing what works.

  7. Updates

    Updates in rings, with rollback

    Software and configuration reach the fleet in rings: a canary site first, then a few, then all, each ring gated on health and data completeness. A failed gate stops the wave and returns each node to its last good release, without a site visit.

  8. Operations

    Every node watched, every incident closed

    The operations console shows every node with its state, its plan and its evidence. Alerts arrive with their data and a runbook; acknowledging one opens a work order, and an incident closes only when the cause is recorded and the fix verified.

  9. Field service

    One crew, from survey to repair

    The same crew surveys, installs, commissions, calibrates and repairs, working from the site’s own record. Each visit updates it, so the next crew knows exactly what is there, when it was last checked and why it was changed. Spares and references are planned from that history.

  10. Failure and recovery

    When a node fails, the fleet knows first

    When a node goes silent or a sensor drifts, the node buffers its data, fails over to a second link where one exists, and the alert carries the evidence a responder needs. Nothing is lost and nothing is counted twice.

  11. Evidence

    Standards you can check

    Metadata follows WIGOS and ISO 19115 practice, observations are served through OGC SensorThings and can be exchanged through WIS 2.0, and every release, calibration and admission is kept as a signed record that an auditor can verify independently, without asking us to explain it.

  12. What you get

    Municipal sensing and connectivity layers

    City-wide LPWAN or private 5G as a shared layer for public sensors and services. Delivered as managed service, for cities, regional governments. Scale: City-wide. Service levels are written as numbers you can measure on your own dashboard. Changes are versioned, tested and reversible.

    Talk to sales
  13. Next step

    Plan a cities deployment

    Tell us the sites, the measurements and the people who will use them. We reply with a design and a scope for cities. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace.

    Plan a deploymentOpen the StudioRead the stories

01Specialized fields

Each field has its own setup.

The measurements, radio, power and crew work differ from one field to the next. Open a field for its full stack, from order to operation.

Specialized field

Urban air quality

Reference stations and dense sensor networks for particles and gases, with weather to trace sources, calibrated against each other, on cellular and LoRaWAN, for street-level maps people can trust.The full field →
Specialized field

Urban heat and trees

Street-level temperature and humidity across neighbourhoods, tree soil moisture and heat-health alerts, on LoRaWAN across the city, so cooling and watering go where people suffer most.The full field →
Specialized field

Streets and mobility

Counts of people, bikes and vehicles, speeds, kerb use and junction safety by camera and radar processed at the edge, on private 5G and fibre, so streets are planned on evidence and privacy is kept.The full field →
Specialized field

Public buildings and energy

Energy, heat and water meters, indoor air and comfort in schools, offices and pools, with weather for normalisation, on the buildings’ own networks behind a security gateway.The full field →
Specialized field

Waste and street services

Bin fill levels, collection routes, transfer station gas and weather, on LoRaWAN across the city, so crews empty what is full and the waste record follows from the work.The full field →
Specialized field

Noise and the night-time city

Class 1 noise monitoring at hot spots, event classification at the edge for nightlife, construction and traffic, with weather, on cellular, so complaints are answered with evidence and noise plans work.The full field →

02Use-case library

Worked use cases, kit to data product.

Each names who deploys it, the kit by device class, the data products it publishes and the standards it is drawn against. Open one for its full page.

Use case · low complexity

Street flood observatory

Ultrasonic depth sensors on poles report street-level water depth as open data and alerts.
Who
Cities, emergency management agencies and universities.
Data
Street-level water depth time series; Open data feed and alerts to emergency management and 311
OGC SensorThings API 1.1 Municipal open-data terms The full use case →
Use case · low to medium complexity

Hybrid air-quality observatory

A few reference analysers and many low-cost nodes, with co-location calibration and an open-data feed.
Who
Cities, public-health units, school districts.
Data
Air-quality index and hyperlocal maps, labelled supplementary; Calibrated time series with quality flags; Publication route to an open air-quality aggregator
EU Directive 2024/2881 (ambient air quality) CEN/TS 17660 (sensor systems) US EPA FEM/FRM reference methods The full use case →

03Cities

Cities: deployment scenarios.

Air quality, noise, traffic, urban heat and street flooding, with open data as a procurement credential.

Cities

Hybrid air-quality network

Reference analysers plus calibrated low-cost nodes; low-cost sensors alone do not meet regulatory requirements.The full use case →

Cities

Municipal low-power radio or private 5G layer

A city-wide connectivity layer as digital public infrastructure.

04Across the industry

Across the classification.

Use cases mapped to the UN ISIC Rev. 4 sections this site covers.

  • Progress capture as site twins
  • Ground movement near excavations
  • Temporary site connectivity
  • Flood and subsidence evidence per property
  • Building twins for portfolios
  • National observing networks as digital public infrastructure
  • Northern and coastal infrastructure awareness (civil, lawful)
  • Incident-base connectivity and sensing

05Proof

What buyers ask to see.

  • Co-location calibration reports against reference monitors, data-completeness service levels, an open-data API, a privacy impact assessment for video and probe sensing, accessible dashboards.
  • Survey accuracy (GSD, check points), deformation precision
  • Method statements, accuracy against ground truth
  • Reporting uptime, format conformance, references from public agencies; decisions stay with the authority

Ready when you are.

Plan a deployment, configure a station or talk to sales. Every request reaches the team that answers it.

Plan a deploymentStation BuilderTalk to sales

Bring us the site.

Survey, design, deployment and operation for cities. The form names who receives your details.

Talk to usPlan a deployment

Cities: where it is deployed.

Reference design, drawn to scale · drag to turn