brla-gov/legacy-baton-rouge-traffic-incidents-2010-2020-2tu5-7kif
Loading...

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

"brla-gov/legacy-baton-rouge-traffic-incidents-2010-2020-2tu5-7kif:latest"."legacy_baton_rouge_traffic_incidents_2010_2020"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "fatality", -- Will be marked with 'X" if the crash involved a fatality
    "relation_roadway", -- Location of the crash in relation to the highway
    "injury", -- Will be marked with 'X" if the crash involved an injury
    "st_name", -- Crash location - street name
    "location_kind", -- Describes the land use in the area of the crash
    "geolocation_state",
    "crash_date", -- Date of crash
    "crash_time", -- Time of crash
    "subzone", -- When used with district and zone, will show subzone of where the crash happened
    "st_type", -- Crash location - street type
    "train_involved", -- Will be marked with 'X" if the crash involved a train
    "road_condition", -- Environmental or physical condition of roadway
    "alignment", -- Orientation and slope of roadway
    "file_number", -- Accident Number
    "tot_veh", -- Number of vehicles involved in crash
    "district", -- District of where the crash happened
    "zone", -- When used with district, will show zone of where the crash happened
    "st_number", -- Crash location - street number
    "formattedstreet", -- Fully formatted street address
    "at_intersection", -- Will be marked with 'X" if the crash happened at an intersection
    "closest_street", -- Closest street to where the crash happened
    "surface_cond", -- Road surface condition
    "surface_type", -- Road surface type
    "primary_factor", -- Primary causative factor for the crash
    "second_factor", -- Secondary causative factor for the crash
    "weather", -- Prevailing weather condition at time of crash
    ":@computed_region_jrqt_zu77",
    ":@computed_region_uvg4_nwq8",
    ":@computed_region_i2e6_956r",
    ":@computed_region_8siy_mghw",
    ":@computed_region_tqy7_429i",
    ":@computed_region_qfmj_2fwi",
    ":@computed_region_9v63_zwfd",
    ":@computed_region_92rf_uvyc",
    ":@computed_region_hfgy_t898",
    "geolocation_address",
    "geolocation", -- Full street address for geocoding
    "lighting", -- Lighting condition 
    "access_control", -- Degree of control by public authority to the abutting land
    ":@computed_region_tm4z_r3je",
    ":@computed_region_8tu6_j4iw",
    "geolocation_zip",
    "geolocation_city",
    "road_type", -- Layout of roadway
    "manner_of_collision", -- Manner which vehicles initially came into contact 
    "hit_run", -- Will be marked with 'X" if the crash was a 'hit and run'
    "occured_on", -- Type of roadway
    "st_direction", -- Crash location - street direction
    ":@computed_region_ntzg_c2w3",
    "pedestrian" -- Will be marked with 'X" is the crash involved a pedestrian
FROM
    "brla-gov/legacy-baton-rouge-traffic-incidents-2010-2020-2tu5-7kif:latest"."legacy_baton_rouge_traffic_incidents_2010_2020"
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 brla-gov/legacy-baton-rouge-traffic-incidents-2010-2020-2tu5-7kif with SQL in under 60 seconds.

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, 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 brla-gov/legacy-baton-rouge-traffic-incidents-2010-2020-2tu5-7kif: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 brla-gov/legacy-baton-rouge-traffic-incidents-2010-2020-2tu5-7kif

Checkout 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 brla-gov/legacy-baton-rouge-traffic-incidents-2010-2020-2tu5-7kif:latest

This will download all the objects for the latest tag of brla-gov/legacy-baton-rouge-traffic-incidents-2010-2020-2tu5-7kif 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 brla-gov/legacy-baton-rouge-traffic-incidents-2010-2020-2tu5-7kif: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 brla-gov/legacy-baton-rouge-traffic-incidents-2010-2020-2tu5-7kif:latest

This 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, brla-gov/legacy-baton-rouge-traffic-incidents-2010-2020-2tu5-7kif is just another Postgres schema.

Related Documentation:

Loading...