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 lobbyist_agent_employers table in this repository, by referencing it like:
"wa-gov/lobbyist-agent-employers-e7sd-jbuy:latest"."lobbyist_agent_employers"or in a full query, like:
SELECT
":id", -- Socrata column ID
"training_certified", -- After October 27th, 2020: the date that the lobbyist was trained. Prior to October 27th 2020: the date they certified with the Public Disclosure Commission that they completed the training, not the date they did the actual training
"employment_year", -- The year the agent was employed by the lobbyist/firm.
"agent_bio", -- The biographical data submitted by the agent.
"employment_registration_title", -- The name of the employer who hired the lobbyist/firm. When the lobbyist firm is hired through another lobbyist (subcontract) this is the name of the employer with the hiring firm included in parenthesis.
"lobbyist_address", -- The address of the lobbyist firm.
"lobbyist_email", -- The email address associated with this lobbyist firm.
"agent_name", -- The registered name of the agent.
"lobbyist_phone", -- The phone number associated with the lobbyist firm.
"lobbyist_firm_name", -- The lobbyist firm who employs the agent.
"employer_title", -- The name of the employer.
"employment_registration_id", -- The unique identifier representing the relationship between a Lobbyist Firm, an Agent, and an Employer.
"filer_id", -- The unique id assigned to the lobbyist/firm that employs this agent. The filer id is consistent across years.
"id", -- An auto-generated unique identifier representing a relationship between a Lobbyist firm, an Agent, and an Employer for a given year.
"employer_id", -- The unique identifier for the employer's registration.
"agent_pic_url", -- A link to the agents picture.
"employer_url", -- A link to the employer registration data including the employer's lobbyists and a link to the employer's annual reports (L3).
"employment_registration_url", -- A link to the employment contract, showing Compensation, Employment Type, Employer Areas of Interest, Lobbying Term, Reimbursement Agreements, and Lobbying Periods.
"lobbyist_firm_url" -- A link to the registration information submitted by the lobbyist.
FROM
"wa-gov/lobbyist-agent-employers-e7sd-jbuy:latest"."lobbyist_agent_employers"
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/lobbyist-agent-employers-e7sd-jbuy 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/lobbyist-agent-employers-e7sd-jbuy: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/lobbyist-agent-employers-e7sd-jbuyCheckout 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/lobbyist-agent-employers-e7sd-jbuy:latestThis will download all the objects for the latest tag of wa-gov/lobbyist-agent-employers-e7sd-jbuy 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/lobbyist-agent-employers-e7sd-jbuy: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/lobbyist-agent-employers-e7sd-jbuy: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/lobbyist-agent-employers-e7sd-jbuy is just another Postgres schema.