Public-Observing-Unci-Maka

Observing Unci Maka

Welcome to the Observing Unci Maka repository, part of the Environmental Data Science Innovation and Impact Lab (ESIIL) at CU Boulder. This repository serves as the central hub for our working group, hosting our project description, member bios, codebase, and more.

Our Project

This working group brings together Tribal members, scientists, students and NASA remote sensing researchers to formulate new methods of using existing earth observation data to identify, monitor, and address environmental injustices in Tribal communities. We have two in-person meetings that we are using to gather preliminary insights to how NASA datasets could be used to address important socio-environmental issues near Tribally-managed lands as well as landscapes that sustain cultural resources that are important for Indigenous Ways of Being and Knowing.

Project Proposal

Project Proposal

Project Deliverables - Updated May 2026

Group Members

Sylvie Alexander

Shannon Boldt

Max Cook

Summer Dupree

Ayia Lindquist

Betty Poley

Bob Rabin

Darryl Reano, Co-Investigator (Indigenous Data Sovereignty). Website

Cynthia Sanders

Jim Sanovia

Shawn Serbin

Vanessa Taho

Gabriel Talayumptewa

Joni Tobacco

Sam Toledo

Elisha Yellow Thunder

Long Biographies for our Team

Meeting Notes and Agendas

Meeting Notes

Contributing to This Repository

We welcome contributions from all group members. To maintain the quality and integrity of the repository, please adhere to the following guidelines:

Observing Unci Maka

A repository for the development of code and workflows for the Observing Unci Maka ESIIL working group.

Instructions for setting up local Python environment and Git commands (from Max)

Instructions adapted from Earth Data Science.org

  1. Installing Python on your personal computer from miniconda

    Note: if you already have Python installed you may skip ahead to #3

    • Download the correct (e.g., Windows, MacOS, or Linux) miniconda from: https://docs.anaconda.com/miniconda/
  1. Installing Git and Bash (for interacting with GitHub) Windows
    • Download the Git Installer for Windows

      Run the installer by double-clicking on the downloaded file and by following the steps below:

    • Click on “Run”.
    • Click on “Next”.
    • Click on “Next”.
    • Click on “Next”.
    • Click on “Next”.
    • Click on “Next”.
    • Leave the selection on “Git from the command line and also from 3rd party software” and click on “Next”.
    • Click on “Next”.
    • Leave the selection on “Checkout Windows-style, commit Unix-style line endings” and click on “Next”.
    • Select the second option for Use Windows’ default console window and click on “Next”.
    • Click on “Next”.
    • Click on “Install”.
    • When the install is complete, click on “Finish”.

    This installation will provide you with both Git and Bash within the Git Bash program.

More instructions for what Bash is and how to use it can be found on the EarthDataScience.org tutorial

  1. Clone the repository to your local machine and setup the Python environment\

Cloning the repository essentially sets up a folder on your local machine that is a copy of the GitHub repository. Any changes you make in this folder (i.e., writing new code) can be “pushed” to the GitHub repository for all to see.

Note: Further instructions for cloning repositories can be found at this link

  1. Install/setup the Python environment

For our work, we have a “.yaml” file, which is a Python environment file that can be used to install all the dependencies we will need for coding. Updates to this file with new packages, etc., allows us to keep a consistent environment for everyone working on the project. You may have to periodically reinstall the environment as we make changes (adding new packages).

** To setup the environment for the first time:**

*To update your ‘py-unci-maka’ environment:*

Note: These steps are for updating the environment you’ve created. As we develop code, we will periodically be updating the “.yaml” file with new Python packages. To update the conda environment, or to make sure you are using the most recent version, follow these steps…

*To push local changes to GitHub:*

How to Update the Website

The website is built from the docs/ folder. Every time you change a file there, the website updates automatically.

Step by Step

  1. In the repository, click the docs/ folder.
  2. Click on index.md. This is the home page of your website.
  3. In the top right, click the pencil icon (✏️) to edit.
  4. Change the text to describe your project (for example, add your team’s name and a short description of what you’re studying).
  5. Scroll down. In the Commit changes box, write a short message like updated homepage with project info.
  6. Click Commit changes. That’s it! In about a minute, refresh the website link and you’ll see your changes.

Common Tasks

Add a new webpage:

Create a new .md file inside docs/ (like methods.md). It will become a new page on your site.

Add a picture:

Put the file in docs/assets/ and add it to a page with caption.

Instructions for working in CyVerse

  1. Login to CyVerse if you have an account, or email maxwell.cook@colorado.edu for access

————————————– Hope this Helped! ————————— ————————————————– —————————————– ————————————————————- ————————————————

Code Repository

This section of the repository will include all the code developed for the project. You can structure it as follows:

————————————– Hope this Helped! ————————— ————————————————– —————————————– ————————————————————- ————————————————

Getting Help

If you encounter any issues or have questions about how to contribute, please refer to the ESIIL Support Page or contact the repository maintainers directly.

Customize Your Repository

As a new working group, you’ll want to make this repository your own. Here’s how to get started:

  1. Edit This Readme: Replace the placeholder content with information about your specific project. Ensure that the introduction, project overview, and objectives clearly reflect your group’s research focus.

  2. Update Group Member Bios: Add details about each group member’s expertise, role in the project, and professional background. Include links to personal or professional web pages to foster community engagement and collaboration.

  3. Organize Your Code: Structure your codebase in a way that is logical and accessible. Use directories and clear naming conventions to make it easy for all members to find and contribute to different parts of the project.

  4. Document Your Data: Include a data directory with README files explaining the datasets, sources, and any preprocessing steps. This will help new members understand and work with the project’s data effectively.

  5. Outline Your Methods: Create a detailed METHODS.md file where you describe the methodologies, software, and tools you will be using in your research. This transparency will support reproducibility and collaborative development.

  6. Set Up Project Management: Utilize the ‘Issues’ and ‘Projects’ features on GitHub to track tasks, discuss ideas, and manage your workflow. This can help in maintaining a clear view of progress and priorities.

  7. Add a License: Choose and include an appropriate open-source license for your project, ensuring that the broader community understands how they can use and contribute to your work.

  8. Create Contribution Guidelines: Establish a CONTRIBUTING.md file with instructions for members on how to propose changes, submit issues, and contribute code.

  9. HI SHANNON!!!

  10. Review and Merge Workflow: Decide on a workflow for reviewing and merging changes. Will you use branch protection? Who will have merge privileges? Document this process to avoid confusion.

  11. Establish Communication Channels: Beyond GitHub, set up additional communication channels like Slack, Discord, or email lists for quick and informal discussions.

Remember, the goal is to make your repository clear, accessible, and useful for all current and future members of your working group. Happy researching!

This site is open source. Improve this page.