Release Notes for Location Intelligence

You can now add KML and ZipShaped files into Location Intelligence.

You can now add layers to bring datasets into Location Intelligence.

You can now search CSV, Parquet, and Snowflake datasets.

You can now create point layers and spatialize the data from the Latitude and Longitude columns in CSV, Parquet, and Snowflake datasets.

Inputs with projection OGC:CRS84 now load correctly in Location Intelligence.

Layers with null geometries now load correctly in Location Intelligence.

You can now run the analysis in workspaces. You need to use the users folder output home directory configured in your storage preferences.

You can now create regions around geometries. To do so, go to New Analysis and select Trade Area.

You can now create a proportional symbol map. To do so, style the size of a point layer's radius by a numeric column.

You can style by Radius and Color to create a multivariate map.

Support for Snowflake inputs with Geometry or Geography columns.

Ability to change the radius of point layers.

Add Data button has been renamed to Add Layers.

The default layer name is updated to reflect the column name for the source data.

Duplicate layer names will auto-increment on input. Auto-increment is no longer global.

You can now use run an analysis on an analysis layer.

Color ramps based on a selected attribute can be consistently applied to numeric fields. Field types are defined by the schema of the source data.

Adding large datasets may result in a timeout error while the app generates map tiles for the data.

When a dataset loads into Location Intelligence, the default map layer name will auto-increment (2), (3), (4).

The duplicative map layer names are based across all the projects the user has in Location Intelligence.

Using an analysis layer to run a second analysis returns an error.

Color ramps based on a selected attribute are not consistently applied to map layers.