texas-gov/child-and-adult-care-food-programs-cacfp-emergency-x8zu-m9gr
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_emergency table in this repository, by referencing it like:

"texas-gov/child-and-adult-care-food-programs-cacfp-emergency-x8zu-m9gr:latest"."child_and_adult_care_food_programs_cacfp_emergency"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "ntsnackreimbursement", -- Total evening snack reimbursement for claim month
    "pmsnackreimbursement", -- Total afternoon snack reimbursement for claim month
    "lunchreimbursement", -- Total lunch meal reimbursement for claim month
    "amsnackreimbursement", -- Total morning snack reimbursement for claim month
    "breakfastreimbursement", -- Total breakfast meal reimbursement for claim month
    "ntsnacktotal", -- Number of evening snacks served at site for the claim month
    "lunchservedpaid", -- Number of paid lunch meals served at site for claim month
    "lunchservedfree", -- Number of free lunch meals served at site for claim month
    "lunchtotal", -- Number of lunch meals served at site for claim month
    "amsnacktotal", -- Number of morning snacks served at site for the claim month
    "claimdate", -- Month and year for which meals were reported by the site for reimbursement. 
    "supperadp", -- Average Daily Participation (ADP) for supper meals. Calculated as number of supper meals served at site in claim month divided by number of site supper service days for site in claim month
    "lunchadp", -- Average Daily Participation (ADP) for lunch. Calculated as the number of lunch meals served at the site in claim month divided by the number of lunch service days at the site in claim month.
    "amsnackadp", -- Average Daily Participation (ADP) for morning snacks. Calculated as calculated by number of morning snacks served at site in claim month divided by number of morning snack service days at the site in claim month
    "breakfastadp", -- Average Daily Participation (ADP) for breakfast. Calculated as the number of breakfast meals served at the site in claim month divided by the number of breakfast service days at the site in claim month.
    "breakfasttotal", -- Number of breakfast meals served at site for the claim month
    "breakfastdays", -- Number of days breakfast meals served at site for claim month
    "supperreimbursement", -- Total supper meal reimbursement for claim month
    "ntsnackservedfree", -- Number of free evening snacks served at site in claim month
    "ntsnackadp", -- Average Daily Participation (ADP) for evening snacks. Calculated as number of evening snack meals served at site in claim month divided by number of evening snack service days at site in claim month
    "supperservedredc", -- Number of reduced price supper meals served at site in claim month
    "breakfastservedfree", -- Number of free breakfast meals served at site for claim month
    "sitename", -- Site name
    "totalreimbursement", -- Total federal meal reimbursement for site for claim month, including Cash-in-Lieu of Commodities.
    "supperservedfree", -- Number of free supper meals served at site in claim month
    "pmsnacktotal", -- Number of afternoon snacks served at site for the claim month
    "freeeligqty", -- Number of participants enrolled at site approved for free meals for claim month
    "enrollmentqty", -- Number of participants enrolled at site for claim month
    "sitecounty", -- County in which the site is located
    "cecounty", -- County in which the Contracting Entity (CE) is located 
    "pmsnackadp", -- Average Daily Participation (ADP) for afternoon snacks. Calculated as calculated by number of afternoon snack served at site in claim month divided by number of afternoon snack service days at the site in claim month
    "ntsnackservedpaid", -- Number of paid evening snacks served at site in claim month
    "ntsnackservedredc", -- Number of reduced price evening snacks served at site in claim month
    "suppertotal", -- Number of supper meals served at site in the claim month
    "supperdays", -- Number of days supper meals served at site for claim month
    "pmsnackservedpaid", -- Number of paid afternoon snacks served at site in claim month
    "pmsnackservedredc", -- Number of reduced price afternoon snacks served at site in claim month
    "pmsnackdays", -- Number of days afternoon snacks served at site for claim month
    "lunchservedredc", -- Number of reduced price lunch meals served at site for claim month
    "amsnackservedpaid", -- Number of paid morning snacks served at site in claim month
    "amsnackservedfree", -- Number of free morning snacks served at site in claim month
    "amsnackdays", -- Number of days morning snacks were served at site for claim month
    "affiliation", -- Affiliation refers to the relationship the site has with its CE sponsor. Affiliated sites are part of the Contracting Entity (CE) organization. Unaffiliated sites are not part of the Contracting Entity (CE) organization. Data displayed as: Affiliated/Unaffiliated
    "tdaregion", -- Texas Department of Agriculture (TDA) service region
    "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
    "reporttype", -- Type of information being reported in the dataset 
    "siteid", -- Number assigned to identify site within CE
    "ntsnackdays", -- Number of days evening snacks served at site for claim month
    "pmsnackservedfree", -- Number of free afternoon snacks served at site in claim month
    "amsnackservedredc", -- Number of reduced price morning snacks served at site in claim month
    "ceid", -- Unique number assigned to Contracting Entity (CE) to identify organization as a CACFP sponsor
    "cename", -- Contracting Entity (CE) name
    "supperservedpaid", -- Number of paid supper meals served at site in claim month
    "lunchdays", -- Number of days lunch was served at site for claim month
    "breakfastservedpaid", -- Number of paid breakfast meals served at site for claim month
    "breakfastservedredc", -- Number of reduced price breakfast meals served at site for claim month
    "redceligqty", -- Number of participants enrolled at site at site approved for reduced price meals for claim month 
    "covidmealsite", -- COVID-19 Meal Site indicator. Indicates whether site operated under USDA flexibilities offered in response to the COVID-19 pandemic. Data displayed as: Yes/No.
    "typeoforg", -- Type of organization the Contracting Entity (CE) operates as. Data displayed as: Independent Center/Sponsor of Affiliated & Unaffiliated Sites/Sponsor of Affiliated Sites/Sponsor of Unaffiliated Sites/(blank)
    "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. 
    "paideligqty", -- Number of participants enrolled at site not approved for free or reduced price meals for claim month
    "esc" -- Educational Service Center (ESC) region
FROM
    "texas-gov/child-and-adult-care-food-programs-cacfp-emergency-x8zu-m9gr:latest"."child_and_adult_care_food_programs_cacfp_emergency"
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-emergency-x8zu-m9gr 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-emergency-x8zu-m9gr: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.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-emergency-x8zu-m9gr" \
  --handler-options '{
    "domain": "data.texas.gov",
    "tables": {
        "child_and_adult_care_food_programs_cacfp_emergency": "x8zu-m9gr"
    }
}'

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-emergency-x8zu-m9gr is just another Postgres schema.

Related Documentation: