[Feature Request]: Add admin level labels

[wadhwamatic]

Provide a clear and concise description of what you want to happen.

Admin levels (i.e. admin 1, admin 2) are not terms that all users will be familiar with. They would instead know the local names for the admin levels, like province, district, etc.

1. I want to be able to configure the labels in layers.json. For example, see the last line here:

  "admin_boundaries": {
    "type": "boundary",
    "path": "data/mozambique/moz_bnd_adm3_WFP.json",
    "admin_code": "adm3_source_id",
    "admin_level_codes": ["adm1_source_id", "adm2_source_id", "adm3_source_id"],
    "admin_level_names": ["adm1_name", "adm2_name", "adm3_name"],
    "admin_level_local_names": ["adm1_name", "adm2_name", "adm3_name"],
    "admin_level_labels": ["Province", "District", "Sub-district"]
    }
  }

2. The labels should be translatable through the translation json files
3. Users should see the labels instead of 'Admin x' in the PRISM UI. This includes in Charts > Admin selection; and Analysis > Baseline layer selection

Is there anything else you can add about the proposal? You might want to link to related issues here, if you haven't already.

No response

[ericboucher]

Maybe we should switch to a map by level? Something like this?

"admin_boundaries": {
  "type": "boundary",
  "path": "data/mozambique/moz_bnd_adm3_WFP.json",
  "admin_levels": {
    "admin_1": {
      "code": "adm1_source_id",
      "local_name": "adm1_name",
      "label": "Province"
    },
    "admin_2": {
      "code": "adm2_source_id",
      "local_name": "adm2_name",
      "label": "District"
    },
    "admin_3": {
      "code": "adm3_source_id",
      "local_name": "adm3_name",
      "label": "Sub-district"
    }
  }
}

or even using numbers directly as keys 0, 1, ... Let's investigate if that would help make the admin logic and chart logic simpler

[wadhwamatic]

Yes, that approach sounds good @ericboucher