Changes in this Release for this Guide

New Features for Oracle Spatial Studio Release 26.1.0

• Added support to upload an image that replaces an existing GeoRaster object in a table.

  See Replacing a Raster Image in a GeoRaster Table for more information.

• Added support for creating a 3D scene dataset directly from a 3D tileset URL or CZML URL.

  See Creating a Dataset from 3D Scene Formats for more information.

• Added support to automatically create Spatial Studio datasets on all geometry tables and views found in an Oracle Database connection.

  See Creating Multiple Datasets Automatically from a Connection for more information.

• Added support for resizing and re-positioning visualizations in Active Project page.

  See Multiple Visualizations on a Canvas for more information.

• Added support to highlight the results of a feature search in or near the map viewport.

  See Searching Locations and Features on a Map for more information.

• Added support to select the preferred language for the user interface in Spatial Studio.

  See Setting Preferences in Spatial Studio for more information.

• Added support to view the currently logged-in user and Spatial Studio session details on the Console page.

  See Viewing Session Info for more information.

• Added support to search and find map symbols by name in the map visualization layer settings panel.

  See the images in Applying Predefined Symbols to a Map Layer, Applying Custom Map Symbols to a Map Layer, and Applying an Animated Map Symbol to a Map Layer for more information.

• Added support for deploying Spatial Studio on Apache Tomcat 11.x.

  See Installing Spatial Studio on Apache Tomcat for more information.

• Added support for deploying Spatial Studio on Oracle WebLogic Server 15.x.

  See Installing Spatial Studio on Oracle WebLogic Server for more information.

Upgrading to Spatial Studio 26.1.0

If you are running a Spatial Studio version:

• Earlier than 22.3.0: You must first download and successfully log into Spatial Studio 22.3.0. This is because a new version control mechanism is introduced for the metadata schema in 23.1.0 and Spatial Studio expects any existing metadata schema to already be at the version of Spatial Studio 22.3.0. Then you can upgrade to Spatial Studio 26.1.0.

  Otherwise, Spatial Studio version 26.1.0 will log the following SEVERE error message and abort the startup process.

  !!! Spatial Studio ver. 22.3.0 must be run at least once against your repository schema before upgrading to this version !!!

  See Upgrading to Spatial Studio 22.3.0 for more information.
• 22.3.0 or later: See Upgrading Spatial Studio to upgrade to Spatial Studio 26.1.0.