wrong coordinates in EPSG:2056

[gpt]

In version 3.0 beta 2 the coordinates for the swiss grid (2056) are calculated wrong, see appendix. For this map position (see mouse on screenshot: 7.256028174, 47.143598009) the coordinates should be: 2586149.188, 1221418.753 (EPSG:2056) (see ​http://www.swisstopo.admin.ch/internet/swisstopo/en/home/apps/calc/navref.html).
The definition for EPSG:2056
(+proj=somerc +lat_0=46.95240555555556 +lon_0=7.439583333333333 +k_0=1 +x_0=600000 +y_0=200000 +ellps=bessel +towgs84=674.374,15.056,405.346,0,0,0,0 +units=m +no_defs)
is correct in MapGuide.
Even though the source data is in EPSG:3857 (PseudoMercator) and the mouse coordinates are correct in LatLon and EPS:3857, the calculation for EPSG:2056 results in wrong coordinates.
There is no NTv2-gridshift-transformation necessary for EPSG:2056.[[BR]] The WMS functionality (offering WMS out of MapGuide) has to be checked as well.

[gpt]

Screenshot MapGuide 3.0b2 mouse position

[gpt]

correct 2056-coordinates

[jng]

Just a reminder that Fusion does not use CS-Map (ie. The MgCoordinateSystem APIs) for coordinate transformations on the client-side (eg. Coordinate display). Fusion uses proj4js for this purpose.

I just want to confirm that it is proj4js that is incorrectly projecting EPSG:3857 -> EPSG:2056 and not CS-Map/MgCoordinateSystem?

[gpt]

We didn't checked it in detail, but in previous versions (e.g. 3.0b1) the coordinate transformation worked (almost) as expected. The transformation EPSG:4326 -> EPSG:2056 showed correct coordinates, while EPSG:3857 -> EPSG:2056 was wrong.

[jng]

Ticket retargeted after milestone closed

[jng]

Milestone renamed