Hand-in-Hand Geospatial Platform

The Hand-in-Hand Geospatial Platform is a supporting tool for the Hand-in-Hand (HiH) Initiative, an evidence-based, country-led and country-owned initiative to accelerate the Sustainable Development Goals (SDGs), SDG1 and SDG 2, using the most sophisticated tools available, including advanced geo-spatial modeling and analytics to identify the biggest opportunities to raise the incomes and reduce the inequities and vulnerabilities of rural populations, who constitute the vast majority of the world's poor. The platform brings together over 20 technical units from multiple domains across FAO, from Animal Health to Trade and Markets, integrating data from across FAO on Soil, Land, Water, Climate, Fisheries, Livestock, Crops, Forestry, Trade, Social and Economics, among others.

Website: https://www.fao.org/hih-geospatial-platform/en/

Type of Digital Public Good

  • ✅  Open content
  • Open data
  • Open software
  • Open standard
  • Open AI model

1. Is it relevant to one of the Sustainable Development Goals?

2. Does it use an appropriate open license?

Yes, this project is licensed under the following license(s):

3. Is ownership clearly defined?

Is the ownership of the project and everything that the project produces clearly defined and documented?

Yes

If yes - please link to the relevant copyright, trademarks, or ownership documentation for the project.

https://www.fao.org/hih-geospatial-platform/en/

4. Does the license of libraries/dependencies undermine the openess of the project?

Does this open project have mandatory dependencies (i.e. libraries, hardware) that create more restrictions than the original license?

No

If yes - are the open source components able to demonstrate independence from the closed component(s) and/or are there functional, open alternatives?

Not Applicable

If yes - please describe how the open source components are independent and/or list the open alternatives for the closed component:

Not Applicable

5. Is there documentation?

Does some documentation exist of the source code, use cases, and/or functional requirements. For software projects, this should be present as technical documentation that would allow a technical person unfamiliar with the project to launch and run the software. For datasets and data projects, this should be present as documentation that describes all the fields in the set, and provides context on how the data was collected and how it should be interpreted. For content collections, this should indicate any relevant compatible apps, software, hardware required to access the content and any instructions about how to use it.

Yes

If yes - please link to the relevant documentation:

6. Is non PII data and/or content accessible?

Does this project collect or use non-personally identifiable information (non-PII) data and/or content?

No

If yes - is there a mechanism for extracting or importing non-personally identifiable information (non-PII) from the system in a non-proprietary format?

Not Applicable

If yes - describe the mechanism for extracting or importing non-personally identifiable information from the system in a non-proprietary format:

Not Applicable

7. Does the project adhere to privacy and other applicable international and domestic laws?

Has this project taken steps to ensure adherence with relevant privacy, domestic, and international laws? For example, the General Data Protection Regulation (GDPR) in the European Union or the Supplementary Act A/SA.1/01/10 on Personal Data Protection for the Economic Community of West African States (ECOWAS) (yes/no)

Yes

If yes, please list some of relevant laws that the project complies with:

If yes, please describe the steps this project has taken to ensure adherence (include links to terms of service, privacy policy, or other relevant documentation):

8. Does the project adhere to standards and best practices?

Does this project support standards? (i.e. Web Content Accessibility Guidelines (WCAG) 2.1 or other standards such as those listed on W3C)

Yes

Which standards does this project support (please list)

  • HTTPS

Can you point to evidence of your support? (i.e. please link to your validator, open test suite, etc.)

Not Applicable

Was this project built and developed according to or in adherence with any design, technical and/or sector best practices or principles? i.e. the Principles for Digital Development?

Yes

Which principles and best practices does this project support (please list)

  • Principles For Digital Development
  • Human Centered Design Principles

9. Does the project do no harm by design?

Has this project taken steps to anticipate, prevent and do no harm by design?

On the whole, does this project take steps to ensure that it anticipates, prevents and does no harm by design?

Yes

Is there any additional information you would like to share about the mechanisms, processes or policies that this project uses to avoid doing harm by design?

http://www.fao.org/contact-us/privacy-policy/en/

9.a. Data Privacy & Security

Does this project collect or store personally identifiable information (PII) data and/or content?

No

If yes - please list the types of data and/or content collected and/or stored by the project:

Not Applicable

