All resources
Water and shoreline segmentation

Sentinel-2 water masks with RasterForge

When RasterForge fits Sentinel-2 water mask workflows, what imagery and review standards matter, and when a simpler GIS or index-based process is better.

Updated
2026-06-15
Audience
Remote-sensing teams evaluating water, reservoir, shoreline, and wetland mask workflows
Primary topic
Sentinel-2 water masks

Who this is for

Use RasterForge when a team needs reviewed water masks from Sentinel-2 or Sentinel-2-derived GeoTIFFs and the output needs to move into a GIS workflow as masks or GeoJSON.

This is strongest for repeated work: reservoirs across many dates, shoreline checks across a project area, or wetland scenes where a reusable segmentation profile can save setup time.

When RasterForge fits

RasterForge is useful when water is visible in a render and a reviewer needs to correct ambiguous edges. The workflow keeps imagery, render settings, segmentation profiles, masks, GeoJSON edits, and review selections together.

It is especially helpful when the inclusion rule matters. For example, one project may treat flooded vegetation as water, while another may require strict open-water boundaries only.

When RasterForge is not the best tool

RasterForge should not replace simple index workflows when those are enough. If NDWI or another water index with a threshold gives a stable result and the team only needs a raster mask, a GIS or remote-sensing script may be faster.

It is also not a substitute for field validation, hydrologic modeling, or domain QA. Outputs should be reviewed before downstream use.

Input imagery considerations

Sentinel-2 water work depends heavily on render choice. Start with a render where land, water, vegetation, cloud, and shadow are visually distinct. Turbid water, sediment, cloud shadow, wet soil, and floating vegetation can all confuse the target.

Use a small AOI first. Include easy water, hard edges, bridges, vegetation, cloud shadows, and narrow channels so the first run exposes failure modes before a broader project run.

Review and QA expectations

Review shorelines at several zoom levels. Check islands, cloud edges, narrow rivers, and mixed wetland boundaries separately. If the exported mask will be used by another team, document the inclusion rule before export.

For step-by-step product instructions, use the practical docs workflow: Create Sentinel-2 water masks with RasterForge.

Practical workflow

  1. Choose a small AOI with easy water, hard water, shadows, vegetation, and bare wet soil.
  2. Pick a render where water is visually separable from land and vegetation.
  3. Run one profile on the representative AOI before expanding to more scenes.
  4. Review edge cases before exporting, especially where water mixes with sediment, cloud shadow, or vegetation.

Common failure modes

False positives often come from cloud shadow, dark roofs, wet soil, asphalt, and shaded vegetation. False negatives often appear in narrow rivers, turbid water, flooded vegetation, and shallow water near shore.

If those cases dominate the scene, a water index, a scripted remote-sensing workflow, or manual GIS review may be a better primary method.

Buyer fit and handoff details

RasterForge fits Sentinel-2 water mask projects when visual review and GIS export are part of the deliverable. NDWI, Earth Engine, or Python can be better when the team needs calibrated, code-only processing at scale.

For buyer context, read Best water mask segmentation software, NDVI and NDWI thresholds vs promptable segmentation, and Google Earth Engine vs RasterForge.

FAQ

Is RasterForge better than NDWI for water masks?

Not always. If NDWI or another index gives a reliable mask, use the simpler method. RasterForge is more useful when the target needs visual review, boundary cleanup, or reusable profiles across scenes.

Can the output be used directly for hydrology or compliance?

Treat RasterForge output as reviewed image-derived data, not regulatory truth. Use domain QA and field or authoritative sources where required.

Example outputs

Typical outputs are reviewed raster masks, edited GeoJSON water polygons, and a project review selection that records which layer was chosen as the master result for each image.

Need product steps rather than buying context? Read the practical RasterForge workflow guides.

Sources

These resource pages are fit and workflow guides. Verify sensor, licensing, scientific, and operational requirements before using exported masks or vectors in production decisions.

Related resources