Query the Data Delivery Network
Query the DDNThe 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 protocol. 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 tristate_memorial_hospital_quarterly_discharges table in this repository, by referencing it like:
"wa-gov/tristate-memorial-hospital-quarterly-discharges-69jw-mwgp:latest"."tristate_memorial_hospital_quarterly_discharges"or in a full query, like:
SELECT
":id", -- Socrata column ID
"year", -- Year of the population count recorded in this dataset.
"acutecareotherdischarges", -- The number of patients with private insurance who leave an acute care unit after receiving treatment.
"acutecareselfpay", -- The number of patients who leave the Acute care unit without private or public insurance plans after receiving treatment.
"acutecaremedicaiddischarges", -- The number of Medicaid beneficiaries who leave an acute care unit after receiving acute care treatment.
"acutecare_medicaredischarges", -- The number of Medicare beneficiaries who leave an acute care unit after receiving acute care treatment.
"emergencyroomvisits", -- Number of patients seen by the Emergency Department.
"totalinpatientsurgeries", -- Number of surgeries performed on admitted patients
"psychrehabcdumedicaredis", -- The number of Medicare beneficiaries who leave a Psychiatric/Rehabilitation/or Co-occurring Disorder Unit (CDU) bed after receiving treatment.
"homehealthvisits", -- Number of visits from home health care providers.
"totalnewborndays", -- Number of days newborns spent in hospital.
"psychrehabcdumedicaidpat", -- The number of days Medicaid beneficiaries spent in a Psychiatric/Rehabilitation/or Co-occurring Disorder Unit (CDU) bed.
"snfotherpatientdays", -- The number of days Medicare beneficiaries spent in a Psychiatric/Rehabilitation/or Co-occurring Disorder Unit (CDU) bed.
"swingbedmedicaidpatientdays", -- The number of days patients without private or public insurance spent in swing beds.
"psychrehabcduotherdischarges", -- The number of patients with private insurance who leave a Psychiatric/Rehabilitation/or Co-occurring Disorder Unit (CDU) bed after receiving treatment.
"snfmedicaredischarges", -- The number of Medicare beneficiaries who leave a skilled nursing facility (SNF) bed after receiving treatment.
"totalbirths", -- Number of babies born.
"snfselfpaypatientdays", -- The number of days patients with private insurance spent in skilled nursing facility (SNF) bed.
"swingbedselfpaypatientdays", -- The number of days patients with private insurance spent in swing beds.
"swingbedmedicaiddishcharges", -- The number of Medicaid beneficiaries who leave a swing bed after receiving treatment.
"quarter", -- Fiscal quarter during which this population count was recorded.
"psychrehabcdumedicarepat", -- The number of days Medicaid beneficiaries spent in a Psychiatric/Rehabilitation/or Co-occurring Disorder Unit (CDU) bed.
"acutecareselfpaypatientdays", -- The number of days patients with private insurance spent in the Acute care unit.
"snfmedicarepatientdas", -- The number of days Medicaid beneficiaries spent in a skilled nursing facility (SNF) bed.
"licensedbeds", -- The maximum number of patient beds approved by the State of Washington.
"swingbedselfpaydischarges", -- The number of patients who leave a swing bed without private or public insurance plans after receiving treatment.
"snfotherdischarges", -- The number of patients who leave a skilled nursing Facility (SNF) bed with private insurance plans after receiving treatment.
"allothervisits", -- Number of outpatient visits that do not fall into a previous category.
"observationvisits", -- Number of patients seen for a short period of time while provider decides whether or not to admit.
"outpatientsurgeryvisits", -- Number of patients receiving care without requiring an overnight stay during a given quarter
"numberofadmissionsfromer", -- Number of patients admitted to the hospital from the Emergency Department during a given quarter.
"psychrehabcduotherpatientdays", -- The number of days patients without private or public insurance spent in a Psychiatric/Rehabilitation/or Co-occurring Disorder Unit (CDU) bed.
"psychrehabcdumedicaiddis", -- The number of Medicaid beneficiaries who leave a Psychiatric/Rehabilitation/or Co-occurring Disorder Unit (CDU) bed after receiving treatment.
"snfmedicaidpatientdays", -- The number of days patients without private or public insurance spent in a skilled nursing facility (SNF) bed.
"psychrehabcduselfpaypati", -- The number of days patients without private or public insurance spent in a Psychiatric/Rehabilitation/or Co-occurring Disorder Unit (CDU) bed.
"swingbedotherpatientdays", -- The number of days Medicare beneficiaries spent in a skilled nursing facility (SNF) bed.
"swingbedmedicarepatientdays", -- The number of days Medicaid beneficiaries spent in swing beds.
"acutecareotherpatientdays", -- The number of days Medicare beneficiaries spent in swing beds.
"acutecaremedicaidpatientdays", -- The number of days patients without private or public insurance spent in the Acute care unit.
"acutecaremedicarepatientdays", -- The number of days Medicaid beneficiaries spent in the Acute care unit.
"ttoalselfpaydischarges", -- The number of days Medicare beneficiaries spent in the Acute care unit.
"psychrehabcduselfpaydischarges", -- The number of patients without private or public insurance who leave a Psychiatric/Rehabilitation/or Co-occurring Disorder Unit (CDU) bed after receiving treatment.
"snfselfpaydischarges", -- The number of patients who leave a skilled nursing Facility (SNF) bed without private or public insurance plans after receiving treatment.
"snfmedicadedischarges", -- The number of Medicaid beneficiaries who leave a skilled nursing facility (SNF) bed after receiving treatment.
"swingbedotherdischarges", -- The number of patients with private insurance who leave a swing bed after receiving treatment.
"swingbedmedicaredischarges" -- The number of Medicare beneficiaries who leave a swing bed after receiving treatment.
FROM
"wa-gov/tristate-memorial-hospital-quarterly-discharges-69jw-mwgp:latest"."tristate_memorial_hospital_quarterly_discharges"
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 wa-gov/tristate-memorial-hospital-quarterly-discharges-69jw-mwgp with SQL in under 60 seconds.
Query Your Local Engine
bash -c "$(curl -sL https://github.com/splitgraph/splitgraph/releases/latest/download/install.sh)"Read the installation docs.
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, 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 (like this repository), where the author has pushed Splitgraph Images to the repository, you can "clone" and/or "checkout" the data using sgr cloneand sgr checkout.
Cloning Data
Because wa-gov/tristate-memorial-hospital-quarterly-discharges-69jw-mwgp:latest is a Splitgraph Image, you can clone the data from Spltgraph Cloud to your local engine, where you can query it like any other Postgres database, using any of your existing tools.
First, install Splitgraph if you haven't already.
Clone the metadata with sgr clone
This will be quick, and does not download the actual data.
sgr clone wa-gov/tristate-memorial-hospital-quarterly-discharges-69jw-mwgpCheckout the data
Once you've cloned the data, you need to "checkout" the tag that you want. For example, to checkout the latest tag:
sgr checkout wa-gov/tristate-memorial-hospital-quarterly-discharges-69jw-mwgp:latestThis will download all the objects for the latest tag of wa-gov/tristate-memorial-hospital-quarterly-discharges-69jw-mwgp and load them into the Splitgraph Engine. Depending on your connection speed and the size of the data, you will need to wait for the checkout to complete. Once it's complete, you will be able to query the data like you would any other Postgres database.
Alternatively, use "layered checkout" to avoid downloading all the data
The data in wa-gov/tristate-memorial-hospital-quarterly-discharges-69jw-mwgp:latest is 0 bytes. If this is too big to download all at once, or perhaps you only need to query a subset of it, you can use a layered checkout.:
sgr checkout --layered wa-gov/tristate-memorial-hospital-quarterly-discharges-69jw-mwgp:latestThis will not download all the data, but it will create a schema comprised of foreign tables, that you can query as you would any other data. Splitgraph will lazily download the required objects as you query the data. In some cases, this might be faster or more efficient than a regular checkout.
Read the layered querying documentation to learn about when and why you might want to use layered queries.
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, wa-gov/tristate-memorial-hospital-quarterly-discharges-69jw-mwgp is just another Postgres schema.