New field - Beneficiary Location: Scope

As described in this Github issue:
While describing the particular geographic area(s) that a grant benefit is very useful, some additional data might help classify and help users understand the scope to which this grant applies.

For example:

International - a grant applicable to the world/global
National - a grant applicable to a whole country
Regional - a sub region of a country (e.g., London in UK context)
District - (local authority in UK context)
Local - (ward level)
A focus would be to properly describe the above (proposed) codes, without slipping into UK specifics

This, however, brings us again to the question of codelists.

Should this field help to add more context to beneficiary location?

I am interested to know how IATI and Open Contracting deal with this and if we can implement that as well. If they use a specific codelist then we should consider using it too.

We’re considering this kind of feature for SmartyGrants. It’s very likely that simply choosing one pre-defined region will be too restrictive. For instance, a project near the boundary of two or more regions can’t accurately choose one as the area of benefit.

So at the least, you may want to consider an array of locations. You probably don’t want to allow full-blown polygon geometry to be embedded in the CSV :slight_smile:

There are several sources for region identifiers - see https://mapzen.com/blog/who-s-on-first/ or a few, MapIt is another (eg). And for reference, how OpenSpending does it.

1 Like

This would be useful for Beehive, and we’ve been using a simple classification similar to the example for a while e.g.

@rachel.rank IATI deal with activity-scope (a bit different from beneficiary but the outworkings are similar) through a matching codelist

More simply, the choices are:

name description
Global The activity scope is global
Regional The activity scope is a supranational region
Multi-national The activity scope covers multiple countries, that don’t constitute a region
National The activity scope covers one country
Sub-national: Multi-first-level administrative areas The activity scope covers more than one first-level subnational administrative areas (e.g. counties, provinces, states)
Sub-national: Single first-level administrative area The activity scope covers one first-level subnational administrative area (e.g. country, province, state)
Sub-national: Single second-level administrative area The activity scope covers one second-level subnational administrative area (e.g. municipality or district)
Single location The activity scope covers one single location (e.g. town, village, farm)

I could see that some of these would be useful in this use case