texas-gov/child-and-adult-care-food-programs-cacfp-day-care-73ar-9py5
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-73ar-9py5:latest"."child_and_adult_care_food_programs_cacfp_day_care"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "totalmealreimbursement", -- Total amount reimbursed for claimed meals. Does not include Administrative funds.
    "ntsnackreimbursement", -- Total evening snack reimbursement for site for claim month
    "supperreimbursement", -- Total supper reimbursement for site for claim month
    "pmsnackreimbursement", -- Total afternoon snack reimbursement for site for claim month
    "lunchreimbursement", -- Total lunch reimbursement for site for claim month
    "breakfastreimbursement", -- Total breakfast reimbursement for site for claim month
    "totalmealssnacks", -- Total Breakfast, Lunch, Supper, and Snacks for site for claim month.
    "totalsnacks", -- Sum of AMSnacks, PMSnacks, and NTSnacks for site for claim month.
    "ntsnacktotal", -- Total number of evening snacks served at site in claim month
    "tieriilowntsnack", -- Number of Tier II Low evening snacks served at site in claim month
    "tieriihighntsnack", -- Number of Tier II High evening snacks served at site in claim month
    "tierintsnack", -- Number of Tier I evening snacks served at site in claim month
    "tieriilowsupper", -- Number of Tier II Low suppers served at site in claim month
    "tierisupper", -- Number of Tier I suppers served at site in claim month
    "pmsnacktotal", -- Total number of afternoon snacks served at site in claim month
    "tieriilowpmsnack", -- Number of Tier II Low afternoon snacks served at site in claim month
    "tieripmsnack", -- Number of Tier I afternoon snacks served at site in claim month
    "lunchtotal", -- Total number of lunches served at site in claim month
    "tieriilowlunch", -- Number of Tier II Low lunches served at site in claim month
    "tieriihighlunch", -- Number of Tier II High lunches served at site in claim month
    "tierilunch", -- Number of Tier I lunches served at site in claim month
    "tieriilowamsnack", -- Number of Tier II Low morning snacks served at site in claim month
    "tieriihighamsnack", -- Number of Tier II High morning snacks served at site in claim month
    "tieriamsnack", -- Number of Tier I morning snacks served at site in claim month
    "breakfasttotal", -- Total number of breakfasts served at site in claim month
    "tieriihighbreakfast", -- Number of Tier II High breakfasts served at site in claim month
    "tieribreakfast", -- Number of Tier I breakfasts served at site in claim month
    "daysservedtieriilow", -- Number of days meals were served at the Tier II Low reimbursement category in claim month
    "daysservedtieriihigh", -- Number of days meals were served at the Tier II High reimbursement category in claim month
    "sitecounty", -- County in which the site is located
    "sitename", -- Site name
    "siteid", -- Number assigned to identify site within Contracting Entity (CE)
    "typeofagency", -- Type of agency the Contracting Entity (CE) operates as. Data displayed as: Educational Institution/For Profit Organization/Government Agency/Indian Tribe/Military Installation/Private Non Profit Organization
    "tdaregion", -- Texas Department of Agriculture (TDA) service region
    "cecounty", -- County in which the Contracting Entity (CE) is located 
    "cename", -- Contracting Entity (CE) name
    "ceid", -- Unique number assigned to Contracting Entity (CE) to identify organization as a CACFP sponsor
    "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. 
    "odprecid", -- Unique ODP record ID. Data format : [CE ID #]-[Site ID #]
    "claimdate", -- Month and year for which meals were reported by the site for reimbursement. 
    "amsnackreimbursement", -- Total morning snack reimbursement for site for claim month
    "suppertotal", -- Total number of suppers served at site in claim month
    "tieriihighsupper", -- Number of Tier II High suppers served at site in claim month
    "tieriihighpmsnack", -- Number of Tier II High afternoon snacks served at site in claim month
    "amsnacktotal", -- Total number of morning snacks served at site in claim month
    "tieriilowbreakfast", -- Number of Tier II Low breakfasts served at site in claim month
    "daysservedtieri", -- Number of days meals were served at the Tier I reimbursement category in claim month
    "esc", -- Educational Service Center (ESC) region
    "reporttype" -- Type of information being reported in the dataset 
FROM
    "texas-gov/child-and-adult-care-food-programs-cacfp-day-care-73ar-9py5: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-73ar-9py5 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-73ar-9py5: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-73ar-9py5" \
  --handler-options '{
    "domain": "data.texas.gov",
    "tables": {
        "child_and_adult_care_food_programs_cacfp_day_care": "73ar-9py5"
    }
}'

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-73ar-9py5 is just another Postgres schema.