Use case
Map widgets colour countries using a boundaries file that ships with the platform.
Administrators can already replace the base map with their own file from Settings > Parameters > Map configuration, but they cannot replace the country boundaries drawn on top of it. A deployment that needs different boundaries has no way to provide them, and the colouring can end up out of step with a custom base map.
Current workaround
None. Changing the boundaries means rebuilding the platform image, which is not an option on SaaS deployments.
Proposed solution
Let administrators upload their own country boundaries file in Settings > Parameters > Map configuration, next to the custom map, and go back to the bundled one at any time. A file that cannot be used is rejected with an explanation. The bundled file remains the default, so nothing changes for deployments that do not upload one.
Additional information
The boundaries file is currently compiled into the frontend bundle, where it weighs about 6 MB compressed. Serving it on its own takes it out of the bundle.
If the feature request is approved, would you be willing to submit a PR?
Yes
Use case
Map widgets colour countries using a boundaries file that ships with the platform.
Administrators can already replace the base map with their own file from Settings > Parameters > Map configuration, but they cannot replace the country boundaries drawn on top of it. A deployment that needs different boundaries has no way to provide them, and the colouring can end up out of step with a custom base map.
Current workaround
None. Changing the boundaries means rebuilding the platform image, which is not an option on SaaS deployments.
Proposed solution
Let administrators upload their own country boundaries file in Settings > Parameters > Map configuration, next to the custom map, and go back to the bundled one at any time. A file that cannot be used is rejected with an explanation. The bundled file remains the default, so nothing changes for deployments that do not upload one.
Additional information
The boundaries file is currently compiled into the frontend bundle, where it weighs about 6 MB compressed. Serving it on its own takes it out of the bundle.
If the feature request is approved, would you be willing to submit a PR?
Yes