Skip to content

CERSGIS/Hackathon

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 

Repository files navigation

HACKATHON GUIDELINE DOCUMENTATION

INTRODUCTION

The Sustainable Management of Wetland and Floods for Strengthening Food Security and Resilience of Ecosystems in West Africa (GDZIHAO) project is a support program for Environment and Security Monitoring (GMES & Africa). It was set up by the African Union in partnership with the European Union. The Center for Remote Sensing and Geographic Information Services (CERSGIS) and fourteen (14) other partners across West Africa intend to implement services to monitor wetlands management and flooding across the region. The European Union, through the support program, offers the possibility for African institutions to have free access to tools and geospatial technologies of the European Space Program (ESA). Such an opportunity facilitates access to applications, products, and services derived from Earth Observation (EO) data, and the geospatial information provided would be of great added value in improving knowledge for better monitoring and rational management of wetlands. As part of the project activities, a hackathon to bring together groups of creative thinkers and problem-solvers to explore the use of EO data and computer coding is an efficient approach to address wetland challenges. This documentation will include the hackathon schedule, judging criteria, submission requirements, team formation rules, code of conduct, and any other relevant information. It will be shared with all participants at the beginning of the hackathon and will be made readily available for reference throughout the event.

DATE AND VENUE

The event will take place on the 16th of June, 2023 from 9:00 a.m. to 3:00 p.m. at the CERSGIS Training Room.

GENERAL PROCEDURE

Duration

The hackathon will take place over two months. The first month will be used for a meeting with the teams to provide a general overview of the GDZHIAO project and the hackathon itself. Possible themes or challenge areas will be discussed with participants. In the second month, a period of 4 weeks will be allotted to the teams for adequate preparation and completion of their respective projects. In the second week of preparation, a progress meeting will be held for teams to ask questions, express concerns and give feedback on their progress so far.

Team Size

There will be a total of three groups, each consisting of 4 - 6 members.

Satellite Imagery Requirements

All satellite imagery used in the hackathon must be sourced exclusively from the Sentinel imagery. The Sentinel satellites, operated by the European Space Agency (ESA) as part of the Copernicus program, provide high-quality, open-access remote sensing data that can be used for a wide range of applications, including app development. It is important to adhere to this requirement and only use Sentinel imagery to ensure compliance with data usage policies, copyright laws, and ethical considerations. Please refrain from using any other satellite imagery during the hackathon to ensure fair and consistent use of data by all participants.

Themes/Challenges

Six different themes or challenges will be carefully curated to inspire creativity and innovation among the participants. These challenges will address solutions to challenges at specific Ramsar sites. The challenges are listed below:

Challenge 1: Mapping Wetland Vulnerability: “Assessing Flood Risk and Vulnerability using Earth Observation Data”

Area of Interest: Sakumo Lagoon Ramsar Site

Expectations: Make use of satellite imagery and other remote sensing data to develop innovative approaches to analyze and map wetland vulnerability to floods. It should include identifying areas at risk, mapping key vulnerabilities such as infrastructure and human settlements, and assessing the impacts of floods on the wetland ecosystem.

Results: Solutions involving developing vulnerability assessment models, applications, or tools, and designing decision support systems for wetland managers to prioritize actions and resources for flood risk reduction and resilience building.

Challenge 2: Wetland Watch: “Mapping Ecosystem Changes in Wetlands Using Earth Observation Data”

Area of Interest: Sakumo Lagoon Ramsar Site

Expectations: Make use of earth observation data, such as satellite imagery and remote sensing techniques, to characterize ecosystem changes in the Sakumo Ramsar site. develop innovative approaches to map and monitor the wetland’s vegetation dynamics, land cover changes, and hydrological shifts using time-series data.

Results: Solutions should involve developing machine learning algorithms for change detection, creating interactive visualization tools for data analysis, and designing decision support systems for wetland managers to assess and manage ecosystem changes in wetlands.

Challenge 3: Wetland Watchers: “Leveraging Earth Observation Data for Real-time Monitoring of Wetland Water Quality”

