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 service_requests_since_2016 table in this repository, by referencing it like:
"memphistn-gov/service-requests-since-2016-hmd4-ddta:latest"."service_requests_since_2016"or in a full query, like:
SELECT
":id", -- Socrata column ID
"map_page", -- -
"location1",
"street_name", -- SR street name
"sr_creation_channel", -- Service request creation channel (phone or web)
"request_type", -- Request type (acronyms correspond to department: SWM = Solid Waste Management, EMI = Environmental Maintenance, CE = Code Enforcement, etc.)
"postal_code", -- Service request zip code
"next_open_task_date", -- Next open task date
"incident_resolved_date", -- Date service request status changed to "Resolved"
"incident_number", -- Unique incident number
"group_name", -- Group responsible for service request (similar to Division/Department)
"full_address", -- Full service request address with city, state and zip code
"division", -- City division responsible for service request
"creation_date", -- Auto-generated service request creation date (may be after user-reported REPORTED_DATE if person waited to submit request)
"close_date", -- Date service request status changed to "Closed"
"city", -- City (Memphis)
"category", -- Incident category
"address3", -- Service request address3
"address1", -- Service request address
"resolution_code_meaning", -- Resolution code meaning
"owner_name", -- Owner name
"mlgw_status", -- MLGW status
"mlgw_on", -- Last date MLGW utility services were turned on
"location_1", -- Incident location
"last_updated_by", -- -
"last_update_date", -- Date service request last updated (auto-generated)
"followup_date", -- Followup date
"created_by_user", -- User who created service request
"address2", -- Service request address2
"summary_1",
"zone",
"resolution_summary", -- Summary of incident resolution/actions taken
"request_status", -- Request status: Open, In Progress, Closed, etc.
"reported_date", -- User-submitted service request report date
"last_update_login", -- -
"district", -- City council district in which SR incident address is located
"department", -- City department responsible for service request (departments fall within divisions)
"resolution_code", -- Code indicating how the incident was resolved and/or actions taken to address the service request
"number_of_tasks", -- Number of tasks
"incident_type_id", -- Incident type ID
"swm_code", -- Solid Waste Management code
"state", -- SR state (TN)
"parcel_id", -- -
"last_modified_date", -- Date service request last modified (user-generated)
"incident_id", -- Unique incident ID
"collection_day", -- Scheduled collection day
"area", -- Service request area
"request_priority", -- Request priority: High, Medium, or Low
"target_block",
"sub_district", -- Council sub-district in which SR incident is located
"created_by", -- -
"ce_category", -- Code enforcement category
":@computed_region_me95_vbw4",
":@computed_region_xf2b_u4zq",
":@computed_region_h7zg_xcqb",
":@computed_region_ni4r_4h6x",
":@computed_region_gxae_hf64"
FROM
"memphistn-gov/service-requests-since-2016-hmd4-ddta:latest"."service_requests_since_2016"
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 memphistn-gov/service-requests-since-2016-hmd4-ddta 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 memphistn-gov/service-requests-since-2016-hmd4-ddta: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 memphistn-gov/service-requests-since-2016-hmd4-ddtaCheckout 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 memphistn-gov/service-requests-since-2016-hmd4-ddta:latestThis will download all the objects for the latest tag of memphistn-gov/service-requests-since-2016-hmd4-ddta 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 memphistn-gov/service-requests-since-2016-hmd4-ddta: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 memphistn-gov/service-requests-since-2016-hmd4-ddta: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, memphistn-gov/service-requests-since-2016-hmd4-ddta is just another Postgres schema.