set default terrain for all maps with 2025.02

[Landry Breuil]

hi,

migrating our 2024.02 to 2025.02.00-georchestra-02, it seems with the
work that happened on the terrain selector, the 'default config' for the
terrain isnt taken anymore from localConfig.json (eg
defaultMapOptions.cesium.terrainProvider key).

i had this so far, which worked fine:


"terrainProvider": {
"type": "cesium",
"url": "https://3d.georchestra.org/terrain/",
"requestVertexNormals": true
}

i've read
https://docs.mapstore.geosolutionsgroup.com/en/latest/developer-guide/mapstore-migration-guide/#removal-of-terrain-from-cfgadditionallayers-property-using-the-new-background-selector
and managed to setup a new default terrain for the default/new maps, by
adding that section to new/config.json

{
"id": "24507c64-05b5-480d-b612-df5dc5e3b092",
"group": "background",
"provider": "cesium",
"title": "RGE ALTI",
"type": "terrain",
"url": "https://3d.georchestra.org/terrain/",
"visibility": true
}

but:
- im not sure this applies requestVertexNormals: true
- it doesnt apply to *existing* maps, which fallback to the default
boring ellipsoid. in 2024.02 those existing maps used to load my
configured default terrain..

that's with the fix for
https://github.com/georchestra/mapstore2-georchestra/issues/804 (eg
https://github.com/geosolutions-it/MapStore2/pull/12581).

i've also seen https://github.com/geosolutions-it/MapStore2/issues/9838
that seems 'related' but without actual fix/remediation.

so, should the terrainProvider by dropped from localConfig.json ? or
should it be the default instead of the ellipsoid, and one doesnt need
to edit all its maps ? or i'm missing something somewhere ?

thanks for your guidance.
--
Landry Breuil