Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Enhancing Urban Planning Outcomes with Geographic Information Systems and Digital Twin Technologies
Introduction Business challenges Solution overview Partner Overview Solution Architecture Validation
Validation
GIS urban and Smart City
Results Findings
Integration of GIS and Digital Twin platforms
Results Findings
Enhance GIS workflow with Digital Twin simulation capabilities
Results Findings
Conclusions References

Integration of GIS and Digital Twin platforms

Home > Workload Solutions > Computer Vision > White Papers > Enhancing Urban Planning Outcomes with Geographic Information Systems and Digital Twin Technologies > Integration of GIS and Digital Twin platforms

Integration of GIS and Digital Twin platforms

  • Results

    This CityEngine to Omniverse integration validation investigates how to install, connect, and share GIS models with the Omniverse platform:

    1. Install connector.
    2. Connect.
    3. Test interoperability.

    Install Connector

    Install the connector from the Omniverse Launcher menu. See Omniverse Launcher Overview. Select the connector for the corresponding CityEngine version.

    Note CityEngine must be installed before the connector.

    Figure 5. Omniverse CityEngine install
    This figure shows a screenshot of the installation page for the CityEngine Ominiverse Connector.

    Connect

    To connect CityEngine to the Omniverse Nucleus server:

    1. Within the CityEngine GUI. Select layers, shapes and models.
    2. Choose File > Export Model.
    3. Select Omniverse Connector.
    4. Specify the Nucleus hostname, path on server, and export name. For example: myName.
    5. On the Nucleus webpage dialog box, click Log in.
      Note: The Omniverse web login page appears only once. If skipped or incorrect credentials are specified, relaunch to establish connection.

    6. Click Finish.

    The exported CityEngine scene (layers, shapes, models) are written to the previously specified file name and file path on the Omniverse Nucleus server.

    Figure 6. Omniverse CityEngine install
    This figure shows a screenshot of the process for installing the CityEngine Ominiverse Connector.

    The exported CityEngine 3D model can now be worked on within the Omniverse platform.

    Test interoperability

    The Omniverse CityEngine connector provides a unidirectional link from CityEngine to an Omniverse Nucleus server instance.

    Figure 7. Live Sync is enabled on the Omniverse Nucleus server to watch for updates from CityEngine
    This image shows a screenshot of Live Sync enabled on the Omniverse Nucleus server.

    In this example, the LIVE option is enabled and the Example_Urban_Design Omniverse Nucleus root layer is synced using the CityEngine connector. Applications built on top of Omniverse templates such as USD Composer can automatically detect when CityEngine updates Nucleus instance and prompt in app for layer reloading as shown in the following figure.

    Figure 8. Omniverse USD Composer App prompted when CityEngine updates Nucleus instance
    This image shows a screenshot of the Omniverse USD Composer App prompt that displays when CityEngine updates a Nucleus instance.