A curated collection of tools, tutorials, code, and resources for Earth Observation and geospatial satellite imagery analysis.
Awesome-EarthObservation-Code is a curated GitHub repository that aggregates open-source tools, tutorials, code examples, and projects related to Earth Observation and geospatial satellite imagery. It solves the problem of fragmented resources by providing a single, community-maintained directory for developers and researchers working with remote sensing data.
Geospatial developers, data scientists, remote sensing researchers, and students who need to discover and evaluate tools for processing, analyzing, and visualizing satellite imagery across various programming ecosystems.
It saves time by centralizing hundreds of EO resources, supports multiple languages and frameworks, and is continuously updated through community contributions. Unlike proprietary platforms, it is entirely open and focused on practical, code-first implementations.
A curated list of awesome tools, tutorials, code, projects, links, stuff about Earth Observation, Geospatial Satellite Imagery
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Aggregates hundreds of tools, libraries, and projects across optical, SAR, LiDAR, and machine learning, as shown in the detailed table of contents covering multiple programming languages.
Accepts pull requests and acknowledges contributors in a file, ensuring ongoing community input and diversity of resources, as highlighted in the README.
Includes tutorials, courses, YouTube channels, and documentation links, helping users from introduction to advanced topics, as seen in sections like 'Training and Learning'.
Covers resources for Python, R, JavaScript, Rust, Scala, and more, catering to varied developer preferences in geospatial workflows, as emphasized in the key features.
The README warns that many resources are over two years old, with some code retired or >10 years old, risking compatibility issues and obsolete practices.
Updated infrequently by the maintainer and reliant on community PRs, leading to potential staleness and unverified broken links over time.
No systematic vetting for code quality, maintenance status, or functionality, requiring users to independently validate each resource before use.