Stacks

1 min read

A Stack is a named bundle of insights you run together. Instead of ticking the same eight indices every time you analyze a new area, save them once as a Stack and apply them in a single click. Stacks are the muscle memory of a repeatable exploration workflow.

Creating a Stack #

The quickest way is straight from a Visual: in the Insights step, select the insights you want and choose Save as Stack. The dialog asks for:

  • Stack name and an optional description.
  • Confirmation of the selected insights in the bundle.

The platform automatically works out the instruments that support the whole stack — only instruments that can run every insight in it — so a Stack always knows where it can be applied.

📷 Screenshot pending — the Save-as-Stack dialog with a name and its selected insights.

Using and managing Stacks #

Open the Stacks panel in the left rail to see your saved stacks. Each card shows the stack’s name, description and the insights it contains. Selecting a Stack in a Visual applies all of its insights at once, exactly as if you’d ticked them individually.

The Stack Details window shows the full bundle: total insights, the instruments it’s compatible with, and each insight (you can open any of them in Insight Details from here).

Best practices #

  • Build stacks around a question, not a mineral list: an “iron-oxide alteration” stack, a “clay + carbonate” stack, a “vegetation-masked geology” stack.
  • Keep a stack’s insights on the same instrument family so it stays broadly applicable — a stack mixing hyperspectral-only insights with multispectral ones can only run where all of them work.
  • Name stacks operationally so the next person on the project knows what they’re for.
Updated on July 27, 2026