Support for WMTS

Hi Stian,

WMTS is not supported in MicroStation. And unfortunately it seems it will be also not supported in MicroStation CONNECT Edition ... at least doesn't work in the current EAP2 testing version.

With regards,

Jan

To bad. The Norwegian Mapping Authority delivers both WMS and WMTS maps, but the WMS has a daily limit of 300 views/calls to the server. The WMTS has a limit of 10000 views/calls.

Happy Christmas

-Stian

Stian,

Bentley Systems currently does not support WMTS maps. Defect # 19459 has been opened for the request to support WMTS maps. Can you send me your Account ID, Company Name and contact information and I will add your request to Defect # 19459?

frank.mcallister@bentley.com

Hi Stian,

As Jan WMTS is not currently supported.

That being said it does not necessarily mean that you could do more request to the Norwegian Mapping Authority server with WMTS.

Why?

Well the WMTS unity of querying is a tile compared to WMS, which was a region. I'm not well versed into WMTS, but let's say that the tile are 256 per 256 pixels. Let's say furthermore that you want to display a region of 1100 per 770 pixels. That means that you would require 15 tiles to display this region if the tiles are aligned with the region border, or 30 if there are not (which would be most of the time). Which means 30 queries.

For WMS MicroStation does only one query for the whole displayed region.

So 300 WMS worth of 30 tiles equals 9000 tile queries.

That being said I'm not sure what the views/calls unity is referring to so my computation might be wrong.

Still worth checking.

Thanks,

Mathieu

Hi Stian,

As Jan WMTS is not currently supported.

That being said it does not necessarily mean that you could do more request to the Norwegian Mapping Authority server with WMTS.

Why?

Well the WMTS unity of querying is a tile compared to WMS, which was a region. I'm not well versed into WMTS, but let's say that the tile are 256 per 256 pixels. Let's say furthermore that you want to display a region of 1100 per 770 pixels. That means that you would require 15 tiles to display this region if the tiles are aligned with the region border, or 30 if there are not (which would be most of the time). Which means 30 queries.

For WMS MicroStation does only one query for the whole displayed region.

So 300 WMS worth of 30 tiles equals 9000 tile queries.

That being said I'm not sure what the views/calls unity is referring to so my computation might be wrong.

Still worth checking.

Thanks,

Mathieu

Hi.

I've not checked your're computation, but from what I've seen in other software that we use is that the tiles are cacheable. Once I've "zoomed" in on my project location, the tiles are cached on my harddrive (and can be used when I'm offline as well.)

-Stian

Hi Stian,

Since WMS server doesn't provide information about their tiling strategy or the different resolution factor of their data it is very hard to cache correctly the data while providing the same results as if the data was always directly queried from the server, which is why we do not cache WMS data. Also I think there is legal issue regarding physically caching the WMS data so that the WMS server doesn't need to be access.

For those reasons we almost always query the data from the server, though we do have some RAM caching when new WMS data is requested at the same resolution (i.e. : panning).

HTH,

Mathieu

Is it possible to disable this WMS caching in RAM? It acts weird in v8i and CONNECT editions. At some zoom levels it doesn't refresh view and shows low resolution and correct resolution image at the same time. It is most noticable for WMS which have lines only. Also as there are no indication if request is finished users are confused when it is actually loaded.

Hi Otto,

The caching has been there for many years, my guess is more the WMS server is doing weird things (we have seen that quite often).

Have you tried with different WMS server to see if it occurs with all servers?

Thanks,

Mathieu

It is weird WMS server named Bentley Geo web publisher it has been weird for many years :)

Regarding the WMS caching in MS there seem to be issues with refreshing the view starting from SS3. It doesn't seem to be related to server as there are no issues in other WMS clients and also in v8i SS1 it works much better. See attached example(not from GWP server). Borders are not correctly shown when zooming in and out.

ST_WMS_robeza-EPSG3059.zip