citydata-mesaaz-gov/fire-and-medical-opioid-overdose-incidents-qufy-tzv6
Icon for Socrata external plugin

Query the Data Delivery Network

Query the DDN

The 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 fire_and_medical_opioid_overdose_incidents table in this repository, by referencing it like:

"citydata-mesaaz-gov/fire-and-medical-opioid-overdose-incidents-qufy-tzv6:latest"."fire_and_medical_opioid_overdose_incidents"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "location", -- Geo location of the incident, calculated by truncated Latitude and Longitude coordinates. Estimated location only to within approximately 1/3 mile radius.
    "location_address",
    "month", -- Month the incident occurred
    "incident_id", -- Unique 911 call for service identifier. See the dataset description for more information.
    "unit_name", -- The Fire/Medical unit that wrote the incident report
    "longitude", -- Longitude of location where the incident happened, truncated to 2-3 decimal points. Estimated location only to within approximately 1/3 mile radius.
    "incident_disposition", -- Final call status. See the dataset description for more information.
    "patient_age", -- Age category assigned based on patient age
    "location_city",
    "pd_save", -- The administration of Narcan by Police restored patient vitals (breathing/heart rate)
    "location_state",
    "gender", -- Gender of Patient
    "time_of_day", -- Morning: 6am-11:59amAfternoon: Noon-5:59pmEvening: 6pm-11:59pmOvernight: Midnight - 5:59am
    "complaint_reported_by_dispatch", -- Code representing how the incident was initially dispatched by Fire 911 dispatcher
    "opioid_overdose_review", -- Validation that opioid overdose occurred based on at least one of 3 possible criteria: Self-reported or witness account, evidence found or positive response to Naloxone / Narcan treatment.
    "day_of_week", -- Day of week the incident occurred
    "incident_date", -- Date and Time the incident occurred
    "treatment_or_medication_given", -- Names of medications and treatments provided
    "location_zip",
    "latitude", -- Latitude of location where the incident happened, truncated to 2-3 decimal points. Estimated location only to within approximately 1/3 mile radius.
    ":@computed_region_yvgd_jnii", -- This column was automatically created in order to record in what polygon from the dataset 'Hexagon 8th Square Mile Project' (yvgd-jnii) the point in column 'location' is located.  This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
    ":@computed_region_5spd_7gy6", -- This column was automatically created in order to record in what polygon from the dataset 'Mesa Census Tracts To City Boundary v2022' (5spd-7gy6) the point in column 'location' is located.  This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
    ":@computed_region_c54k_jm6w", -- This column was automatically created in order to record in what polygon from the dataset 'Hexagon 16th Square Mile Project' (c54k-jm6w) the point in column 'location' is located.  This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
    ":@computed_region_c83p_wm8i",
    ":@computed_region_fcpr_wj2n",
    ":@computed_region_y4ir_tfjh",
    "pd_narcan", -- Police administered Narcan prior to arrival of Fire/Medical unit
    "year" -- Year the incident occurred
FROM
    "citydata-mesaaz-gov/fire-and-medical-opioid-overdose-incidents-qufy-tzv6:latest"."fire_and_medical_opioid_overdose_incidents"
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 citydata-mesaaz-gov/fire-and-medical-opioid-overdose-incidents-qufy-tzv6 with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at citydata.mesaaz.gov. When you querycitydata-mesaaz-gov/fire-and-medical-opioid-overdose-incidents-qufy-tzv6: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

Install Splitgraph Locally
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 citydata.mesaaz.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 \
  "citydata-mesaaz-gov/fire-and-medical-opioid-overdose-incidents-qufy-tzv6" \
  --handler-options '{
    "domain": "citydata.mesaaz.gov",
    "tables": {
        "fire_and_medical_opioid_overdose_incidents": "qufy-tzv6"
    }
}'

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, citydata-mesaaz-gov/fire-and-medical-opioid-overdose-incidents-qufy-tzv6 is just another Postgres schema.