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 registration_of_charities_paid_solicitors table in this repository, by referencing it like:
"colorado-gov/registration-of-charities-paid-solicitors-37wu-kn3g:latest"."registration_of_charities_paid_solicitors"or in a full query, like:
SELECT
":id", -- Socrata column ID
"fiscalyearenddate", -- Ending (month/day/year) tax year this report covers
"fiscalyearstartdate", -- Beginning (month/day/year) tax year this report covers
"programserviceratio", -- Program service ratio
"expirationdate", -- Date when non profit expires
"dateformed", -- Date when non profit was formed
"principalcountry", -- Country for principal address
"principaladdress2", -- Second line of the principal address
"statusdate", -- Date currentStatus was assigned
"currentstatus", -- Organization registration status with CDOS office
"legalbusinessformation", -- Legal Business Formation
"pbcannualbenefitreport", -- For PBC organizations, instructions on obtaining the annual benefit report including location
"unrestrictedassests", -- Unrestricted assets
"expensesothercomment", -- Other expenses comment
"expensesother", -- Other expenses
"expensesfundraising", -- Fundraising expenses
"expensesfromprogramservices", -- Expenses from program services
"revenuetotal", -- Total of all revenues
"revenuefromcontibutions", -- Revenue from contributions
"totalexpensesplusmanagementgeneraldividedbycontributions", -- (Total fundraising expenses + total management and general expenses) divided by total contributions
"expensesdividedbycontributions", -- Total fundraising expenses divided by total contributions
"irsdeterminationdate", -- Date of application for exemption or date of letter of determination of exemption
"nteecode3", -- National Taxonomy of Exempt Entities Code Description
"nextrenewalregistrationdate", -- Due date for entity’s next renewal of registration
"registrationapproveddate", -- Date and time at which registration was approved
"cfosigneddate", -- For Charitable Organizations, date CFO signed registration
"cfoname", -- For Charitable Organizations, CFO first and last name
"authorizedofficersigneddate",
"phone", -- Phone (area code + 7 digit number + extension)
"mailingprovince", -- Province for the mailing address, if available
"mailingzipcode", -- Mailing zip code
"mailingstate", -- Mailing state
"mailingcity", -- Mailing city
"mailingaddress2", -- Second line of the mailing address
"mailingaddress", -- Mailing address
"residentialcounty", -- Residential county
"principalzipcode", -- Principal zip code
"principalcity", -- Principal city
"principaladdress", -- Principal address
"amendmententityid", -- If filing type is Amendment, then Entity ID of master or renewal record
"fein", -- Federal Employer Identification Number
"entityid", -- Entity Id
"reportingperiodend", -- End (month-day) of fiscal year
"reportingperiodbegin", -- Beginning (month-day) of fiscal year
"placeformed", -- Place where non profit was formed
"principalprovince", -- Province for principal address, if there is one
"revenuefromother", -- revenue from other sources
"conflictofinterestaffirmation", -- Paid Solicitor Conflict of Interest affirmation (boolean or null if not a paid solicitor)
"pbcbenefitreportsent", -- For PBC organizations, whether benefit annual report was sent to stockholders (y, n, n/a, null if non-pbc)
"pbcrecordingmethod", -- For PBC organizations, recording/accounting method 'accrual', 'cas', or customer input.
"permanentlyrestrictedassets", -- Permanently restricted assets
"temporarilyrestrictedassets", -- Temporarily restricted assets
"endofyearassestsminusliabilities", -- End of year assets minus end of year liabilities
"endofyeartotalliabilities", -- Total end of year liabilities
"endofyearassests", -- Total end of year assets
"expensesaffiliates", -- Payment to affiliates expenses
"expensesfromadministrativeother", -- Administrative and other general expenses
"revenuefromspecialevents", -- Revenue from special events and activities
"revenuefrominvestments", -- Revenue from investments
"revenuefromgovernment", -- Revenue from government
"statedgiftnottaxdeductible", -- If organization state clearly gifts or contributions were not tax deductible, then ‘Y’
"solicitednontaxdeductiblegifts", -- If organization solicited any non-tax deductible gifts or contributions, then ‘Y’
"relatedtootherorganization", -- If organization is related to any other organization, then ‘Y’
"relatedorganizationsname", -- Name of related organization
"totalmanagementgeneralexpensespreviousyear", -- Total management and general expenses in previous year
"totalfundraisingexpensespreviousyear", -- Total fundraising expenses in previous year
"outsideprofessionalfundraiserfees", -- Outside professional fundraisers fees
"donationstaxdeductible", -- If donations to organization are tax deductible, then ‘Y’
"nteecode2", -- National Taxonomy of Exempt Entities Code Description
"nteecode1", -- National Taxonomy of Exempt Entities Code Description
"paymentprocesseddate", -- Date and time payment was processed
"authorizedofficername", -- Official first and last name
"website", -- Website URL
"fax", -- Fax number
"mailingcountry", -- Country for the mailing address
"filingtype", -- Filing type: Master, Amendment, Renewal, Extension, Fiscal Year Change, Estimate Extension
"registranttypeabbr", -- Registrant Type
"expensestotal", -- Total of all expenses
"revenuefromsales", -- Revenue from sales
"programservicerevenue", -- Program service revenue
"totalcontributionsraisedpreviousyear", -- Total contributions raised in previous year
"extensionfiled", -- If extension was filed, then ‘Y’
"taxexemptcode", -- Tax exempt code - IRS subsection
"principalstate", -- Principal state
"documentid", -- The number assigned to each document a user files
"name", -- Charitable Organization, Paid Solicitor or Professional Fundraising Consultant name
"publicbenefitcorporation", -- If organization is a pbc or not
"consolidatedregistrationstatement", -- Is organization’s registration a consolidated Registration statement (‘Y’ or ’N’)
"taxexemptstatus", -- If tax exempt organization, then ‘Y’ else ‘N’
"actualfinancialsprovided", -- If actual financials are provided then ‘Y’ else ‘N’
"relatedorganizationtaxexempt", -- If related organization is tax exempt, then ‘Y’
"pbcpromotedbenefit", -- For PBC organizations, how it promoted benefit information
"conflictofinterest" -- Paid Solicitor Conflict of Interest (boolean, null if not a paid solicitor)
FROM
"colorado-gov/registration-of-charities-paid-solicitors-37wu-kn3g:latest"."registration_of_charities_paid_solicitors"
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 colorado-gov/registration-of-charities-paid-solicitors-37wu-kn3g 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 colorado-gov/registration-of-charities-paid-solicitors-37wu-kn3g: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 colorado-gov/registration-of-charities-paid-solicitors-37wu-kn3gCheckout 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 colorado-gov/registration-of-charities-paid-solicitors-37wu-kn3g:latestThis will download all the objects for the latest tag of colorado-gov/registration-of-charities-paid-solicitors-37wu-kn3g 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 colorado-gov/registration-of-charities-paid-solicitors-37wu-kn3g: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 colorado-gov/registration-of-charities-paid-solicitors-37wu-kn3g: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, colorado-gov/registration-of-charities-paid-solicitors-37wu-kn3g is just another Postgres schema.