|V1031060-01.zip contains a self-contained, easy to deploy Quick Start of Oracle Spatial Studio||184.108.40.206.0|
|V1031059-01.zip contains a Java EE Enterprise Application aRchive (EAR) file for WebLogic Server||220.127.116.11.0|
Version 22.2 – August 29, 2022
Revamped the UI and component layout in the Active Project page, to provide a more streamlined user experience, and more screen real estate for the visualizations.
Spatial Studio's user interface now supports 9 additional languages: German, Spanish, French, Italian, Japanese, Korean, Portuguese, simplified and traditional Chinese. User will be able to switch to one of these languages during the login step. If Studio is configured to use IDCS as its login provider then the locale of the user's IDCS profile will automatically determine Studio's language upon logging in.
The nearest neighbor spatial analysis now has a new form (SDO_NN_V2) to address some accuracy and performance issues in the original SDO_NN analysis. Both forms will exist in Spatial Studio but new nearest neighbor analyses can only be created using the new form.
Reverse Geocoding has been enhanced with an option to ignore unnamed streets (alleys, entranceways) and use only named streets when deriving address information from the nearest street segment.
Improved large Shapefile upload performance.
Improved Shapefile charset support during upload. Studio will now auto-detect the charset included in the .cpg file, or the header of the .dbf file. Contents of the Shapefile can now be previewed in its native charset.
When uploading a Shapefile with a custom GEOGCS (Geographic Coordinate System) projection file, Studio will now assign a best-matched geodetic SRID from the target Spatial database, instead of defaulting to EPSG:4326. User can still override the auto matched SRID.
Improved Tasks/jobs feedback and status reporting, with the UI for the Tasks page also significantly improved.
Most types of long running tasks (except longitude/latitude index creation) can now be terminated by the user if needed.
When generating a new access token, user can now limit its scope to allow only streaming datasets' contents. This promotes better integration with 3rd party applications that only need the access to a certain Studio dataset or analysis's GeoJSON or vector tile data.
When performing a spatial analysis on a dataset with indexed longitude/latitude columns, the result analysis dataset will now use a SDO_GEOMETRY type column to represent the original longitude and latitude NUMBER-typed columns. This provides better stability in chaining more analyses on top of each other..
Oracle Database 12.2 and 18c releases are desupported.