Create field validation campaigns

Field validation turns reviewed outputs or field observations into a signed-in workspace workflow. Use it when a project needs real-world checks, mobile capture, observation review, and field-package export.

The public tools page can help people discover field validation, but the live workflow stays in the app at /field because it uses workspace data, authenticated APIs, geolocation permissions, IndexedDB offline queueing, and a mobile map route.

Campaign sources

RasterForge supports three campaign modes:

  • Project campaigns copy reviewed masters or project layer GeoJSON into a field campaign snapshot.
  • GeoJSON campaigns import a standalone WGS84 FeatureCollection from another GIS or model workflow.
  • Point campaigns capture observations without a predefined feature layer.

Create a campaign

  1. Open Field
    Go to the signed-in Field workspace from the app or from the field validation tool launcher.
  2. Choose a source
    Pick Project, GeoJSON, or Points depending on what the field team needs to validate.
  3. Choose a form
    Use the default quick validation form or select a reusable form from the form library.
  4. Import features
    For projects, choose reviewed masters or layers. For GeoJSON, upload a WGS84 FeatureCollection and choose the label field.
  5. Open mobile validation
    Use the mobile validation route for GPS-centered capture, offline queueing, and feature navigation.
  6. Review and export
    Review observations in the dashboard, then export the campaign package when the field round closes.

GeoJSON readiness

Standalone GeoJSON campaigns require WGS84 longitude/latitude coordinates and supported geometry. Use the public GeoJSON Validator before upload when the file came from another tool.

For field campaigns, RasterForge copies supported feature geometry, primitive properties, labels, bounds, and centroids into a campaign snapshot. Unsupported geometry is skipped with an import summary so the campaign is stable while field work is underway.

Mobile capture expectations

The mobile validation route is designed for phones and tablets. It can show nearby campaign features, current GPS state, heading diagnostics, sync status, and a collapsible task sheet. When local storage is available, observations can queue offline and sync later.

Watch GPS accuracy before saving observations. Low accuracy may still be useful, but the observation should be interpreted with that uncertainty.