Your search did not match any results.
We suggest you try the following to help find what you’re looking for:
Version 21.1 – April (current date), 2021
Improved Time Slider visualization performance to better handle a dataset with many data points.
Added two new file formats for data upload: CSV and KML files. For KML files, currently Studio supports geoplace features found in top level folders only.
Map visualization now supports Place Search, where a user can enter a place name or address to re-center the map.
Spatial Analysis no longer creates a database view by default. In the past, when a user created a new spatial analysis dataset, a new view was also created in the database schema. This is no longer the case. Instead, Spatial Studio will record only the information and parameters used to build the spatial analysis as part of the new dataset. This declutters the user's schema, and it also paves the way for future enhancements in this area.
Improved Oracle Spatial SRID (Spatial Reference ID) matching accuracy when uploading Shapefiles.
Dataset page now keeps the current column sorting order when adding or removing datasets
Fixed an issue where sometimes a dataset without a geometry column can be dragged and dropped on a Map visualization.
Fixed various UI layout issues and misalignments in the Project page.
Fixed an issue where sometimes the Table visualization crashes.
Version 20.1.1 - February 2, 2021
Fixed an issue where sometimes the Spatial Studio connection cannot be used for uploading new datasets.
Updated several third party libraries.
Easier dataset creation via uploading, where more than one dataset file and type can be uploaded in one zip file.
More than one dataset can now be dragged and dropped onto a map visualization in a single action.
Visualization of GeoRaster data, including Virtual Mosaic.
Visualization of true 3D Tiles tile set. A new type of Visualization has been introduced to support 3D point cloud and city models.
Custom basemap support. A custom basemap can be hosted locally or on a 3rd party tile server.
Improved map data visualization performance, especially for large datasets.
When a dataset in a map visualization contains Date Type column, a time slider can be added to the map visualization to view historic data interactively.
Ability to create (database) synonyms for datasets so the name of a spatial analysis result can be changed.
A new category of spatial operations has been added: Analytics. An easy-to-use user interface ensures a simple and optimal way of performing common spatial analyses such as Summarize within Distance, Summarize by Region, and Nearest Neighbor.
A Project can be exported, including all contents of the datasets. The exported Project can be imported into a different Spatial Studio instance where all datasets and visualizations will be restored.
Public Published Projects support, where all the datasets are public. A Public Published Project can be further customized to show minimal amount of Spatial Studio UI elements for a cleaner, more easily embeddable map visualization.
A Published Project can now update itself from the source project.
Better support for Date type columns in datasets, including client-side filtering by dates on a map visualization.
Public dataset support. Public dataset contents can be accessed through REST endpoints by anyone, without logging into Spatial Studio first.
Spatial Studio's application banner can now be customized to suite an organization's needs.
Validation of geometries stored in spatial features of Oracle Database.
Improved shapefile SRS detection and Spatial SRID auto-matching.
Precaching of vector tiles of a dataset can now be based on a custom bounding box.
Lat/Lon indexes can now be created on top of float or double typed columns.
Better support for cluster deployment, with automatic synchronization of cached metadata across cluster nodes.
A JWT Access Token can now be generated and used to invoke Studio's RESTful endpoints for accessing and processing a user's resources. This means automated spatial analysis can occur, without the need for user involvement.
Spatial Studio now adopts a strict content security policy, where all third party domains (such as that of a custom basemap), must be explicitly listed in Spatial Studio's safe domain list.
Major revamp of every aspect of the user interface for a cleaner and more streamlined look. datasets.