If yes - does this project share this data and/or content with third parties?

No

Please describe the circumstances with which this project shares data and/or content with third parties. Please add links as relevant.

Not Applicable

If yes - does the project ensure the privacy, security and integrity of this data and/or content collection and has it taken steps to prevent adverse impacts resulting from its collection, storage and distribution.

Yes

If yes - please describe the steps, and include a link to the privacy policy and/or terms of service:

For site security purposes and to ensure that this service remains available to all users, FAO employs software programs to monitor network traffic to identify unauthorized attempts to upload or change information, or otherwise cause damage.
Except for authorized investigations and to maintain required correspondence files, no other attempts are made to identify individual users or their usage habits. Raw data logs are used to determine the number of users and, occasionally, which general domains are accessing the FAO website. FAO also collects anonymous information about users’ browsing behaviour when users visit the website, through the use of cookies. By using the FAO website, users agree that FAO can place cookies on users’ computer, mobile phone or handheld devices.
Any information provided to FAO by users is held with the utmost care and security, and is not used in any manner other than that set forth in the Privacy Policy (http://www.fao.org/contact-us/privacy-policy/en/), or in any additional site-specific policies, without users' explicit consent.
All FAO employees who have access to or are associated with the processing of personal data are obliged to respect the confidentiality of official business matters, including personal data.

9.b. Inappropriate & Illegal Content

Does this project collect, store or distribute content?

No

If yes - what kinds of content does this project, collect, store or distribute? (i.e. childrens books)

Not Applicable

If yes - does this project have policies that describe what is considered innappropriate content? (i.e. child sexual abuse materials)

Not Applicable

If yes - please link to the relevant policy/guidelines/documentation.

Not Applicable

If yes - does this project have policies and processes for detecting and moderating innappropriate/illegal content?

Not Applicable

If yes - please describe the policies and processes for detecting, reporting and removing innapropriate/illegal content (Please include the average response time for assessment and/or action. Link to any policies or descriptions of how inappropriate content is handled):

Not Applicable

9.c. Protection from harassment

Does this project facilitate interactions with or between users or contributors?

No

If yes - does the project take steps to address the safety and security of underage users?

Not Applicable

If yes - please describe the steps this project takes to address risk or prevent access by underage users:

Not Applicable

If yes - does the project help users and contributors protect themselves against grief, abuse, and harassment?

Not Applicable

If yes - please describe the steps taken to help users protect themselves.

Not Applicable

Development & deployment countries

List of countries this project was developed in.

  • Afghanistan
  • Angola
  • Bangladesh
  • Bhutan
  • Burkina Faso
  • Burundi
  • Cabo Verde
  • Cameroon
  • Chad
  • Ecuador
  • El Salvador
  • Eritrea
  • Ethiopia
  • Gabon
  • Gambia
  • Guatemala
  • Guinea
  • Guinea-Bissau
  • Haiti
  • Honduras
  • Kiribati
  • Laos
  • Malawi
  • Mali
  • Mozambique
  • Nepal
  • Niger
  • Nigeria
  • Pakistan
  • Papua New Guinea
  • Peru
  • Rwanda
  • Sao Tome and Principe
  • Senegal
  • Solomon Islands
  • Somalia
  • Sudan
  • Syria
  • Tajikistan
  • Tuvalu
  • Uganda
  • Tanzania
  • Yemen
  • Zimbabwe

List of countries this project is actively deployed in.

  • Afghanistan
  • Angola
  • Bangladesh
  • Bhutan
  • Burkina Faso
  • Burundi
  • Cabo Verde
  • Cameroon
  • Chad
  • Ecuador
  • El Salvador
  • Eritrea
  • Ethiopia
  • Gabon
  • Gambia
  • Guatemala
  • Guinea
  • Guinea-Bissau
  • Haiti
  • Honduras
  • Kiribati
  • Laos
  • Malawi
  • Mali
  • Mozambique
  • Nepal
  • Niger
  • Nigeria
  • Pakistan
  • Papua New Guinea
  • Peru
  • Rwanda
  • Sao Tome and Principe
  • Senegal
  • Solomon Islands
  • Somalia
  • Sudan
  • Syria
  • Tajikistan
  • Tuvalu
  • Uganda
  • Tanzania
  • Yemen
  • Zimbabwe