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 annual_collision_report_collision_severity table in this repository, by referencing it like:
"edmonton-ca/annual-collision-report-collision-severity-77sf-j5rj:latest"."annual_collision_report_collision_severity"or in a full query, like:
SELECT
":id", -- Socrata column ID
"total_serious_minor_injury", -- Total Number of Serious and Minor Injury Collisions
"minor_injury_collisions", -- # of Minor Injury Collisions
"serious_injury_collisions", -- # of Serious Injury Collisions
"injuries_intersection_percent", -- % Injury Occurred at Intersections
"injuries_intersection", -- # of Injuries Occurred at Intersections
"fatalities_intersection", -- # of Fatalities Occurred at Intersections
"total_fatalities_injuries", -- Total Number of Fatalities and Injuries
"total_serious_minor_injuries", -- Total Number of Serious and Minor Injuries
"serious_injuries_pedestrian", -- # of Pedestrians Serious Injuries
"minor_injuries_motorcyclist", -- # of Motorcyclists Minor Injuries
"serious_injuries_bicyclist", -- # of Bicyclists Serious Injuries
"fatality_vehicle_passenger", -- # of Vehicle Passengers Fatally Injured
"fatality_bicyclist", -- # of Bicyclists Fatally Injured
"injuries_fatalities_per_1", -- Injury and Fatality Rate per Population
"property_damage_only_pdo", -- Collisions with Property Damage of $2000.00 or Greater and No Injuries or Fatalities
"total_collisions", -- Total Number of Motor Vehicle Collisions
"pedestrian_collisions", -- Collisions involving Pedestrians
"motorcycle_collisions", -- Collisions involving Motorcycles
"year", -- Year Collision Occurred
"total_fatal_injury_collisions", -- Total Number of Fatal and Injury Collisions
"total_fatalities", -- Total Number of Road Users Fatally Injured
"fatalities_per_1_000", -- Fatality Rate per Population
"private_motorcycles", -- # of Registered Motorcycles
"private_passenger_vehicles", -- # of Registered Motor Vehicles (Including Passenger Cars, Trucks, Utility Vehicles, Vans, and "Other" Vehicles)
"population", -- City of Edmonton Population
"injuries_midblock", -- # of Injuries Occurred at Midblocks
"fatalities_midblock_percent", -- % Fatality Occurred at Midblocks
"total_minor_injuries", -- Total Number of Minor Injuries
"minor_injuries_pedestrian", -- # of Pedestrians Minor Injuries
"fatality_pedestrian", -- # of Pedestrians Fatally Injured
"bicycle_collisions", -- Collisions involving Bicycles
"fatalities_intersection_1", -- % of Fatality Occurred at Intersections
"fatality_vehicle_driver", -- # of Vehicle Drivers Fatally Injured
"injuries_midblock_percent", -- % of Injury Occurred at Midblocks
"serious_injury_motorcyclist", -- # of Motorcyclists Serious Injuries
"injuries_per_1_000_population", -- Injury Rate per Population
"minor_injuries_bicyclist", -- # of Bicyclists Minor Injuries
"fatal_collisions", -- # of Fatal Collisions
"fatalities_midblock", -- # of Fatalities Occurred at Midblocks
"total_serious_injuries", -- Total Number of Serious Injuries
"fatality_motorcyclist", -- # of Motorcyclists Fatally Injured
"collisions_per_1_000" -- Collision Rate per Population
FROM
"edmonton-ca/annual-collision-report-collision-severity-77sf-j5rj:latest"."annual_collision_report_collision_severity"
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 edmonton-ca/annual-collision-report-collision-severity-77sf-j5rj with SQL in under 60 seconds.
This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.edmonton.ca. When you queryedmonton-ca/annual-collision-report-collision-severity-77sf-j5rj:latest on the DDN, we "mount" the repository using the socrata mount handler. The mount handler proxies your SQL query to the upstream data source, translating it from SQL to the relevant language (in this case SoQL).
We also cache query responses on the DDN, but we run the DDN on multiple nodes so a CACHE_HIT is only guaranteed for subsequent queries that land on the same node.
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 (like this repository), 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, where the author has pushed Splitgraph Images to the repository, you can "clone" and/or "checkout" the data using sgr cloneand sgr checkout.
Mounting Data
This repository is an external repository. It's not hosted by Splitgraph. It is hosted by data.edmonton.ca, and Splitgraph indexes it. This means it is not an actual Splitgraph image, so you cannot use sgr clone to get the data. Instead, you can use the socrata adapter with the sgr mount command. Then, if you want, you can import the data and turn it into a Splitgraph image that others can clone.
First, install Splitgraph if you haven't already.
Mount the table with sgr mount
sgr mount socrata \
"edmonton-ca/annual-collision-report-collision-severity-77sf-j5rj" \
--handler-options '{
"domain": "data.edmonton.ca",
"tables": {
"annual_collision_report_collision_severity": "77sf-j5rj"
}
}'That's it! Now you can query the data in the mounted table like any other Postgres table.
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, edmonton-ca/annual-collision-report-collision-severity-77sf-j5rj is just another Postgres schema.