Frequently asked questions

A city digital twin is a measurable 3D copy of a city, including its terrain, buildings, roads and infrastructure. It is updated with data from institutional systems and sensors, so you can test a decision in the twin before implementing it on the ground.

A digital twin does three things together: it shows the city in 3D in the same coordinate system as your organisation’s geographic data, it shows data from sensors and institutional systems where it is measured, and it tests a change before it is made on the ground. A 3D map does only the first; GIS comes close to the first two but offers neither 3D nor simulation.

Ready today: a 3D city with real terrain, buildings, roads and rail; a city editor for adding roads, intersections, traffic lights and buildings; lane-level traffic simulation and intersection indicators; sun and weather that follow the city’s real time; and the same city in the browser, on desktop and on a VR headset. Live links to sensors, public transport vehicle positions, cameras, the signal system and your city information system are set up during the project by connecting to your organisation’s systems.

The app for desktop and VR is the city’s most detailed 3D twin, where specialists design new projects and run traffic and disaster scenarios. The web platform opens in the browser, where departments switch on layers, colour the map by data and run analyses. The mobile app is in the pockets of field crews and citizens: 3D map, navigation, field data collection and notifications.

Yes. All three apps share the same city data and the same user accounts. A change made on the desktop appears on the web and on mobile with no extra step; a record entered in the field reaches the screen at headquarters at the same moment.

The detailed 3D twin runs as a desktop app for Windows and macOS, in the browser and on a VR headset connected to a computer. The web platform needs no installation and opens in a standard browser on a computer or tablet. The mobile app is for iOS and Android.

To show the whole city quickly, the web platform and the mobile app present buildings as simple volumes with their real footprint and height. When a closer look at a single building or area is needed, you switch to the detailed 3D twin on the desktop with the same data.

We start with the data your organisation already has: city information system layers, building and address data, the road network, the digital elevation model and orthophotos, plus LiDAR and older 3D models where available. Surveys are planned for areas where data is missing or out of date.

The twin is built in the same coordinate system as your city information system, so the layers line up exactly. Once it is connected to your city information system’s service, building, parcel and zoning changes are reflected in the twin at set intervals. This link is set up during the project, based on your organisation’s service.

Yes. The brand of sensor or device does not matter; air quality, noise, meter and similar readings are taken from your organisation’s sensor and network monitoring systems and shown in the twin at their real location, with a time chart. Each connection is set up during the project, based on the relevant system’s service.

Yes, by connecting to your organisation’s systems: intersection counters, travel time measurements, public transport vehicle positions, car park occupancy, city cameras and the signal system. A connection depends on the system having a working, documented service; we establish this together in the first step.

Terrain is produced from the digital elevation model, and buildings from their footprint and floor data, with storey heights. Roads come with their lanes and street names; bridges, viaducts and tunnels are formed from elevation data. Façades can be textured with photographs, and selected critical structures are also modelled in detail.

LOD is the level of detail of a building model. LOD1 is a flat-roofed block, LOD2 shows the roof shape, and LOD3 shows façade details such as windows, doors and balconies. The usual set-up is LOD2 citywide and LOD3 for critical structures such as hospitals, stations and bridges. In the web platform and the mobile app, buildings are shown as simple volumes for speed.

Models are positioned in the same coordinate system as your city information system. The model is as accurate as your source data; areas where data is missing or out of date can be improved with new surveys.

No, it is rule-based. Each vehicle is simulated individually at lane level and obeys traffic lights, priority and yield-to-the-right rules. When you close a road or reverse its direction, vehicles redistribute to other roads live. Because the same road network always gives the same result, two designs can be compared fairly.

For each intersection approach: queue length, control delay, level of service from A to F, saturation and turning distribution; for each road: average speed, speed drop and travel time. When a traffic light is added to an intersection, conflicting movements are detected and a conflict-free phase plan is built.

Disaster and planning scenarios are added to the twin during the project, according to your needs. The foundation is ready: real terrain, buildings and road network, plus a traffic simulation that reroutes when a road is closed. Assembly areas, hospitals and critical roads are brought together on the same 3D map.

Navigation is a feature of the mobile app: live location, routing and voice guidance, by car, on foot or by public transport. Stops, lines, transfers and estimated arrival times are shown on the map. Citizen-facing features such as notifications, parking information and complaint submission are added depending on the project.

Yes. The area map is downloaded to the device, so work continues in tunnels, basements or rural areas. Once the connection returns, data entered in the field syncs automatically.

They enter geolocated notes, photos and forms, log faults and requests, and track work orders. Every record reaches the screen at headquarters instantly. New work orders or incidents in the area arrive as instant notifications, by person, role or area.

Yes. The system is installed on your organisation’s own servers as a container-based, on-premises deployment; your data never leaves your organisation.

With an on-premises deployment, data stays in your own infrastructure. HTTPS, session management and audit logs are part of the deployment; compliance with KVKK (Türkiye’s personal data protection law) and penetration testing are addressed together during deployment.

Usually a district centre or a priority area, a few connected systems and one or two modules; most organisations start with traffic. At the end of the pilot, your organisation uses the explorable 3D twin, the live layers of the connected systems and the selected modules. The rest of the city is added area by area.

A contact person from each department; access to data and service documentation; city information system layers, the elevation model and orthophotos; a list of critical structures; access permissions and a test environment for the services to be connected; and server and network infrastructure for the on-premises deployment.