texas-gov/child-and-adult-care-food-programs-cacfp-day-care-u3xf-ey9y
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 child_and_adult_care_food_programs_cacfp_day_care table in this repository, by referencing it like:

"texas-gov/child-and-adult-care-food-programs-cacfp-day-care-u3xf-ey9y:latest"."child_and_adult_care_food_programs_cacfp_day_care"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "cestreetaddressline1", -- Contracting Entity (CE) street address, line 1
    "applicationeffectivedate", -- Date Contracting Entity (CE) is approved to begin program participation for program year. 
    "geocoded_column", -- Geo-location of site based on site street address for map visualization. Null values in geo-location data is most likely due to a P.O. Box address listed for a site address.
    "participatingascacfpcent", -- Contracting Entity (CE) also participates as a sponsor for CACFP centers. Data displayed as: Y/N 
    "capacity", -- Licensed site capacity
    "licenseexpirationdate", -- Date the license or registration expires
    "licenseeffectivedate", -- Date the license or registration takes effect
    "license_registrationnumber", -- Site’s license or registration number
    "ifother_pleaseexplain", -- If “other” is indicated, explanation of meal preparation method.
    "numberofchildrenenrolled", -- Number of children enrolled in program
    "sitecontactphone", -- Site contact phone number. Site contact is the person in charge of this center on a daily basis.
    "sitecontactemail", -- Site contact email address. Site contact is the person in charge of this center on a daily basis.
    "sitecontactlastname", -- Site contact last name. Site contact is the person in charge of this center on a daily basis.
    "sitecontactfirstname", -- Site contact first name. Site contact is the person in charge of this center on a daily basis
    "sitecontactsaluation", -- Honorific salutation for site contact. Optional entry. Format: Mr., Ms. Dr., etc.
    "sitemailingaddresszipcode", -- Site mailing address, zip code
    "sitemailingaddressstate", -- Site mailing address, state
    "sitemailingaddresscity", -- Site mailing address, city
    "sitemailingaddressline2", -- Site mailing address, line 2 (if applicable)
    "sitemailingaddressline1", -- Site mailing address, line 1
    "sitestreetaddresszipcode", -- Site street address, zip code
    "sitestreetaddressstate", -- Site street address, state
    "sitestreetaddresscity", -- Site street address, city
    "sitestreetaddressline2", -- Site street address, line 2 (if applicable)
    "sitestreetaddressline1", -- Site street address, line 1
    "sitecounty", -- County in which the site is located
    "sitename", -- Site name
    "siteid", -- Number assigned to identify site within CE
    "ceadministratorphone", -- CE administrator phone number
    "ceadministratoremail", -- CE administrator email address 
    "ceadministratortitleposition", -- CE administrator title or position
    "ceadministratorlastname", -- CE administrator last name
    "ceadministratorfirstname", -- CE administrator first name
    "ceadministratorsalutation", -- Honorific salutation for CE administrator. Optional entry for CE. Format: Mr., Ms., Dr., etc.
    "cemailingaddresszipcode", -- Contracting Entity (CE) mailing address, zip code
    "cemailingaddressstate", -- Contracting Entity (CE) mailing address, state
    "cemailingaddresscity", -- Contracting Entity (CE) mailing address, city
    "cemailingaddressline2", -- Contracting Entity (CE) mailing address, line 2 (if applicable)
    "cemailingaddressline1", -- Contracting Entity (CE) mailing address, line 1
    "cestreetaddresszipcode", -- Contracting Entity (CE) street address, zip code
    "cestreetaddressstate", -- Contracting Entity (CE) street address, state
    "cestreetaddresscity", -- Contracting Entity (CE) street address, city
    "cestreetaddressline2", -- Contracting Entity (CE) street address, line 2 (if applicable)
    "tdaregion", -- Texas Department of Agriculture (TDA) service region
    "esc", -- Educational Service Center (ESC) region
    "cecounty", -- County in which the Contracting Entity (CE) is located
    "countydistrictcode", -- County District Code for county in which Contracting Entity (CE) in located
    "typeofagency", -- Type of agency the Contracting Entity (CE) operates as. Data displayed as: Government Agency/Military Installation/Private Non Profit Organization
    "cename", -- Contracting Entity (CE) name
    "ceid", -- Unique number assigned to Contracting Entity (CE) to identify as program sponsor
    "reporttype", -- Type of information being reported in the dataset
    "programyear", -- A program year for Child and Adult Care Food Programs (CACFP) is defined as October 1 of one year through September 30 of the following year. 
    ":@computed_region_9y59_55ru",
    ":@computed_region_fd5q_j34z",
    ":@computed_region_ywmh_rrwq",
    ":@computed_region_hy99_5a2i",
    ":@computed_region_346f_s9gh",
    "howaremealsprepared" -- Method used by site to prepare meals. Data displayed as: Prepared on site/Other
FROM
    "texas-gov/child-and-adult-care-food-programs-cacfp-day-care-u3xf-ey9y:latest"."child_and_adult_care_food_programs_cacfp_day_care"
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 texas-gov/child-and-adult-care-food-programs-cacfp-day-care-u3xf-ey9y with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.texas.gov. When you querytexas-gov/child-and-adult-care-food-programs-cacfp-day-care-u3xf-ey9y: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 data.texas.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 \
  "texas-gov/child-and-adult-care-food-programs-cacfp-day-care-u3xf-ey9y" \
  --handler-options '{
    "domain": "data.texas.gov",
    "tables": {
        "child_and_adult_care_food_programs_cacfp_day_care": "u3xf-ey9y"
    }
}'

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, texas-gov/child-and-adult-care-food-programs-cacfp-day-care-u3xf-ey9y is just another Postgres schema.