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 li_intent_project_details table in this repository, by referencing it like:
"wa-gov/li-intent-project-details-t9je-9qwa:latest"."li_intent_project_details"or in a full query, like:
SELECT
":id", -- Socrata column ID
"prime_phone_number", -- Prime Contractor Phone Number
"insuranceaccount", -- Company Filing The Form - Industrial Insurance Account ID
"hiringcomapanylicense", -- Hiring Contractor's Contractor License Number
"email", -- Company Filing The Form - Email Address
"hiringcomapanyubi", -- Hiring Contractor's UBI Number
"phone", -- Company Filing The Form - Phone Number
"hiringcompanyname", -- Hiring Contractor's Name
"expected_start_dt", -- Company Filing The Form - Expected Work Start Date
"companyname", -- Company Filing The Form - Company Name
"license", -- Company Filing The Form - Contractor Registration Number
"contractnumber", -- Contract Number
"contractname", -- Contract Name
"bid_due_date", -- Project Bid Due Date
"prime_ubi_number", -- Prime Contractor's UBI Number
"prime_contractor_reg_number", -- Prime Contractor's Contract License Number
"prime_company_name", -- Prime Contractor Name
"agencyphone", -- Awarding Agency Contact Phone Number
"agencycontact", -- Awarding Agency Contact Person
"project_id", -- Unique Identifier of the project
"primeintent", -- Prime Contractor's Intent ID Number
"hiringcomapanyinsuranceaccount", -- Hiring Contractor's Industrial Insurance Account ID
"companyzip", -- Company Filing The Form - Zip Code
"companyaddress1", -- Company Filing The Form - Address 1
"cntrct_amt", -- Estimated Contract Amount
"city", -- City
"application_received_date", -- Intent Received Date
"projectlocation", -- Project Site Address Or Directions
"cntrct_award_dt", -- Project Contract Award Date
"agencyname", -- Awarding Agency Name
"awarding_agency_address", -- Awarding Agency Address
"intent_id", -- Intent ID Number
"anysubcontractor", -- Did Your Company Hire Any Subcontractors?
"numberofowner_operatorworked", -- Number Of Owner Operators Who Performed Work
"time_matr_flg", -- Time And Materials
"omwbe_certification", -- OMWBE Certification
"companycity", -- Company Filing The Form - City
"amount", -- Estimated Contract Amount
"anyapprentices", -- Did Your Company Have Apprentices Perform Work?
"companystate", -- Company Filing The Form - State
"companyaddress2", -- Company Filing The Form - Address 2
"ubi", -- Company Filing The Form - UBI Number
"yourcompanyemployeesworked", -- Company Filing The Form - Will Your Company Have Employees Perform Work On This Project?
"owner_operatorsworked", -- Did Owner/Operators Perform Work?
"allworksubcontracted" -- Was All Work Subcontracted Out?
FROM
"wa-gov/li-intent-project-details-t9je-9qwa:latest"."li_intent_project_details"
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 wa-gov/li-intent-project-details-t9je-9qwa 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 wa-gov/li-intent-project-details-t9je-9qwa: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 wa-gov/li-intent-project-details-t9je-9qwaCheckout 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 wa-gov/li-intent-project-details-t9je-9qwa:latestThis will download all the objects for the latest tag of wa-gov/li-intent-project-details-t9je-9qwa 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 wa-gov/li-intent-project-details-t9je-9qwa: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 wa-gov/li-intent-project-details-t9je-9qwa: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, wa-gov/li-intent-project-details-t9je-9qwa is just another Postgres schema.