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 311_service_requests_for_fiscal_year_2016_2017 table in this repository, by referencing it like:
"dallasopendata/311-service-requests-for-fiscal-year-2016-2017-7ysp-mvs9:latest"."311_service_requests_for_fiscal_year_2016_2017"or in a full query, like:
SELECT
":id", -- Socrata column ID
"prc_instance_id", -- Internal Key
"x_value", -- Denotes a point where (x axis) horizontal lines intersect on a map
"prc_outcome_desc", -- Documents the action taken on a service request
"status_date", -- Date the service request was completed
"updated_date", -- Date the service request was last updated with new information or activity
"over_due_on", -- The service request and all activities should be completed by the listed date
"res_department_desc", -- City Departments and Offices
"location_display_name", -- Street Address
"service_request_number", -- Unique ID given to each documented request for a city service; the first two digits designate the last two digits of the calendar year the service request was created (e.g., 16 = 2016)
"lat_long_location_zip",
"lat_long_location", -- Denotes a location point on a longitude line (perpendicular to the equator) and latitude line (parallel to the equator)
"y_value", -- Denotes a point where vertical (y axis) lines intersect on a map
"priority_desc", -- Denotes the precedence of how a service request will be handled
"created_date", -- Date the service request was created
"lat_long_location_address",
"lat_long_location_state",
"lat_long_location_city",
"method_received_desc", -- Mode in which 311 receives the request for service
"suspense_duration_days", -- The time allotted for the initial inspection and/or assessment. (There may be variance from department to department concerning calendar versus business days.)
"prc_type_desc", -- Litter Type of complaint submitted by customer or service offered by the City
"config_location_value", -- Geographical borderlines for legislative representation throughout the city
":@computed_region_2f7u_b5gs",
":@computed_region_sjyw_rtbm",
"status_desc" -- Denotes whether a service request is currently being actively worked or has been resolved
FROM
"dallasopendata/311-service-requests-for-fiscal-year-2016-2017-7ysp-mvs9:latest"."311_service_requests_for_fiscal_year_2016_2017"
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 dallasopendata/311-service-requests-for-fiscal-year-2016-2017-7ysp-mvs9 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 dallasopendata/311-service-requests-for-fiscal-year-2016-2017-7ysp-mvs9: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 dallasopendata/311-service-requests-for-fiscal-year-2016-2017-7ysp-mvs9Checkout 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 dallasopendata/311-service-requests-for-fiscal-year-2016-2017-7ysp-mvs9:latestThis will download all the objects for the latest tag of dallasopendata/311-service-requests-for-fiscal-year-2016-2017-7ysp-mvs9 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 dallasopendata/311-service-requests-for-fiscal-year-2016-2017-7ysp-mvs9: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 dallasopendata/311-service-requests-for-fiscal-year-2016-2017-7ysp-mvs9: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, dallasopendata/311-service-requests-for-fiscal-year-2016-2017-7ysp-mvs9 is just another Postgres schema.