Geosoftware II at ifgi - WiSe 2020/11

Open Earth Observation Data Processing

Teachers: @nuest, @edzer, @DaChro

LSF/QISPOS

Learnweb course

Initial training resources

Handouts for presentations on technical background and concepts required for this year's project task in Geosoftware II at ifgi. These handouts are the core of the preparation of a topic by each student/pair of students. The handout should be prepared in a manner so that fellow students can use it as a starting point for getting up to speed on the new topics and making decisions during their project work. The presenting students remain experts on the topics for future questions and are very welcome to update the documents in this repository during the course.

Due date: November 4th, 2020, 14:00 hrs CET.

Process

1. Fork this project
2. Do your research
3. Create a folder for your topic (topic-title-no-capitals-with-hyphens-but-not-underscores)
4. Add a file handout.md file in your folder
   • Take a look at the markdown syntax
   • Split up your work into logical sections and use informative names for each of these
   • Add any additional files needed (graphics not already available online, for example) to your folder
   • Add your GitHub username at the beginning of the document, e.g. @nuest
5. Add a git tag handout-submission-<name> and push it to your fork
6. Send a pull request before the submission deadline containing your handout (not the presentation)
   • Give the pull request a useful name and description, and @-mention all contributors in the pull request description
   • Implement the feedback by the lecturers
   • Update the pull request by pushing the changes to your repository
7. Create a presentation based on your handout (optional: add it to your folder)
8. Present at the seminar (approx. 10 minutes + 5 minutes questions and discussion, prepare to fill the 5 minutes with additional content if no questions are asked)
9. Incorporate feedback from the presentation into the handout and update the pull request (don't forget to sync your fork/merge upstream master beforehand)
10. If you see an error in or want to add information to a colleague's handout ...
    1. Make a comment to the open PR if it is still open
    2. At any later point in time: make the changes yourself (fetch and merge into your fork, make the changes, send a pull request to the original author of the topic and present your changes, original author may then merge and send a PR to the main repository)
11. Teacher merges the final handout version after grading

Evaluation

The evaluation is conducted based on the content of the handout, the presentation itself, and the discussion afterwards during the course. Be prepared for questions by your fellow students and the teachers, but also prepare some additional content or questions yourself so that you can stick to (= fill up completely) your presentation time slot.

Topics & content

Make sure you cover at least the mentioned keywords. More is better, but only really better if you evaluate alternatives, phrase opinions, and provide guidelines for your fellow students.

See https://github.com/Geosoft2/geosoft2-2020/issues?q=is%3Aissue+is%3Aopen+label%3Atopic.

Please provide a draft of the covered content or any questions as soon as possible through commenting on the respective topic's issue, to retrieve feedback and adjust before you spend too much effort.

Individual reports

After the submission of the final project material, each student writes an individual report. This is to aptly grade individual contributions to the project work, which ideally is reflected by the student's commits (or at least co-authored commits to the code repository (because it is a programming course), but sometimes also takes other forms. The report is written from the personal perspective, includes the following contents/sections, and is submitted as a single document in PDF format via LearnWeb which is at most 3 DIN-A4 pages.

• contributions in the form of commented pull requests (or commits) of most relevant contributions, incl. noteworthy lessons learned or challenges
• learning achievements, i.e., most important lessons learned during the course, be they practical or organisational
• role(s) in the team taken during the course of the semester, potentially connected with the leanings and contributions

Further resources

• Coding guidelines (How to write good code?) are in code-guidelines.md.