Choose a supported handoff
The satellite workflow accepts georeferenced GeoTIFF/JPEG2000 imagery, raw Sentinel-2 SAFE ZIP packages or loose JP2 spectral bands. Upload handling includes resumable transfer, band mapping and a project-task handoff. Keep original imagery and metadata so the selected bands and their meaning remain traceable.
For Landsat, Planet, Airbus or Maxar data, qualify a licensed, prepared GeoTIFF handoff with known bands, georeferencing and processing level. These names describe potential data sources; they do not imply a direct catalogue connector, automatic purchase, tasking service or universal product-format importer.
Preserve the spectral information
A web preview, screenshot or colorized JPEG is useful for orientation but is not a replacement for spectral imagery. Confirm which channels represent blue, green, red, red-edge, NIR, SWIR1 and SWIR2. Record the source resolution, scale and NoData values, then align the bands on an appropriate common grid.
The reviewed formula catalogue contains 42 entries: 35 spectral indices, five individual-band products and two temperature conversions. Only entries supported by the actual input bands are relevant. NDVI needs red and NIR; NDRE needs red-edge and NIR; MNDWI needs green and SWIR1; NBR needs NIR and SWIR2.
Match the analysis to the application
Agriculture workflows can review vegetation-index patterns and compare field conditions. Water and coastal projects can inspect water extent and flood/recession layers. Urban and regional work can examine land-cover classes and visual change. Exported outputs can include raw-value and colorized GeoTIFFs, classification vectors and class statistics.
Classification includes vegetation, water, bare ground, built-up and a proximity-based wetland category. Treat these as reviewable analytical layers. Bare terrain can be confused with built-up surfaces, and the wetland label is not an ecological survey result.
Make before-and-after scenes comparable
Use compatible georeferencing, acquisition dates, band meaning and analysis extents. Check seasonal differences, cloud/shadow coverage and source processing level before attributing a pixel difference to a real event. Sentinel-2 scene-classification information can exclude cloud and shadow where supplied; other inputs require an explicitly qualified masking workflow.
The reviewed UI offers visual, elevation and flood comparison. Additional transition matrices and formula-based comparisons exist in the API/model and require deployment-specific verification. Keep permanent water, newly flooded and receded areas distinct when interpreting flood outputs.
Define the handover before running a large area
Provide the AOI boundary, scene identifiers, acquisition dates, license context, coordinate system and requested map layers. Ask for a representative-area trial with a documented band map and a quality review. Match the export to the receiving GIS: raster values for further computation, vectors for boundaries and CSV statistics for reporting.
The website Experience Zone illustrates the workflow and proposal outputs. Actual processing requires the configured Suite service and supplied scene files; it does not acquire satellite imagery automatically.
Manufacturer and data references
Dataset questions
Can I upload Sentinel-2 SAFE instead of making a preview first?
Yes. The reviewed Suite source includes Sentinel-2 SAFE ZIP and loose JP2 preparation. Retain actual spectral bands and metadata; a true-colour preview cannot replace those inputs.
Does HelloGeo Suite include a satellite imagery subscription?
No subscription or automatic acquisition service is established by the reviewed implementation. Supply appropriately licensed imagery and confirm the required preparation and deployment workflow.