What this tool launches
Use this field validation launcher when reviewed image-derived outputs need real-world checks. It opens the signed-in RasterForge field workspace where you can create project-backed campaigns, upload standalone WGS84 GeoJSON, capture point observations, review answers, and export field packages.
This page is intentionally only a launcher and explainer. The live field validation workflow remains in the RasterForge app because it needs account access, workspace data, D1-backed campaigns, mobile geolocation permissions, offline capture, and field-specific map behavior.
When field validation fits
Field validation is useful after segmentation review, not before the imagery workflow has a candidate output. Start with Review when the source is a RasterForge project, then open field validation to copy reviewed masters or layer outputs into a field campaign snapshot.
| Source | Use field validation when |
|---|---|
| Reviewed RasterForge project | The team needs to check selected masks, boundaries, or objects outside |
| Standalone GeoJSON | The team has WGS84 features from another GIS or model workflow |
| Point-only observations | The team needs GPS observations without a predefined feature layer |
For product steps, read Field validation campaigns and Review outputs before GIS handoff.
Good checks before a campaign
- Use GeoJSON Validator before standalone imports.
- Confirm reviewed masters are intentional before creating a project-backed campaign.
- Keep form questions short enough for mobile capture.
- Treat GPS accuracy and observation notes as part of the evidence, not as decoration.
- Export and archive field packages when a campaign closes.
Related RasterForge pages
Field validation is especially relevant to satellite image segmentation for environmental monitoring, wetland monitoring image segmentation workflows, and field boundary segmentation software. For source raster setup, use the GeoTIFF Inspector.
FAQ
Does this public page collect GPS data?
No. This page only explains and launches the signed-in RasterForge workflow. GPS positions and observations are handled by the app field routes.
Can field validation replace expert review?
No. It helps organize observations against candidate outputs, but it does not turn image-derived data into regulatory truth by itself.
Can I validate a GeoJSON file that was not created in RasterForge?
Yes, if it is a WGS84 FeatureCollection with supported geometry. Run the GeoJSON validator first, then create a standalone GeoJSON campaign in the app.
Why is field validation listed with browser tools?
The tools hub is the discovery layer for practical checks and adjacent workflows. Field validation belongs here because it helps teams move from reviewed imagery outputs to field observations, even though the live campaign workflow requires a signed-in RasterForge account.