GET RESULTS INTO THE RIGHT HANDS

A deliverable should open the next door.

Plan the handoff as carefully as the collection. Deliver useful files, prepare GIS connections and equip field teams with data they can take to the site.

Project releasesGIS handoffOffline dataAccess control

FEATURE / 05

Data distribution

  • Project deliverables
  • Controlled release links
  • Originals and derivatives
  • GIS service workflows

Platform overview →

CAPABILITIES

Different audiences. Deliberate delivery.

An analyst may need source data, a client may need a release package and a field crew may need a map. Choose the delivery method around that need.

Project deliverables

The private workspace pilot organizes uploaded files and immutable ZIP releases around a project and its authorized recipients.

Controlled release links

Pilot release links require sign-in and current download permission. An email address or category label alone does not grant access.

Originals and derivatives

Keep original collections distinct from processed outputs so teams understand what they are reviewing or downloading.

GIS service workflows

The broader engine exposes configured OGC and Esri-compatible services. Confirm the client, data type and authentication profile for each connection.

Open-format handoffs

Select practical raster, vector, point-cloud and scene formats for the receiving system instead of making every user adopt the same tool.

Field-ready data

Use Field Sentinel's supported offline formats and preparation workflows to bring maps and reference data beyond reliable coverage.

THE WORKFLOW

A clear path through the work.

Select

01

Identify the audience and required outputs.

Package

02

Prepare a clear, versioned handoff.

Authorize

03

Apply the access appropriate to that audience.

Use

04

Open the data in GIS, review or field workflows.

THE RESULT

Make the handoff part of the project.

Give the receiving team a clear description of the contents, coordinate system, collection and intended use. Good delivery reduces ambiguity about which result should be used next.

WHAT YOUR TEAM TAKES FORWARD

  • Project-oriented file and release organization
  • A choice of connected and offline workflows
  • Delivery planning for analysts, customers and field crews

AVAILABILITY & WORKFLOW SCOPE

Private workspace delivery is a pilot capability. Uploaded files are not automatically validated as native geospatial formats. Broad service endpoints in the shared engine are separate from tenant-qualified cloud delivery.

QUESTIONS, ANSWERED

A few useful details.

Are release links public?

The private deliverables pilot uses authenticated links with fresh permission checks. A link alone is not authorization to download.

Does uploading a model make it a hosted scene?

No. File delivery and hosted geospatial publication are different workflows. Hosting requires a supported, validated publication profile.

BRING YOUR NEXT PROJECT

Let’s connect your workflow.

Start with a collection, an operational challenge or a deliverable. We’ll help map the path from capture to a useful result.