Oracle Spatial Studio is a no-code web tool for accessing the spatial features of Oracle Database. The release of Oracle Spatial Studio 22.1 introduces a variety of valuable new capabilities as summarized here. The Oracle Cloud Marketplace has now been updated with this latest version for new deployments. Please find the listing here. (To upgrade existing deployments, please follow instructions here.) The following walks you through the Marketplace deployment.
Review the prerequisites listed under Usage Instructions, namely 1) if your OCI user is not in the OCI Administrators group, then assign required policies and 2) create Secret(s) in OCI Vault to store passwords.
Once prerequsitises are complete you may Launch Stack to begin the stack wizard.
You may leave defaults, or edit the stack name and description.
Then click Next.
Click Next to continue.
Leave the default resource name prefix, or edit if desired. Select an Availability Domain and then Server Instance (Compute) Shape.
Note: You now have the option to deploy Spatial Studio to flexible shapes (”Flex shapes”) with the ability to customize the number of OCPUs and the amount of memory for your instance. You now also have the option to deploy to Arm-based compute, which has seen growing popularity for Cloud deployments. The minimun recommended Flex memory for Spatial Studio is 4GB.
Scroll down to continue.
You may leave the default HTTPS port and Spatial Studio admin user name or edit if desired. As described in the prerequisites, you must select a Secret to use for the admin password.
Scroll down to continue.
You may leave defaults for network configuration which creates new virtual network for the deployment. You may also select an existing virtual network.
Scroll down to continue.
Browse and select (or copy/paste) your SSH public key..
Scroll down to continue.
On first startup, Oracle Spatial Studio requires connection to an Oracle Database for its metadata repository. The Oracle Spatial Studio deployment process on the Cloud Marketplace now provides the following options for metadata repository configuration:
Select your preferred strategy for Spatial Studio's metadata reopository connection. If creating a new Autonomous Data Warehouse or using an existing Autonomous Data Warehouse, you will need to select a Secret for the database user's password.
Click Next to continue.
Review the summary of your stack configuration.
Scroll to the bottom and check Run Apply in order to automatically run the stack (i.e., perform the deployment) after you click Create..
Click Create to create and apply the stack.
You will be navigated to the Job Details page for your stack Apply job. Log content will begin to appear after roughly 1 minute, and deployment will complete in roughly 5 minutes. When State shows Succeeded your job is done. If State shows Failed then the log will contain the cause, such as lack of resource quota in your account.
Scroll down to the bottom of the log for important details:
You may also click on the Application Information tab which provides a button to open your Spatial Studio instance aliong with other deployment info. As noted in Comments, wait 2-3 minutes after Apply job completion to access your Spatial Studio instance.
After waiting 2-3 minutes following stack Apply job completion, click the button to Open Spatal Studio or navigate to the instance URL shown in the log. The deployment is pre-configured with a self-signed HTTPS certificate, so you will see a browser security warning. Accept and proceed to the site.
Log in using the Spatial Studio administrator user name (default is admin unless changed in the stack wizard) and password (password associated with the Secret used in the stack wizard).
We hope you enjoy the new features of Spatial Studio 22.1!
Some resources to learn more about Spatial Studio:
David Lapp is a Senior Principal Product Manager at Oracle Corporation. His responsibilities include strategy and planning for Oracle's Spatial and Graph technologies and cloud services, and their use across the Oracle Cloud including machine learning and analytics. Prior to his current role in product management, David spent nearly 10 years in technical pre-sales covering analytics and spatial technology for the North American Public Sector. David is a graduate of the University of Washington.
Previous Post