1 of 8

Track:

Team Members:

#

Team:

Institution(s):

Submission Title

2 of 8

Important: File Naming Convention for Final Slide Deck

​

​

Attention Teams: To ensure our judges can locate and review your work accurately, all final files must follow the naming convention below. Consistent filing is a professional requirement; final submission files that are not named correctly will potentially not be considered during the judging process. Refer to Discord for team number rules.

Use the following naming convention for your final submission:

Track_Team#_00_SLIDES_Institution

  • Track: Use the abbreviation related to your track;
    • MCC, for Mangroves and Coastal Cities
    • ISC, for Innovating the Net-Zero Supply Chain
    • AIB, for Climate Change and the Alpine Information Battle
  • Team Number: Use at least two digits, e.g., 01 for Team #1, 112 for Team #112. This is the same as your discord team number.
  • Priority: Use 00_SLIDES for your slide deck.
  • Institution Acronym: ASU for Arizona State University, UEES for Universidad de Especialidades Espíritu Santo, ESPOL for Escuela Superior Politécnica del Litoral, CY for CY Cergy Paris University, UNWE for University of National and World Economy, etc.

Example: If you are Team #5 in the Mangroves and Coastal Cities track and you are working at ASU, your slidedeck will be named: MCC_05_00_SLIDES_ASU.pptx

​

​

​

​

​

​

​

3 of 8

Important: File Naming Convention for Supporting Docs

​

​

Attention Teams: To ensure our judges can locate and review your work accurately, all supporting documents must follow the naming convention below. Consistent filing is a professional requirement; files that are not named correctly will potentially not be considered during the judging process. It is not necessary to turn in any supporting documents, but you are free to do so if you feel it will provide added value or context to your submission. Judges will only use your final slide deck for scoring. Use the following naming convention for any supporting documents:

Track_Team#_01_Description_Institution

  • Track: Use the abbreviation related to your track
    • MCC, for Mangroves and Coastal Cities
    • ISC, for Innovating the Net-Zero Supply Chain
    • AIB, for Climate Change and the Alpine Information Battle
  • Team Number: Use at least two digits, e.g., 01 for Team #1, 112 for Team #112. This is the same as your discord team number.
  • Priority: Use 01 for the first supporting document, 02 for the second, and so on.
  • Description: Use a short description for your supporting document, such as “Video”, “Code”, or “Prototype.”
  • Institution Acronym: ASU for Arizona State University, UEES for Universidad de Especialidades Espíritu Santo, ESPOL for Escuela Superior Politécnica del Litoral, CY for CY Cergy Paris University, UNWE for University of National and World Economy, etc.

Example: If you are Team #5 in the Mangroves and Coastal Cities track, working from CY, and you turn in a video and your code, your supporting documents will be named:

MCC_05_01_Video_CY.mp4, and MCC_05_02_Code_CY.zip

​

​

​

​

​

​

​

4 of 8

Introduction (1-3 Slides)

​

​

This section will be used to introduce your team, your approach to the problem, and a brief summary of your findings.

​

Section should include:

  • Team Members (Name, Year, University, Major, Role on Team)
  • Approach - description of how your team approached the problem statement including what you decided to focus on and what data sets you decided to use
  • Executive Summary
    • Initial results (if any)
    • Opportunities for further exploration
    • Lessons learned (paths or approaches taken that didn’t work out, etc)

​

​

​

​

​

​

​

5 of 8

Maps / Data Visualization (2-5 Slides)

This section will be used to show your visualizations of the data created in Google Earth Engine.

​

Section should include:

  • Screenshots of data visualization, mostly map products from GEE
  • Can also include alternative data sources and reference images if used
  • Visuals should have a descriptive summary of what you are showing (optional key takeaway)
  • All images should list what data source(s) are shown in the visual
  • Multiple images can be included on each slide to show a progression or viewing the same event across multiple data sets
  • Can use arrows, boxes, etc to highlight what you are showing in each image

Key Takeaway Box

6 of 8

Analysis / Quantitative Correlation (1-4 Slides)

This section will discuss the analysis of the data and correlation of satellite imagery with any additional research, background, and non-map or non-satellite products used by your team during the Hackathon to address the track Problem Statement.

​

Section should include:

  • Summary of key findings addressing your track Problem Statement and Key Questions
  • Correlating findings between Earth Observation data and the track goal
  • List of reference material, sources, and additional data used for the analysis

7 of 8

Impact / Why (1-2 Slides)

This section will summarize what you believe the impact of leveraging Earth Observation could be on the track goal.

​

Section should include:

  • Opinion from your team on whether using satellite data could make an impact on the problem statement and key questions of your track
  • Should answer the question “so what?” when it comes to using satellite data
  • Team can explore whether the use of satellite data could impact policy changes
  • Discuss some possible implementations or further study that could address the UN SDG’s

8 of 8

Thank you