Repository files navigation

• Overview & Data Sources
  • The Covid Tracking Project
  • John Hopkins University
• How to consume
  • 1. Connection information
    • Connections credentials
      • Credentials
      • Connection Points
  • 2. Choose your Topics
    • Streams are available on these topics
    • Example topic subscriptions
  • 3. Create your application
    • Sample Applications to Get Started Quickly
    • COVID19 Stream Processors
• Test Topics
• Contribution
• Credit
• Disclaimer

This repo provides streams information and example applications on how to consume COVID19 related topics aggregated from different data sources. Below is a list of the different data sources used to feed the published streams.

A team from theThe Atlantic launchedThe Covid Tracking Project to collect and publish testing data available for US states and territories.

A team atJohns Hopkins University Center for Systems Science and Engineering (JHU CSSE) has developed thisinteractive web-based dashboard to provide researchers, public health authorities, and the general public with a user-friendly tool to track the COVID-19 pandemic as it unfolds. Their team has also been nice enough to periodically (usually once or twice a day) upload the data to thisGithub Repo which has been very popular in the developer community; but has led to developers wanting to receive updates in a more efficient manner. To further their teams’ efforts, help the community, and to “do our part”, we at Solace have created an application that polls the feature service, looks for differences in the data, and publishes updates into an Event Broker we are making available for public use. This allows anyone to consume data updates in near real-time. The data is being published into the event brokers using dynamic topics which allows subscribers to pick, choose and filter on the specific data that they want to consume; e.g., a developer could choose to only get updated when an update it available for a specific Country & Province/State that they are interested in.

Any client application could consume those streams by subscribing to the topic of choice as per the diagram below. Note that the streams are provided over Solace PubSub+ Event Broker that has built-in support for a variety of open standard protocols and APIs.

Connect to the PubSub+ broker using one of the connection end points below. For more details, check out theSolace Developer Portal and theAPI docs samples for the different messaging APIs and protocols

MessageVPN :covid-19-streams
Client Username :covid-public-client
Client Password:covid19

Note: if you want to receive notifications via a REST end point that supportsPOST, contact us atcovid19-project@solace.com

As of right now, the following is the list of streams available for consumption

Subscribe to one or more of the available topics above to receive the required data.Note that the streams defined asupdate above only send events when updates actually occur which can be infrequently. For development purposes we are providingtest topics that get published every few minutes

For more more information on using topic wildcards check outSMF Topic Subscriptions andMQTT Topic Subscriptions

Note: If you have your own COVID-19 event stream that you'd like to share please contact us atcovid19-project@solace.com

Subscribing to the following streams will give you the corresponding results:

After connecting and choosing the topics to listen on, it's time to build your application. Check out the examples below for applications that consume the streams.

Below are Spring Boot microservices used to create the event current streams available for consumption. They are also good examples if you would like to consume the streams and republish them into an event broker. Note that they are not intended to be run with the provided credentials as we are running them as a services.

Note: Contact us atcovid19-project@solace.com to add more event stream into the current broker.

This section includes information about test streams that are available. Since actual updates can occur infrequently, we are providing these test streams strictly for development purposes. Instead of only receiving events when updates occur, these topics, which includetest as a level, will regularly receive events whether or not an update has actually occurred. Once you have completed development you should remove thetest level from your topic and you’ll only receive events when actual updates occur.

Note that theraw streams is regularly updated every ~45 seconds

SeeContribution guidelines form more details

• Social Preview Image byGerd Altmann fromPixabay

1. As per Johns Hopkins UniversityTerms of Use this data is public strictly for educational and academic research purposes.
2. Data streams are provided and maintained bySolace under the same terms of use.