pa-gov/covid19-unusable-vaccine-current-county-health-r5v4-zbqw

  • covid
  • covid-19
  • disease
  • doh
  • health
  • + 4

Query the Data Delivery Network

Query the DDN

The easiest way to query any data on Splitgraph is via the "Data Delivery Network" (DDN). The DDN is a single endpoint that speaks the PostgreSQL wire procotol. Any Splitgraph user can connect to it at data.splitgraph.com:5432 and query any version of over 40,000 datasets that are hosted or proxied by Splitgraph.

For example, you can query the covid19_unusable_vaccine_current_county_health table in this repository, by referencing it like:

"pa-gov/covid19-unusable-vaccine-current-county-health-r5v4-zbqw:latest"."covid19_unusable_vaccine_current_county_health"

or in a full query, like:

SELECT 
    ":id", -- Socrata column ID
    "county", -- County where the clinic is located.
    ":@computed_region_nmsq_hqvv", -- This column was automatically created in order to record in what polygon from the dataset 'Pennsylvania County Boundaries' (nmsq-hqvv) the point in column 'georeferenced_latitude_longitude' is located.  This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
    "lost_or_unaccounted_for", -- Quantity of vaccine doses reported as wasted due to loss of the vaccine or inability of the clinic to account for the vaccine.
    "other", -- Quantity of vaccine doses wasted for reasons other than those listed above.
    "clinic_name", -- Physical street addess of the clinic.
    "clinic_state", -- State where the clinic is located
    "broken_vial_syringe", -- Quantity of vaccine doses wasted that is due to a broken vial and/or syringe.
    "vaccine_drawn_but_not", -- Quantity of vaccine doses wasted that that was drawn into a vial but not administered to a patient.
    "georeferenced_latitude_longitude", -- Georeferenced column for use in creating mapping visualizations with both latitude and longitude based on the Clinic address.
    "open_vial_but_not_administered", -- Quantity of vaccine doses wasted where vial was opened but the doses were not administered before the doses became unviable.
    "spoilage", -- Quantity of vaccine doses wasted where the full vial was never opened and is not unviable.
    "clinic_street_address", -- Physical street address of the clinic.
    "clinic_city", -- City where the clinic is located.
    "clinic_zip" -- Zip code where the clinic is located.
FROM
    "pa-gov/covid19-unusable-vaccine-current-county-health-r5v4-zbqw:latest"."covid19_unusable_vaccine_current_county_health"
LIMIT 100;

Connecting to the DDN is easy. All you need is an existing SQL client that can connect to Postgres. As long as you have a SQL client ready, you'll be able to query pa-gov/covid19-unusable-vaccine-current-county-health-r5v4-zbqw with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.pa.gov. When you querypa-gov/covid19-unusable-vaccine-current-county-health-r5v4-zbqw:latest on the DDN, we "mount" the repository using the socrata mount handler. The mount handler proxies your SQL query to the upstream data source, translating it from SQL to the relevant language (in this case SoQL).

We also cache query responses on the DDN, but we run the DDN on multiple nodes so a CACHE_HIT is only guaranteed for subsequent queries that land on the same node.

Query Your Local Engine

Install Splitgraph Locally

bash -c "$(curl -sL https://github.com/splitgraph/splitgraph/releases/latest/download/install.sh)"
 

Splitgraph Cloud is built around Splitgraph Core (GitHub), which includes a local Splitgraph Engine packaged as a Docker image. Splitgraph Cloud is basically a scaled-up version of that local Engine. When you query the Data Delivery Network or the REST API, we mount the relevant datasets in an Engine on our servers and execute your query on it.

It's possible to run this engine locally. You'll need a Mac, Windows or Linux system to install sgr, and a Docker installation to run the engine. You don't need to know how to actually use Docker; sgrcan manage the image, container and volume for you.

There are a few ways to ingest data into the local engine.

For external repositories (like this repository), the Splitgraph Engine can "mount" upstream data sources by using sgr mount. This feature is built around Postgres Foreign Data Wrappers (FDW). You can write custom "mount handlers" for any upstream data source. For an example, we blogged about making a custom mount handler for HackerNews stories.

For hosted datasets, where the author has pushed Splitgraph Images to the repository, you can "clone" and/or "checkout" the data using sgr cloneand sgr checkout.

Mounting Data

This repository is an external repository. It's not hosted by Splitgraph. It is hosted by data.pa.gov, and Splitgraph indexes it. This means it is not an actual Splitgraph image, so you cannot use sgr clone to get the data. Instead, you can use the socrata adapter with the sgr mount command. Then, if you want, you can import the data and turn it into a Splitgraph image that others can clone.

First, install Splitgraph if you haven't already.

Mount the table with sgr mount

sgr mount socrata \
  "pa-gov/covid19-unusable-vaccine-current-county-health-r5v4-zbqw" \
  --handler-options '{
    "domain": "data.pa.gov",
    "tables": {
        "covid19_unusable_vaccine_current_county_health": "r5v4-zbqw"
    }
}'

That's it! Now you can query the data in the mounted table like any other Postgres table.

Query the data with your existing tools

Once you've loaded the data into your local Splitgraph engine, you can query it with any of your existing tools. As far as they're concerned, pa-gov/covid19-unusable-vaccine-current-county-health-r5v4-zbqw is just another Postgres schema.

Related Documentation: