Important Participant Info

Shortcuts on this page:

What to bring

Open Earth Observation and Remote Sensing Data

Building a Team

Rules of Conduct

 

What to bring

The most important thing is to bring your ideas, spirit of fun and helping others!

Tech and equipment

Most participants form teams and work together and allocate different tasks to different team members. For instance you may be great at ideating and creating a marketing pitch through a storyboard. Another team member may mine data for the concepts so needs a computer and someone else could focus their energy on elements of a winning video. So not everyone needs a laptop but if you have one then bring – for some tea members a tablet would also be enough.

– Laptop
– Mouse and mousepad
– Adaptors and power cables (some may be supplied)
– Headphones
– USB thumb drives, external hard drives
– Phone and charger
– Camera or video equipment – although not required

Can I leave equipment at the venue overnight? We discourage this, however recognise some people like to have their monitor at the events. Please be aware that you do this at your own risk and organisers accept no responsibility for any possessions left unattended at the venue.

The other stuff

Hackathon is great fun, but it can also be an intense and stressful weekend at times. Bring what you need to stay productive and comfortable.

– Comfortable clothing
– Music or podcasts
– Any data you’ve downloaded for the event, or notes you’ve made
– Your favourite snacks and drinks (we’ll provide some meals and snacks!)
– A water bottle
– Pen, paper, maybe your notebook
– Any medications you may need
 

 

Open Earth Observation and Remote Sensing Data

Get yourself prepped with this short presentation: an overview of ESA, NASA, EstHUB and other opendata data portals and tools, how to access, download and work with remote sensing and geospatial datasets!

Check this short presentation for resources and learn yourself some GIS:

https://kodu.ut.ee/~kmoch/SpaceTech_2019_open_geodata/#/1

NASA Open Data

Some background reading about virtual “Data Bootcamp”, and start looking into NASA’s open data portals:

• https://open.nasa.gov/explore/datanauts/
• https://open.nasa.gov/open-data
• https://open.nasa.gov/media/databootcamp/?prev=/explore/data-bootcamp/&prev_title=Data%20Bootcamp

Consider checking ideas and projects that have been successful in the last years:

– https://2018.spaceappschallenge.org/ and for the years before, 2017…

ESA Open Data

We want you to mesh data from NASA with data from ESA (European Space Agency), Europe’s counterpart to NASA. It might even be of wider interest to both NASA and ESA data users, which websites are better to navigate, or what different types of data is available:

• ESA Open
• http://open.esa.int/
• https://earth.esa.int/web/guest/home
• http://www.geoportal.org/
• https://earth.esa.int/web/guest/data-access/how-to-access-esa-data
• https://sentinels.copernicus.eu/web/sentinel/user-guides
• https://earth.esa.int/web/guest/data-access/browse-data-products

 

 

Building a team

We have set-up a public collaboration repository. Here we want to fill in info for the teams and ideas and link their repositories:

https://github.com/SpaceAppsTartu/2019/wiki

If you think you have a great idea for a project and/or you would like to gather a team for the hackathon, announce your idea and proposed team name. At the start of the event you will pitch your idea to the participants, so they can join your team.

Please have a look at the role descriptions (below). Ideally, you can identify the role that best suits you and each team needs to have at least one of each. 

THE HACKER
Resembling MacGyver with your ability to wield code, programing languages, tools or hardware gadgets, everyone else get dizzy trying to keep up with you when you are plugged into the Matrix.
Examples: Backend Ninja, Fullstack Dev, Maker, Engineer
The Hacker role is mainly meant for Dev/Coding, frontend/backend programming skills. But we also suggest this role for also less programming related capabilities around hardware, engineering, building things and making things work in general.

 

THE VISIONARY
We all have problems and you want and know to solve them. You come to the hackathon with an idea. Your passion and creativity to come up with and explore solutions motivates others to get behind the problem as well.
Examples: Product Manager, Primary and secondary Research/Analysis, Domain Expert, Scientist
The Visionary role has in-depth knowledge about some specific field, for example, geography, space, biology, history etc. This knowledge helps to find niches that add advantages. Data analysts, healthcare professionals, teachers, and other specialists are also visionaries how provide valuable insight into how a product should be designed and how will be adopted.

 

THE DESIGNER
We all love pretty and good looking things. You can make beautiful things and you make things beautiful.
Examples: Web Design, UX/UI design, Branding, Marketing, Draw beautiful things
The Designer role is primarily concerned with the beautiful design, presentation and usability of about anything that your team creates. It’s all about colours, shape and user experience.

 

THE HUSTLER
You are a doer, you get things done. You know how to sell anything to anyone. You enable and support everyone else, and do the things which are outside of others’ fields. You resolve road blocks so the the team can keep working away.
Examples: Team lead, Support, Sales
The Hustler role is typically a hybrid of a leader, a sales person and the guy who just gets stuff done. You organise resources and make sure everyone has something to do and the team can work at full efficiency.
Please identify and select which role is most suitable for you.

If you really can’t find a role for you, don’t worry, we’ll find suitable team for you based on the areas you feel most comfortable with via a skillshare wall.

 

 

Rules and Code of Conduct

 

Be respectful. Be thoughtful. Be open. Be awesome.

All design elements, code, hardware builds, etc. for your project must be created during the event. You can plan and discuss with your team in advance. Written documents and design sketches are allowed. You may also incorporate pre-existing material that is freely available to the public into your project, such as public domain images, Creative Commons music, open source libraries, existing APIs and platforms, and the like.
Teams must be comprised of 4-6 people.

The team members must spend the majority of their design/coding time at the hackathon location.
Any intellectual property developed during the hackathon will belong to the team that developed it, but data and source code most be made available under an open data or open source license.

This hackathon is a community event intended for learning, collaboration, and engagement. We value the participation of each member and want everyone involved to have an enjoyable and fulfilling experience. Accordingly, all staff and participants are expected to show respect and courtesy to others throughout the event. To make clear what is expected, all staff, participants, volunteers, mentors and judges in the hackathon are required to conform to the following Code of Conduct. Organizers will enforce this code throughout the event.

*Be Respectful* Be kind to others. Do not insult or put down other attendees. Behave professionally. Remember that harassment and racist, sexist, or exclusionary jokes are not appropriate for this event

*Be Thoughtful* In the spirit of education and inclusiveness, there may be minors participating in the hackathon. Keep this in mind when speaking.

*Be Open* We welcome attendees from all backgrounds. This event is about increasing the overall amount of learning, partnership, and engagement.

*Be Awesome* and Have Fun Hack, meet new people, get creative, and have a good time. Getting something meaningful done within such a short amount of time can be stressful, but we’d like to encourage everyone to take a break every now and then to relax and enjoy the event.

In other words, use this time and space to enjoy the process of hacking! Whether it’s your first time at a hackathon or your 50th, it’s always good to remember not to focus so heavily on the end result that you don’t enjoy the process of making it happen. And bear in mind that the process of getting productive at a hackathon can be a bit messy and slow to start.

All of this to say: we want this hackathon to be a safe place to create, learn, and build up a supportive community. Thank you for being a part of it!

 

Media

You grant us a release to be photographed and for this material to be shared via social media and included in case study materials about the Hackathon.

You acknowledge and agree that your image, name and voice may be used by organisers to produce any of the following Hackathon-related content:

– Digital video
– Social media content – inclusive of LinkedIn, Twitter, Facebook, blogs, and others
– Print
– Photography

We respect your privacy and will not share your personal information submitted through the registration process with third parties without your prior consent.

Rules and code of conduct based on Valley Hackathon and guidelines from Hackbright Academy.