Oracle Spatial Studio Downloads

Oracle Spatial Studio v19.2.0 Release Notes

23 October 2019

Feature Enhancements

General speed up of database queries and rendering of vector data.

Overhauled file upload UI to allow zipped files and a mix of different types in one upload.

Added a new JVM parameter -Doracle.sgtech.config for specifying the absolute file path of the sgtech_config.json file. Note that the containing folder of the specified sgtech_config.json file is now considered the "working folder" of Spatial Studio. The working folder is used to store all temporary files and logs generated during the Studio runtime.

Logs files are now stored under an independent folder for each node of a WebLogic Server cluster.

Added an option to the dataset properties dialog so that (advanced) users can disable or customize the automatic "feature sampling" that happens when displaying a dataset with large amount of records.

Added support for "clustering" style when displaying point data set on a map visualization.

When creating a new Project, a map visualization is automatically added to the project.

Published projects have a Copy URL button for easier sharing.

The Spatial Analysis dialog has a new operator to support attribute-based filtering.

Quick Start encrypts Spatial Studio user passwords by default. See the README that comes with Quick Start for more details.

One or more datasets can be added to a new or existing Project from the Data page.

Added support for uploading GeoJSON data files.

When creating a new dataset from a database connection, all the existing tables with Spatial data will be indicated as such.

Newly created datasets with various issues, such as not having a Key column, now have links showing how to fix those issues.

A scale bar and map zoom control can be added to a map visualization.

A user will no longer lose work he has done in an active project even if his current session timed out and the active project wasn’t saved.

Spatial Studio checks that its metadata repository schema has Oracle Spatial and Graph or Oracle Locator installed and has the necessary quota.

Enhanced handling of feature selection and de-selection across multiple visualizations. For instance, when selections are cleared in a visualization, only the selected features from the same dataset will be cleared in other visualizations, leaving other datasets' selected features intact.

In the config file sgtech_config.json, for the Studio repository schema connection, a user can use a managed JavaEE data source by specifying its JNDI name.

Improved validation logic when creating a new connection.

If Clear Address Geocode is invoked on a dataset with a running Geocode job, that job will now be aborted.

Bug Fixes

• Fixed various UI layout related issues.
• Fixed various issues related to dataset geocoding and post-geocoding result analysis.
• Fixed an issue where a non-admin user was able to create/specify the metadata repository schema connection details (in a new Spatial Studio instance).
• Fixed an issue that prevented vector tiles from being pre-generated on datasets.
• Fixed various scenarios where excessive use of JDBC connections may occur during map visualization.
• Fixed an issue where sometimes a dataset's statistics gathering status does not change even after a forced "Update Stats" operation.
• View-based and spatial analysis datasets have more precise statistics.
• Fixed an issue where 3D geometries may fail to be rendered (with no vector tiles generated).
• Fixed an issue so the Studio's metadata tables can be updated even in a compressed Oracle Database.
• Fixed an issue where when creating a new dataset, the list of existing database tables may include secondary and temporary tables.
• Fixed an issue where the option to not create an Spatial index is not honored when uploading a shapefile.
• Fixed various issues related to using Function Based indexes, as well as an issue where existing (user-created) Function Based indexes were not honored on longitude/latitude columns.
• Fixed an issue where the Spatial Analysis operator dialog sometimes opened twice.
• Fixed an issue where a spreadsheet with more than 20,000 rows cannot be uploaded.
• Fixed an issue where records selected using the Circle selection tool on a map visualization cannot be used in an analysis.
• Fixed an issue where the Distance measuring tool sometimes displays incorrect result.

Oracle Spatial Studio v19.1.0 Release Notes

1 July 2019

Things you need to know first

This is the very first release of Oracle Spatial Studio, a self-service geospatial data visualization and analysis tool built on top of the highly performant Oracle Spatial database technologies.

By default, only HTTPS requests are enabled for the Studio. As the Studio application accepts database credentials in a web form, this is highly recommended. If the user wants to enable HTTP access, check the config file.

Known Issues

• The Quick Start ships with a randomly generated, self-signed SSL certificate for enabling HTTPS access, as such you will need to add a security exception to your browser for Studio.
• Some Spatial analysis operators such as Buffer are not available when a target dataset resides in an Autonomous Database.
• For some uploaded shapefiles, Spatial Studio may fail to automatically match the best or even correct SRID. In such cases you may need to examine the .prj file that came with your shapefile and consult Oracle Spatial's Spatial Reference systems to figure out the best SRID to use for your shapefile geometries, then enter it manually in the upload screen.
• When you have more data than can be displayed on the map, Spatial Studio will automatically optimize the performance by showing only a certain percentage of your geometries on the map. Currently there is no indication on the map to alert you when data sampling has been performed by Spatial Studio. Data sampling typically occurs when you have more than 10k features in a given map tile.
• Visualizations added to a project cannot be re-positioned or resized manually.
• Connection pools and data sources defined in your Java EE container cannot be used to create Spatial Studio connections, including for the repository schema itself.
• UI texts, labels and tooltips are English only.
• Upload spreadsheet might pick wrong datatype (i.e., number instead of text) which the user cannot override. This is due to determination of datatype based on a sampling of the data. To fix this, move a row with a character value in the offending column to the top of the spreadsheet.
• Adding a view-based dataset to an analysis will show ‘Dataset SRID unknown’ warning. This can be ignored.
• Studio may stall in responding with as log message “All connections in the universal connection pool are in use.” Refer to doc to configure connection pools.