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 transportation_network_providers_trips_2018_2022 table in this repository, by referencing it like:
"cityofchicago/transportation-network-providers-trips-2018-2022-m6dm-c72p:latest"."transportation_network_providers_trips_2018_2022"or in a full query, like:
SELECT
":id", -- Socrata column ID
"shared_trip_authorized", -- Whether the customer agreed to a shared trip with another customer, regardless of whether the customer was actually matched for a shared trip.
"pickup_centroid_latitude", -- The latitude of the center of the pickup census tract or the community area if the census tract has been hidden for privacy. This column often will be blank for locations outside Chicago.
"pickup_community_area", -- The Community Area where the trip began. This column will be blank for locations outside Chicago.
"additional_charges", -- The taxes, fees, and any other charges for the trip.
"trip_start_timestamp", -- When the trip started, rounded to the nearest 15 minutes.
"trip_total", -- Total cost of the trip. This is calculated as the total of the previous columns, including rounding.
"trip_id", -- A unique identifier for the trip.
"pickup_centroid_longitude", -- The longitude of the center of the pickup census tract or the community area if the census tract has been hidden for privacy. This column often will be blank for locations outside Chicago.
"dropoff_centroid_latitude", -- The latitude of the center of the dropoff census tract or the community area if the census tract has been hidden for privacy. This column often will be blank for locations outside Chicago.
"dropoff_community_area", -- The Community Area where the trip ended. This column will be blank for locations outside Chicago.
"dropoff_census_tract", -- The Census Tract where the trip ended. This column often will be blank for locations outside Chicago.
"pickup_centroid_location", -- The location of the center of the pickup census tract or the community area if the census tract has been hidden for privacy. This column often will be blank for locations outside Chicago.
"trips_pooled", -- If customers were matched for a shared trip, how many trips, including this one, were pooled. All customer trips from the time the vehicle was empty until it was empty again contribute to this count, even if some customers were never present in the vehicle at the same time. Each trip making up the overall shared trip will have a separate record in this dataset, with the same value in this column.
"dropoff_centroid_longitude", -- The longitude of the center of the dropoff census tract or the community area if the census tract has been hidden for privacy. This column often will be blank for locations outside Chicago.
"dropoff_centroid_location", -- The location of the center of the dropoff census tract or the community area if the census tract has been hidden for privacy. This column often will be blank for locations outside Chicago.
"fare", -- The fare for the trip, rounded to the nearest $2.50.
"tip", -- The tip for the trip, rounded to the nearest $1.00. Cash tips will not be recorded.
"trip_miles", -- Distance of the trip in miles.
"trip_seconds", -- Time of the trip in seconds.
"trip_end_timestamp", -- When the trip ended, rounded to the nearest 15 minutes.
"pickup_census_tract" -- The Census Tract where the trip began.This column often will be blank for locations outside Chicago.
FROM
"cityofchicago/transportation-network-providers-trips-2018-2022-m6dm-c72p:latest"."transportation_network_providers_trips_2018_2022"
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 cityofchicago/transportation-network-providers-trips-2018-2022-m6dm-c72p 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 cityofchicago/transportation-network-providers-trips-2018-2022-m6dm-c72p: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 cityofchicago/transportation-network-providers-trips-2018-2022-m6dm-c72pCheckout 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 cityofchicago/transportation-network-providers-trips-2018-2022-m6dm-c72p:latestThis will download all the objects for the latest tag of cityofchicago/transportation-network-providers-trips-2018-2022-m6dm-c72p 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 cityofchicago/transportation-network-providers-trips-2018-2022-m6dm-c72p: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 cityofchicago/transportation-network-providers-trips-2018-2022-m6dm-c72p: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, cityofchicago/transportation-network-providers-trips-2018-2022-m6dm-c72p is just another Postgres schema.