Description
MapStore2 currently supports a fixed list of coordinate reference systems (CRS) defined at deployment time in a configuration file. This feature extends that capability by connecting MapStore2 to a GeoServer endpoint that exposes thousands of standardized CRS definitions, allowing administrators to search and add projections on demand, without redeploying or editing configuration files.
From a user perspective, user with edit permissions will be able to:
- Search a projection from a remote endpoint, the input placeholder will inform the user with the
search GeoServer label
- Type a code will show the list of available projection in the remote service
- Add the projection to the available list and use it
- Remove the projection if not needed anymore
- Now the CRS selector include a zoom to projection maximum extent
The existing behavior is fully preserved: deployments that do not configure the endpoint are unaffected, and statically configured projections continue to work exactly as before.
What kind of improvement you want to add? (check one with "x", remove the others)
Other useful information
Refactoring Goals
Introduce a configurable GeoServer endpoint that allows searching and loading CRS projection definitions at runtime, while:
Keeping full backward compatibility with static projectionDefs in localConfig.json
Centralizing all projection registration logic new Module ProjectionRegistry
Eliminating ConfigUtils.getConfigProp("projectionDefs") reads
Persisting new crs definitions inside the map resource for unauthenticated access
Removing the recompose HOC from getProjectionDefs.js
Description
MapStore2 currently supports a fixed list of coordinate reference systems (CRS) defined at deployment time in a configuration file. This feature extends that capability by connecting MapStore2 to a GeoServer endpoint that exposes thousands of standardized CRS definitions, allowing administrators to search and add projections on demand, without redeploying or editing configuration files.
From a user perspective, user with edit permissions will be able to:
search GeoServerlabelThe existing behavior is fully preserved: deployments that do not configure the endpoint are unaffected, and statically configured projections continue to work exactly as before.
What kind of improvement you want to add? (check one with "x", remove the others)
Other useful information
Refactoring Goals
Introduce a configurable GeoServer endpoint that allows searching and loading CRS projection definitions at runtime, while:
Keeping full backward compatibility with static projectionDefs in localConfig.json
Centralizing all projection registration logic new Module ProjectionRegistry
Eliminating ConfigUtils.getConfigProp("projectionDefs") reads
Persisting new crs definitions inside the map resource for unauthenticated access
Removing the recompose HOC from getProjectionDefs.js