GIS exports and handoff packages
RasterForge exports are based on selected project review masters. A layer may include a Pixel mask, a GeoJSON vector export, or both depending on the run, layer state, and export settings. The Export page works from the selected image/class scope, so Review should be checked before downloading project handoff files.
GIS download formats
The Export page builds GIS-ready downloads from reviewed master layers.
| Format | Use when | Notes |
|---|---|---|
| GeoPackage | You want a compact project handoff for GIS tools. | Recommended for reviewed project handoff when selected GeoJSON outputs have WGS84 georeferencing. |
| GeoJSON | You want web-friendly vector features or a simple single-cell vector download. | Single-cell per image/class downloads can stay raw GeoJSON; broader packages use reviewed scope and manifest metadata. |
| Shapefile | You need compatibility with older GIS workflows. | Supports Polygon and MultiPolygon features and requires WGS84 georeferenced vector output. |
GeoPackage and Shapefile exports are enabled only when selected reviewed GeoJSON outputs have WGS84 georeferencing. If a cell has no georeferenced GeoJSON, generate or update GeoJSON and confirm image bounds before expecting those formats. GeoJSON can still be useful for a single-cell download even when the broader package is not ready for georeferenced formats.
Export modes
GIS downloads can be organized with the Export page download mode:
- Per image/class files: one output per reviewed image/class cell.
- Merged by class: one output group per class across the selected images.
- Single collection: one combined vector collection for the selected scope.
Use per image/class files when QA needs to trace each output back to an image. Use merged by class for most project handoff workflows. Use a single collection when the downstream tool expects one vector dataset.
Pixel masks and GeoJSON
Pixel masks represent segmented areas as raster outputs. They are useful for raster workflows, visual inspection, and downstream processing where pixel alignment matters. GIS exports can include mask PNGs in the package. Single-cell GeoJSON downloads stay GeoJSON-only.
GeoJSON represents segmented areas as vector features. It is useful for GIS review, object editing, measurement, and integration with vector workflows.
GeoJSON can be generated from a stored mask bundle with postprocess settings such as minimum score, minimum area, maximum area, top K, IoU deduplication, and simplify tolerance. If object edits already exist, updating GeoJSON may create a new layer so the edited state is not overwritten unexpectedly.
Handoff packages and summaries
Project handoff exports use the selected image/class scope:
- Summary PDF: a human-readable project summary, optionally with bounded visuals when a representative preview is available.
- Summary CSV: tabular project and output status for audit, QA, or handoff tracking.
- Review ZIP: reviewed outputs packaged from the current Review selections.
Use All reviewed before download when the handoff should represent the full reviewed project.
Classes and review
Class labels and class groups come from segmentation profile settings or layer metadata. Review selections decide which layer is the master output for an image/class pair. Use Review before exporting project results so the ZIP or GIS package reflects explicit image and class choices.
Composites
Composite layers combine existing layers with union, subtract, intersect, or xor operations in Segment. Review can also create a union-style composite when adding another layer to a selected image/class cell. Composites are useful when the final output is a combination of model runs, but they inherit the quality of their inputs. The default beta limit is eight inputs per composite.
Cache and re-export caveat
Live GeoJSON recalculation depends on stored mask bundles and related artifacts. If required cached model output is no longer available, rerun segmentation or regenerate the needed layer before export.