chronicdata-cdc-gov/behavioral-risk-factor-data-tobacco-use-2011-to-wsas-xwh5
Icon for Socrata external plugin

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 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 behavioral_risk_factor_data_tobacco_use_2011_to table in this repository, by referencing it like:

"chronicdata-cdc-gov/behavioral-risk-factor-data-tobacco-use-2011-to-wsas-xwh5:latest"."behavioral_risk_factor_data_tobacco_use_2011_to"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "submeasureid", -- Submeasure identifier code - can be used for filtering; used in application
    "stratificationid3", -- Race identifier code - can be used for filtering; used in application
    "measureid", -- Measure identifier - can be used for filtering
    "topicid", -- Topic identifier code - can be used for filtering; used in application
    "sample_size", -- Sample size
    "high_confidence_limit", -- Confidence interval upper limit
    "low_confidence_limit", -- Confidence interval lower limit
    "displayorder", -- Display order; used in application
    "geolocation", -- Geolocation codes for mapping purposes
    "topictype", -- Type of topic
    "stratificationid4", -- Education identifier code - can be used for filtering; used in application
    "stratificationid2", -- Age identifier code - can be used for filtering; used in application
    "topictypeid", -- Topic type identifier code - can be used for filtering; used in application
    "geolocation_state",
    "geolocation_address",
    "stratificationid1", -- Gender identifier code - can be used for filtering; used in application
    "geolocation_zip",
    ":@computed_region_he4y_prf8",
    ":@computed_region_bxsw_vy29",
    "geolocation_city",
    "datasource", -- Data source
    "response", -- Response categories
    "topicdesc", -- Topic description
    "measuredesc", -- Measure description
    "locationdesc", -- Location description
    "year", -- Year
    "locationabbr", -- Location abbreviation
    "data_value", -- Value of the data
    "data_value_unit", -- Indicator of the type of data value ($, %, etc)
    "data_value_type", -- Type of data (yes/no, percentage, dollar, etc)
    "gender", -- Gender of respondents
    "data_value_std_err", -- Standard error for the data value
    "data_value_footnote_symbol", -- Where applicable, this text is associated with the footnote symbol
    "data_value_footnote", -- Where applicable, this text is associated with the footnote text
    "education", -- Education level of respondents
    "age", -- Age of respondents
    "race" -- Race of respondents
FROM
    "chronicdata-cdc-gov/behavioral-risk-factor-data-tobacco-use-2011-to-wsas-xwh5:latest"."behavioral_risk_factor_data_tobacco_use_2011_to"
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 chronicdata-cdc-gov/behavioral-risk-factor-data-tobacco-use-2011-to-wsas-xwh5 with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at chronicdata.cdc.gov. When you querychronicdata-cdc-gov/behavioral-risk-factor-data-tobacco-use-2011-to-wsas-xwh5: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)"
 

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 (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 chronicdata.cdc.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 \
  "chronicdata-cdc-gov/behavioral-risk-factor-data-tobacco-use-2011-to-wsas-xwh5" \
  --handler-options '{
    "domain": "chronicdata.cdc.gov",
    "tables": {
        "behavioral_risk_factor_data_tobacco_use_2011_to": "wsas-xwh5"
    }
}'

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, chronicdata-cdc-gov/behavioral-risk-factor-data-tobacco-use-2011-to-wsas-xwh5 is just another Postgres schema.