Sergey Voinov

> Maybe @voinSR can also verify this? As @boeckMt mentioned, initially we had something like addLayer and addLayergroup... maybe it was intention to keep it in one method and use...

in mapService i found projectionChange: Subject which can do the trick. But think it could make sense to bring this into mapState, isn't it?

i think we need to store somewhere a container with projection definitions for the map and to move the logic for projection switch to mapState (as we do with coordinates)...