Recent Posts

Pages: [1] 2 3 ... 10
Add-ons / Re: Geocaching4Locus - switch to new Groundspeak API v1
« Last post by freischneider on Yesterday at 13:55:34 »
I had contact with arcao today. The API is in progress.
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« Last post by menion on Yesterday at 13:23:28 »
Important links
- blog post about major version (not yet published)
- list of news of public versions

22. 5. 2019 - Locus 3.38.0
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« Last post by menion on Yesterday at 13:22:47 »
These were quite long two months. It is probably for the first time, I publish a version after such a long time since the previous release. Last two days I spend by fixing various problems we found and just now, the new version was published on Google Play.

We have an option to publish version only for certain part of users (probably random selection). So today, it will be only for 10% of users. If there won't be any unsolvable problem, I'll enable version for all users tomorrow. Thanks for understaning.

And mainly thanks for the help. Update of map system was a big task for me and I'm really glad, version with this change is out. Now we can fine-tune it :).
Some more information, this seems WMTS based. I don't know much about WMTS though, but Locus didn't accept the URL when I tried it in the WMS (sic) "add source link manually" dialog.

There is a redirection function where the (A) URLs below redirect to a tile at the respective (B) URLs. The example URLs form a 2x2 grid which I have marked with NW/SW/NE/SE. The zoom level identifier for these tiles was 707a0e89c7a346cfbe522572b1bdfd6d.

(A) https://api.[provider].net/maps/[map id]/wmts/tiles/[zoom level identifier]/2/0
(B) https://[provider][map id]/[zoom level identifier]/0/2048/1024/1024

(A) https://api.[provider].net/maps/[map id]/wmts/tiles/[zoom level identifier]/2/1
(B) https://[provider][map id]/[zoom level identifier]/1024/2048/1024/1024

(A) https://api.[provider].net/maps/[map id]/wmts/tiles/[zoom level identifier]/3/0
(B) https://[provider][map id]/[zoom level identifier]/0/3072/1024/1024

(A) https://api.[provider].net/maps/[map id]/wmts/tiles/[zoom level identifier]/3/1
(B) https://[provider][map id]/[zoom level identifier]/1024/3072/1024/1024

Still the reference system is just local unless the "zoom level identifier" provides more information than I can get out of it, so I'm just as stuck as before.
I am trying to set up a custom <provider> for maps with small local coverage. It uses a tile URL structure that I am not used to, despite having successfully added a lot of custom providers before. I am grateful for any help or insight.

The tiles are stored on as 1024x1024 PNGs, like this:
https://[provider name][map id]/[32 digit hexadecimal, seemingly random(?!), zoom level identifier]/[number representing X position]/[number representing Y position]/1024/1024
(no file extension)

Zoom level identifiers are different for every map. For one map, from far out to close, they are:

To further illustrate the naming, this is a 3x3 grid of tiles with everything up to and including the zoom level identifier ("707a0e89c7a346cfbe522572b1bdfd6d") cut off:
[...]/3072/2048/1024/1024 [...]/4096/2048/1024/1024 [...]/5120/2048/1024/1024
[...]/3072/3072/1024/1024 [...]/4096/3072/1024/1024 [...]/5120/3072/1024/1024
[...]/3072/4096/1024/1024 [...]/4096/4096/1024/1024 [...]/5120/4096/1024/1024

This is a 2x2 grid of tiles on the next (closer) zoom level ("56918450a00a49fbb5a3e3e290511ebd"):
[...]/9216/7168/1024/1024 [...]/10240/7168/1024/1024
[...]/9216/8192/1024/1024 [...]/10240/8192/1024/1024

The tile reference system for every zoom level seems to start in the (local) top left corner at [...]/0/0/1024/1024 and then the X and Y position indicators increase by 1024 for every tile (becoming rather large numbers in the bottom right at closer zoom levels).

I can live with creating a unique provider ID/"map" for every zoom level, which seems necessary? However, even with that I can't see how I could get the rest of the <url> code right.

I can find my way around the reference system without much difficulty, using multiples of 1024. But since the tile indicators are just related to the upper right corner of the local map, not to any global system, how can Locus know where to look for a specific tile? Could the "overall" position be part of the 32 digit hexadecimal number somehow?

Have you seen this before? Do you have any suggestion on how to wrap this into a Locus custom <provider>?

Troubles & Questions / VK-172 USB Receiver
« Last post by ndoggac on May 21, 2019, 21:38:11 »
Curious if anyone had attempted to utilize the VK-172 USB GNSS receiver yet?  It uses the Ublox7 chipset, and is pretty cheap.  Found it under several random (Chinese?) brands on Amazon (Wingoneer, HiLetGo, DIYMall, etc).  I would assume this would work like any other external receiver that shows up as a COM port (typically using bluetooth as opposed to USB) and sends NMEA messages.  Guess you would need an OTG cable to utilize the receiver while also powering your device.

Also curious if this receiver also gives you Galileo tracking?  Doesn't seem obvious in any of the reviews.
[DE] - deutschsprachiger Forumsbereich / Re: Tracks aufzeichnen
« Last post by michaelbechtold on May 21, 2019, 20:59:21 »
Ahhh, wenn es Dein Huawei ist, dann heißt die Option: Akku -> Starten
Dort bei Locus den Schalter ausschalten, worauf eine Auswahl kommt. Sekundärer Start und Hintergrundbetrieb zulassen, dann "OK"
[DE] - deutschsprachiger Forumsbereich / Re: Tracks aufzeichnen
« Last post by michaelbechtold on May 21, 2019, 20:54:18 »
Hallo Walter,
je nach Android-Version (Nr. und Hersteller) heißt die Einstellung ein wenig anders, aber sinngemäß muss Locus vom Batterie- manchmal auch Memory-Sparmechanismus des Androids ausgenommen werden.
Zudem hilft es Locus als Service laufen zu lassen (Locus-Einstellung).
Welches Modell mit welcher Ausstattung /Android-Version, Hersteller, RAM) hast Du denn ?
[DE] - deutschsprachiger Forumsbereich / Tracks aufzeichnen
« Last post by Imacfux on May 21, 2019, 20:39:35 »
Guten Abend,

die Aufzeichnung der Tracks ist bei mir sehr unzuverlässig :

wenn ein Track aufgezeichnet wird und ich eine andere App aufrufe oder ein eingehendes Gespräch annehme, dann wird die Aufzeichnung entweder ganz abgebrochen oder angehalten. Und wenn ich dann nicht darauf achte, dass die Aufzeichnung angehalten ist und wieder starte, dann komme ich am Ziel an und der Track wurde nur teilweise aufgezeichnet.

Was mache ich falsch?

Pages: [1] 2 3 ... 10