Legal

Data sources and licences

Which data sources Digital Twin Simulation uses, the licence each one carries, and the attribution they require.

OpenStreetMap

OpenStreetMap is the working example of a geographic data source for Digital Twin Simulation: map data is read, and tags are derived from it onto simulation cells.

  • Licence: Open Data Commons Open Database License (ODbL) 1.0, with the OSM contributor database under the Database Contents License.
  • Attribution required: yes.
  • Share-alike: applies to derived databases — if you publicly distribute a derived database, it must be offered under ODbL. Producing maps or results from the data does not by itself trigger this.
Required credit for map imagery derived from OpenStreetMap:
© OpenStreetMap contributors, available under the Open Database License (ODbL).
More information: openstreetmap.org/copyright

Where a visual on this site is derived from OpenStreetMap data, that credit appears with the visual or in the footer of the page carrying it.

Your own data

Digital Twin Simulation is designed to work with the data a customer already holds — municipal registers, traffic counts, internal GIS layers. That data is not ours and is not covered by anything on this page. It stays under the customer's own terms, and under the arrangement agreed for the pilot or project.

Data sources under consideration

Because tags can be set from any source, other datasets can be connected as they are needed. Each carries its own licence and its own credit, listed here as it comes into use.

Third-party content in the demo

One demo on this site — the walkability showcase — is rendered over Google Photorealistic 3D Tiles, loaded in Cesium. This is presentation only. Neither Google nor Cesium contributes anything to the simulation: the tiles are what you see, and Digital Twin Simulation is what computes the flow on top of them. The engine does not depend on either, and the rendering layer is replaceable.

Notices shown with the demo:
  • The Google Maps logo, unmodified and unobscured.
  • The Cesium ion logo, prominently displayed.
  • Where Google content carries its own notices, these appear unaltered beside it: Google and the Google logo are trademarks of Google LLC. Imagery © Google, Maxar Technologies, and other contributors. Google Maps content is used under the Google Maps Platform terms.
  • Cesium — © Cesium GS, Inc. Cesium and Cesium ion are trademarks of Cesium GS, Inc. Used under the Cesium ion terms of service.

The exact copyright line that must appear depends on the imagery actually shown, and Google publishes it with the data. Where Google's own notices differ from the summary above, Google's wording applies.

How the demo is produced

  • Attribution stays visible. For static content such as a video, a "Data attribution" link on its own is not sufficient: the credit is legible in the video itself, in its caption, or on the page beside it, and is never covered part-way through a clip unless it is displayed prominently elsewhere in the same video.
  • Google content is never shown alongside a non-Google map. Google's terms prohibit it, so the two demos on this site are kept visually separate — never in the same screen or the same shot.
  • Map features are not traced out of the imagery. Building outlines, road centrelines and elevations are not digitised from it. The simulation tiles are generated by the engine.
  • Google content is not cached or re-hosted, and no map products are derived from it.
  • An active Cesium ion account is required while the content is in use. Static material such as a promotional video may remain published after the account ends.

A note on the other demo visuals

The remaining visuals on the site — including the "one engine, several domains" strip — are stylised diagrams we drew ourselves, not renders of real map data. They are labelled as such on the page.

This website

This site is deliberately plain: no advertising, no third-party analytics, no tracking, no embedded maps. It therefore sets no third-party cookies. The only things stored in your browser are two functional preferences — your language, and your light or dark theme. The privacy statement lists exactly what those are.