I also have this begun having this problem. I have updated to the latest version of Connect and when I try to load a WMS from the
server the Save and Save and Attach are greyed out presumably because the Projected Coordinates did not come across from the server.
There is also an error message saying the WMS Map bounding box is invalid.
Is this still a defect or has something changed in the new version?
Any suggestions gratefully received!
regards
Mike
Hi
I've just met these 'errors' in trying to attach a WMS 1.3.0 in MicroStation - there are issues with the retrieved coordinates, and it doesn't help to apply a Manual Range Method - well, it does help activating the Save buttons, but there's not coming a WMS map through, only a message in the Status bar saying 'The WMS Map bounding box is invalid'
maybe it is the WMS version 1.3.0 that is causing troubles?
I'm not able to view the 'Defect 538218' link below, but I'm interested in knowing the status.
Example - two .xwms file that works and doesn't work:
This xwms fil works:
<?xml version="1.0" encoding="utf-8" standalone="yes"?><BentleyWMSFile> <VERSION>1.3</VERSION> <URL>kortforsyningen.kms.dk/topo25 <REQUEST> <VERSION>1.1.1</VERSION> <SRS>EPSG:25832</SRS> <LAYERS>topo25_klassisk</LAYERS> <STYLES /> <FORMAT>image/png</FORMAT> <TRANSPARENT>TRUE</TRANSPARENT> </REQUEST> <MAPEXTENT> <BBOX>142300,6027400,975900,6458300</BBOX> </MAPEXTENT> <LayerList> <LAYER TITLE="DTK/kort25 klassisk" NAME="topo25_klassisk" ABSTRACT="DTK/kort25 klassisk" /> </LayerList> <SERVICE> <MAXWIDTH>1024</MAXWIDTH> <MAXHEIGHT>1024</MAXHEIGHT> </SERVICE> <CapabilitiesRequest> <URL>kortforsyningen.kms.dk/service </CapabilitiesRequest> <EditorData> <RangeMethod>Calculated</RangeMethod> <LayerRange>Intersection</LayerRange> <UseModelCoordSysUsefulRange>True</UseModelCoordSysUsefulRange> <UseMapCoordSysUsefulRange>True</UseMapCoordSysUsefulRange> <ExplicitSRS>False</ExplicitSRS> </EditorData></BentleyWMSFile>
- - - - - - - - -
This xwms file doesn't work (I've edited the BBOX values manually in MicroStation):
<?xml version="1.0" encoding="utf-8" standalone="yes"?><BentleyWMSFile> <VERSION>1.3</VERSION> <URL>api.dataforsyningen.dk/dhm_DAF <REQUEST> <VERSION>1.3.0</VERSION> <SRS>EPSG:25832</SRS> <LAYERS>dhm_kote_2_5_m</LAYERS> <STYLES /> <FORMAT>image/png</FORMAT> <TRANSPARENT>true</TRANSPARENT> </REQUEST> <MAPEXTENT> <BBOX>142300,6027400,975900,6458300</BBOX> </MAPEXTENT> <LayerList> <LAYER TITLE="DHM kote, 2,5 m" NAME="dhm_kote_2_5_m" ABSTRACT="Kotepunkter (top og bund for 2,5 m kurverne) afledt fra DHM" /> </LayerList> <SERVICE> <MAXWIDTH>10000</MAXWIDTH> <MAXHEIGHT>10000</MAXHEIGHT> </SERVICE> <CapabilitiesRequest> <URL>api.dataforsyningen.dk/service </CapabilitiesRequest> <EditorData> <RangeMethod>Manual</RangeMethod> <LayerRange>Union</LayerRange> <UseModelCoordSysUsefulRange>True</UseModelCoordSysUsefulRange> <UseMapCoordSysUsefulRange>True</UseMapCoordSysUsefulRange> <ExplicitSRS>False</ExplicitSRS> </EditorData></BentleyWMSFile>
WMS 1.3 was at least in documentation supported in v8i. It was "fixed" in CONNECT and is no longer supported.
This whole situation around partial supported WMS in Bentley products for years is strange as WMS attach window clearly recognizes 1.1.0, 1.1.1 and 1.3.0 versions and even creates valid xwms file but it doesn't show correctly in view. Not to mention the recently introduced WMTS is also mostly unusable.
Thanks for replying, Oto :-)
I also noticed the support for WMTS and I am sorry to learn that this implementation also has flaws.
I don't understand the '[WMS 1.3] is no longer supported [in CONNECT]', and I'm really troubled with this lack of proper support, as my customers wants WFS ("Sorry, you can't have it'), okay then, let's have WMS ("Sorry, MicroStation seems to be having some problems with the WMSs, I'm afraid").
It's not an option to push them into Map PowerView when they need it MicroStation, where they do their valuable design work ... I might as well just point at QGIS as a better option, as it'll handle all the OGC webservices and also has the all CAD editing tools they need in the first stages of their design process.
Not to mention for QGIS bug reporting and timelines are transparent not like this when you get reply that it will be fixed in some obscure and distant version and when new version comes out it is not that new version where it is fixed.
I actually succeeded in getting the 1.3 WMS services to display properly, when I manually edited the xwms file and replaced 1.3 with 1.1.1 in the <VERSION> tag _and_ edited ted <BBOX> to something correct, that I found in an old 1.1.1 file. But I wasted a LOT of time to get here ...