ArcGIS Online

What's New in Scene Viewer (December 2020)

We’ve heard a lot of feedback from Scene Viewer users wishing to create experiences that evolve with a constantly changing system of record. This release for Scene Viewer introduces a new workflow to update attributes with scene layers with associated feature layers, so users will be able to see changes in symbology without having to update the scene layer cache.  This Scene Viewer release also addresses better experiences with navigation, searching and visual quality with transparency.  With this release, users will be able to get to where they need to be, find what they’re looking for and better see what’s behind transparent objects.

Attribute editing for scene layers with associated feature layers

Scene Layers and the I3S specification have fundamentally changed how 3D GIS data is performantly streamed over the web.  Whether depicting realistic buildings with 3D Objects, an entire US State’s lidar data or large integrated mesh with draped data, the experiences available today would not be possible without scene layers.  In our previous release, Scene Viewer supports more performant point scene layers, and will continue to be performance improvements to scene layers and the I3S specification.

Scene Layers do, however, have one issue for users that are constantly updating features for a live picture of their 3D data:  they’re cached features that would need to be rebuilt to show the changes.  We’ve recently introduced the ability to do partial rebuilds on a scene layer with associated feature layer, which reduced the need to rebuild an entire scene layer to see changes.

With this release, scene layers now refer to the associated feature layer for attribute information.  This means that attributes can be edited on the feature layer, and those changes will be immediately reflected in pop ups and scene layer symbology without needing to rebuild the cache.  This helps in use cases where, for example, a real estate company wants to quickly update the status of their available properties for a 3D web application that the sales team uses to discuss with clients.  The GIS professional can now use ArcGIS Pro to make quick attribute and symbology changes that are reflected in a scene and 3D web application shared with the larger group.  Alternatively, administrative staff can make quick changes to attributes in a web application just as well. This workflow retains the performance of a scene layer with the ability to update feature layer attributes and symbology on the fly.

There are other useful benefits to this workflow.  Customized pop ups can be configured for scene layers on the associated feature layer! In the associated feature layer’s visualization tab, users can author and save pop ups that will now be referred to when a user click on a feature in the scene layer.  These pop ups utilize charting, images, and arcade scripting to best communicate information.

Pop ups on 3D Object Scene Layer
The associated feature layer is capable of delivering attribute editing and pop ups.

For the scene layer to respond to attribute changes in the feature layer, those users must also have access to that editable feature layer.  This can be potentially dangerous, as this enables editing for more people than intended.  To mitigate the risk of unintended access to editable data, ArcGIS Online offers editor tracking which limits editing to the owner of the feature layer.  Using the following workflow, users can share the scene layer with associated feature layer widely without exposing the feature layer to unintended editors.

Preparing associated feature layer for single-user editing

To make the editable feature layer available for public consumption (for immediate attribute updates and configurable pop ups), editor tracking must be enabled at the point of publishing.  Follow these steps:

  1. Right-click the multipatch or point layer to be published. Mouse to “Sharing…> Share as Web Layer.”
  2. Under the General Tab, fill out Name, Summary and Tags (these are required).
  3. Under Layer Type, ensure that the box next to Feature is checked. This setting is to publish the associated feature layer.
  4. Set Sharing with Groups or Everyone as appropriate. See this best practices document if more information is needed.
  5. Click the Configuration tab and click the second icon for associated feature layer properties.
  6. Check “Enable editing and allow editors to: Add update and delete features”
  7. Check “Preserve editor tracking info”
Share as web layer configuration
Configuring associated feature layer for editor tracking information.

8.  Publish the layer.

9.  Navigate to the recently published feature layer in ArcGIS Online.

10.  If the layer is shared publicly, navigate to the Settings Tab, and check to enable “Public Data Collection.”

11.  Under the feature layer’s Setting Tab, scroll to “Editing” and check “Keep track of who created and last updated features.”

