We still see no improvements in WMS attachments even in latest Microstation 2023.
Creating new WMS attachment is still dysfunctional despite multiple support requests. It defaults to WMS 1.3 version it can't show correctly and no option to switch to OGC 1.1.1 version.
Example URL:
https://lvmgeoserver.lvm.lv/geoserver/zmni/ows
dominic SEAH said: Do you have a list of essential sites and features that they can test against before releasing?
Of course they have it was attached to all previous service requests. Seems the coding is outsourced and they do only changes to "fix" bug without actually revising the code. Seems OGC standards are not even followed.
How many more bugs to solve it. When I asked that WMS 1.3 can't be attached I didn't mean that it should be "fixed" to use 1.1.1 version only.There is nothing wrong with server but with Microstation hardcoded request to only ask for "VERSION=1.1.1". Please log another issue then that can't create a new WMS 1.3. connection.
Hi Oto,
Apparently this Issue occurs quite randomly but as it has been replicated, it will be further investigated.
This issue has been associated to BUG 1297324.
Thanks for reporting this to our attention.
Zeno
Oto said: Please do a code audit by senior developer as it a mess now.
These WFS / WMS problems seem to be dragging on... for a long time.
Bentley seems to be struggling here even to get the basix down. Do you have a list of essential sites and features that they can test against before releasing? It seems like Mstn stumbles after two clicks out of the box every time, which shouldn't be happening.
Dont know if its because the product managers cant spec the requirements properly and are short changed by the coders they hire. Or maybe the spec writing process is too onerous and they default to 'agiling' or muddling through with no binding road map.
And now check the preview it will be wrong. It is all dysfunctional.Also how to create such 1.3.0 connection from scratch.