Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - 2012

This was an upgrade from Android 13 to 14, the device has never been wiped, things worked fine on Android 13 as late as in August. I cannot say how I survived for so long, but I did.

But more importantly - whew! I found all my 18.66 GB of Locus data in /storage/emulated/0/Locus (equivalent to /sdcard/Locus).
I see that in Locus > Set up > Settings > Backup & filesystem > File system manager > Set the main directory it is now clear that the "Internal storage" (ie /sdcard/Locus as above) location is no longer a valid option and the suggested location is instead

So data seems OK so far, on to migrating the data and setting things up to work smoothly from now on.
The problem with the suggested location is that the file managers cannot access /storage/emulated/0/Android/data/* locations.

I see here that there is a tool for transferring the data:
Though it seems it is now accessible through Locus > Set up > Settings > Backup & filesystem > App data transfer.
I am not sure why this transfer hasn't triggered before for me, and if it will indeed be able to handle my (unusually large?) amount of data without a snag. I don't have that much free space on the device, but maybe I could free it up.

It seems that I will still have a more complicated procedure adding/modifying custom generated map data in the future. I used to just do this with my Android file manager/editor apps. But I guess there is no simple way around it anymore.
Quote from: michaelbechtold on November 06, 2023, 14:14:48First let's understand if we talk about the same device. If not - do you have access to the previous one?

It is the same device, sorry to be unclear!
Forgot to mention that I also had a bunch of bought downloaded map content.

I can use adb and/or Android file managers if that is of help.
OK, I've seen the signs and messages about Android file management issues coming up. But I haven't paid enough attention and been proactive, the process to futureproof things never seemed straightforward to me (other things going on in life forcing me to deprioritize this for a long time) and I am now in a situation that I probably could have avoided. But is there anything I can do now to minimize damages?

The situation:
I have been using Locus for many many years and have a large number of custom tracks and points, custom offline and online (provider) maps. I use these a lot and make additions often.
Suddenly some time ago, everything custom was gone. (I am not totally surprised because I was dreading this because I hadn't put the time into learning about the change that I recognized I should have.)
I am on Android 14 since some recent time. I am pretty sure that I have had some backup set up to run at regular intervals, internal to Locus and backing up to Google Drive probably. But I don't think(?) it backed up the massive (multi-GB large) custom offline maps I have made.

What can I do (if possible) to recover as much as I can of what I had? (What should I not do, that could make things worse?)

How should I set upp things to run well from now on?

Sorry to be the one to come with a self-afflicted mess and ask for help. I am really thankful for your advice and afraid that if I start trying to fix things myself it will not work out well.
Is cloud sync planned for map items (calibrated maps especially) and/or offline maps? Our maybe it is already there but I can't find it?
If you think user scripts for this purpose would be interesting, you can take a look at this idea I added to Locus Help Desk (and vote for it if you like):
I haven't looked at this in many years. It's cool seeing what you guys have done since then.

I think the map/tiles that j3rry would like to see is the one I originally set out to try and get into Locus, and all the early posts (from way back in 2012) of this thread are about how to access those tiles properly.
I also think, like jusc, that Locus (still) does not have the capability to handle this type of tile URLs directly. The script for Mobac by Nicolas P seems very nice, I have not tested it.

I still wish we could handle this in Locus, and with proper geo-alignment. It would be very nice if Locus could support some kind of user scripts to handle this type of issues, and we could seamlessly integrate many more tile servers.
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>?

Thanks for your response and suggestion. I will try MAPC2MAPC as you suggest and see how that works for me!

I have a map from a custom map source that I would like to view in a 3D map environment like Google Earth (pro) on Windows (or Android, but I think that is much harder if at all possible?). I am already using it as an overlay with other maps in Locus, and have downloaded it as a personal SQL map.

I have seen people doing similar things (external overlay maps shown as clinging-to-ground in Google Earth) with a service called CalTopo ( They add a custom layer with the map URL (similar to Locus custom map sources) and then if you are a paid subscriber to the service you can get a live link to a Super-Overlay ( KML file (served on the site) which can be added to Google Earth to serve up layer tiles. (see example images at But I don't know if this program could really do what I want, I would much rather have a local file that I could add to Google Earth. And also I would rather not mess around with other programs since I like Locus so much. :)

Is it possible to export a saved map to KMZ to open in Google Earth? Would it otherwise be an idea for future functionality for Google Earth integration? Or is there some better way to do this? (Long-time wish is of course 3D display support in Locus, but that is another feature request/wish already. ;D)

Here are some more example images using CalTopo to show the Strava (no longer possible for detailed zooms after Strava requiring login!), just to show what things can look like in Google Earth:
OK, further testing reveals that apparently the WMS maps work fine with every other "background" map except the first one I tried. Good news I guess! :)

The one with problems is the Swedish Lantmäteriet Topo map, available in Locus shop. I notice that it has the flag for "does not allow overlays" set, seems there is a good reason for that. A shame though, it's a very good map.

Sorry to bother you!

There are some Swedish government provided WMS maps for bike routes that I would like to use in Locus.

All technical information about them is available from here:

They are used for presentation in several formats on different pages of this site:

I am able to add the WMS versions in Locus with these URLs:  (background map of Sweden and northern Europe)  (data available in a large area around Gothenburg, Sweden)  (data available in a large area around Stockholm, Sweden)

As far as I can see they are WMS version 1.3.0 which as far as I understand is supported by Locus Pro.

(WMTS versions give errors when I try to add them, as I expected.)

When I use them in Locus they are (as expected) overlaid a background map. The bicycle view maps look good, the background map seems to scale wrongly in some way and looks quite "pixely".

The real problem starts when I want to move the map view around, the WMS overlay moves at another speed scale than the background layer map, creating an unintended "parallax" effect. Very cool to look at but very difficult to use as a map. :)

Something seems wrong with the scaling of these maps. Is the error on the server side, or is it Locus that does not handle them properly? Or is it something I could fix with settings/customization?

I've also been playing around with trying to add the WMTS versions as "normal" custom online maps through XML using provider URLs as examplified below, but I can't get them to work properly and I don't think it is possible really?{z}&TILEROW={y}&TILECOL={x}&FORMAT=image%2Fpng%3B%20mode=8bit
I understand, no problem! It is important that relations with map providers are good.

But now at least I know it's not just because I'm not looking hard enough. :)
I would like to set an online overlay layer that i define in custom/providers.xml together with the Basemap Satellite map that is free in Locus store. If I had the provider id of the Basemap Satellite map I think I could do this with setting the background property for my map to that id. But how can I find out the provider id of a non-custom map?
I know I can let the user manually set my overlay layer as overlay and the other map as (background) map, but that is not really what I want to do.
Is this possible?