Large Raster Runs¶
Use prepared tiles when the segmentation area is too large or expensive to prepare as one scene.
Large-raster segmentation has two steps:
- build tile directories from source rasters
- run segmentation from those prepared tiles
Build Tiles¶
1 2 3 4 5 6 7 8 9 10 11 12 | |
Each tile directory contains the aligned inputs used by segmentation:
img.tifchm.tifcost.tifseeds.gpkg
tile and overlap are expressed in raster CRS units. For projected data in meters, tile=500.0 creates approximately 500-meter tiles.
Segment Prepared Tiles¶
1 2 3 4 5 6 7 8 9 10 11 12 13 | |
Use this when you trained or received a samstars model bundle.
Segment With Separate Model Files¶
1 2 3 4 5 6 7 8 9 10 11 | |
Use this path when you have a SAM decoder checkpoint and a StarDist model directory instead of a model bundle.
CPU is the supported baseline. Use "cuda" or "mps" only after verifying
the accelerator as described in Installation.
Choosing Tile Settings¶
Use tiles large enough to include useful crown context, but small enough to keep proposal generation stable. Increase overlap when edge effects are visible near tile boundaries.
The outer tile size controls prepared segmentation units. Polygon refinement can also use internal windows through stardist_window_size_m, stardist_window_overlap_m, and stardist_dedup_iou_thr.
Outputs¶
The final polygon output is:
1 | |
Persistent runs also keep tile records, pending records, proposal rasters, proposal records, scale stats, and optional labels under the segmentation output directory.
See Data Preparation, Segmentation, and Examples for related workflows.