Area of Interest: Owabi Wildlife Sanctuary

Expectations: Make use of satellite imagery and other remote sensing data to monitor the water quality of wetlands in real-time, by utilizing satellite imagery to detect changes in water color and quality. Indicate the presence of pollutants, sediment, or algae blooms and good water quality.

Results: Solutions should include identifying water pollution sources, tracking changes in water quality parameters, and predicting potential threats to wetland ecosystems.

Challenge 4: Wildlife Spot: “Earth Observation Data for Creating a Marketing App for Tourist Attraction in a Wildlife Sanctuary”

Area of Interest: Owabi Wildlife Sanctuary

Expectations: Utilizes earth observation data to create an innovative marketing application for tourist attractions in a wildlife sanctuary. The application could feature real-time wildlife sightings, species identification, and interactive maps to guide tourists to the best viewing spots. Participants can develop algorithms to detect and track wildlife activities in the sanctuary using satellite imagery and other remote sensing techniques.

Results: The application should be a user-friendly interface, create data visualization tools, and a comprehensive solution that integrates earth observation data, geospatial analysis, and machine learning algorithms to create a unique user and impactful app that promotes wildlife conservation and sustainable tourism.

Challenge 5: SALT: “Satellite Assisted Monitoring of Sea Level Rise Impacts on Coastal Wetlands”

Area of Interest: Keta catchment area

Expectations: Make use of satellite imagery and other remote sensing data to monitor and assess the impacts of sea level rise on the coastal wetland of the Keta Ramsar area. develop innovative approaches that utilize satellite imagery, elevation data, and hydrological models to assess changes in wetland extent, elevation, and salinity due to sea level rise.

Results: Solutions should involve developing sea level rise impact models, creating vulnerability assessment tools, and designing visualization tools for decision-makers to prioritize adaptation measures for coastal wetland conservation and management.

Challenge 6: Mangrove-Rescue: “Using Earth Observation Data for Mangrove Restoration Monitoring and Assessment”

Area of Interest: Keta catchment area

Expectations: Make use of satellite imagery and other remote sensing data to monitor and assess mangrove restoration efforts along the wetland. develop innovative approaches that utilize remote sensing techniques, geospatial analysis, and machine learning algorithms to assess the success of mangrove restoration activities, including vegetation cover, structural characteristics, and hydrological connectivity in the catchment area.

Results: Solutions should involve developing restoration monitoring models, creating restoration assessment tools, and designing decision support systems for restoration practitioners to optimize mangrove restoration outcomes.

MENTORS AND JUDGES

Each team will be assigned a mentor to guide them through the preparation period. Mentors will be recruited and selected based on the following criteria:

  • Technical expertise in computer programming
  • Background knowledge of the topic
  • Impartiality and fairness
  • Willingness and availability to provide guidance
  • Professionalism

Judges will also be recruited and selected to determine the winner of the event. These judges will be selected based on the following criteria:

  • Impartiality and Fairness
  • Understanding of the judging criteria
  • Professionalism
  • Technical expertise
  • Communication skills
PRIZES

The prizes will be awarded as follows:

  • First Place Prize: GHC 5,000
  • Runner - Up Prize: GHC 3,000
  • Second Runner - Up Prize: GHC 1,000
JUDGING CRITERIA

Results are judged based on the following criteria:

Creativity and Innovation

The judges will evaluate the creativity and originality used in developing the product that considers usability, design, and intuitiveness.

Functionality and Features

The criteria will evaluate the functionality and features of the product. This will include its usability, performance, stability, performance, and reliability. Judges will assess whether the product meets its intended purpose and provides a smooth and intuitive user experience.

Solutions

The product will be reviewed to determine if it is a new and efficient solution that addresses the identified challenge and identifies useful patterns, change detections, and other insights to provide actionable information. Judges will evaluate the product's potential to solve real-world problems, its marketability, and its potential to create value for users or stakeholders.

Technical Implementation

This criterion assesses the technical implementation of the product, including the quality of the code, the use of appropriate programming languages, frameworks, and libraries, and adherence to best coding practices. Judges will evaluate the technical complexity, scalability, and maintainability of the product.

