Documentation

Everything the studio does, panel by panel.

Lisaris EO Studio turns a boundary on a map into a measurement you can put in front of someone else. This documentation covers every panel in the product: what it does, what each control changes, and how to read what comes back.

If you are new

Work through parts one to six in order. They take you from an empty map to a finished result, and they introduce the three ideas the rest of the product assumes you know: what a validation posture is, what coverage means, and why provenance is printed on every result.

If you have used the studio before and want one specific answer, the sidebar is grouped by task and the search in your browser will find a control by its on-screen name. Controls are named here exactly as they appear on screen.

The parts

PART 01

The shell

Navigation, notifications, and how panels dock.

PART 02

Explore

Search, draw or upload a boundary, then search the archives.

PART 03

Areas

Results, trends, composites and comparisons for one boundary.

PART 04

Analytics catalogue

Methods, postures, availability and plan tiers.

PART 05

Running an analysis

Constellation, scene, layers, and the two standing lanes.

PART 06

Reading a result

Layers, legends, statistics, coverage and the map tools.

PART 07

Comparing two dates

Pairs, thresholds, scene offset and the patch count.

PART 08

Monitoring

Rules, cadences, seasonal comparisons and confounders.

PART 09

Workflows

Nodes, ports, caching and run history.

PART 10

Getting imagery

Imagery requests, the Order Desk and your orders.

PART 11

Sharing with a client

Publishing, engagements and the client portal.

PART 12

Administration

Members, calibration, plans, credits and sessions.

PART 13

Reference

Refusals, glossary and the checks to run before quoting a number.

Conventions

Controls are named as they appear on screen: Draw AOI, Run analysis, Publish to client.
A line such as Explore › Images › Constellations is a location in the interface, read left to right.
Values in monospace are what the product itself prints: layer keys, granule identifiers, thresholds and wavelengths.
A refusal is a case where the studio declines to produce a number. Every refusal names its reason on screen. They are documented because knowing why one happens is faster than working around it. Part thirteen lists all of them.

The one rule worth carrying

Nothing in the studio quotes a figure without also telling you what kind of claim it is. Three lines do that work: the posture on a layer, the coverage on a result, and the provenance printed underneath it. Part four defines postures, part six shows where the other two live, and part thirteen is the reference table for all three.

The API

This documentation covers the studio interface. If you are integrating against the platform rather than using it, the API reference is a separate document with request samples in six languages and a test console. It is linked from Settings › API keys, where you also create the key you will authenticate with.