Provide the source
Enter a WebScene item ID, point to a CatalogLayer or service URL, or select a local JSON document. Authentication can be configured for controlled ArcGIS Enterprise sources.
Configuration automation
Point to the source.
Generate the starter.
Give the workflow an Esri WebScene ID, CatalogLayer URL or local JSON file. Generate reviewable Unity C# and configuration JSON instead of rebuilding every layer setup by hand.
3 input modesWebScene, CatalogLayer or local JSON
Unity outputC# starter and configuration JSON
Visible warningsUnsupported mappings stay explicit
RepeatableSame source, controlled generation
The workflow
No-code for operators. Reviewable output for integrators.
The companion GameEngine Geospatial Configuration Converter automates the repetitive mapping work while preserving a controlled validation step before a generated scene configuration is released.
Map scene content
Extract scene metadata, camera position, elevation and supported operational layers. Translate known layer types into target game-engine configuration models.
Review compatibility
Keep unmapped content and version-sensitive behavior visible through warnings instead of silently presenting a partial scene as complete.
Generate Unity files
Export a Unity C# configuration starter and structured JSON for ArcGIS Maps SDK or Cesium-oriented delivery pathways.
Validate and deploy
Load the generated result into the controlled GeoVerse3D build, check the exact Unity, SDK, plugin, service and device matrix, then publish the approved profile.
View mode and camera
Carry global or local scene context plus initial longitude, latitude, altitude and orientation values into generated configuration.
Supported operational content
Map scene, integrated mesh, building, image tile, vector tile, 3D Tiles, point cloud and elevation pathways where the selected SDK provides a compatible target.
C# plus structured JSON
Produce human-reviewable files that can be inspected, versioned and tested instead of burying the configuration inside a one-off manual scene.
Warnings and validation gates
Surface unsupported layer types, custom symbology and platform limitations so delivery teams know where an adapter or manual styling decision is still required.
Practical no-code model
Simple inputs. Controlled delivery.
| User | What they provide | What the workflow returns |
|---|---|---|
| GIS publisher | An approved WebScene ID or service URL | A repeatable game-engine configuration package and a report of content that needs review. |
| Field or program team | A local JSON configuration and target mission profile | A prepared Unity starter that can be validated without asking the user to write scene-initialization code. |
| Integration engineer | The target SDK, plugin version, device and security environment | Explicit mappings, generated C#/JSON and the exceptions that still require engineering. |
| Release owner | The accepted test matrix and approved source configuration | A controlled artifact that can be regenerated, reviewed and traced to the source scene. |
Automation without silent assumptions.
Catalog layers may require service discovery, custom symbology may need target-specific styling and certain Esri layer types have no direct equivalent in every Unity or Cesium path. GeoVerse3D keeps those boundaries visible so “no-code” does not become “no control.”
Bring a WebScene
or layer catalog.
We’ll generate the starter, review the mappings and identify the exact integration work needed for your target experience.
Plan a configuration review