NgRx Store - Latest

Spectrum Spatial Analyst Extensibility Guide

Product type
Software
Portfolio
Locate
Product family
Spectrum™ software
Product
Spectrum™ software > Spatial > Spectrum Spatial Analyst
Version
Latest
ft:locale
en-US
Product name
Spectrum Spatial Analyst
ft:title
Spectrum Spatial Analyst Extensibility Guide
Copyright
2025
First publish date
2007
ft:lastEdition
2025-10-28
ft:lastPublication
2025-10-28T15:15:05.535000
L1_Product_Gateway
L2_Product_Segment
L3_Product_Brand
L4_Investment_Segment
L5_Product_Group
L6_Product_Name

NgRx store is the base architecture for the Spectrum Spatial Analyst Extensibility Platform. It is the primary mechanism to consume the resources of the Spectrum Spatial Analyst Extensibility Platform in third-party components via the use of store actions and selectors.

For example, if you want to listen to the map click event in your custom component you will use a selector to achieve this. Similarly, if you want to add a new layer to the map from your custom component you will dispatch an action for this. For the store to be used in a component you need to add it as a parameter in the component’s constructor. We have provided various examples to showcase how it can be used.

The real power of the Spectrum Spatial Analyst Extensibility Platform comes from re-using many services, components, and third-party libraries that come out of the box with Spectrum Spatial Analyst. For example, you can utilize the extensive set of services the platform exposes for the query features by SQL, at an XY or within a user-drawn region, rather than coding this into your component. There are also multiple sets of utilities exposed via the Spectrum Spatial Analyst Extensibility Platform. A complete list of these can be found in the API docs shipped with Spectrum Spatial Analyst installation.

Though API docs list all of the functionality in Spectrum Spatial Analyst components, developers are advised to only use the public APIs or components of the Spectrum Spatial Analyst extensibility platform. This is necessary to maintain backward compatibility. Backward compatibility is not guaranteed when using private API, which is subject to change without notice.