finances-worldbank/afghanistan-reconstruction-trust-fund-artf-project-79y4-tfzf
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 afghanistan_reconstruction_trust_fund_artf_project table in this repository, by referencing it like:

"finances-worldbank/afghanistan-reconstruction-trust-fund-artf-project-79y4-tfzf:latest"."afghanistan_reconstruction_trust_fund_artf_project"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "closing_year_sy", -- Solar year within which the Closing Date falls.
    "effective_year_fy", -- Fiscal year within which the Effective Date falls. The fiscal year begins on July 1st of the previous year and runs through June 30th of the designated year.
    "trust_fund_number", -- Refers to Trustee Account. The Trustee Account is the account at the highest level in the Trust Fund hierarchy into which Contributions or other funds are received. Every Trust fund hierarchy has one Trustee Account.
    "fund_allocation_year_cy", -- Calendar year within which the Posting Date falls.
    "project_name", -- Short descriptive project name.
    "project_id", -- A Bank project is referenced by a project ID (Pxxxxxxx).  More than one loan, credit, or grant may be associated with one Project ID. Projects with no project ID represent Bank-executed work.
    "trust_fund_grant_number", -- Trust Fund grant ID.  Projects are identified by this ID.
    "allocation_amount_in_usd", -- Amount allocated to project from FUND/Trust Fund Program to Trust Fund Grant. Negative amounts refer to cancelations or refunds.
    "disbursed_amount_in_usd", -- Amount disbursed from project to payee, per Grant disbursement arrangements. Negative amounts refer to cancellations or refunds.
    "sector", -- Corresponding Sector/Theme.
    "end_of_period_date", -- As Of Date represents the date as of which balances are shown in the report.
    "fund", -- Fund/Program type.
    "effective_year_cy", -- Calendar year within which the Effective Date falls.
    "trustee_fund_name", -- Refers to the Trustee Fund name used in the World Bank system to identify a Trustee Account.
    "project_status", -- Project status. Active, or closed. Note: Closed projects may still receive applications through Application Deadline Date.
    "application_deadline_year_fy", -- Fiscal year within which the  Application Deadline Date falls. The fiscal year begins on July 1st of the previous year and runs through June 30th of the designated year.
    "effective_date", -- The date on which a legal agreement becomes effective, or is expected to become effective.
    "closing_year_cy", -- Calendar year within which the Closing Date falls.
    "fund_allocation_date", -- Allocation or Disbursement posting date. An amount (that is not $0.00) in the Allocation Amount  or Disbursement column corresponds to the date in Transaction Posting Date column.
    "fund_allocation_year_sy", -- Solar year within which the Posting Date falls.
    "application_deadline_date", -- The date specified in the legal agreement (or extension) after which the Bank will no longer process disbursement request applications from the Borrower.
    "closing_year_fy", -- Fiscal year within which the Closing Date falls. The fiscal year begins on July 1st of the previous year and runs through June 30th of the designated year.
    "fund_allocation_year_fy", -- Fiscal year within which the Posting Date falls. The fiscal year begins on July 1st of the previous year and runs through June 30th of the designated year.
    "window", -- ARTF has three different funding moves:  "Investment window" i.e Infrastructure, urban development, HRD etc ; "Recurrent Cost"  i.e support operational cost of the grant operation agreement;  and "Monitoring Agent fee".
    "application_deadline_year_cy", -- Calendar year within which the  Application Deadline Date falls.
    "closing_date_most_recent", -- The date specified in the legal agreement (or extension) after which the Bank may, by notice to the borrower, terminate the right to make withdrawals from the loan account.
    "application_deadline_year_sy", -- Solar year within which the  Application Deadline Date falls.
    "effective_year_sy", -- Solar year within which the Effective Date falls.
    "task_team_leader" -- Task Team Leader for project.
FROM
    "finances-worldbank/afghanistan-reconstruction-trust-fund-artf-project-79y4-tfzf:latest"."afghanistan_reconstruction_trust_fund_artf_project"
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 finances-worldbank/afghanistan-reconstruction-trust-fund-artf-project-79y4-tfzf 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 finances-worldbank/afghanistan-reconstruction-trust-fund-artf-project-79y4-tfzf: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 finances-worldbank/afghanistan-reconstruction-trust-fund-artf-project-79y4-tfzf

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 finances-worldbank/afghanistan-reconstruction-trust-fund-artf-project-79y4-tfzf:latest

This will download all the objects for the latest tag of finances-worldbank/afghanistan-reconstruction-trust-fund-artf-project-79y4-tfzf 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 finances-worldbank/afghanistan-reconstruction-trust-fund-artf-project-79y4-tfzf: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 finances-worldbank/afghanistan-reconstruction-trust-fund-artf-project-79y4-tfzf: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, finances-worldbank/afghanistan-reconstruction-trust-fund-artf-project-79y4-tfzf is just another Postgres schema.

Related Documentation:

Loading...