texas-gov/school-nutrition-programs-food-service-management-d9ps-bznv
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 school_nutrition_programs_food_service_management table in this repository, by referencing it like:

"texas-gov/school-nutrition-programs-food-service-management-d9ps-bznv:latest"."school_nutrition_programs_food_service_management"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "childnutdirphone", -- Child Nutrition Director (CND) phone number
    "childnutdiremail", -- Child Nutrition Director (CND) email address
    "childnutdirtitleposition", -- Child Nutrition Director (CND) title or position
    "childnutdirfirstname", -- Child Nutrition Director (CND) first name
    "superintendentphone", -- CE administrator/superintendent phone number
    "superintendentemail", -- CE administrator/superintendent email address
    "superintendenttitleposition", -- CE administrator/superintendent title or position
    "superintendentfirstname", -- CE administrator/superintendent first name
    "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
    "cestreetaddresscity", -- Contracting Entity (CE) street address, city
    "cestreetaddressline2", -- Contracting Entity (CE) street address, line 2 (if applicable)
    "cestreetaddressline1", -- Contracting Entity (CE) street address, line 1
    "terminateddate", -- Date FSMC contract was terminated.
    "effectivedate", -- FSMC contract effective date, if applicable
    "fsmcname", -- Name of Food Service Management Company (FSMC), if applicable
    "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
    "cename", -- Contracting Entity (CE) name
    "ceid", -- Unique number assigned by TDA to Contracting Entity (CE) to identify organization as program sponsor
    "childnutdirlastname", -- Child Nutrition Director (CND) last name
    "finalyear", -- Final year of FSMC contract, if applicable
    "fsmcmanaged", -- School nutrition program will be managed by a Food Service Management Company (FSMC). Data displayed as: Y/N
    "typeoforg", -- Type of organization the Contracting Entity (CE) operates as within a specific nutrition program. Data for CACFP Centers displayed as: Independent Center/Sponsor of Affiliated & Unaffiliated Sites/Sponsor of Affiliated Sites/Sponsor of Unaffiliated Sites. Data for SFSP displayed as: Nonresidential Summer Camp/Private Non Profit/Residential Camp/School Food Authority/Unit of Government.  Data for School Nutrition Programs and SSO displayed as: Charter/Private/Public/RCCI (Residential Child Care Institution). 
    "superintendentlastname", -- CE administrator/superintendent last name
    "procurementtype", -- Contract type, if applicable. Data displayed as: Fixed Price/Cost + Free/(blank)
    "numberofrenewalyears", -- Number of optional FSMC renewal years, if applicable
    "initialyear", -- Initial year of FSMC contract, if applicable. Data displayed as: YYYY/(blank)
    "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/Other
    "reporttype", -- Type of information being reported in the dataset
    "programyear", -- A program year for School Nutrition Programs is defined as July 1 of one year through June 30 of the following year
    "childnutdirsalutation", -- Honorific salutation for Child Nutrition Director (CND). Optional entry for CE. Format: Mr., Ms. Dr., etc.
    "superintendentsalutation", -- Honorific salutation for Superintendent. Optional entry for CE. Format: Mr., Ms. Dr., etc.
    "cestreetaddressstate", -- Contracting Entity (CE) street address, state
    "enddate", -- FSMC contract end date, if applicable
    "tdaregion" -- Texas Department of Agriculture (TDA) service region
FROM
    "texas-gov/school-nutrition-programs-food-service-management-d9ps-bznv:latest"."school_nutrition_programs_food_service_management"
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/school-nutrition-programs-food-service-management-d9ps-bznv 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/school-nutrition-programs-food-service-management-d9ps-bznv: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/school-nutrition-programs-food-service-management-d9ps-bznv" \
  --handler-options '{
    "domain": "data.texas.gov",
    "tables": {
        "school_nutrition_programs_food_service_management": "d9ps-bznv"
    }
}'

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/school-nutrition-programs-food-service-management-d9ps-bznv is just another Postgres schema.