Fabric Studio · Invite-Only Beta
Geospatial workflows weren't built to be portable. Studio is the visual workspace where you compose a Pattern — a portable representation of a pipeline, separated from the tools that execute it — and submit it to Fabric Engine. Build visually, run anywhere, walk away with every byte.
We onboard in small cohorts as capacity allows — typically 2–5 new users per week.
The problem
Every mission starts from zero. Analysts rebuild the same ingestion and harmonization plumbing across every project because the last pipeline lives in a notebook that only ran once, on one machine, with one analyst's assumptions baked in.
Studio inverts that. You compose the pipeline visually, and the workspace writes a Pattern — a portable description of the whole workflow, separated from the tools that run it. The Pattern travels with you to the next mission, the next team, the next deployment. You keep your judgment; Fabric removes the plumbing.
The interface
A collapsible tree of the processing steps available, grouped by stage as folder groups. Toggle steps on and off; each shows an active count, so your workflow takes shape as you build. The left edge highlights to indicate the current selection.
Click any step to load its configuration form in the center column. Breadcrumb navigation shows your position in the workflow. Contextual info boxes — tips, success confirmations, and amber warnings — surface guardrail feedback as you configure. Previous / Next navigation moves through the sequence without losing state.
A vertical map of your workflow that updates in real time as steps are toggled on and off. Steps that can run in parallel render side-by-side, and clicking any node loads its configuration. You see the whole pipeline take shape before you run it.
The workflow
Start from a blank workspace and build it up step by step, or open one of the example Patterns for fire and wildfire, vegetation analysis, terrain, flood response, or general-purpose workflows. When Iris is available, you will also be able to describe your goal in plain language and get a generated starting Pattern.
Your starting Pattern loads into a visual workspace with steps pre-configured. Every configuration is editable: adjust, extend, or strip back as needed. The Process Map on the right updates in real time as you make changes.
Enter a location name and Studio geocodes it to a bounding box automatically, or pull a country, state, or county boundary from OpenStreetMap. Your AOI scopes every step downstream.
Turn on the sources you need: Sentinel-2, Sentinel-1 SAR, Landsat, SRTM, Copernicus DEM, OpenStreetMap, ERA5, and more. Set date ranges and cloud-cover thresholds per source. The Process Map updates with each change.
Clip, reproject, resample, align, and mosaic your sources so they line up. Studio's guardrails watch your configuration and flag mismatches — like mixed resolutions or projections — recommending the fix inline, before you run.
Add standard spectral indices (NDVI, NDWI, NBR, and more), write custom band math, run harmonized vegetation analysis across multi-sensor inputs, or detect floods from SAR. The band picker only offers indices your selected sources can actually support.
Review the workflow in the Process Map. When ready, click Run. Studio submits to Engine and opens the live execution panel, where progress and logs stream in real time as each step completes.
Export your Pattern for version control, programmatic execution, or to hand off to a teammate. Analysis-ready outputs — Cloud-Optimized GeoTIFF (COG), GeoJSON, GeoPackage (GPKG), JSON reports, and a W3C PROV provenance manifest — are immediately compatible with ArcGIS, QGIS, Felt, Python, R, and any OGC-compatible tool.
What you keep
Scripts don't travel. Patterns do. Studio preserves the analytical judgment your scripts already encode — band choices, thresholds, composite logic — and replaces the boilerplate around them with a portable, provenance-tracked pipeline. Drop back to code whenever you want: export the Pattern, or run custom expressions inline.
Studio recommends; you decide. Every step is editable, every guardrail is advisory, every configuration is visible in the Process Map before a Pattern is submitted. W3C PROV provenance documents every transformation line-by-line, so you always know exactly what ran and why.
Outputs land in your storage as standard open formats — Cloud-Optimized GeoTIFF (COG), GeoJSON, GeoPackage (GPKG), W3C PROV manifests. No proprietary wrappers, no data tax. If you walk away, you walk away with every byte, every Pattern, every manifest.
Intelligent guardrails
Studio surfaces configuration guidance while you're composing the workflow, before anything is submitted to Engine. These are not post-hoc error messages — they appear inline as you configure.
Studio checks your configuration as you build — flagging mismatched projections, dimensions, or resolutions, and recommending the fix inline. The band picker only offers indices your current sources can support, so you're never wiring incompatible inputs by hand.
The result: a pipeline that works the first time, without learning which preprocessing steps are prerequisites for which analysis tasks.
Spectral indices
Normalized Difference Vegetation Index. Quantifies live green vegetation density — the workhorse index for crop health, drought, and land-cover change.
Normalized Difference Snow Index. Discriminates snow and ice from cloud cover and other bright surfaces.
Water body and flood extent mapping — the standard indices for delineating open water and saturated ground.
Burn severity and fire scar mapping, including change detection between pre- and post-fire acquisition dates.
Normalized Difference Built-up Index. Identifies built-up and impervious surfaces for urban growth and construction monitoring.
Write your own expressions for anything a standard index doesn't cover — from simple ratios to multi-band composites and conditional masks.
Where outputs go
Studio sits in the middle stack: ingestion, harmonization, preprocessing. The deep analysis and cartography happen downstream, in the tools your team already trusts. Fabric is the enabler that delivers analysis-ready data into those environments — not a replacement for them.
A Cloud-Optimized GeoTIFF from Studio loads into QGIS or ArcGIS as easily as any local raster. A GeoPackage opens directly in Felt for collaborative mapping. Python and R read the same outputs via rasterio or terra. The W3C PROV manifest travels with the data, so the provenance story is intact wherever the analysis lands.
FAQ
Studio is in Invite-Only Beta. Fabric Engine, the runtime underneath, is live and processing data today. We'll be honest about whether your use case is one we can support well right now — rather than overpromising and backfilling later.
Cloud-Optimized GeoTIFF (COG) for raster outputs, GeoJSON and GeoPackage (GPKG) for vector outputs, JSON for statistical reports, and a W3C PROV manifest per run. Everything loads directly into ArcGIS, QGIS, Felt, Python, R, or any OGC-compatible tool — no format conversion required.
No. Studio is no-code by default: toggle steps, fill in forms, run. When you need code — custom band math, a bespoke transformation — drop into expression fields or export the Pattern and run it programmatically. Your choice, per workflow.
Geospatial analysts and engineers who have rebuilt an ingestion pipeline more than once and know exactly which hours they want back. We onboard in small cohorts — typically 2–5 new users per week as capacity allows — to keep the feedback loop tight.
Under the hood
Every workflow built in Studio becomes a Pattern that Engine executes. The reproducible runs, analysis-ready guarantees, and full provenance record are Engine features — Studio gives you a visual way to compose them.
Explore Fabric Engine →Also in the platform
Iris Natural-language Pattern generation · In TestingWe onboard in small cohorts as capacity allows. Request an invite and we'll be honest about whether your use case is one we can support today.