nicholasob7 / Visualize-Covid-Data

Making Visualizations with Covid Data

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Visualize-Covid-Data

Making Visualizations with Covid Data

Objective

Create responsive website that is user-friendly and easy to find information about COVID 19

Collaborators

Nick Chitsamrerng, Sameera Begum and Nicholas O'Brien

Instructors

Nick Do and Kris Pritchard

Project

Organized in fulfillment of a group project assessed as part of a final mark for the AWS restart course Unitec NZ Semester 1 2022

Project Development

Organizing live data to facilitate comparison and analysis with static historical data and interpretation. Easy to understand, update, upgrade.

Data Source

disease.sh - Open Disease Data API

https://disease.sh/

Requirements

charts.js

https://www.chartjs.org/

moment.js

https://momentjs.com/

Day 1-28/06/2022

Tuesday

Meeting 1.

  • Held meetings at 10 am with Nick Chitsamrerng, Sameera Begum, and Nicholas O'Brien.
  • Team agreed to shift from an ecommerce website to a real time world statistics site.
  • Currently favoring NZ based statistics.
  • Focused on Covid 19 relavent data and analysis.
  • Contemplating Tourism/GDP or Health/pop'n demographics.
  • Organized meeting with Nick Do at 4pm.

Meeting 2.

  • Held a meeting at 4pm with Nick Do, Nick Chitsamrerng, Sameera Begum, and Nicholas O'Brien.
  • Nick Do outlined a structure for project plan and first steps.
  • Investigated a number of data sites.
  • Arranged to hold a zoom meeting the following day at 10.30.

Day 2-29/06/2022

Wednesday

Meeting 3

  • Held discord meeting at 10.00 am with Nick Chitsamrerng, Sameera Begum, and Nicholas O'Brien.
  • Sameera noted difficulties with Stats NZ website, will have to recheck site later tonight or tomorrow after signup period indicated during Sameera's live chat.
  • Nick Chitsamrerng shared a site called disease.sh with api suitable for project.
  • Sameera called an end to the discord session and led us into a zoom call with Nick Do which she had organised the day before.

Meeting 4

  • Held zoom meeting at 10.30 am with Nick Do, Nick Chitsamrerng, Sameera Begum, Nicholas O'Brien.
  • Shared disease.sh site and its major data source website with Nick Do.
  • Sameera expressed concern that the disease.sh was already a finished product and might not fulfill our project goals.
  • Nick Do indicated that in fact the api in disease.sh would be much easier to customise within a tailor made front end.
  • Nick Do continued to specify minimum requirements for the project involving a minimum 3 visualizations with at least one interactive tool each.
  • Nick Do advised us to sign up for Miro, generate 6 proposals for at least 3 visualizations drawn from disease.sh api.
  • Nick Do advised he would be available for a follow up meeting the next day at the same time.
  • Nick Do requested we have a miro whiteboard prepared for the following meeting sceduled 10.30 30/06/2022.
  • Sameera posed the question of potentially changing the project to one which was more focused on raw data processing.
  • Nicholas O'Brien objected to changing the current project and suggested we manage the basic structure of the current project and potentially add on more specifically data processed components after initializing the functionality of a world map and time scale.
  • Team agreed to move forward with the current project.

Day subsequent actions

  • Nick C generated a miro team, invitations sent to team members.

Meeting 5

  • Held discord meeting at 8pm with Nick Chitsamrerng, Sameera Begum and Nicholas O'Brien.
  • Using discord and Miro the team organised 6 proposed visualisations to pitch with Nick Do the following morning.
  • Nicholas O'Brien identified artefacts in some New Zealand data which exhibited discrepancy between daily vaccinations totals and overall total vaccinations updated.
  • These discrepancy were notable for a correlation to another data sets.
  • Team resolved to inquire Nick Do concerning "dailyPerHundred & dailyPerMillion" in vaccinations per country.

Day 3-30/06/2022

Meeting 6

Presenting 6 Proposals

  • Held microsoft teams meeting at 10.30am with Nick Do, Nick Chitsamrerng, Sameera Begum and Nicholas O'Brien.
  • Using teams Miro Whiteboard six proposals for visualizations were offered up to Nick Do.
  • Nick Do classed in turn all six proposals as either easy, medium or hard.
  • Team elected three seperate visualizations with an example of easy, medium and hard difficulty levels.
  • It was suggested that we may gain time to incorporate all six proposals into the deployment.

Identifying a need to apply data science

  • Nicholas O'Brien raised a discrepancy in the NZ data for vaccinations administered. Nick Do commented on this.
  • The team agreed it to be a worthy exercise in data science that we take note of this discrepancy and it's management in contents presented to the user interface.

Forming 3 required workstreams

  • Nick Do directed the team to split into 3 workstreams.
  • The first workstream was to research libraries desirable for use in the project.
  • Nick Chitsamrerng elected this work stream.
  • The second workstream was to research cloud solutions for a react project.
  • Sameera Begum elected this workstream.
  • The third workstream was to create a react app, remove unnecessary files and upload it to Github.
  • Nicholas O'Brien elected this workstream.
  • Nick Do advised the first two tasks may take 2-3 days to complete.
  • Nick Do advised that the third task should be complete for the following day in order to begin additional components of the third workstream the following day.

Day 4-1/07/2022

