[Feature Request]: French Translations in global deployment

[gislawill]

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

PRISM's global deployment with PMTiles-driven admin boundaries (#1417) currently only supports English names for admin units. To make this deployment useful to a broader audience, we should add support for French translations to this global deployment.

Similar to other deployments, the process for adding translations to admin boundaries involves updating the properties on the vector dataset. However, because our admin boundaries are coming from PMTiles created by a GeoParquet, the process is slightly different than how we update the GeoJSON admin boundaries.

How to update

The global admin boundaries are found in a GeoParquet stored in S3 (link — @gislawill to update link to PRISM instance). Read this data into Python using your preferred tool (GeoPandas, DuckDB, etc).

You can then add three new columns to the dataset: dv_adm0_name_fr, dv_adm1_name_fr, dv_adm2_name_fr.

For all vectors at admin level 0, you only need to provide dv_adm0_name_fr. The others can be left None.
For all vectors at admin level 1, you only need to provide dv_adm0_name_fr and dv_adm1_name_fr. The other can be left None.
For all vectors at admin level 2, all fields must be provided.

Once all data is provided, you'll rewrite the GeoParquet with the new fields and update the global admin boundary configuration file in VT Foundry to include these new fields in the vector data stored in PMTiles.

Finally, you can update the shared layer configurations (frontend/src/config/shared/layers.json) to use these new fields by including these keys:

{
  "global_admin2_boundaries": {
    ...
    "admin_level_local_names": ["dv_adm0_name_fr", "dv_adm1_name_fr", "dv_adm2_name_fr"]
  },
  "global_admin1_boundaries": {
    ....
    "admin_level_local_names": ["dv_adm0_name_fr", "dv_adm1_name_fr"]
  },
  "global_admin0_boundaries": {
    ...
    "admin_level_local_names": ["dv_adm0_name_fr"]
  },
  ...
}

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]

What is the initial source of the boundary data? Do other languages exist there?

[ericboucher]

This is potentially linked to #1459
Maybe we should switch to a [langugage] key-based approach?