Open duncandewhurst opened 8 years ago
We need to decide whether to simplify IATI's location choices or else build smart tools to abstract this complexity from end users and publishers?
Agree with all of the above and think we could lump potential solutions into four buckets:
Simplify IATI standard and/or improve guidance I agree that with the complexity of IATI's location choices - in making NGO Aid Map IATI compliant, we were confused about which of IATI's many location elements we should publish data on. We could address this issue by either:
Provide geocoding tools As Mel suggests, I think it would also be useful to provide publishers with tools that would allow them to extract ADM2s from things like project titles, descriptions, documents, etc. and then add that data to their IATI file and/or internal systems. DG developed an open aid geocoder earlier this year.
Advocate for improvement in internal systems We may also need to do a bit of advocacy to get organizations to start capturing this information internally (ADM2 or more precise location info), if they aren't already. It may also be that only actors further down the aid chain have this data.
Work on opening and/or improving ADM2 data in gazetteers We've been trying to add ADM2 data to NGO Aid Map and are finding that openly licensed sources are out of date and that better sources aren't available to all organizations. Here again the ideal solution would seem to involve a mix of tools and advocacy.
Open aid geocoder is a great resource -- would be happy to set up a demonstration.
Additionally, wanted to ask if we're thinking of bundling all ADM2 information -- i.e. a list of all relevant locations -- or if we want to somehow include a attribution system whereby locations are tied to shares of funding, allocation of resources, specific activities, proportion of the project, etc.
IATI supports a sufficient level of location data but the quality of published data is poor.
How do we encourage or force better publication of location data down to admin 2 level?
The current IATI location documentation has too many choices and too much complexity.