Hi,
this is my contribution to (sporadic) discussions (and complains) about WMTS support quality in MicroStation and other products.
Recently, I was asked by my customer for help with WMS and WMTS in MicroStation CONNECT Edition and how such data can be printed. Because we found a lot of issues during WMTS testing, and the final decision is that there are so many disfunctions and bugs that WMTS in MicroStation cannot be used in production (especially when compared with other products), I put together a few examples, using public data sources, so anybody can repeat the testing (and it’s used as test case for Bentley support as well ;-).
A basic requirement is simple: To use WMTS in MicroStation instead of WMS, because of speed and also, because some data providers migrate their servers from WMS to WMTS.
We use typically one coordinate systems only and the systems is “just XY coordinates”, so the task should be simple: To place raster to the right position in model (it is how WMS works with no big problems). The system is S-JTSK and usually EPSG 5514 is recommended to use (in the past it was 102067, now treated as obsolete).
A summary of tests:
No EPSG set in model (no-EPSG.dgn):
EPSG 5514 set in model (EPSG-5514.dgn):
I also tried how the files mentioned above (no-EPSG.dgn and EPSG-5514.dgn) work when used as references. Because only map in EPSG 32633 with applied transformation to EPSG 5514 works (displayed in the right position), I tested only this combination.
The results are not good:
Other products, like QGIS (tested myself) or Autodesk Civil 3D (told me by my customer ;-) work fine without any problem (I am not sure about AutoCAD or ArcGIS, but I do not hear any complains).
The test data is attached.
To log the found issues officially, I plan to create service ticket with link to this post also.
With regards,
Jan
test_data.zip
Service Request number 7001511884 created.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Excellent analysis with evidence!
Jan Šlegr said:Bentley Support confirmed the reported issue(s) and the development was notified
Good result!
Regards, Jon Summers LA Solutions
Jon Summers said:Excellent analysis with evidence!
Thanks :-)
It took a huge amount of time (the most of yesterday) to put everything together in some understandable form, but as developer I know that without clear, exact and reproducible description, bugs cannot be fixed quickly.
Another (sad and pessimistic) question is why such crucial feature does not work perfectly from the first version, especially when competitive products offers it in better quality for last several years.
Regards,
Jan Šlegr said:Service Request number 7001511884 created
An update: Bentley Support confirmed the reported issue(s) and the development was notified
Not only WMTS is dysfunctional everything related to WMS/WMTS is not production ready and only somewhat barely works.
U17.11. Trying to create new WMTS connection from this source - https://ims-web.vvd.gov.lv/geoserver/gwc/service/wmts?REQUEST=GetCapabilities
2. Wrong location - https://servisi.lgia.gov.lv/lksopen/rest/services/ORTO/Ortofoto_v1/MapServer/WMTS/1.0.0/WMTSCapabilities.xml
3.Error(WMTS map tile matrixes are not organized as definition of well-known scale set GoogleMapsCompatible.) - https://portals.daugavpilsnovads.lv/arcgis/rest/services/tmpOrtofoto2017/MapServer/WMTS/1.0.0/WMTSCapabilities.xml
Seems a little improvement as before in U17 it showed this:
4. Raster outside design plane error - https://gis.geoportals.lv/server/rest/services/Hosted/LV_3D_reljefs/ImageServer/WMTS/1.0.0/WMTSCapabilities.xml
Result 0/4 wmts usable.