wa-gov/vehicle-registration-summary-8xjw-yrdy
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 vehicle_registration_summary table in this repository, by referencing it like:

"wa-gov/vehicle-registration-summary-8xjw-yrdy:latest"."vehicle_registration_summary"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "gvwr_range_pounds", -- This is the weight range (in pounds) of the maximum operating weight of a vehicle including its chassis, body, engine, engine fluids, fuel, accessories, driver, passengers, and cargo. It is typically associated with Trucks.
    "gvwr_class", -- This is a numeric classification (1-8) for the maximum operating weight of a vehicle including its chassis, body, engine, engine fluids, fuel, accessories, driver, passengers and cargo. It is typically associated with Trucks.
    "transaction_type", -- This is the category of activity that was performed as defined by Department of Licensing.
    "transaction_count", --  This is the number of times an activity was completed.
    "vehicle_primary_use", -- This describes the intended use as defined by WAC 308-96A-099. This is sometimes referred to as ‘use class’.
    "fiscal_year", -- This represents the 12 consecutive months beginning July 1st and ending June 30th, and is named for the calendar year in that it ends in. For example, July 1, 2023, through June 30, 2024, is fiscal year 2024. This aligns with the State of Washington's fiscal year.
    "county", -- This is the geographic region of the state associated with the record. These addresses may be located in other states.
    "electrification_level", -- This describes how effectively a vehicle uses electricity to power it. A Mild Hybrid electric vehicle uses an electric battery and electric motor to supplement the power of an internal combustion engine (ICE) but cannot power the vehicle using electricity alone. The only energy source added externally for this type of vehicle is a petroleum product. A Strong Hybrid electric vehicle also uses an electric battery and electric motor to supplement the power of an ICE. It can power the vehicle using electricity alone. The only energy source added externally for this type of vehicle is a petroleum product. A Plug-in Hybrid electric vehicle uses an electric battery and electric motor as an alternative power source to its ICE. It can be powered using electricity alone, and can also be charged by an external source of electricity. An Electric Vehicle only uses electricity as a source of power.
    "vehicle_type", -- This is the category of the vehicle based on its physical appearance and/or intended use, as defined by the manufacturer.
    "calendar_year", -- This represents the 12 consecutive months beginning on January 1st and ending on December 31st.
    "state" -- This is the geographic region of the country associated with the record. These addresses may be located in other states.
FROM
    "wa-gov/vehicle-registration-summary-8xjw-yrdy:latest"."vehicle_registration_summary"
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 wa-gov/vehicle-registration-summary-8xjw-yrdy 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 wa-gov/vehicle-registration-summary-8xjw-yrdy: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 wa-gov/vehicle-registration-summary-8xjw-yrdy

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 wa-gov/vehicle-registration-summary-8xjw-yrdy:latest

This will download all the objects for the latest tag of wa-gov/vehicle-registration-summary-8xjw-yrdy 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 wa-gov/vehicle-registration-summary-8xjw-yrdy: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 wa-gov/vehicle-registration-summary-8xjw-yrdy: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, wa-gov/vehicle-registration-summary-8xjw-yrdy is just another Postgres schema.

Related Documentation:

Loading...