Locus Free beta - WMTS support

Yes, as far as I noticed it happens only with WMTS. WMS and regular Locus maps (downloaded form Locus store) do not seem to be affected. The number of displayed waypoints do not seem to have any influence, be it 5, 10 or 200, it is the very same effect.

According to today's info on Geoportal, there is some breakdown over there, so testing WMS and WMTS today may be difficult, since no new tiles are loaded. This is actually good, becaue it means (as far as I understand it) Locus is using cached tiles and again WMTS at larger zoom makes waypoint float over the map. This does not happen with cached WMS.

Actually, tracklogs "float" above the WMTS layer, too.

Here's link to my video with problem displayed.

https://drive.google.com/file/d/1THHgux1iEDn50COTJda6W5H7thc6pFGN/view

Hi,

unfortunate;y we have to close this ticket as unsolved. I'm sorry but we can't solved it and there isn't any quick solution. Due this fact is official support for WMTS postponed indefinitely.

Thank you for understanding.

I understand that pinpoiting a source of the "floating" problem may be a pain, since the bug is a bit odd one - it only appears at bigger zoom levels on WMTS layer (ISOK). Zoomed-out views do not seem to be affected. There was no opacity control for WMTS in the beta version but I wonder (purely as a mental excercise) what would happen if there was such control, i.e. WMTS layer could be used at some opacity with regular Locus map from the store. Would the regular map keep the waypoints/tracks "pinned" to proper place then?

Still, even viewing WMTS layers from within Locus (even with current bug) is a boost, since it eliminates the need of using another external application like Geoportal app. Having the layer enabled in Locus simplifies our work in the field.

I underastand that huinting for an elusive solution to WMTS problem may stretch your resources at the moment, especially when there are other pressing matters but I sincerly hope that the idea will not be entirely buried but merely shelved, awaiting better oporrtunity to deal with. Can we hope for it?

Will the WMTS browsing be retained in its present shape in the beta versions or you intend to remove it entirely?

Thanks.

Hi Menion!

Really great to see that you work on implementing support for wmts layers! This pushes your app to a new level regarding professional or enthusiast users. Have been testing the feature thoroughly and noticed just a single glitch: The Dimension 'Time' in the WMTSGetCapabilities Response seems not to be implemented, it looks something like this:

<Dimension>
<ows:Identifier>Time</ows:Identifier>
<Default>current</Default>
<Value>current</Value>
</Dimension>

Besides that it would be great if one could use the wmts layer as an overlay above (or below) any other map - as it's the case with the other types of maps.

Just one final question: are there multiple threads that fetch the tiles from the server or is this done serially? I would like to know because I write a small wmts-server in Python for personal use that is going to run on my phone. I could spare the hassle of dealing with multiple threads if there was just a single fetcher thread. If it's multithreaded it would be nice to know how many parallel requests my app should be able to handle.

Thanks a lot & keep up your great work

Paul

Hi, despite the slight bug with the 'floating waypoints' which I am experiencing as well - I sincerely hope that wmts in Locus maps feature is only postponed and not abandoned altogether. It shouldn't be to hard to fix given that for every pixel on a wmts map one can calculate a corresponding latitude/longitude quite easily. Another small thing I noticed: there seems to be a restriction regarding the minimum scale denominator of a tile matrix that is displayed. Right now this limit seems to be at some value between 7143 and 5357. Please lift this restriction in future releases.

Thanks!

Paul

After the latest update to beta version ISOK disappeared from list of WMS services. Adding the path, as I did before, dos not work returning an error.

WMTS support worked well in some recent beta versions. "Floating waypoints" bug disappeared. Now and then in various beta updates WMTS service disappear from the list of servers, then comes back in another update. The most recent beta versions again made it disappear again. I understand this is intended and related to ongoing work on the beta version. Am I right?

Well I guess, that you probably added WMTS map into Locus couple months ago (in some beta that supported WMTS). Current beta version really doesn't allow to add WMTS map. But I think that we could release official final version that supports WMTS during summer.

Yes, I added a path to WMTS map long time ago, but it worked well in subsequent betas. It used to disappear in some newer versions, then it came back all by itself without my interaction and now, since two or three recent betas, it disappeared again.

This is good news that you are going to add it to final version!