About the Compute Environment in Spatial Studio

You can provision a dedicated compute environment to run Spatial Studio.

By default, Spatial Studio runs using resources that are automatically allocated through the Oracle Cloud Infrastructure (OCI) Control Plane on your Autonomous AI Database instance. You can perform most of the typical activities such as uploading a shapefile (less than 50 MB), geocoding a small dataset, or creating map visualizations, using these shared resources. However, they may not be sufficient in certain scenarios, such as the following:

• Uploading images for GeoRaster datasets
• Uploading large files exceeding 50MB
• Geocoding tables with more than 500 records
• Using the Spatial AI labeling function

In such cases, Spatial Studio can be attached to a newly created compute environment with greater compute power and memory. The compute environment is shared by all users of your Autonomous Database Serverless instance. Any user can create the compute environment; however, only the Spatial Studio administrator can detach it. Detaching the compute environment terminates all active user sessions connected to that environment.

Note:

You are billed by the hour when running Spatial Studio on a newly created compute environment. For instance, if you use the compute environment for only 15 minutes and then terminate it, you will still be charged for a full hour.

The status in the application header (top right) indicates whether Spatial Studio is attached to a compute environment. The compute environment can be available in one of the following states:

• Detached (default): Spatial Studio is not attached to a compute environment.
• Attached: Spatial Studio is attached to a compute environment.
• Attaching: Spatial Studio is in the process of attaching to a compute environment.