I very strongly recommend against putting pages like this up, unless you are qualified, especially with claims like "always updated", and especially as you are giving medical advice like "stay at home".
Some years ago, when I lived in a boat, I wanted better presentation of the river conditions (which you would look at if you wanted to go out for a cruise). I put something similar together. It scraped the UK's Environment Agency website and showed the status of various stretches of the River Thames on a Google Map. Just for fun.
I got an angry email when the scraper broke and the data got out of date. "You're putting lives at risk". I took his point, and took the site down.
The odds are much higher in this case. It might seem like a nice portfolio piece, but could be dangerous.
This is on point. This is why I never released an app I made for ocean diving conditions. Hydrographic offices exist to provide accurate information, and to be liable for what they produce. I could waive liability, but then I could still endanger people. It isn't worth it. Don't give people advice, don't assume the role of a professional if you aren't one.
I made this infographic since I was not able to quickly understand the number on the official website.
I would take it as a 'general' website, and I think that people know that they should check the official website in order to have something 100% reliable.
Also, the line at the end is a simple suggestion that any government is trying to say to the population to avoid overcrowding of hospitals. But I will edit the phrase to be lighter and less 'instructive'.
> I made this infographic since I was not able to quickly understand the number on the official website. I would take it as a 'general' website, and I think that people know that they should check the official website in order to have something 100% reliable.
No, I know enough people that don't. Look into the low educated part of your family (if you have that part). In my family the low educated people will believe anything that says Stanford or Harvard without any source other than just typing it. Heck, they would almost see this comment as reputable.
In your visualization, the data for The Netherlands is wrong by a few days. It's not 804, it's 1135. I remember it to be 950+ yesterday. My source is the National Institute for Public Health and the Environment [1]. Apparently your source is John Hopkins? I'm not entirely sure, I quickly skimmed it. But I don't want old information on HN.
It has a nice design though. But because of its exponential nature and my knowledge of humans being terrible on it, I'm on edge. I don't want misinformation or stale data.
I think my experience was similar to yours. The reason I made it was to make the presentation of interesting data more accessible. But the lesson I took from it is that people put data to all kinds of uses, including those I didn't think about.
I was really surprised by that email, but it was enough to make me understand.
If you linked to your sources, show prominently the last time the data was updated, don't give any advice and clearly state that it's just for interest only, I think this would be less risky.
But whatever you do, there will be someone, somewhere, using your page for a reason you didn't expect.
Get rid of it entirely, you have no way of words, you have no writing skills. Does one figure out one has symptoms at home? I am to make a call and I have to do it with a phone?
Clearly state you are a programmer and why you've made the page. Then it is cool. Nice visuals... WE ARE ALL GOING TO DIE!
"In case of symptoms or doubts, stay at home, do not go to the hospital or medical offices but call your family doctor, pediatrician or medical guard on the phone."
That is the CDC's advice for Americans. The UK's advice may be different. I am not qualified to say which is 'correct' for a site available internationally. I don't think the author of the site is either.
I agree with this. Only go to reputable sources for information [1]. If you have an academic background, then you know how to do this. If you don't know how to do this, ask someone on how to do this. It's quite a nuanced skill to learn all at once.
[1] My sources (but please do your own research):
1. WHO
2. RIVD (Dutch)
3. Dr. Mike on YouTube (and then verify the sources -- mostly medical journals -- he uses)
Maybe one thing OP could do is prominently display the last updated time, instead of saying "updated three times a day". Though he/she does display the time period at the top.
But generally this is good advice - not add to the noise already there on the internet, even though OP's intentions are likely honest and they are just trying to help.
Interestingly this uses JHU data [1] (with lag because they don’t push in real time), yet somehow managed to omit part of the data, e.g. 8k cases in South Korea completely missing.
I just fixed it, there was a problem with the map.
Anyway, the data are pulled from the original repository three times per day to avoid too much traffic. I will try to increase the number of updates :)
- Use dense and small fonts, there is no need to follow the current trends of massive typography
- Create a layout that is easy to follow
- Do not highjack the scroll wheel (if you're in the zoomable region of the map, I can't scroll because it zooms instead)
Shouldn't mortality rate be determined by total dead out of total recovered? Doing it the other way, total dead out of total infected, assumes everyone infected will recover.
I've read that dead / recovered overestimates since cases that end in death tend to close more quickly than cases that end with a recovery. Neither are great though and dead / cases underestimates since some of those cases might end in death as you say.
Bottom line is it's hard to get good estimates and we should let epidemiologists do their job.
I know why, but with full-width graphs that take up most of the screen, the scrolling issue is a real problem. As none of the graphs have content that needs to scroll within their viewport, you need to set the height/width/overflow/display to a combination that doesn’t cause this.
The pie chart is fine. They can be bad when one wants to compare several similar categories, but they are fine when used to compare a part to a whole. Also it has a hole in the middle, which mitigates the problem of visual angle comparison.
It's not good to blindly follow rules, just because it's fashionable to say a certain thing. Especially in the fields of data visualization and user experience, which are mostly pseudoscience bullshit anyway...
Some years ago, when I lived in a boat, I wanted better presentation of the river conditions (which you would look at if you wanted to go out for a cruise). I put something similar together. It scraped the UK's Environment Agency website and showed the status of various stretches of the River Thames on a Google Map. Just for fun.
I got an angry email when the scraper broke and the data got out of date. "You're putting lives at risk". I took his point, and took the site down.
The odds are much higher in this case. It might seem like a nice portfolio piece, but could be dangerous.