Data Retrieval#
This section outlines how IATI data is retrieved by CDFD.
Data Source#
CDFD downloads a daily snapshot of all IATI data from the IATI Data Dump, a tool built by the IATI community.
CDFD currently uses all IATI data published to version 2.01 of the standard or above. This includes both valid and invalid data, so activities that are not accessible via other IATI tooling may be found in CDFD outputs.
Data Extraction#
Activity level#
The following elements are extracted from each IATI activity:
| Activity Element | Description |
|---|---|
| iati-identifier | The unique identifier for the activity. |
| title | The title of the activity. Where possible, the relevant language version is included for supported languages (English, French, Spanish and Portuguese). |
| description | The description of the activity. Where possible, the relevant language version is included for supported languages (English, French, Spanish and Portuguese). |
| reporting-org | The name of the organisation publishing this IATI data, mapped from the list of reporting organisations as recorded on the IATI Registry. |
| reporting-org/@type | The type of reporting organisation publishing this IATI data. |
Note
The description element is not included in whole country/region downloads available from the home page. This is due to file size limitations.
Transaction level#
Important
Only incoming fund, outgoing commitment, disbursement, and expenditure transaction types are included in CDFD’s analysis.
The following elements are extracted from each transaction. If these four fields do not exist, the transaction is not processed.
| Transaction Element | Description |
|---|---|
| value | The transaction value in the published currency. |
| transaction-date/@iso-date | The date of the transaction. |
| value/@value-date | The date to be used for determining the exchange rate for currency conversions. |
| transaction-type | The transaction type. |
Transaction or activity level#
For some elements, the data can be declared at transaction or activity level. Transaction level is used by CDFD as default, backed up by activity level elements.
| Transaction Element | Activity Element | Description |
|---|---|---|
| @currency | @default-currency | The transaction currency, or the activity default currency. |
| aid-type | default-aid-type | The transaction aid type, or the activity default aid type. Only DAC aid types are included. |
| finance-type | default-finance-type | The transaction finance type, or the activity default finance type. |
| flow-type | default-flow-type | The transaction flow type, or the activity default flow type. |
| provider-org | reporting-org or participating-org | The transaction provider organisation. |
| receiver-org | reporting-org or participating-org | The transaction receiver organisation. |
| @humanitarian | @humanitarian | The transaction humanitarian flag, or the activity humanitarian flag. A boolean value, where 1 = True and 0 = False. |
Provider and receiver organisations#
Where provider or receiver organisations are not declared, the following activity level logic is applied:
| Transaction Type | Provider org | Receiver org |
|---|---|---|
| 1 - Incoming Funds | participating-org - Funding org | reporting-org |
| 2 - Outgoing Commitment | reporting-org | participating-org - Implementing org |
| 3 - Disbursement | reporting-org | participating-org- Implementing org |
| 4 - Expenditure | reporting-org | participating-org - Implementing org |
As there can be multiple funding organisations reported for one activity, there may be multiple values in this field.
Multi-value elements#
When recipient country/region or sector are declared at activity level, they may have multiple values with percentage splits.
A “Multi Country” column has been added CDFD outputs to indicuate that a transaction is part of a multi country/region project, where 1 = True and 0 = False.
| Transaction Element | Activity Element | Description |
|---|---|---|
| recipient-country | recipient-country | The transaction recipient country, or the list of activity recipient countries. |
| recipient-region | recipient-region | If no recipient countries are declared, DAC regions are used. |
| sector | sector | The transaction sector, or the list of activity sectors. Only DAC 5 digit sector codes are used to reduce complexity. |