STAC catalog search
Queries the Copernicus STAC API by area, dates and cloud cover and returns a CSV of scenes to choose from, without downloading anything.
Deliverable: list of scenes with cloud cover, tile and levelOcto for Sentinel-2, Landsat, CBERS, STAC and Orfeo ToolBox
Sentinel-2 at 10 m with a 5-day revisit at the Equator, Landsat 9 at 30 m since 2021: all searched through a STAC catalog and processed by script with GDAL, rasterio and Orfeo ToolBox. Octo lists the scenes, builds the false color with the same contrast across dates, calculates NDVI with clouds masked and delivers clipped mosaics as COG, with provenance noted. Interpretation, the report and the signature stay with the licensed professional.
Six possible deliverables, taken from the survey. All of them separate what is a sensor fact from what is interpretation, and all go to the responsible professional before becoming a conclusion.
Queries the Copernicus STAC API by area, dates and cloud cover and returns a CSV of scenes to choose from, without downloading anything.
Deliverable: list of scenes with cloud cover, tile and level8-4-3, SWIR or agriculture composites, with the same stretch across dates, so the difference comes from the ground.
Deliverable: COG per date + recorded parametersCalculates on surface reflectance, masks cloud and shadow using the SCL and measures the fraction of valid pixels for each date.
Deliverable: NDVI series + validity tableReprojects scenes from different zones, joins them in a VRT, clips by the boundary and writes a COG, with seam lines in the report.
Deliverable: clipped mosaic + gap reportNDVI, NDWI and free expressions with otbcli_RadiometricIndices and otbcli_BandMath, with memory capped per process.
Reads rasters already delivered and flags unapplied scale, swapped bands, mixed CRS and dates missing from the legend.
Deliverable: list of findings for the leadThe same Octo cycle, applied to satellite imagery. Each arm has a narrow role; people interpret, conclude and sign.
Scene collection, products already delivered, installed tools (GDAL, OTB, Python) and where the imagery comes from.
Mission, sensor, level, scale, offset, band numbering and CRS of each scene.
Provider token kept out of the code, terms of use for each source and care with sensitive areas before publishing.
Sentinel-2, Landsat or CBERS depending on the question; GDAL, rasterio or OTB; remote window or download.
Search, composite, index, mask, mosaic and clip, with parameters recorded in the product metadata.
Value range, fraction of valid pixels, same stretch across dates, CRS and nodata. A generated file is not a correct file.
A product is delivered or published only after the lead's review, with the image date and source in the legend.
Scenes, dates, levels, formulas, masks, versions and who approved each product.
Octo works as support. It does not interpret imagery as an expert report, does not conclude that a violation occurred and does not sign technical products.
The criteria Octo uses to choose, with the documentation for the installed version.
| Task | Path | Note |
|---|---|---|
| Search Sentinel-2 scenes | CDSE STAC API, sentinel-2-l2a collection | v1 endpoint; the old one was discontinued on Nov 17, 2025 |
| Long time series | Landsat (Collection 2) | On 8/9, NDVI with B5 and B4 |
| Brazilian imagery | INPE catalog (CBERS, Amazonia) | Check bands and terms |
| Comparable false color | gdalbuildvrt -separate + gdal_translate -scale | Same stretch across dates |
| NDVI with mask | rasterio + SCL, by windows | Surface reflectance; nodata declared |
| Batch indices | otbcli_RadiometricIndices, otbcli_BandMath | -ram caps memory |
| Mosaic across different zones | gdalwarp -t_srs + gdalbuildvrt | Output CRS chosen by the cartographer |
| Clip by boundary | gdalwarp -cutline -crop_to_cutline | Official area boundary |
| Delivery | COG with provenance in the metadata | Date and source in the legend |
Three steps. Each one only makes sense after the previous one has shown results on your team.
A proposal, not a promise
Octo lists the scenes and products the team already has and checks the level, scale, CRS and date of each one.
STAC search, composite, masked NDVI and clipped mosaic, each product with provenance.
Each new pass is searched, processed and checked; what changes beyond the threshold goes to the professional to assess.
Each point below has a source published by the project or by the organization responsible for the standard. The sources are in the next section.
7
points with a published source, each with its reference shown alongside.
stac.dataspace.copernicus.eu/v1, sentinel-2-l2a collection; old endpoint discontinued on Nov 17, 2025.Source: CDSE documentationdata.inpe.br/bdc/stac/v1, CC BY 4.0 collections; CBERS-4A WPM 2 m, MUX 16 m, WFI 55 m; Amazonia-1 WFI 64 m; CBERS-4 MUX 20 m.Source: INPE STAC, /collectionsOcto prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.
Surveys, calculates, organizes and produces the documents: spreadsheets, reports, maps and drafts.
Deliverable: material ready to checkThe licensed professional checks what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.
Step: review by the signerOcto does not sign. Projects, technical reports, ART/RRT, accountability reports and any official document are still signed by the company's or agency's licensed professional: here, the technical lead for the map or the survey.
Signature: technical lead for the map or surveyMission pages, Copernicus documentation and repositories, consulted on Oct 31, 2026.
The assessment starts with an inventory of the scenes and products your team already has: mission, level, scale, CRS and date of each one. You get the list of what can be compared, what needs to be redone and the decisions only the responsible professional makes.