What Twinise is for

A live 3D model of a real place, fed by real sensors, so the question “how is it actually doing?” has an answer you can see. Start with the situation closest to yours.

Worked example · City scale

A whole city, live in one model

We built a live 3D twin of Newcastle upon Tyne in Unreal Engine on open data from the Newcastle Urban Observatory. It brings 760 sensors, through eight groups of feeds, into one Twinise site: journey-time and footfall counters, air-quality monitors, river and rain gauges and thermometers.

  • Live values pinned where each sensor stands in the city.
  • Air-quality readings drawn as a layer across the city, interpolated between monitors.
  • A river-level alert on the Tyne that fires when a threshold you set is crossed.
  • The last 24 hours replayed in a minute.
A 3D view of Newcastle at 14:00 with vehicle counts drawn as a red and orange glow over the city, the Central Motorway corridor in yellow and a river-level alert on the left
The last 24 hours replayed in a minute: vehicles counted by 92 central plate sensors, drawn as a heat layer, with a Tyne river-level alert on the left. Contains data from the Newcastle Urban Observatory, Newcastle University, licensed under CC BY 4.0. Readings are shown as received; the wind and comfort studies are Twinise simulations, not Urban Observatory data. This uses Environment Agency flood and river level data from the real-time data API (Beta), and Tyne and Wear traffic data, © Newcastle City Council, both under the Open Government Licence v3.0. Contains Met Office data © Crown copyright. Layers drawn over the map are interpolated and visualised by Twinise. Place names © OpenStreetMap contributors. Imagery: Google.
A 3D view of the Tyne at Dunston with a glowing ring above the river showing the last 24 hours of water level as two tidal waves
The Dunston river gauge on the Tyne: its last 24 hours drawn as a ring over the river, the two tides as two waves. Contains data from the Newcastle Urban Observatory, Newcastle University, licensed under CC BY 4.0. Readings are shown as received; the wind and comfort studies are Twinise simulations, not Urban Observatory data. This uses Environment Agency flood and river level data from the real-time data API (Beta), and Tyne and Wear traffic data, © Newcastle City Council, both under the Open Government Licence v3.0. Contains Met Office data © Crown copyright. Layers drawn over the map are interpolated and visualised by Twinise. Place names © OpenStreetMap contributors. Imagery: Google.
A 3D view of Newcastle at dusk with a blue air-quality layer draped over the city between monitors and labelled readings from air, river and rain sensors
PM2.5 interpolated between 14 monitors and drawn over the city. It is a visualisation of the readings, not a measurement at every point. Contains data from the Newcastle Urban Observatory, Newcastle University, licensed under CC BY 4.0. Readings are shown as received; the wind and comfort studies are Twinise simulations, not Urban Observatory data. This uses Environment Agency flood and river level data from the real-time data API (Beta), and Tyne and Wear traffic data, © Newcastle City Council, both under the Open Government Licence v3.0. Contains Met Office data © Crown copyright. Layers drawn over the map are interpolated and visualised by Twinise. Place names © OpenStreetMap contributors. Imagery: Google.

We built this on open data as a demonstration. The Urban Observatory has not endorsed it and nobody in Newcastle is a customer. The traffic layer and clock rings are Twinise visualisations drawn over the map. The same portal, alerts and Unreal plugin work with your own sensors.