Start: 3pm 10 July 2022

Ends 5:15pm 12 July 2022


Indivduals and teams. Participation may be remote or in-person. All hackathon participants must register for attendance at the #CDE22 conference ether in-person or online.

Project and Submission Requirements

  • Narrative explaining what you did and the methods and outcomes you reached. 
  • Audience Talk: Each team will be asked to talk for 5 minutes to teh conference audience at 4:45pm on Tuesday 12th July
  • Video. The Devpost platform accepts links to YouTube, Vimeo or Youku. Shoudl be no more than 20 minutes
  • File Upload. Combine files into a single ZIP file.
  • Other Entry name and description.
  • Multiple Solutions. Each team or individiual may submit only one entry


We are offering awards of up to £3000 for the best solutions to helping general public better understand our environment and sciences.

  • First place award £3,000
  • Second place award £1,500
  • Third place award £500

Awards are made to the team, to be shared out amongst team members.

Judging Criteria and Winner Selection

In running the Hackathon, we seek to create a body of excellent open access public visualisations of environment data .However, the Hackathon is also a competition, with financial awards for first, second and third place offered as a further incentive.

A judging panel to be appointed by NERC will review all the entries for the Hackathon and will determine the winning entries, who will be contacted to receive their team award. Teams will receive comments from the panel relating to their entry.

Depending on the number of entries, it is our intention that judging will take one week from the completion of the hackathon event.

The criteria for the judging will involve a consideration of (a) the Specific Fit of the solution to the challenge focus, (b) the practical Measurability of the outcome, (c) the Achievability of the solution, (d) the Relevance of the approach put forward and addressed in (e) the Timebound period of the Hackathon – in effect a ‘SMART’ approach. To detail further, we will assess all entries according to the following criteria:

‘S’ (specific) = Does the solution you deliver match with the specific challenge of the Hackathon? Is it clear enough from your entry for the judges to assess you have completed a solution?

‘M’ (measurable) = Does the solution you put forward permit a ‘measurable outcome’? Does your entry meet expectations?

‘A’ (achievable) = Is the digital solution put forward sensible and practical? Was the solution achieved within the time frame, opportunity and resources?

‘R’ (relevant) = Does the solution put forward have scientific merit (in NERC remit), with relevance to the overall Hackathon theme? Does the solution have the desired impact?

‘T’ (timebound) = Has the topic been adequately addressed satisfactorily within the allocated week?

Please note the judging panel’s decision will be final.


All attendees, sponsors, partners, volunteers and staff at our hackathon are required to agree with the following code of conduct. Organisers will enforce this code throughout the event. We expect cooperation from all participants to ensure a safe environment for everybody.

Our hackathon is dedicated to providing a safe and comfortable environment and harassment-free experience for everyone, regardless of the following:
  • gender
  • gender identity and expression
  • age
  • sexual orientation
  • disability
  • physical appearance
  • body size
  • race
  • ethnicity
  • nationality
  • religion
  • political views
  • previous hackathon attendance or lack of
  • computing experience or lack of
  • chosen programming language or tech stack
We do not tolerate harassment of hackathon participants in any form. Sexual language and imagery is not appropriate at any hackathon venue, this includes the following.
  • hacks
  • talks, presentations, or demos
  • workshops
  • any parties associated to the hackathon
  • social media
  • any other online media
Hackathon participants violating these rules may be sanctioned or expelled from the hackathon  at the discretion of the hackathon organisers.