How seeg-brazil/seeg_mut works
Project type and purpose
• This is a data‐processing pipeline rather than a traditional web or microservice application. Its goal is to generate high-resolution greenhouse-gas (GHG) emission/removal estimates for Brazil by
• running spatial analyses on Google Earth Engine (GEE)
• exporting geospatial outputs (GeoJSON)
• ingesting those outputs plus auxiliary tabular data into an R‐based estimation module
File structure
• Top-level directories:
1._Spatial_analyses – contains GEE JavaScript scripts (.js), Python scripts/notebooks (.py, .ipynb) for land‐cover transitions, mask creation, spatial filtering, area calculations, and export.
2._Estimates – an R project folder with an Estimates.R script under R/script, plus a data subfolder containing all auxiliary CSV/XLS(X)/ODS tables.
aux – houses images (logos, README illustrations).
__Output – holds the exported GeoJSON time‐series layers.
• Key indicators:
• A two‐stage ETL pipeline (Spatial → Export → Statistical Estimates).
• Dependencies on external cloud services (GEE), local runtimes (Python, R), and data files.
README for additional insights
• Confirms GEE (JavaScript + Python API) as the spatial‐analysis engine.
• Confirms R 4.x + RStudio for the estimation stage.
• Describes workflow:
Spatial analyses in GEE → export assets → local/Colab Python for some steps → R reads outputs & aux data for final emission/removal calculations.
Elements
• GEE Scripts → GEE Assets
• GEE Assets → __Output GeoJSON
• __Output & aux_data → R Script
• R Script → Final Outputs
• Blue for cloud services (GEE)
• Green for local code modules
• Orange for data stores/files
Final recommendations
• Essential elements (services, runtimes, data flows) without over-complicating; two layers (cloud vs. local) plus data exchange is enough