Projection fix

[voinSR]

PR Checklist

Please check if your PR fulfills the following requirements:

• [x] The commit message follows our guidelines: https://github.com/dlr-eoc/ukis-frontend-libraries/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• [x] Tests for the changes have been added (for bug fixes / features)
• [x] Docs have been added / updated (for bug fixes / features)
• [x] The Project is building and passes all tests without errors

PR Type

• [x] Bugfix
• [x] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [ ] Documentation content changes
• [ ] Other... Please describe:

What is the current behavior?

Wrong projection defs led to error messages described in #199

Issue Number: #199

What is the new behavior?

• fixed of projections defs in demo-maps/projections.

• included option to fit view extent to the new projection. This is helpful e.g. when in one map user publish several different projections that do not cover common areas like Arctic and Antarctic Polar projection, in this case it make sense to navigate to the extent of the newly selected projection. This feature is optional and it is up to user to use it <ukis-projection-switch [mapSvc]="mapSvc" [projectionList]="projections" [fitViewToNewExtent]="true" [mapStateSvc]="mapStateSvc"></ukis-projection-switch> </clr-vertical-nav-group-children>

Does this PR introduce a breaking change?

• [x] Yes
• [ ] No

minor breaking change that should not affect much. The demo-map has been updated.

• @dlr-eoc/map-tools:
  • Input 'mapSvc' of ProjectionSwitchComponent become mandatory and not optional
  • Additional mandatory input in ProjectionSwitchComponent "mapStateSvc" and optional "fitViewToNewExtent"