Messages

My brain cannot process this. What's the difference? OK, the first is a time span, the second is a specific point in time. But it's about the same thing?

You cannot view this attachment.

Therefore all karen are regenerated.

Nooo, the world needs less Karens.

Hello,
times in the app for sync purposes are handled independently on the time of the device, so there should generally be no problem related to the "time" itself.

There's an update 4.19.0.2 on Gdrive, 17th Oct.

Hi,

I don't want to "steal" another's idea, so I'll just point you to the source:

a method that, (at least for Samsung devices) as far as I can tell, enables EVERY file manager to handle Android/data and Android/obb on Android 13, is described here:

https://xdaforums.com/t/cant-access-android-13-android-data-folder.4491183/page-3#posts

Take a look at the post beginning "I bet you are having a really bad day" (or so.)

Additional infos;
-MT Manager can be sideloaded from a site mentioned a few posts further down (#46) (I didn't find it on apkmirror),
-"easily" in the first post means "navigate to Android/data, tap "Property/Modify" and tick the two missing options".
-If, in the Play Store, you have Automatic Updates activated, the app Files (which you can search for by that name in MT Manager in other System languages as well), will be re-updated quickly - don't know if that would create a problem.)

v1.3.2

• Track grade codes now as a setting
• Indicators for unpaved roads (new setting)

Track grades, see screenshot. OSM grades go from 1 to 5. 1=no marker, 2-3=one marker, 4=two markers, 5=three markers.

I've added an option. Not in the release yet.
https://github.com/TapioOfTapiola/oam_theme_tapiola/blob/main/Tapiola.xml

3 weeks before I can provide further info or discuss/ check issues.

OK... and now I noticed, in your example the logic is vice versa, you are marking the unsealed road.

Ok, experiments... the problem is consistency. 51.324,7.98681 in Nordrhein-Westfalen, Germany.

Screenshot has mostly Highway:Residential, but road surface is only defined for some of them... (asphalt, the ones with blue lines).

Attached xml line 1929+

Does it make sense stiill? Please test in your area. I can add another option "Sealed road indicators" and default it to off.
And if so, do you really think those indicators should be on higher level roads, (highway:primary etc)?

I think it shouldn't be used in residential areas. I.e. just used for v="track|byway|road|path|unclassified"

One suggestion is to distinguish the road/ track surface eg. between sealed & unsealed.

Hi Andrew, let's please discuss this here. OK, I looked at your test position at -42.51336, 147.64366 in Tasmania.

There I don't see the need to check for road surfaces...? At least for Germany roads k=highway v=primary/secondary/tertiary (in my theme from yellow to dark orange) already imply they will be an asphalt road. Do you think an extra layer, like a dashed line is useful and necessary?
Smaller roads/paths may be in need of your idea. If you have an example position, let me know.

The contour lines mentioned in the news are embedded into the .map files. And display (or not) is controlled by the theme.
The hgt files are optional and allow the dynamic elevation Feature.

I'm using x-plore, grant access as requested, and can read/write from/to /Android/data, even on Android 13, Sept. security level (tested this morning). And even on EXT SD/Android/data

Hi,
I just started playing with the new routing engine in 4.19 and found something very discouraging : Locus now refuses to route on private roads, even in Walk mode or when I draw manual lines to get to the private roads. 

This makes it very difficult for those of use who use private land with permission, including private forests and cemeteries.

It would be sweet to have a setting that allows private road, trail and theough-gate routing. At very least we should be able to manually route around gates and generate road routes on private land.
-Donald

There are quite a lot of possibilities regards how the link to a map legend may be defined.

Could you please share with me a theme with PDF legends that does not work for you as expected? Thanks!

Thanks Memion, I've uploaded a draft of the latest v4 OS Map theme to here:

OS Map v4 draft.zip

There are 4 theme files, day/night themes for v3/v4 maps. There are lnk files for these that point to common/shared day/night legend pdf files.

I've got the maps and themes located on external sd card: /storage/6366-3530/Android/media/menion.android.locus/mapsVector

Which seems to work smoothly for me... except loading the legend gives the attached error. This used to work when I last checked (probably last year). Error is occurring in both LM4 and Classic versions.

Thanks for helping.

Note:This isn't the final release of the theme (still working on the legend files).

Hello OS,
thanks for the huge amount of screenshots  . I was mainly curious about your setup in the Altitude manager screen, where seems to be everything "correctly" disabled. In such case, the received altitude should be completely un-affected by any internal optimization and visible values should really be values that Locus Map received.

The question here is what values the app receives. In the app settings > GPS & sensors is a setting called "Google Services assisted location". This switch between two modes. First (when disabled) is the old method where the app receives raw data. The second use pre-computed values by the Google Play services library and I've already noticed that in rare cases, values were not correct. So if you have an option to test it, suggest disabling this setting and giving a second try.