Public Demo Guide

Troutclub Demo Guide

A quick guide to what is available in the public cyndrio demo, what is intentionally read-only, and how to explore Troutclub end to end.

What this public demo includes

This demo is a read-only cyndrio deployment centered on a single processed site: troutclub. It is meant to show the finished Troutclub workflow, layer outputs, and Beacon experience without opening the full write pipeline yet.

How to use it

  • Start on the create page and run the guided Troutclub sample workflow to simulate an upload and reveal the demo project.
  • Use the homepage to inspect the Troutclub boundary against forecast overlays, fire alerts, and cached coverage.
  • Open Layers Overview to compare the generated 2D and 3D outputs.
  • Enter Beacon for the ops-style workspace with alerts, routes, hazard context, and response assets.

What “Forecast Overlays” means

The homepage forecast status corresponds to the live National Weather Service point forecast pulled for the selected site. cyndrio uses that forecast context to drive the wind vectors, weather timeline, and temperature heatmap around Troutclub.

What is disabled in demo mode

  • Uploading new LAS data
  • Reprocessing the site
  • Saved threshold edits and annotation saves
  • Bulk file downloads
  • Project deletion and other write actions

Why downloads are disabled

For the public demo, the goal is to let users inspect the finished outputs without turning the site into a raw data distribution endpoint. Browser-safe visual layers remain viewable inside cyndrio, and threshold preview is available locally in the browser, but bulk and raw downloads are intentionally blocked in this first release.

What comes next

The next product step is a fuller hosted cyndrio app where authenticated users can move beyond the Troutclub demo and eventually upload and process their own data.