Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Caroline Edwards - Master Checklist #12

Open
ceedwards1 opened this issue Sep 7, 2021 · 0 comments
Open

Caroline Edwards - Master Checklist #12

ceedwards1 opened this issue Sep 7, 2021 · 0 comments
Assignees
Labels
checklist Keeping on track

Comments

@ceedwards1
Copy link

ceedwards1 commented Sep 7, 2021

Getting Started

  • Review the academic calendar.
  • Review the syllabus.
  • Update your ArcGIS Online (AGOL) profile to include a personalized photo or avatar and your areas of special skills (e.g., "I'm good at data vis", "I'm a StoryMap master", or "I literally know how to use Python").
  • Create and/or update your GitHub account.
    • Includes your preferred name (so we know who you are)
    • Includes the same profile image you used for your AGOL profile (to help us know it's you)
  • Choose a focus: programming or analysis (delete the one you don't want).
    • Programming focus: you already have some experience using Python, so begin your journey by looking at Notebooks, the cloud-based programming environment for solving your geospatial problems
  • Join the GroupMe chat (email your professor your preferred email for GroupMe)
    • Like a comment or just say "hi"
  • Log into AGOL and make sure you are a member of the "AdvGIS - Fall 2021" group
  • I completed the Ice Breaker challenge on the first day of classes

On GitHub

  • Familiarize yourself with the Markdown syntax (see resources below)
  • Introduce yourself to the class with a comment on the Welcome Discussion.
  • (Wait until you hear from your instructor that it's okay to do this) Create a new issue on our repository's Issues, title it with your name (e.g., Davis's Checklist), copy-and-paste The Master Checklist content to the "Write" section, under Assignees: assign yourself, under Labels: checklist. Be sure to note your issue's unique number.
    • This is your copy of the master checklist
    • Use it to keep track of your accomplishments as you go through the semester
    • You may also see how your peers are progressing to judge your own time management
  • Create your Report Wiki on our repository's Wiki page
    • This is where you submit your weekly tasks, goals, and accomplishments
    • See Home page for instructions

The Consultancy

  • Find a team (in groups of up to three people) to work together
  • Form your consultancy.
    It should have:
    • Name: Carto Consulting
    • Members: Caroline, Dominic, Matt, Lydia
    • Logo: CARTO
    • Slogan: Put on your Thinking Map
  • Create a publicly accessible website and provide the following:
    • Site URL: CARTO consulting
    • Your site should include at least the following:
      • Overview page (who we are / what we do)
      • Blog page (should be updated at least weekly including milestones, methods and other relevant updates)
      • Geoethics page (define geoethics and how you apply it to your work)
  • Add your consultancy group details here.

The Reproducibility Project and Client Meeting

  • Propose a paper for approval here.
  • Update your website with the following:
    • Link to article you are reviewing
    • Video (~20 min or less) that summarizes your article (background, methods, and results + your first impressions)
    • Video (~10 min or less) on data collection or creation (w/ map or visual)
    • Audio/video (~ 5 min or less) on a geoprocess or challenge you faced
  • Prepare a publicly accessible progress report for your client meeting
    • It may be your website, slideshow, StoryMap, or another web-accessible document. Make it clear on your website how / where to access it.
    • Be sure to include visual aids
    • Remember that your client is not a GIS expert; tone your report for a lay audience
  • Schedule a progress report meeting with your client here
  • Write down your thoughts regarding the experience of working through this project and the client meeting in your weekly report
    • Copy and paste your response here:
    • So far the reproducibility project has gone very smoothly. Each week during our class meeting we decide our focus for the week - whether it be simply reading the article to get a grasp of our tasks, assigning each map to reproduce, working in ArcGIS Pro, creating the final videos, or preparing for our client meeting. Our group has done a good job of staying on task and helping each other when one is stuck. Our biggest challenge was knowing where to start with the reproducibility project and which maps to reproduce, but once we got started it's been smooth sailing.
  • Rate your paper's level of reproducibility (based on your opinion)
    • The levels are:
      • S: satisfactory (methods are clear and reproducible)
      • M: marginal (it is hard to say because some methods are unclear and/or data are outdated or not readily available)
      • U: unsatisfactory (there is no known way to reproduce these methods)
    • Our consultancy gives our paper the rating of M for the following reasons: At a first glance, the paper appeared to be reproducible; the tools used to create each map were clearly defined, the maps were simple enough, with one tool used for each, and the data sources were clearly stated. But upon recreation, we ran into issues with tools and data that yielded different results and different looking maps from the original. With all three analyses (the GWR, Hot spot analysis, and cluster analysis), the inputs to the tools were not described, so we used the defaults assuming that the paper would have specified a depart from the default. This produced different results, with the symbology for the maps looking completely different from the original, and the cluster analysis saying it was clustered when the original said it was not. Part of this could be attributed to the outdated software used in the original article (ArcMap), but it is unclear exactly what was different between these tools in ArcPro and ArcMap. Going further, the lack of inputs provided for the regression made it impossible for the GWR to run, and it was unable to be recreated.
      Additionally, we had issues with the data collection. The grocery store dataset used in the article had different points now than in 2015, and it was unclear what categories the article considered grocery stores; is a ‘ethnic market’ or ‘convenience store’ a grocery store? Additionally, with the auxiliary roads, the data sources no longer existed and were incredibly hard to find similar results. Although we ultimately found a file that looked the same as the original, it was much harder to find than it should have been.

The Special Works Solutions

  • Prepare two methodologies for solving one of the special works projects
    • The special works project should emphasize a skill set that one of the consultants identified as a weakness in the pre-semester survey
    • Solutions may be typed or recorded
  • Solution Method 1:
    • Solved to "basic" level
    • Solved to "intermediate" level (tick both boxes)
  • Solution Method 2:
    • Solved to "basic" level
    • Solved to "intermediate" level (tick both boxes)
  • We posted our solutions to our consultancy website
  • We presented a discussion of our solutions in class or on GitHub

The Novel Datasets

  • Our consultancy created a novel dataset
    • in a file geodatabase and/or
    • in GeoJSON format
  • We posted a link to our dataset (with a license, description, and relevant metadata) to our consultancy website
  • We presented a discussion of our dataset (and the methods for its creation) in class or on GitHub

Engagement

  • Sign up here to schedule to contribute at least once to each of the five weekly topics.
    If you are a certificate student, instead sign up for one topic each week.
  • Each week, respond to and/or engage with the five weekly discussion posts.
    If there is no natural response, then please respond with a reaction to the comment.
    • I responded to more than five discussion posts on GitHub
    • I responded to more than ten discussion posts on GitHub
  • Complete your weekly reports.
    • Your personalized issue link (from the new issue you created above): _______
    • Reports completed:
      • Week 1 (optional)
      • Week 2 (optional)
      • Week 3
      • Week 4
      • Week 5
      • Week 6
      • Week 7
      • Week 8
      • Week 9
      • Week 10
      • Week 11
      • Week 12
      • Week 13
      • Week 14
      • Week 15
  • Share a selfie where you are holding or standing next to a physical item within Swem library (e.g., an open book, a painting, or a map) to our GitHub discussion board with a short description of the item and how it relates to a geospatial topic

Become More Geoethical

  • Listen to the lecture on Geoethics
  • Complete the Google Takeout challenge
  • Find and share an article that has a geoethical concern and share it during your discussion topic week
  • Listen to an episode of the VerySpatial podcast; use the search bar to filter results for "ethics" or other ethical term, phrase or idea
    • Link to episode you listed to: Episode 632
    • I shared a discussion on 10/19/2021 that summarizes the ethics topic in the podcast linked above in class or on GitHub
  • Listen to one or more student examples here.
  • Research, script, and record a podcast episode on the topic of geoethics, including at least three (3) sources or citations
    • Share your podcast

Managing Your Data

  • I read about metadata (e.g., here)
  • I organized the items I own on AGOL.
    • This includes creating folders and/or updating item names
    • This includes updating the metadata (summary, description, terms of use, tags, and credits (attribution) appropriately on all shared items (organizationally, publicly or with groups)
    • I shared a plan on how I organize my AGOL content and/or a system for tagging items in class or on GitHub

Getting Started With Notebooks

Additional Practice

Complete at least three (3) hours or six (6) tutorials from one of the following sites: (1) Esri Academy; (2) ArcGIS Developer Guides; (3) Learn ArcGIS; (4) other approved resource (*include names of and links to each tutorial completed)

Final Touches

  • I updated this checklist to match my accomplishments (you are not required to complete everything on this checklist)
  • I completed the course evaluation
    • Please include your thoughts on the course structure, topics, things that worked, and things that didn't work for you
  • I am signed up for the CGA listserve
    • The link is available on the CGA homepage
  • I grant unrestricted permission to use media (e.g., web content, audio or video) I created for educational purposes
    Note that you are not required to tick this box and, at any time, you may request that materials you made for this class be removed from use in past, current, and future classes
@ceedwards1 ceedwards1 added the checklist Keeping on track label Sep 7, 2021
@ceedwards1 ceedwards1 self-assigned this Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
checklist Keeping on track
Projects
None yet
Development

No branches or pull requests

1 participant