covidmap / app

coming soon - realtime/interactive map of COVID-19's impact on the global health system

COVID Impact Map

With the threat of COVID-19 looming large across the global healthcare system, many ragtag software teams have sprung up to build tools that might help. Most, however, focus on tracking the virus itself, not the virus' local impact on the healthcare system that must respond to it - which is a big problem, for all of us.

Because this data really doesn't exist, we're creating it with a few inputs, and then this piece of software turns that into a useful app. We are going to be accepting crowd-sourced inputs for certain report types, and others will be available only for healthcare staff.

At the end of the day, this repo is made by concerned citizens/volunteers, and we're trying our best. If the app doesn't work, we're very sorry, we are probably working on it right now (as long as the world is still under quarantine). If it doesn't accomplish what you need, we're all ears. In both cases - file a bug, or PRs are certainly welcome.

-COVID Impact Map Team

Slack / Productboard

If you'd like to contribute, or join our Slack channel (to help us or keep us company!) fill out the form link below. For Productboard access, do the same, and in both cases make sure the email you list is the one where you want to receive your invite.

Productboard lets you suggest features, vote on features, and see the roadmap in realtime.

Development process

First, clone the repo. Then, make sure you have Bazelisk and make working in your environment. If you want to use the auto-reload/auto-rebuild functionality, you'll also need to install ibazel. Once you've done that, you should basically be set to go!

You can run make help to get a list of local dev commands. That should output something like the following:

COVID Impact Map:

build                          Build the app.
clean                          Clean ephemeral build targets.
deploy                         Deploy the app to production.
dev                            Build the app, start it up, and auto-reload with changes.
distclean                      Clean ephemeral targets and dependencies.
forceclean                     DANGEROUS: Wipe all local changes and force-reset codebase.
gateway                        Build and push the gateway (Envoy) container image.
help                           Show this help text.
image                          Build a container image for the app, locally.
push                           Build and publish a container image for the app, tagged with the current source tree hash.
run                            Run the app locally.
test                           Run any testsuites.

So you can just run make build to build the app, or make run to run it locally. If you run it locally, the app will be available at http://localhost:8080 by default.

Simulating production

To simulate the full production stack, the app makes use of Skaffold. The tool is intelligent enough to push the entire app to your local Kubernetes cluster, and keep it up to date as you develop. In this operating mode, you should do the following additional steps to get it fully working:

1. Add 127.0.0.1 beta.covidmap.link to your /etc/hosts (or equivalent on your OS)
2. Visit https://beta.covidmap.link:8443 in your favorite browser

Team behind this app

Coming soon.

Licensing

This app will be released under the MIT license. For other licensing details, see GUST, the framework this app is written with.

app's Issues

Should require submitter to search for and select a facility

basic crappy implementation: (please improve this with predictive search from all 8k options)
Hospital Name *

Copy/paste from this list: https://docs.google.com/spreadsheets/d/1Qm11H2R3kom5cRqoPcC3ObnVWzAUp_yPSfO57tPQdUo/edit?usp=sharing (soon we hope to auto-populate this)

Your answer: ______________

Should require submitter to submit semi-structured data (sentiment + details)

example flow: (feel free to improve)
This Facility is: *

• Facing a shortage

• Seeing an increase

• Other: ______

...Of... * (what is this referencing)

_________________ Your answer

...and this is *

• Good/Better than before

• Bad/Worse than before

Trim leading/following whitespace

The dataset could use a clean w.r.t. whitespace.

Hospital status report submission

goals:

• quick to fill out,

• gather sentiment (from good/bad &/or shortage/surplus options) and assumed reliability (from source)

• make the macro view of needs more visible (there are many other good efforts to connect needs/offers directly, could integrate later)

see demo with necessary data to collect: https://docs.google.com/forms/d/e/1FAIpQLSePZv29Vy1dC7cYNkayID-N6lbzWzgxLxoCy1rMK8ZBuSqMbw/viewform

Hospital Pins: Nationwide

Description

We need to plot pins on the map (defined in #5), for every hospital we know of in our dataset, which currently covers the continental United States + Alaska + Hawaii.

We should plot these points on the map as individual pins, for now all the same shape. Later we should try and vary the shape/icon based on facility type.

Pins should change color based on recent status reports

Description

Based on the most recent reports submitted on the app, the pins for each hospital should change color. As pressure on a given facility increases, it should reflect the current state of that pressure on the map.

For instance, the map should depict a blue/regular color dot when no pressure is experienced at a healthcare facility, and perhaps orange or red if high pressure is experienced at the facility (with varying shades in between to indicate degree).

Part of #7.

Should require submitter email

We should require a valid email address to submit a report.

Data duplication in `trauma` fields

Access: Public, Short Domain

covidmap.com and c19map.com were taken. i have c19status.com
I'm requiring it to be a .com, sorry (can also have a separate tinyurl if desired)

any other ideas will be entertained 👍

subfeatures:

• covidmap.link (#3)
• c19status.com (#4)

Alternate domain: `c19status.com`

Hook up the alternate domain, and get it properly redirecting.

part of #2

Form: Report Submission

So far we've chosen Google Forms for this. That should suffice for now, as long as we can get responses out of Google Forms easily, and as long as (operationally) it doesn't present a burden to reporting users.

UPDATE: We are probably building a form. We'll see.

Main domain: `covidmap.link`

Hook up the main domain, covaid.io. This means SSL needs to work, and DNS.

part of #2

Map Interface

Description

The main interface for the COVID Impact Map is, well, a map. This may not be a huge surprise. Basically, when you load up the app, there should be a giant map interface that takes up the predominant amount of screen real estate.

The user should be able to scroll, pan, and zoom. They should be able to easily locate an area on the map using a search box, which we can hook up to Google's Places API.

Notable Features

The map needs to support:

• Pins laid out on the map for each hospital that we have in the dataset
• Ability to click each pin, which reveals a fly-over that describes basic metadata regarding the selected location
• An option to browse to a detail page for the selected hospital

All of the above should be outlined in tickets under this major component.

Should require submitter to confirm source

Source *

First-hand (I am experiencing this)

Second-hand (I was told directly by a first-hand source)

Social media (require to copy/paste source link)

Other: __________

Map should consistently center on user's location

The map currently inconsistently centers on either current location or on latitude zero and longitude zero (off the coast of Nigeria):

Should optionally differentiate between time of submission and time of report

People could report things later, and we want to make sure reports aren't misleading if being interpreted in realtime.