Assignment 4: Weather API

Provided Code

Clone your repo using this link: https://github.com/kiboschool/programming2-w4-fileio

Setup

Documentation about the API and the format of the responses is available at http://www.7timer.info/doc.php. You will need to reference this material as you complete the assignment.

Just like the videos, we will be adding to the weather API example! You should aim to complete all the following parts. But before you dive into completing the tasks below, spend some time reading the code to familiarize yourself with what is provided.

Part 1: Add a New City

Add a new city. You can usually find the coordinates for a city on the wikipedia page for a city, then look on the panel on the right side for "coordinates".

Once you have the coordinates, format them the same way that the existing entries are written. Note that "S" or "south" is negative and "N" or "north" is positive. Add the new city to the list in map_city_to_coords and try it.

Part 2: Wind Direction

Add a feature to the program, so that it shows the wind direction alongside the temperature. Show the wind direction in a descriptive way, for example display "from the southwest" instead of "SW" and "from the north" instead of "N".

Also, you will have to reference the API documentation in order to interpret what the values contained in the API response actually mean.

Once completed, the output displaying the weather data for a particular hour should look like the following:

The temperature is 10 and the wind is approaching at 3.4-8.0m/s (moderate) from the south

Hint: Open the api_output.json file and look for wind. Remember that a dictionary can contain other dictionaries. It's sometimes easier to get the data in two steps.

Part 3: Avoid Saving to File

Currently the program saves the json information to a file, and then reads the information back in from the file. This is unnecessary - isn't there a way to get the information without needing to save to a file first? Modify the program so that it doesn't save to a file.

Hints:

Right now the get_api_results function does not need to return anything, but you can change it so that it will return a value at the end.
The data type returned by the decode() method is a string.
And remember that there is a function json.loads() that loads from a string instead of a file.

Grading

Criteria	Proficient	Competent	Developing
Coding Style (20%)
1. Indentation and Formatting	Code is consistently well-indented and follows PEP 8 formatting guidelines.	Code is mostly well-indented and follows PEP 8 guidelines with minor deviations.	Code lacks consistent indentation and does not follow PEP 8 guidelines.
2. Naming Conventions	Meaningful and consistent variable/function/class names following PEP 8 conventions.	Mostly meaningful names, with occasional inconsistencies.	Variable/function/class names are unclear or inconsistent.
3. Comments and Documentation	Comprehensive comments and clear documentation for major functions and complex logic.	Adequate comments explaining major sections of code.	Lack of comments or insufficient documentation.
4. Appropriate Use of Language Constructs	Demonstrates advanced understanding and appropriate use of Python language constructs (e.g., list comprehensions, generators).	Generally applies language constructs correctly, with occasional lapses.	Misuses or misunderstands key language constructs.
Persistence (50%)
5. Completeness	Evidence that all components of the assignment were attempted. All functionality present.	Evidence that most elements of the assignment were attempted. Most functionality present.	Little evidence of completion of work. Incomplete or major functionality missing.
6. Timeliness	Assignment started early (based on GitHub data). GitHub commits show steady progress. Submitted on time.	Assignment is submitted late but GitHub data demonstrates an early or reasonable start date, with significant iteration on arrival to solution (i.e., multiple commits showing progress)	Submitted late. GitHub repository data shows late start and minimal iteration.
7. Use of Resources	Assignment is fully complete and provides all functionality. If assignment is not fully complete, student attended office hours (or additional help sessions) and/or asked high quality and timely questions on Discord.	Assignment is not fully complete and there is minor evidence of effort to get assistance on assignment (e.g., office hours attendance or Discord discussions).	Assignment is incomplete and no evidence of seeking assistance.
Correctness (30%)
8. Test Cases	Percentage of automated test cases that pass.

Evidence of Persistence:

In the event that you are unable to get your program fully functional, you will receive partial credit based on your evidence showing the amount of effort that went into learning the underlying concepts to complete the assignment or that you persistently sought appropriate assistance. Examples of persistence may include, but is not limited to, the following: Git commit history showing evolution of your program, attendance to office hours (Instructor or TA), asking thoughtful questions in the appropriate Discord forums, formation of study groups, completion of additional practice exercises, reading of third-party resources, etc.

To receive partial credit, you must create a file called PERSISTENCE.md in your GitHub repo alongside the README.md file, and include your evidence of persistence, for example, links to your Discord questions, narrative explaining dates and times of office hour sessions that you attended and what you learned, links to resources that you referenced, links to ChatGPT conversations that you initiated (focusing on concepts not just getting answers), etc. The better you can demonstrate your work on learning, the easier it will be to provide partial credit, so be thorough. Make sure that file is properly committed to your repo, and included in your Gradescope submission.

Submitting Your Work

Your work must be submitted Anchor for degree credit and to Gradescope for grading.

For coding tasks involving Github Classroom:

Ensure that you commit and push your local code changes to your remote repository. (Note: In general, you should commit and push frequently, so that you have a backup of your work, so that there is evidence that you did your own work, and so that you can return to a previous state easily.)
Upload your submission to Gradescope via the appropriate submission link by selecting the correct GitHub repository from the drop-down list.
Export a zip archive of your GitHub repository by visiting your repo on GitHub, clicking on the green Code button, and selecting "Download Zip".
Upload the zip file of your repository to Anchor using the form below.

For cases where you answer questions on Gradescope:

Complete the work in Gradescope by navigating tot he appropriate link.
Export it as a pdf using th Google Chrome plugin: https://gofullpage.com/. This plugin will do multiple screen captures while scrolling through your document, and then stitch them into a pdf that you can download.
Upload the generated pdf to Anchor using the form below.

For any work completed outside of GitHub or Gradescope:

Take either screen captures of your work or export a pdf showing your complete work.
Submit the materials to Gradescope via the appropriate submission link for the course.
Upload the screen captures or pdf files to Anchor using the form below.

Note: Anchor submissions can occur at any time during the term, but it is critical that you upload all of your work to Anchor before the last day of the term. Gradescope submissions must be submitted before the deadline (or the late deadline, if applicable).

Programming 2