12.  Scroll to “What features can editors edit?” and select “Editors can only edit their own features (requires tracking).

13.  Click “Save.”

The publisher is now the user enabled to edit these features.  As a reminder, share the scene layer and the associated feature layers with the same sharing properties to enable the benefits of the associated feature layer.

Context-aware navigation

Interactive zooming, panning and rotating in underground scenes or viewpoints with large tilt has greatly improved. The camera always moves relative to an area of interest, which used to be determined by the exact cursor position. This has caused navigation to jump when the input device happened to point at the horizon or simply the background for scenes with no visible ground.

A new context-aware navigation takes visible objects into account to better predict the area of interest. Users will notice a steadier navigation experience, especially when moving around and towards data visualizing subsurface pipelines and earthquakes for example, but also thin structures such as vegetation or power lines made up of point cloud data.  Try navigating in this scene below.  You no longer have to right-click exactly on features to rotate the camera view.

Transparency visual improvements

Rendering overlapping transparent features in an environment with strict performance requirements and limited capabilities such as the web is challenging. The previous approach assured that the front-most transparent surface and any opaque features behind are always rendered. Other transparent geometries in the back were selectively visible – depending on the camera position. This also meant that changing the camera caused such covered geometries to flicker.

By applying order-independent transparency (OIT) Scene Viewer now renders all transparent objects independently of the camera. This is useful when visualizing large volumetric symbology covering other transparent features. Scenes with semi-transparent 3D WebStyle or firefly symbology also benefit from the transparency improvements.

Transparency improvements
Order-independent transparency enables visualization of transparent objects behind other transparent objects.

Building scene layer search

Users can search for features in building scene layers. Scene Viewer queries the associated feature layer in a building scene layer, allowing users to search for individual features of BIM (Building Information Modeling) data.  Making this data searchable is not unlike configuring search capabilities for other feature layers, but the building scene layer’s associated feature layer has several layers within it that can be configured for searching.  Keep in mind, this requires the building scene layer’s associated feature layer also be shared the same way as the building scene layer.

Building Scene Layer Search functionality is configured by BIM element.

Support for custom coordinate systems

One more improvement that will help users meet specific requirements for their projects:  Scene Viewer now supports custom coordinate system.  Local scenes can now load and visualize more datasets by supporting additional custom coordinate systems defined by a Well-Known Text (WKT) string.  Users can create and utilize custom coordinate systems that refer to a Well-Known Text string, which is essentially a projection file (.prj) that defines the necessary parameters of a coordinate system.

WKT Details
Scene Viewer supports scenes published with a WKT-based custom coordinate system.

ArcGIS Pro already supports coordinate systems with a WKT, so you can specify a coordinate system in ArcGIS Pro and publish scenes using that coordinate system.  Cached layers and basemaps in a scene must have the same spatial reference.

These improvements are intended to help users produce 3D experiences that reflect changes in your system of record that are complimented by the performance of scene layers.  Context-aware navigation enables enjoyable experiences for a wider variety of data and locations, while transparency improvements ensure that users can better incorporate transparency into their design.  Building Scene Layer searching expands the potential for workflows for BIM-based deliverables, and support for WKT supports requirements of various user requirements for custom coordinate systems.


About the authors

Philip is the 3D Web Experience Product Manager at Esri, working to understand customer requirements and apply forward-looking perspective for how we solve problems together with 3D GIS. Having served as an ecologist, crime analyst, GIS Supervisor and CIO, Philip is a 20 year veteran of leveraging GIS to create daily efficiencies and develop long term vision. Philip makes music, reconditions old VW's and plays with his daughters in his not-so-quiet time.


Developer Evangelist at the Esri R&D Center Zürich, creating 3D web apps using the ArcGIS API for JavaScript.


Leave a Reply

Please Login to comment

Next Article

ArcGIS Hub says goodbye to Internet Explorer and Edge Legacy

Read this article