Where infrared.city fits

3,204,804 simulations run on Infrared Core (as of 29 Oct 2026).

infrared.city runs 12 models from one engine, Infrared Core, among them wind, wind comfort, sun, daylight, radiant heat and felt heat (UTCI). It works on real 3D building and terrain meshes, in a browser app, through an API and SDK, and in plugins for Grasshopper, QGIS and ArcGIS. Felt heat for 1 km² takes about 5 s once the geometry is uploaded, and 400 km² took 44 s as four 100 km² runs in parallel. Run times are not like for like across tools: area, grid, simulated hours and physics differ. Sun, sky and radiant heat come from ray tracing. Wind comes from an AI model trained on CFD results, not from a CFD run for each request. The live layer runs a whole city every hour on a forecast. It is a climate layer: it brings the simulation results, not the twin itself.

  • You need the heat a person feels on a 1 m grid, in the streets of one city.
  • You need wind comfort, sun and daylight for buildings.
  • You compare design and adaptation options for a site.

Use both

DestinE works at the scale of the Earth and its climate. infrared.city works at the scale of a street. One shows how the climate of a region changes; the other shows how a street feels and what a design changes there.

Facts side by side

Facts: infrared.city and Destination Earth
infrared.cityDestination Earth
ScaleStreet level, 1 m grid, site to cityThe Earth system
DeliveryBrowser app, API and SDKDestinE Platform, a cloud-based infrastructure with a data lake

The infrared.city values repeat the full comparison. Each value for Destination Earth comes from the sources below.

Sources

  1. Destination Earth home page , accessed 30 Oct 2026.