Our Proposal to IATI¶
More details including the related JSON Scheme and Excel Template you find here:
Project-level Attributes¶
| MapMe Proposal to IATI | Current IATI Standard | Mandatory | Location in the IATI Standard |
|---|---|---|---|
| Project ID -> IATI Identifier | IATI Identifier | Y | Element of an IATI Activity |
| Data Publisher (IATI Org. Identifier) | IATI Organisation Identifier | Y | Element of an IATI Activity |
| Project Title -> Title | Title | Y | Element of an IATI Activity |
| Project Description -> Description | Description | Y | Element of an IATI Activity |
| Project Status -> Activity Status | Activity Status | Y | Element of an IATI Activity |
| Project Start / End Date | Activity Date | Y | Element of an IATI Activity |
| Project Sector -> 5-digit CRS Code | Sector (DAC Vocabulary No. 1: 5-digit CRS Code & Name) | Y | Element of an IATI Activity |
| Recipient Country / Region -> provide alternatives | Recipient Country / Recipient Region | Y | Element of an IATI Activity |
| Project Donor / Client | Participating Organisation | Y | Element of an IATI Activity |
| Finance Type | Finance Type | recommended as Y | Element of an IATI Activity |
| Name of Executing / Implementing Agency | Participating Organisation | recommended as Y | Element of an IATI Activity |
| Date of Data Collection / Latest Update | Date of latest Update | N | Element of an IATI Activity |
| Language Code | Language Code | N | Element of an IATI Activity |
Location-level Attributes¶
| MapMe Proposal to IATI | Current IATI Standard | Mandatory | Location in the IATI Standard |
|---|---|---|---|
| Field ID | - | recommended as Y | Attribute of iati-activity/location |
| Location ID | Location ID | recommended as Y | Sub-element of iati-activity/location |
| Location Name | - | recommended as Y | Sub-element of iati-activity/location |
| Location Activity Description | Location Activity Description | Y | Sub-element of iati-activity/location |
| Assign Location Reach to each Location Type | Geographic Location Reach | Y | Sub-element of iati-activity/location |
| Geographic Exactness (exact, approximate (yet unknown, admin unit, security)) | Geographic Exactness (exact, approximate - to be changed) | Y | Sub-element of iati-activity/location |
| Location Type (Name, Code, Description, Reach, Category) -> list to be updated and expanded, Reach to be added | Location Type (Name, Code, Description, Category) | Y | Sub-element of iati-activity/location |
| Change Geospatial Attributes (point, line, polygon, polygon repositories (admin unit, sectoral repositories) | Administrative / Point -> to be changed | Y | Sub-element of iati-activity/location |
| Location (Sub-)Activity Status | - | recommended as Y | Sub-element of iati-activity/location |
| Location Activity Start / End Date | - | N | Sub-element of iati-activity/location |
| Date of Data Collection / Latest Update | Date of latest Update | N | Sub-element of iati-activity/location |
| Publishing Restrictions (Security) | - | N | Sub-element of iati-activity/location |
We recommend to discontinue / integrate the following IATI standard elements in our proposed new standard core scheme - all to be discussed:
- Geographic Location Class because it conflicts with the proposed location type scheme without adding value. It contains only four categories - whether the location refers to a structure, a populated place (e.g. city or village), an administrative division, or another topological feature (e.g. river, nature reserve). Since the location types are much more precise, this does not add value.
- Geographical Precision: these categories contain overlaps with other categories and its most important elements are already covered by the new proposed categories of exactness together with the location types schema.