Meeting 7

  • Held a microsoft teams meeting with Nick Do, Nick Chitsamrerng, Sameera Begum, Nicholas O'Brien.
  • Nick Do enquired of our progress.
  • Team related progress amounting to close to half of the tasks provisioned per team member.
  • Nicholas O'Brien had deleted too much 'rubbish' from react app and had to reload react app and proceed with more caution.
  • Sameera had closed in on about half of the code required for cloud solution scripts.
  • Nick Chitsamrerng had closed in on a couple of potential solutions and was in progress.
  • Nick Do related follow up and ongoing task for all team members and requested completion of set tasks in preparation for a Monday Meeting.
  • Nick Do closed the meeting.

Week 2 Day 5-4/07/2022

Meeting 8

  • Held meeting micro teams meeting with Nick Do, Nick Chitsamrerng, Sameera Begum, Nicholas O'Brien.
  • Nicholas had completed a hard coded version of the api calls in different files.
  • Nick Do asked him to combine all the api calls into a single file and re-factor.
  • Nick Chitsamrerng had found some libraries necessary for chart visualization.
  • Nick Do installed charts.js as an example of a library to use.
  • Sameera Begum had completed more of her cloud solution

Week 2 Day 6-5/07/2022

Meeting 9

  • Held meeting with Nick Do, Nick Chitsamrerng, Sameera Begum.
  • Nick Do discussed react-simple-map, sending a link to simple-map sandbox, targeting Nick Chitsamrerng and Nicholas O'Brien.
  • Nick Do discussed cloudfront distribution and S3 buckets with Sameera.

Week 2 Day 7-6/07/2022

Meeting 10

  • Held meeting with Nick Do, Nick Chitsamrerng, Sameera Begum, Nicholas O'Brien.
  • Nicholas was still working on refactoring.
  • Nicholas had been watching several tutorials.
  • Sameera had made further progress.
  • Nick C had been watching several tutorials.
  • Nick Do urged us to keep working hard and was pleased with the groupds progress.

Week 2 Day 8-7/07/2022

Meeting 11

  • Held meeting with Nick Do, Nick Chitsamrerng, Sameera Begum, Nicholas O'Brien.
  • Sameera had completed the scripts for a cloud solution.
  • Nicholas had completed a front end tutorial and begun several others.
  • Nick Chitsamrerng had uploaded a number of chart.js files.
  • Nick Do said that Nicholas should refactor the api calls without making them components.

Week 2 Day 9-8/07/2022

Meeting 12

  • Held meeting with Nick Do, Nick Chitsamrerng, Nicholas O'Brien
  • Nick Do took the other two Nicks on a code follow and demonstrated progress via the console.
  • Nicholas remarked on the similarity of the solution to the simplicity of organising a main file from the previous course assignment.

Week 3 Day 10-11/07/2022

Meeting 13

  • Held meeting with Nick Do, Nick Chitsamrerng and Nicholas O'Brien
  • Nick Do took another code follow on the topic of transforming data from api calls into data which could be plotted to a chart.
  • Nick Do installed momentsjs.
  • Nick Do advised Nicholas ignore deprecation warnings and not uninstall react-scripts again.
  • Nick Chitsamrerng forwarded a github tutorial from "Tech with Tim" to Nicholas.
  • Nicholas was very pleased with the content.

Week 3 Day 11-12/07/2022

Meeting 14

  • Held meeting with Nick Do, Nick Chitsamrerng, Nicholas O'Brien.
  • Nick Do a subsequent code follow to complete a rudimentary example calling live disease.sh data into a line chart.
  • Nick Do assessed the task as difficult and wrought with idiosynchracies of javascript.
  • Nick Chitsamrerng and Nicholas O'Brien were impressed by the complexity of the task.
  • Nick Do re-iterated the undesirability of the 'recovered' data available on disease.sh as it ended on 8/04/2021.

Subsequence

  • After the meeting Nick Chitsamrerng and Nicholas O'Brien agreed that adjustment of the yAxis display for goal visualizations was the most important factor in effective data display via chart.js.
  • Nick Chitsamrerng and Nicholas O'Brien also agreed that 'recovered' data was unsuitable unless a time span was able to be solved for disease.sh data.

Week 3 Day 12-13/07/2022

Meeting 15

  • Held meeting with Nick Do, Sameera Begum, Nick Chitsamrerng, Nicholas O'Brien.
  • Nick Chitsamrerng and Nicholas O'Brien reported little luck in sourcing information on transformation of the yAxis in the documentation.
  • On investigation Nick Do agreed that the official documentation for react charts2 and charts.js was not helpful for logscale.
  • Nick Do sourced an open source solution for the problem and adjusted the yAxis to a logarithmic progression.
  • Nicholas O'Brien shared a chart of vaccinations he had worked on the previous night which compiled but did not plot data to a display.
  • Nick Do explained that the reason for the failed display was to do with the transformation of a list instead of a dictionary in regards the data format of the different api.
  • With their increased understanding the team agreed to push ahead with up to six visualizations.
  • Nick Do reminded the team to be wary of data too different to present an effecctive comparison visually and to ensure that a variety of chart types were deployed.
  • Nick also reminded the team of the grade structure for the assignment.
  • To ensure we produce a report and a presentation.

About

Making Visualizations with Covid Data

License:GNU General Public License v2.0


Languages

Language:JavaScript 96.5%Language:CSS 2.2%Language:HTML 0.9%Language:Shell 0.4%