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 summer_meal_programs_seamless_summer_option_sso table in this repository, by referencing it like:
"texas-gov/summer-meal-programs-seamless-summer-option-sso-skk3-4frt:latest"."summer_meal_programs_seamless_summer_option_sso"or in a full query, like:
SELECT
":id", -- Socrata column ID
"seamlesssummercontactemail", -- Summer program contact email address
"seamlesssummercontactlastname", -- Summer program contact last name
"seamlesssummercontactfirstname", -- Summer program contact first name
"childnutdiremail", -- Child Nutrition Director (CND) email address
"childnutdirtitleposition", -- Child Nutrition Director (CND) title or position
"superintendenttitleposition", -- CE administrator/superintendent title or position
"superintendentlastname", -- CE administrator/superintendent last name
"sitestreetaddresszipcode", -- Site street address, zip code
"sitestreetaddresscity", -- Site street address, city
"sitestreetaddressline2", -- Site street address, line 2 (if applicable)
"sitestreetaddressline1", -- Site street address, line 1
"cestreetaddresscity", -- Contracting Entity (CE) street address, city
"cecounty", -- County in which the Contracting Entity (CE) is located
"countydistrictcode", -- County District Code for county in which Contracting Entity (CE) in located
"sitestatus", -- Site is eligible and/or participating in nutrition program. Data displayed as: Active/Inactive.
"typeofagency", -- Type of agency the Contracting Entity (CE) operates as. Data displayed as: Educational Institution/Government Agency/Indian Tribe/Military Installation/Private Non Profit Organization
"cename", -- Contracting Entity (CE) name
"ceid", -- Unique number assigned to Contracting Entity (CE) to identify organization as a program sponsor
"geoloc_data", -- Longitude and Latitude point data based on site street address for map visualization.
"suppertime", -- Time supper service starts and ends. Data displayed as: H:MM – H:MM
"lunchdaysserved", -- Days of the week lunch served at the site during operation Data displayed as: S/M/T/W/TH/F/SA; multiple entries separated by commas
"lunchtime", -- Time lunch service starts and ends. Data displayed as: H:MM – H:MM
"breakfasttime", -- Time breakfast service starts and ends. Data displayed as: H:MM – H:MM
"daysofoperation", -- Days of the week meals served at the site during operation. Data displayed as: S/M/T/W/TH/F/SA; multiple entries separated by commas
"seamlesssummercontacttitleposition", -- Summer program contact title or position
"seamlesssummercontactsalutation", -- Honorific salutation for summer program contact. Optional entry. Format: Mr., Ms. Dr., etc.
"childnutdirphone", -- Child Nutrition Director (CND) phone number
"childnutdirlastname", -- Child Nutrition Director (CND) last name
"superintendentemail", -- CE administrator/superintendent email address
"superintendentfirstname", -- CE administrator/superintendent first name
"sitestreetaddressstate", -- Site street address, state
"cemailingaddressline1", -- Contracting Entity (CE) mailing address, line 1
"siteterminatedasofdate", -- Date that participation in this TDA nutrition program effectively ends for the site. Data displayed as: MM/DD/YYYY / (blank – not terminated).
"sitename", -- Site name
"siteid", -- Identification number assigned to site within CE
"tdaregion", -- Texas Department of Agriculture (TDA) service region
"esc", -- Educational Service Center (ESC) region
"amsnackdaysserved", -- Days of the week morning snacks served at the site during operation Data displayed as: S/M/T/W/TH/F/SA; multiple entries separated by commas
"breakfastdaysserved", -- Days of the week breakfast served at the site during operation Data displayed as: S/M/T/W/TH/F/SA; multiple entries separated by commas
"siteenddate", -- Operational end date for the site
"sitestartdate", -- Operational start date for the site
"sitetype", -- Site type description. Data displayed as: Camp/Closed/Open/Open Restricted
"seamlesssummercontactphone", -- Summer program contact phone number
"cemailingaddresszipcode", -- Contracting Entity (CE) mailing address, zip code
"cemailingaddresscity", -- Contracting Entity (CE) mailing address, city
"cemailingaddressline2", -- Contracting Entity (CE) mailing address, line 2 (if applicable)
"cestreetaddresszipcode", -- Contracting Entity (CE) street address, zip code
"cestreetaddressline2", -- Contracting Entity (CE) street address, line 2 (if applicable)
"sitecounty", -- County in which the site is located
"supperdaysserved", -- Days of the week supper served at the site during operation Data displayed as: S/M/T/W/TH/F/SA; multiple days separated by commas
"mealtypesserved", -- Type of meals served at the site during operation. Data displayed as: Breakfast/Lunch/Dinner/AM Snack/PM Snack; multiple entries separated by commas
"cestatus", -- Contracting Entity is eligible and/or participating in nutrition program. Data displayed as: Active/Inactive
"superintendentphone", -- CE administrator/superintendent phone number
"superintendentsalutation", -- Honorific salutation for CE administrator/superintendent. Optional entry for CE. Format: Mr., Ms., Dr., etc.
"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).
"amsnacktime", -- Time morning snack service starts and ends. Data displayed as: H:MM – H:MM
"siteterminationstatus", -- Termination category for site that is no longer participating in this TDA nutrition program. Data for SSO displayed as: Contracting Entity Closed /Self Cancelled/TDA cancelled/TDA Terminated(blank – not terminated).
"ceapplicationcycle", -- Description of Contracting Entity (CE) application type based on program participation in previous program year. Data displayed as: Continuing/NewApp/Renewal.
"pmsnacktime", -- Time afternoon snack service starts and ends. Data displayed as: H:MM – H:MM
"childnutdirsalutation", -- Honorific salutation for Child Nutrition Director (CND). Optional entry for CE. Format: Mr., Ms. Dr., etc.
"cestreetaddressline1", -- Contracting Entity (CE) street address, line 1
"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).
"childnutdirfirstname", -- Child Nutrition Director (CND) first name
"cestreetaddressstate", -- Contracting Entity (CE) street address, state
"typeoforg", -- Type of organization the sponsored site operates as. Data displayed as: Charter/Private/Public/RCCI (Residential Child Care Institution)
"cemailingaddressstate", -- Contracting Entity (CE) mailing address, state
"siteapplicationcycle", -- Description of site application type based on program participation in previous program year. Date displayed as: NewApp/Renewal.
"programyear", -- A program period for summer meal programs is normally defined as mid-May through the end of August for the same calendar year. Please read About this Dataset for special circumstances for this program year.
"pmsnackdaysserved", -- Days of the week afternoon snacks served at the site during operation Data displayed as: S/M/T/W/TH/F/SA; multiple days separated by commas
"reporttype", -- Type of information being reported in the dataset
":@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 'geolocation_data' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
":@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 'geolocation_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 'geolocation_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 'geolocation_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 'geolocation_data' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
FROM
"texas-gov/summer-meal-programs-seamless-summer-option-sso-skk3-4frt:latest"."summer_meal_programs_seamless_summer_option_sso"
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/summer-meal-programs-seamless-summer-option-sso-skk3-4frt 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/summer-meal-programs-seamless-summer-option-sso-skk3-4frt: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/summer-meal-programs-seamless-summer-option-sso-skk3-4frtCheckout 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/summer-meal-programs-seamless-summer-option-sso-skk3-4frt:latestThis will download all the objects for the latest tag of texas-gov/summer-meal-programs-seamless-summer-option-sso-skk3-4frt 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/summer-meal-programs-seamless-summer-option-sso-skk3-4frt: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/summer-meal-programs-seamless-summer-option-sso-skk3-4frt: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/summer-meal-programs-seamless-summer-option-sso-skk3-4frt is just another Postgres schema.