Design and User Experience

This criterion evaluates the visual appeal, aesthetics, and user experience of the product. Judges will assess the product's design elements, such as layout, typography, color schemes, and use of multimedia, as well as the overall user experience, including ease of use, navigation, and interaction.

Presentation and Demonstration

This criterion evaluates the quality of the team's presentation and demo of the product during the judging process. Judges will assess the clarity of the team's presentation, the effectiveness of the demo, and the ability of the team to effectively communicate the product's features, functionality, and value proposition.

Teamwork and Collaboration

This criterion assesses the teamwork and collaboration skills demonstrated by the team during the hackathon. Judges will evaluate the team's ability to work together, communicate effectively, and leverage each team member's strengths to create a cohesive and well-executed product.

Time Management and Completion

This criterion evaluates the team's ability to manage their time effectively during the hackathon and complete the product within the given timeframe. Judges will assess the product's level of completion, including the extent to which it meets the initial goals and requirements set by the team.

INTELLECTUAL PROPERTY AGREEMENT

As a participant in this hackathon, it's important to understand the intellectual property (IP) considerations associated with the product you create during the event.

Team Ownership

The product developed during the hackathon will be owned by the team that creates it. This means that the team members collectively own the rights to their product, including the code, design, and any other creative elements they have developed.

Event Organizer's Rights

By participating in the hackathon, you grant the hackathon organizer a non-exclusive, royalty-free license to use and showcase the products created during the event for promotional purposes, such as showcasing the winners or promoting future hackathons.

Third-party IP

It's important to respect the intellectual property rights of others. Please do not use any copyrighted, patented, or trademarked material without proper authorization during the hackathon. You are encouraged to use open-source software or obtain proper licenses for any third-party software or resources used in your product.

Confidentiality

If the hackathon involves proprietary or confidential information, you are required to adhere to any confidentiality agreements and not disclose or use any confidential information obtained during the event without proper authorization.

By participating in the hackathon, you acknowledge and agree to the intellectual property considerations outlined above. It's important to fully understand and comply with these considerations to ensure the proper ownership, usage, and protection of intellectual property created during the hackathon.

EVENT DAY ACTIVITY

  • Welcome Address
  • Brief Presentation on the GDZHIAO project
  • Review of Hackathon Judging Criteria
  • Introduction of Teams
  • Introduction of Judges
  • Presentation of Results
  • Time Allotted for Judges’ Assessment
  • Presentation of Final Outcome
  • Presentation of Awards
  • Closing Remarks

RULES

The following rules must be adhered to throughout the hackathon period:

  • Following receipt of the hackathon guidelines, teams will choose a challenge to focus on and communicate their selection to the organizers. If multiple teams select the same challenge or if all selected challenges are concentrated on a particular area of interest, teams may be asked to change their chosen challenge to ensure a diverse range of topics is covered during the hackathon.
  • Teams cannot consist of event organizers or planners.
  • In instances where instructions or conditions are unclear, participants are allowed to ask organizers for clarification during the event.
  • Work that is produced outside of the assigned topic may not be considered.
  • Individuals and teams can be disqualified from the competition if organizers find it necessary to. This may be based on inappropriate participant behavior including, but not limited to, cheating, jeering, physical assault of participants, and disregard for organizers’ authority during the event.
  • Once teams have been formed, group members are not allowed to change teams.
  • Participants are required to submit all their hackathon results through a GitHub repository or within the designated GitHub environment provided by the event organizers. This allows for the easy and organized submission of code, documentation, and other relevant materials. After work is submitted, no additions or edits can be made.

CONCLUSION

In sum, the hackathon has been designed to encourage participants to channel interests in the environment and geospatial technology to design a useful tool that can help address wetland-related challenges. It should be regarded as an opportunity to learn new ideas and expand your geospatial data skillset and have fun in doing so. Please review this document carefully and adhere to the rules and guidelines throughout the hackathon to ensure a fair and smooth competition.

ORGANISERS

gmes gdzh cse cersgis

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published