> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/geodin-ground/workflows-and-integrations/arcgis-integration/arcgis-web-scene.md).

# Publishing and reviewing a web scene

{% embed url="<https://www.youtube.com/watch?v=c1nneSVzYkw>" %}

> **Video chapters:** 0:00 Adding borehole location points & labels | 1:17 Converting annotation units to meters | 2:26 Setting the WGS 1984 coordinate system | 2:42 Publishing the web scene | 3:31 Viewing the published scene online

The ground model in ArcGIS Pro ([Bringing the ground model into ArcGIS Pro](/geodin-ground/workflows-and-integrations/arcgis-integration/arcgis-pro-ground-model.md)) can be published as an **ArcGIS Online web scene**, so stakeholders review soil-type volumes, boreholes, and attached reports directly in a browser - no CAD or GIS software installed. For the 2D point-feature equivalent of this workflow, see [Publish to ArcGIS Online](https://docs.geodin.com/integrations-and-plug-ins/overview/publish-to-arcgis-online) in the GeoDin documentation.

## Requirements

* The ground model and annotation layers in ArcGIS Pro ([Bringing the ground model into ArcGIS Pro](/geodin-ground/workflows-and-integrations/arcgis-integration/arcgis-pro-ground-model.md)).
* The **Borehole** point feature class ([extracted from the MultiPatch](/geodin-ground/workflows-and-integrations/arcgis-integration/arcgis-pro-extract-features.md)), added with a single symbol and the borehole-name label so each location reads clearly on the ground surface.
* An ArcGIS Online account with publishing privileges.

{% hint style="info" %}
**DEM source:** the terrain beneath the model in the videos and in the published demo scene is U.S. Geological Survey (USGS) 1 Meter DEM, obtained from [The National Map Downloader](https://apps.nationalmap.gov/downloader/). It carries through from the elevation surface set in the [first tutorial](/geodin-ground/workflows-and-integrations/arcgis-integration/arcgis-pro-ground-model.md#step-4-set-up-elevation), and it is publicly available, so you can download the same dataset to follow along.
{% endhint %}

### Step 1: Convert elevations to meters

Web scenes expect metric elevations. If the drawing's elevations are in feet:

* Run the **Adjust 3D Z** geoprocessing tool with **Reverse Sign of Z Values = Maintain Z Orientation**, converting **From Feet > To Meters**.

<figure><img src="/files/XaJKR48UuDVExtfGa8ey" alt=""><figcaption><p>Adjust 3D Z converting feet to meters</p></figcaption></figure>

* Then open **Layer Properties > Elevation** for the layer and set the vertical units to **Meters**. Zoom in afterwards to confirm the annotation sits correctly.

<figure><img src="/files/cndEqWo4N2ZuZkBInE2S" alt=""><figcaption><p>Layer elevation set to geometry z-values in meters</p></figcaption></figure>

### Step 2: Set the scene coordinate system

* Open the scene's **Map Properties > Coordinate Systems** and select **WGS 1984 Web Mercator (auxiliary sphere)** - the coordinate system web scenes require.

<figure><img src="/files/kzDBev8u0sVqFgWcvaYR" alt=""><figcaption><p>Scene coordinate system set to WGS 1984 Web Mercator</p></figcaption></figure>

### Step 3: Share the web scene

* On the **Share** tab, choose **Web Scene**.
* Enter a name, pick the destination folder, and set the sharing level (owner, organization, or public).

<figure><img src="/files/jmiQnOE4IWkRA8gTzxCM" alt=""><figcaption><p>The Share As Web Scene pane</p></figcaption></figure>

### Step 4: Analyze, publish, verify

* Click **Analyze** and resolve every error before publishing.

<figure><img src="/files/uRjjWzw4sflDfkBvxpwW" alt=""><figcaption><p>Analyze running before publication</p></figcaption></figure>

* Click **Share** to publish, allow processing to finish, then open the item's portal page and confirm all layers are present.

## Reviewing the scene in the browser

{% embed url="<https://www.youtube.com/watch?v=xLdO-QAudk0>" %}

> **Video chapters:** 0:00 Opening the scene & making the basemap transparent | 0:36 Exploring borehole info & documents | 1:08 Viewing the model by soil type | 1:33 Adding borehole location points on the ground | 1:58 Styling markers & choosing a basemap | 3:07 Slicing the 3D model | 4:06 Capturing & saving a slice

Open the published item with **Open in Scene Viewer**.

* **See through the ground:** open **Basemap** and raise **Ground transparency** so the subsurface model is visible in context.

<figure><img src="/files/jSKNXFI2maCMPoE6vWyQ" alt=""><figcaption><p>Ground transparency revealing the model below the surface</p></figcaption></figure>

* **Toggle layers:** in **Layers**, switch soil-type volumes (clay, sand, chalk, limestone...) and boreholes on and off to focus the review. Clicking a document annotation opens its pop-up - including the attached geotechnical report.

<figure><img src="/files/4RmsDyFfzFbihmnHQAmw" alt=""><figcaption><p>Soil-type volume layers with boreholes in Scene Viewer</p></figcaption></figure>

* **Keep location markers on the surface:** set the borehole point layer's elevation placement to **On the ground**, so markers sit on the terrain instead of inside the model.

<figure><img src="/files/0XmlfFabsGObwu7HhKz6" alt=""><figcaption><p>Elevation placement options for the borehole points layer</p></figcaption></figure>

* **Style the markers:** open **Layer Style** for the borehole points and use the **3D Object** drawing style with a distinct marker color and size, so boreholes are easy to identify against any basemap.

<figure><img src="/files/RPiigNz6q9zbNrqsIlYr" alt=""><figcaption><p>3D Object drawing style for the borehole points</p></figcaption></figure>

* **Pick an informative basemap:** open **Basemap** and choose a map with stronger geographic context (imagery, streets, topographic...) for the final review - then turn the model back on to see the subsurface against its surroundings.

<figure><img src="/files/frS7oGY5l9IXJdo7daah" alt=""><figcaption><p>Choosing a basemap with more geographic context</p></figcaption></figure>

* **Slice the model:** with the **Slice** tool (under Scene tools; hold **Shift** for a vertical slice), cut into the model to inspect subsurface structure and borehole relationships. Adjust the slice angle until the internal features are clearly visible.
* **Capture the view:** open **Slide Manager** and use **Capture slide** to save the current slice view - captured slides are stored with the scene, ready for reporting or the next stakeholder session.

<figure><img src="/files/8F4ih65kQx0m9QW4em3A" alt=""><figcaption><p>A vertical slice through the model, captured as a slide in Slide Manager</p></figcaption></figure>

{% hint style="info" %}
**Off the shelf.** Everything in this section is standard Esri **Scene Viewer** functionality - no GeoDin®-specific setup or add-in is needed once the scene is published. Esri's Scene Viewer documentation covers every control here in full depth.
{% endhint %}

***

{% hint style="info" %}
🌐 **Try it live:** a public demo scene produced with this workflow is available at [arcg.is/0rD1OL3](https://arcg.is/0rD1OL3) - open it in Scene Viewer and explore the volumes, annotations, and Slice tool without setting anything up.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.geodin.com/geodin-ground/workflows-and-integrations/arcgis-integration/arcgis-web-scene.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
