Query the Data Delivery Network
Query the DDNThe 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_contact_information_and table in this repository, by referencing it like:
"texas-gov/school-nutrition-programs-contact-information-and-shme-pbr8:latest"."school_nutrition_programs_contact_information_and"or in a full query, like:
SELECT
":id", -- Socrata column ID
"mealspurchasedfromsfa", -- CE organization purchases meals from a School Food Authority (SFA). Data displayed as: Y/N
"managedbyfsmc", -- School nutrition program contracts with a Food Service Management Company (FSMC). FSMC details can be found in the School Nutrition Program – Food Service Management Company Information dataset. Data displayed as: Y/N
"childnutdirsalutation", -- Honorific salutation for Child Nutrition Director (CND). Optional entry for CE. Format: Mr., Ms. Dr., etc.
"superintendentlastname", -- CE administrator/superintendent last name
"esc", -- Educational Service Center (ESC) region
"grade2", -- Grades served at this site – second (2nd) grade. Data displayed as: Y/(blank)
"cename", -- Contracting Entity (CE) name; sponsor or district name
"cestreetaddresscity", -- Contracting Entity (CE) street address, city
"childnutdiremail", -- Child Nutrition Director (CND) email address
"cestreetaddresszipcode", -- Contracting Entity (CE) street address, zip code
"grade9", -- Grades served at this site – ninth (9th) grade. Data displayed as: Y/(blank)
"gradeheadstart", -- Grades served at this site – Head Start. Data displayed as: Y/(blank)
"superintendentsalutation", -- Honorific salutation for Superintendent. Optional entry for CE. Format: Mr., Ms. Dr., etc.
"childnutdirtitleposition", -- Child Nutrition Director (CND) title or position
"severeneedbreakfast", -- Participation of site in the Severe Needs Breakfast Program (SNB) during the program year. Data displayed as: Y/N
"nationalschoollunchprogram", -- Participation of site in the National School Lunch Program (NSLP) during the program year. Data displayed as: Y/N
"sitestreetaddressstate", -- Site street address, state
"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.
"sitestreetaddressline2", -- Site street address, line 2 (if applicable)
"cep", -- Participation of site in the Community Eligible Provision (CEP) during the program year. Data displayed as: Y/N
"grade10", -- Grades served at this site – tenth (10th) grade. Data displayed as: Y/(blank)
"grade12", -- Grades at this site – twelfth (12th) grade. Data displayed as: Y/(blank)
"geoloc_data", -- Latitude and longitude data based on mappable site address
"sitename", -- Site name; school name
"childnutdirlastname", -- Child Nutrition Director (CND) last name
"cecounty", -- County in which the Contracting Entity (CE) is located
"childnutdirfirstname", -- Child Nutrition Director (CND) first name
"ffvpapproved", -- Participation of site in the Fresh Fruits and Vegetable Program (FFVP) during the program year. Data displayed as: Y/N
"gradeearlyeducation", -- Grades served at this site – early education. Data displayed as: Y/(blank)
"superintendentphone", -- CE administrator/superintendent phone number
"countydistrictcode", -- County District Code for Contracting Entity (CE).
"sitestreetaddressline1", -- Site street address, line 1
"snackpricing", -- Method of snack meal pricing employed by site during the program year
"operationenddate", -- End date of operations for the sponsor or district for the program year.
"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.
"superintendentemail", -- CE administrator/superintendent email address
"superintendenttitleposition", -- CE administrator/superintendent title or position
":@computed_region_czj8_xg26", -- This column was automatically created in order to record in what polygon from the dataset 'Texas U.S. Congressional Districts Plan C235 (Effective Jan 2013)' (czj8-xg26) the point in column 'geoloc_data' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
"childnutdirphone", -- Child Nutrition Director (CND) phone number
"cemailingaddresszipcode", -- Contracting Entity (CE) mailing address, zip code
":@computed_region_45pq_umjc", -- This column was automatically created in order to record in what polygon from the dataset 'Texas State House Districts Plan H414 (Effective Jan 2021)' (45pq-umjc) the point in column 'geoloc_data' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
":@computed_region_5xir_5pdr", -- This column was automatically created in order to record in what polygon from the dataset 'Texas Senate Districts Plan S172 (Effective Jan 2013)' (5xir-5pdr) the point in column 'geoloc_data' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
":@computed_region_de3d_j5mj", -- This column was automatically created in order to record in what polygon from the dataset 'US States Cartographic Boundary Map' (de3d-j5mj) the point in column 'geoloc_data' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
":@computed_region_59h5_km5p", -- This column was automatically created in order to record in what polygon from the dataset 'Texas Counties Cartographic Boundary Map' (59h5-km5p) the point in column 'geoloc_data' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
"superintendentfirstname", -- CE administrator/superintendent first name
"sitestreetaddresszipcode", -- Site street address, zip code
"sitestreetaddresscity", -- Site street address, city
"cemailingaddresscity", -- Contracting Entity (CE) mailing address, city
"cemailingaddressstate", -- Contracting Entity (CE) mailing address, state
"cemailingaddressline2", -- Contracting Entity (CE) mailing address, line 2 (if applicable)
"cestreetaddressstate", -- Contracting Entity (CE) street address, state
"siteapplicationcycle", -- Description of site application type based on program participation in previous program year. Date displayed as: NewApp/Renewal.
"siteterminationstatus", -- Termination category for site that is no longer participating in this TDA nutrition program. Data for CACFP Centers, SNP, SFSP, and SSO displayed as: Contracting Entity Closed /Self Cancelled/TDA cancelled/TDA Terminated(blank – not terminated).
"cemailingaddressline1", -- Contracting Entity (CE) mailing address, line 1
"ceapplicationcycle", -- Description of Contracting Entity (CE) application type based on program participation in previous program year. Data displayed as: Continuing/NewApp/Renewal.
"ceterminationstatus", -- Termination category for Contracting Entity (CE) that is no longer participating in this TDA nutrition program. Data displayed as: Self Cancelled/TDA cancelled/(blank – not terminated).
"cestreetaddressline2", -- Contracting Entity (CE) street address, line 2 (if applicable)
"cestreetaddressline1", -- Contracting Entity (CE) street address, line 1
"cestatus", -- Contracting Entity is eligible and/or participating in nutrition program. Data displayed as: Active/Inactive.
"sitecounty", -- County in which the site is located
"tdaregion", -- Texas Department of Agriculture (TDA) service region
"typeoforg", -- Type of organization the Contracting Entity (CE) operates as within a specific nutrition program. Data for School Nutrition Programs displayed as: Charter/Private/Public/RCCI (Residential Child Care Institution).
"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
"siteterminatedasofdate", -- Date that participation in this TDA nutrition program effectively ends for the site. Data displayed as: MM/DD/YYYY / (blank – not terminated).
"siteid", -- Identification number assigned to site under CE sponsorship
"ceid", -- Unique number assigned by TDA to Contracting Entity (CE) to identify organization as program sponsor
"sitestatus", -- Site is eligible and/or participating in nutrition program. Data displayed as: Active/Inactive.
"grade11", -- Grades served at this site – eleventh (11th) grade. Data displayed as: Y/(blank)
"grade4", -- Grades served at this site – fourth (4th) grade. Data displayed as: Y/(blank)
"grade3", -- Grades served at this site – third (3rd) grade. Data displayed as: Y/(blank)
"grade1", -- Grades served at this site – first (1st) grade. Data displayed as: Y/(blank)
"grade6", -- Grades served at this site – sixth (6th) grade. Data displayed as: Y/(blank)
"siteisp", -- Identified Student Percentage (ISP) reported April of the previous program year. ISP describes the percent of students enrolled who are directly certified to receive free meals without household application. Contributes to determining eligibility of a site or group of sites for electing CEP meal pricing.
"gradekinder", -- Grades served at this site – Kindergarten. Data displayed as: Y/(blank)
"gradeprek", -- Grades served at this site – Pre-kindergarten. Data displayed as: Y/(blank)
"operationstartdate", -- Start date of operations for the sponsor or district for the program year.
"lunchpricing", -- Method of lunch meal pricing employed by site during the program year
"grade7", -- Grades served at this site – seventh (7th) grade. Data displayed as: Y/(blank)
"ceterminatedasofdate", -- Date that participation in this TDA nutrition program effectively ends for the Contracting Entity (CE). Data displayed as: MM/DD/YYYY / (blank – not terminated).
"breakfastpricing", -- Method of breakfast meal pricing employed by site during the program year
"provision2", -- Participation of site in Provision 2 (P2) during the program year. Data displayed as: Y/N
"areaeligiblesnack", -- Participation of site in the Area Eligible Snack during the program year. Data displayed as: Y/N
"universalfreebreakfast", -- Participation of site in the Universal Free Breakfast (UB) during the program year. Data displayed as: Y/N
"specialmilkprogram", -- Participation of site in the Special Milk Program (SMP) during the program year. Data displayed as: Y/N
"afterschoolcareprogram", -- Site participates in the After School Care Program (ASCP) during the program year. Data displayed as: Y/N
"grade8", -- Grades served at this site – eighth (8th) grade. Data displayed as: Y/(blank)
"grade5", -- Grades served at this site – fifth (5th) grade. Data displayed as: Y/(blank)
"schoolbreakfastprogram", -- Participation of site in the School Breakfast Program (SBP) during the program year. Data displayed as, Y/N
"vendmealstosfa", -- CE organization vends meals to a School Food Authority (SFA). Data displayed as: Y/N
"mealspurchasedfromvendorotherthansfa" -- CE organization purchases meals/snacks from a vendor other than a School Food Authority (SFA). Data displayed as: Y/N
FROM
"texas-gov/school-nutrition-programs-contact-information-and-shme-pbr8:latest"."school_nutrition_programs_contact_information_and"
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-contact-information-and-shme-pbr8 with SQL in under 60 seconds.
Query Your Local Engine
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, 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 (like this repository), where the author has pushed Splitgraph Images to the repository, you can "clone" and/or "checkout" the data using sgr cloneand sgr checkout.
Cloning Data
Because texas-gov/school-nutrition-programs-contact-information-and-shme-pbr8:latest is a Splitgraph Image, you can clone the data from Spltgraph Cloud to your local engine, where you can query it like any other Postgres database, using any of your existing tools.
First, install Splitgraph if you haven't already.
Clone the metadata with sgr clone
This will be quick, and does not download the actual data.
sgr clone texas-gov/school-nutrition-programs-contact-information-and-shme-pbr8Checkout the data
Once you've cloned the data, you need to "checkout" the tag that you want. For example, to checkout the latest tag:
sgr checkout texas-gov/school-nutrition-programs-contact-information-and-shme-pbr8:latestThis will download all the objects for the latest tag of texas-gov/school-nutrition-programs-contact-information-and-shme-pbr8 and load them into the Splitgraph Engine. Depending on your connection speed and the size of the data, you will need to wait for the checkout to complete. Once it's complete, you will be able to query the data like you would any other Postgres database.
Alternatively, use "layered checkout" to avoid downloading all the data
The data in texas-gov/school-nutrition-programs-contact-information-and-shme-pbr8:latest is 0 bytes. If this is too big to download all at once, or perhaps you only need to query a subset of it, you can use a layered checkout.:
sgr checkout --layered texas-gov/school-nutrition-programs-contact-information-and-shme-pbr8:latestThis will not download all the data, but it will create a schema comprised of foreign tables, that you can query as you would any other data. Splitgraph will lazily download the required objects as you query the data. In some cases, this might be faster or more efficient than a regular checkout.
Read the layered querying documentation to learn about when and why you might want to use layered queries.
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-contact-information-and-shme-pbr8 is just another Postgres schema.