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 wildland_search_and_rescue_missions_by_nys_forest table in this repository, by referencing it like:
"ny-gov/wildland-search-and-rescue-missions-by-nys-forest-u6hu-h7p5:latest"."wildland_search_and_rescue_missions_by_nys_forest"or in a full query, like:
SELECT
":id", -- Socrata column ID
"activity", -- The primary activity the subject was undertaking in need of a search or rescue response: aircraft, biking, boating, camping, chainsaw climbing: rock/ice, criminal, despondent, fishing, flood victim, hiking, horseback riding, hunting, motor vehicle, off road vehicle/atv/, runaway, Skiing, snowmobile, stranded, swimming, walking, whitewater
":@computed_region_yamh_8v7k",
":@computed_region_wbg7_3whc",
":@computed_region_kjdx_g34t",
"incident_adirondack_park", -- Did incident occur within the geographic boundary of the Adirondack Park (YES/NO)
"last_known_point_county", -- County of the Subject's last known point
"incident_catskill_park", -- Did incident occur within the geographic boundary of the Catskill Park (YES/NO)
"subject_number", -- Number in party being searched for
"situation", -- The situation the subject was in when help was requested: Fugitive, Illness, Injured, Lost, Missing, Overdue, Stranded
"subject_country", -- Subject's country of origin and/or legal residence
"last_known_point_state_land_name", -- Name of the State Land unit, if the incident search area is within a State Land unit
"last_known_point_municipality", -- Municipality of the Subject's last known point
"incident_closed_time", -- Time the incident was completed and demobilized
"location", -- Open Data/Socrata-generated geocoding information.
"incident_start_time", -- Time NYS Forest Rangers were first deployed to the incident
"subject_age", -- Subject’s Age
"subject_state", -- State Subject resides in
"location_found_latitude", -- Latitude in WGS 84/NAD 83 format subject’s location
"location_found_longitude", -- Longitude in WGS 84/NAD 83 format subject’s location
"location_found_elevation", -- Elevation at which the subject was located
"number_of_rangers_involved", -- The total number of DEC Forest Rangers involved in the incident
"last_known_point_land_class", -- Land classification of the land of the subject's last known location (LKP): Conservation, Easement, County Land, DEC Campground, Federal Land, Forest Preserve, Native People's Land, OPRHP State Land, Other DEC Land, Other Municipal Land, Private Land, State Forests, Wildlife Management Area
"found_in_search_area", -- Was the subject located in the established search area: (YES/NO)
"subject_gender", -- Subject’s gender
"incident_number", -- Number assigned to each new incident
"other_agency_involvement", -- Agencies other than DEC involved (YES/NO)
"response_type", -- Nature of the incident: Fugitive Search, Search, Rescue, or Recovery
"incident_region", -- NYSDEC Region that has jurisdiction over the incident: Region 1: (Long Island) Nassau and Suffolk counties Region; 2: (New York City) Brooklyn, Bronx, Manhattan, Queens and Staten Island; Region 3: (Lower Hudson Valley) Dutchess, Orange, Putnam, Rockland, Sullivan, Ulster and Westchester* counties; Region 4: (Capital Region/Northern Catskills) Albany, Columbia, Delaware, Greene, Montgomery, Otsego, Rensselaer, Schenectady and Schoharie counties; Region 5: (Eastern Adirondacks/Lake Champlain) Clinton, Essex, Franklin, Fulton, Hamilton, Saratoga, Warren and Washington counties; Region 6: (Western Adirondacks/Eastern Lake Ontario) Herkimer, Jefferson, Lewis, Oneida and St. Lawrence counties; Region 7: (Central New York) Broome, Cayuga, Chenango, Cortland*, Madison, Onondaga, Oswego, Tioga and Tompkins counties; Region 8: (Western Finger Lakes) Chemung, Genesee, Livingston, Monroe, Ontario, Orleans, Schuyler, Seneca, Steuben, Wayne and Yates counties; Region 9: (Western New York) Allegany, Chautauqua, Cattaraugus, Erie, Niagara and Wyoming counties
"start_date", -- Date NYS Forest Rangers were first deployed to the incident
"technique", -- The method by which the subject was rescued or recovered: Airboat, Aircraft evacuation, Assist/own power, Carry out by foot, Dive team, Evacuation by animal, High Angle, Swiftwater, Technical Rope, Vehicle/boat evacuation
"incident_closed_date_time" -- Date the incident was completed and demobilized
FROM
"ny-gov/wildland-search-and-rescue-missions-by-nys-forest-u6hu-h7p5:latest"."wildland_search_and_rescue_missions_by_nys_forest"
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 ny-gov/wildland-search-and-rescue-missions-by-nys-forest-u6hu-h7p5 with SQL in under 60 seconds.
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, 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 ny-gov/wildland-search-and-rescue-missions-by-nys-forest-u6hu-h7p5: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 ny-gov/wildland-search-and-rescue-missions-by-nys-forest-u6hu-h7p5Checkout 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 ny-gov/wildland-search-and-rescue-missions-by-nys-forest-u6hu-h7p5:latestThis will download all the objects for the latest tag of ny-gov/wildland-search-and-rescue-missions-by-nys-forest-u6hu-h7p5 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 ny-gov/wildland-search-and-rescue-missions-by-nys-forest-u6hu-h7p5: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 ny-gov/wildland-search-and-rescue-missions-by-nys-forest-u6hu-h7p5:latestThis 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, ny-gov/wildland-search-and-rescue-missions-by-nys-forest-u6hu-h7p5 is just another Postgres schema.