This is the delta version of Advanced GIS (Spring 2021).
I plan to utilize GitHub as our main repository for this course. If you have never used GitHub before, don't worry, I only plan to use a limited amount of GitHub's capabilities, namely: a place for sharing documents (Code), a place for tracking questions and answers (Issues), and place for group conversations (Discussions).
First, when you log in, you should see a welcome screen that includes a list of the repositories you have access to and the teams in which you are a member. Everyone in the Spring 2021 class is a member of the delta-squad team. This team is in charge of the advgis-delta repository, a cloud-based storage for documents (Code), issue tracking (Issues), discussions (Discussions), and a wiki (Wiki).
My plan is to use:
Please familiarize yourself with this web interface.
All textual elements (including comments and discussions) use Markdown syntax, so you can embellish your responses with bold, italic, strikethrough, as well as create ordered (numbered) and unordered lists, tables, and embed images or links.
See Resources links below for more.
The welcome video and getting started series is now available on YouTube.
This is an asynchrous remote course. I know a lot you are concerned about time management and collaboration.
First, let's take a look at time management.
Open the Issues tab on our GitHub repository. We are one group trying to solve several geospatial problems. Your goal is to find the most efficient and effective way to solve these challenges. Through communication and collaboration, I expect that you will learn new methods and incorporate your own personal touches for devising creative solutions.
The first issue that I created is a checklist. I have made every effort and tried to create an outline that is both chronological and organized. Treat this as a roadmap, as I will use this as the template for your final evaluation.
Please copy the Markdown from the issue template that I have created, open a new issue, title it "Your GitHub username's Checklist," assign yourself as the responsible party, label it "Checklist."
Every issue has a unique number assigned to it---just like an OBJECT ID in a vector's attribute table. Your issue's number is also associated with a unique website address. The shortcut to referring to issues is using the hash (#) key followed by the unique issue number. This gives you a way to track and refer amongst issues in the GitHub issues tracker.
Each issue also has a comments section where you (and others) can provide feedback. You can tag members of our team by using the at-sign (@) followed by their GitHub username. This allows you notify people when you have a question for them. Please feel free to tag me on certain issues or discussions.
As you work through your checklist, please make comments to help describe what you did, when you did it, how long it took you, and any other references you might need. Feel free to link to other resources, websites, or tag other people or issues.
You can see how the Issue tracker allows us all to stay connected by sharing and communicating what you have done, what you are doing, and what you are currently working on. To help us keep on track, I am asking that you complete a weekly comment in your checklist issue with the following structure:
# Weekly Report 2021-01-01
Summary of accomplishments. _This is only an example. Modify as you see fit._
| Project/Task | Status |
| :----------- | :----- |
| Independent work | Ongoing |
| Tutorials | 3/8 completed |
| Client meeting | Started |
| Esri Credits | 960/1000 |
### Independent Work
Here you can itemize and/or describe the work you did this week, including:
* readings (3 hours)
* tutorials (1.5 hours)
* anything that checks off an item in your checklist
Be sure you include a little summary with each task completed.
It will help you write your final report.
Also, try to estimate (or account) for the amount of time you spent on each activity.
### Projects
Here you can discuss the current status of your projects.
You may create headings to organize your project.
_Note the hierarchy with the hash level, # (heading lv 1), ## (heading lv 2), ### (heading lv 3), #### (heading lv 4)_
Considere also including a time table for each project you are working on.
See below for an example.
Time Table.
| # | Milestone | Description | Completed |
| --- | :-------- | :---------- | --------: |
| 1 | Choosing a paper | I'm debating between two options. Still need to do some preliminary research on data files. | 1/8/21 |
| 2 | Preliminary data research | Searching for DEM raster file for second paper; first link I found was broken. | 1/7/21 |
### This week's challenges
Here you can bring up the major challenges you faced this week.
It can be anything that held you up or slowed you down.
If you are up to the task, create separate issues for these challenges and link to them here.
Remember, issues can be commented on by anyone, including your instructor.
This is a great way to reach out for help or poll the class for advice.
You can drag-and-drop images (such as screenshots) to help provide context.
### To-do items
What's your plan for next week?
Use this to help you plan ahead and prioritize your tasks.
Nothing beats a good checklist.
Consider making some of your own.
- [ ] Be sure to do this first next week
- [ ] If you have time, research [this](#) topic.
- [ ] Visualize [this](#) dataset.