M.App Enterprise Discussions

Discuss topics with other M.App Enterprise Product pioneers and experts to get the most out of it.
Showing results for 
Search instead for 
Do you mean 
Reply
Highlighted
Frequent Contributor
Posts: 102
Registered: ‎01-20-2016
Accepted Solution

WMS EPSG:5650 incomplete

[ Edited ]

Hi,

 

EPSG:5650 WMS does show up incomplete in M.App Enterprise and leaves the red dot on a blank background.

 

WMS-EPSG5650_in-IMAGINE-complete.JPG

 

In IMAGINE it's complete.

WMS-EPSG5650_in-IMAGINE-complete.JPG

 

Any help appreciated.

 

Ruth

Highlighted
Technical Evangelist
Posts: 165
Registered: ‎09-01-2015

Re: WMS EPSG:5650 incomplete

Hi Ruth,

 

is it possible to get the WMS URL? 

 

 

Kind regards,

Stefan

Highlighted
Frequent Contributor
Posts: 102
Registered: ‎01-20-2016

Re: WMS EPSG:5650 incomplete

Hi Stefan,

 

http://www.geodaten-mv.de/dienste/gdimv_dtk?

 

Thank you,

Ruth

Highlighted
Technical Evangelist
Posts: 165
Registered: ‎09-01-2015

Re: WMS EPSG:5650 incomplete

[ Edited ]

The problem is the bounding box of the Coordinate System. Obviously there are differences between http://epsg.io and http://epsg-registry.org/

 

Since we are using the latter one, because this is the official EPSG database, the bounding box of the CRS is exactly where the WMS is cut off. This means you have to set the WMS to another CRS with a bigger bounding box.

 

Official bounding box of the CRS:

Value (Decimal Degrees)
South Bound Latitude
 
47.46
 
West Bound Longitude
 
11.57
 
North Bound Latitude
 
55.03
 
East Bound Longitude
 
15.04

 

 

This means everything west of Wismar gets cut off.

 

Highlighted
Frequent Contributor
Posts: 102
Registered: ‎01-20-2016

Re: WMS EPSG:5650 incomplete

Hi Stefan,

you mean simply changing CRS in MAE GEOSERVICES?

This doesn't help, at least in my case.

 

Ruth

 

Highlighted
Technical Evangelist
Posts: 165
Registered: ‎09-01-2015

Re: WMS EPSG:5650 incomplete

Yes to a coordinate system which allows you to "see" the entire WMS.

 

There is a strange behaviour, when choosing EPSG:4326 because the WMS is mirrored. So either the WMS is wrong with the BBOX or we have to investigate on our side whats happening there.

 

What CRS have you tried? Do you see the WMS at all or is it the same behaviour as before?

Highlighted
Technical Evangelist
Posts: 733
Registered: ‎11-12-2015

Re: WMS EPSG:5650 incomplete

After chatting with Ruth I was able to replicate the issue in EPSG 5650.

I have confirmed that ,as Stefan has recommended here, using another EPSG that expands the bounding box to encapsulate the WMS features (ie. EPSG 3857) resolves the issue. Awaiting confirmation from Ruth, but this should be the way forward here given the EPSG authority definition used in M.App Enterprise for EPSG 5650.

Highlighted
Frequent Contributor
Posts: 102
Registered: ‎01-20-2016

Re: WMS EPSG:5650 incomplete

Stefan, Stephen Smiley Happy

 

I can confirm that WMS is now complete when the whole desktop M.App is switched to EPSG:3857.

I first tried to change settings simply for geoservices, that didn't help.

Vector editing seems to work fine though target projection is EPSG:5650.

 

Thank you,

Ruth