Referencing Third-party Libraries - Spectrum_Spatial_Analyst - 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

The Spectrum Spatial Analyst Extensibility Platform envisages cases where new components may need to reference third-party external libraries. These libraries can be either Angular or normal JavaScript libraries. The Spectrum Spatial Analyst Extensibility Platform facilitates the on-boarding of such libraries with ease. To use new libraries in the component, follow the steps given below. Libraries can be references from the file system of the Spectrum Spatial Analyst server or can be referenced from a hosting site/CDN. The mechanism for registering the library is the same in both cases. There are certain restrictions that the Spectrum Spatial Analyst Extensibility Platform has while embedding a new library.

  1. Only one version of a new library needs to be embedded.
  2. If the library is already available with a certain version, one cannot embed a new version of that library. We provide a list of libraries available out-of-the-box within Spectrum Spatial Analyst via the module config validator page.
  3. Checking for license terms, vulnerability, and certification of new libraries (libs) in the Spectrum Spatial Analyst Extensibility Platform is the responsibility of the component developer.
  4. If someone intentionally violates point 1 and more than one version of the same library is added to the Spectrum Spatial Analyst Extensibility Platform, it cannot guarantee deterministic behavior.
  5. If one module is embedding a specific version of a library, then another module cannot embed another version of the same library.
  6. If one module is embedding a version of a library, that library can be used across multiple modules/components without repeating the same library in the other modules.