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 apd_use_of_force table in this repository, by referencing it like:
"datahub-austintexas-gov/apd-use-of-force-8dc8-gj97:latest"."apd_use_of_force"or in a full query, like:
SELECT
":id", -- Socrata column ID
"officer_commission_date", -- The start date of the officer near the end of the Training Academy at Austin Police Department.
"weapon_used_2", -- The type of weapon used by the officer.
"weapon_used_1", -- The type of weapon used by the officer.
"highest_r2r_level", -- The highest force level by R2R report.
"r2r_level", -- All force levels listed in the R2R report.
"highest_subject_resistance_1", -- The highest subject resistance by subject.
"occurred_on_time", -- The time the incident occurred for which the case report is written. Not all incidents are reported on the day they occurred, therefore reports may be written after the occurred date and time.
"occurred_on_date", -- The date on which the incident, for which the case report is written, occurred. Not all incidents are reported on the day they occurred, therefore reports may be written after the occurred date.
"highest_subject_resistance", -- The highest subject resistance by R2R report.
"sector", -- The Austin Police Department patrol sector where the incident occurred.
"used_pit_s", -- If PIT(s) was used in the incident.
"reason_desc", -- The reason for the use of force.
"case_report_number", -- The case report number for the incident may have many crimes associated with it, as distinguished by Offense ID. The case report number typically is a four-digit year, three-digit day of year, and system generated four-digit occurrence number. Case report numbers that do not follow this pattern may indicate a report intake method outside of computer aided dispatch.
"subject_role", -- The role of the subject in the incident.
"effects_officer_desc", -- The type of injury sustained by the officer.
"used_taser_s", -- If taser(s) was used in the incident.
"geoid", -- The Census Bureau and other state and federal agencies are responsible for assigning geographic identifiers, or GEOIDs, to geographic entities to facilitate the organization, presentation, and exchange of geographic and statistical data. GEOIDs are numeric codes that uniquely identify all administrative/legal and statistical geographic areas for which the Census Bureau tabulates data. From Alaska, the largest state, to the smallest census block in New York City, every geographic area has a unique GEOID. Some of the most common administrative/legal and statistical geographic entities with unique GEOIDs include states, counties, congressional districts, core based statistical areas (metropolitan and micropolitan areas), census tracts, block groups and census blocks.
"unique_id", -- Unique identifier of the response to resistance report.
"number_of_shots", -- Number of shots fired.
"census_tract", -- The Census Track where the incident occurred.
"blkgpnm", -- The Census Block Group where the incident occurred.
"used_chemical_agent_s", -- If chemical agent(s) was used in the incident.
"weapon_used_5", -- The type of weapon used by the officer.
"used_impact_weapon_s", -- If impact weapon(s) was used in the incident.
"highest_subject_injury_by", -- The highest subject injury by subject.
"master_subject_id", -- Unique identifier of the subject.
"officer_yrs_of_service", -- The number of years the officer served at Austin Police Department.
"used_canine_s", -- If canine(s) was used in the incident.
"subject_sex", -- Gender of the subject.
"used_firearm_s", -- If firearm(s) was used in the incident.
"weapon_used_4", -- The type of weapon used by the officer.
"weapon_used_3", -- The type of weapon used by the officer.
"highest_subject_injury_by_1", -- The highest subject injury by R2R report.
"council_district", -- The council district where the incident occurred.
"county_description", -- The county where the incident occurred.
"zip_code", -- The ZIP Code where the incident occurred.
"used_weaponless", -- If no weapon was used in the incident.
"subject_race_ethnicity", -- Race/Ethnicity of the subject.
"nature_of_contact", -- The nature of contact between the subject and the officer.
"officer_organization_desc" -- The unit the officer works for within Austin Police Department.
FROM
"datahub-austintexas-gov/apd-use-of-force-8dc8-gj97:latest"."apd_use_of_force"
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 datahub-austintexas-gov/apd-use-of-force-8dc8-gj97 with SQL in under 60 seconds.
This repository is an "external" repository. That means it's hosted elsewhere, in this case at datahub.austintexas.gov. When you querydatahub-austintexas-gov/apd-use-of-force-8dc8-gj97: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 datahub.austintexas.gov, 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 \
"datahub-austintexas-gov/apd-use-of-force-8dc8-gj97" \
--handler-options '{
"domain": "datahub.austintexas.gov",
"tables": {
"apd_use_of_force": "8dc8-gj97"
}
}'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, datahub-austintexas-gov/apd-use-of-force-8dc8-gj97 is just another Postgres schema.