TreeScoreBeta

Measure first. Claim later.

Where the number comes from.

Satellite-derived green cover estimate

01 · What the estimate means

TreeScore analyses Sentinel-2 Surface Reflectance imagery (COPERNICUS/S2_SR_HARMONIZED). NDVI compares near-infrared and red light: (B8 − B4) / (B8 + B4). It responds to trees, shrubs, grass, lawns and mangroves. Green cover is a vegetation proxy; it is not exact tree canopy or an exact tree count. This is not an official government measurement.

02 · Calibration before publication

Andheri West Core uses the human-approved NDVI threshold 0.35; Juhu uses 0.30. Both apply only to their November 2025–February 2026 boundary, Sentinel-2 method, masks and reviewed reference polygons. The samples are visual references rather than field-verified ground truth. Locality thresholds are not universal TreeScore cutoffs.

03 · Clouds, water and the denominator

The current workflow filters scenes with cloudiness above 60%, retains pixels with Cloud Score+ cs_cdf at least 0.60 and valid spectral bands, then forms a median composite from November 1, 2025 through February 28, 2026. At least three clear observations are required. Pixels with composite NDWI greater than zero are excluded as water. Green area is divided by valid observed land area on a 10 m grid. Cloud and water masks can make mistakes.

04 · Sensitivity of the reviewed beta measurement

Andheri thresholds 0.30, 0.35 and 0.40 yield about 47.5%, 40.2% and 33.5%. Juhu thresholds 0.25, 0.30 and 0.35 yield about 58.3%, 48.8% and 39.6%. This sensitivity reflects mixed urban pixels and threshold choice; it is not a confidence interval. Small purposive samples, basemap timing, shadows and limited independent validation constrain accuracy claims. Processing version: level1-1.0.

05 · Our analysis areas

Each boundary is a TreeScore-defined analysis area, not an official administrative boundary. Andheri uses v0.2. Juhu uses the medium-confidence v0.3 boundary traced after visual QA removed unintended aerodrome and lagoon land before publication. Boundary and calibration are reviewed before a measurement is published. Polygon footprint is not the same as the observed-land denominator.

06 · Change since 2015

The baseline is November 2015–February 2016, not the entire 2015 calendar year. Current estimates use Sentinel-2 surface reflectance. Because that archive begins in 2017, the historical workflow uses a separate TOA collection consistently across all years. It compares identical seasonal windows and the same land pixels, excluding water detected in any selected year. Insufficient early imagery leaves the baseline unavailable. Differences are percentage points; relative change is undefined for a zero baseline.

07 · What qualifies for ranking

Rankings are withheld in the two-locality beta. Andheri and Juhu share the Level-1 processing family and season, but their independently reviewed thresholds differ. TreeScore will introduce rankings only after cross-locality calibration validates direct numerical ordering. Pending and unpublished analyses remain excluded.

08 · Privacy and limitations

Use my location checks your position inside the polygons in your browser. TreeScore does not store it. The basemap loads tiles from OpenStreetMap, which receives ordinary tile requests and your IP address. Ten-metre imagery mixes vegetation and built surfaces; seasonal effects, shadows, sparse observations and boundary uncertainty limit what an estimate proves.

Sentinel-2 surface-reflectance catalog · Historical TOA catalog · Technical methodology

Green-cover estimates are satellite-derived NDVI-based proxies that capture vegetation, not exact tree counts. TreeScore-defined analysis area, not an official administrative boundary.