Messages

I created this cursor and having been using it for many years. I thought perhaps others might like to use it, so here it is.

the symbols used are:
  - empty red circle when stationary and your position is based on network signal.
  - red circle with small inner circle when stationary and your GPS position is locked.
  - red circle with rotating arrow when you are moving.
  - red cross when you scroll away from your position.
  - simple red/white compass symbol.
  - darkened/smoked field of view overlay is used for the show view option.

See attached preview (note blue dashed outlines are not displayed, just the size/edges of the images).

Oh, I see, you mean accessing a legend in a zipped theme...

It would seem that making the path relative to the theme's xml file would make sense. Is the zipped theme unzipped in a local cache somewhere when in use?

@Menion: I saw there are relative paths in the lnk files. But pls.: what exactly does relative mean in a ZIP file that is in _themes folder of Locus base?
Thank you

My lnk files are working relative the Locus directory that contains the mapsVector directory. For my OS theme:

mapsVector/_themes/OS Map/OS Map Day Legend.pdf

Note I have the lnk files located in the same directory as the theme xml files.

Karl.

I understood from earlier posts that the access to EXT SD content is less efficient

What I do not understand is that I haven't changed anything. Locus Map was working with everything located in \ExtSD\Locus\mapsVector (maps and themes) and all that has changed is that now all those files are located in \ExtSD\Android\data\menion.android.locus\files\Locus\mapsVector.

Why should moving and using the exact same files from one location in ExtSD to another make such a difference to the performance? LM3 is still using the \ExtSD\Locus folder and performing as expected. I've seen others complain about the performed on LM3 after the relocation of files...

I guess I can't move the files back to \ExtSD\Locus since this is now marked as not allowed in the app... besides I will eventually hit a problem when I need to add new maps or uninstall/re-install the app...

Well I tried Michael's suggestions:

• moving the themes to IntSD in private folder (while custom folders still point to ExtSD, did not work. Even worse it took ~120 secs with a blank screen on loading, and there was only the internal theme available.
• I notice there were an empty set of Locus folders in IntSD\Locus\ etc, tried moving them there, say result
• Lastly I moved them back to the ExSD\android\data\men... folder and then it returned to the slow loading of about 20secs (~10-15 of blank screen) and still very slow to use...

So.. still looking for a solution/improvement.

I really don;t understand why LM4 was working fine using everything on ExtSD before the Android 11 relocation thing, and now is really sluggish? I sometimes get a pause and the android OS kicks in and asks if I want to close or wait for locus map... never did this before moving the data to private folder...

Hmm... I'm experiencing very slow performance access from lm4 after relocating all my maps/themes etc from their ext_sd root folder you
To their own lm4 ext_sd private folder. Lm4 takes along time to load now with a blank screen for 15-25secs, opening the themes menu is slower and drawing the maps is significantly slower, to point that I would consider it almost unusable.

I kept a copy of the files and restored them after the move, since lm3 is still using them in the root directory. Lm3 is still running fine and snappy, no delays loading or using themes menu.

I was going to uninstall lm3, since I don't want two copies of my maps, and lm4 was looking OK, until now. Now I find using lm3 more of a joy...

Is there a known issue for this performance hit? I don't want to put all my maps on internal memory as they are over 32gb.

Hmm... I'm using the following rule to display a track as gravel:

<rule e="way" k="highway" v="track">
    <rule e="way" k="tracktype|surface" v="grade3|gravel">

I'm not sure now why a picked grade3 for gravel, whe osm states grade2... but it was tailored for v4 OAM... see earlier post with key for the mapping...

Perhaps I should not interpret the tracktypes like this? I think the grades a more a scale of track condition...perhaps I should include grades in the map legend too, e.g gravel or grade3... (Update, just noticed I never added the surfaces to the legend!)


Regarding the .eu maps, I think they use a different tag mapping from OAM, hence they provide their own rendering theme, this is obvious when you compare:
  - v4 Oam, os map v4
  - v3 Oam, os map v3
  - v3 eu, os map v3
  - v3 Oam, openmaps v7 
  - v3 eu, openmaps v7
Attached are matching screenshot.

You can see how the openmap v7 theme really struggles to render the v3 oam.... clearly the tag mapping is significantly different, this is fixed at time of creation of the map.

I would recommend either sticking with using the eu map with the openmap v7 theme, or switching to v4 oam maps if you wish to use one of the many oam themes.

Hmm... I've tested the theme on both lomaps and openandromaps v3 and v4, they all work as expected. Admittedly these are all uk maps. My main thought is that perhaps what is being displayed is what is defined in the map data?

You can configure a quick bookmark to open openstreetmap at the same location and check what is defined for the track in question.  E.g. does it have surface=gravel or tracktype=grade3?

I like the new diatance markers, but when I tried them I got a markers at roughly double the diatance of the previous marker. I'm using imperial units, if I switch to metric units it works as expected. See attached metric vs imperial distance markers.

Ps: would be good to have imperial markers every mile rather than conversions of 1 km to miles...

Hmm... I am aware if this phenomenon and do relunctantly remove outlines at zoom levels below Z14, and this seems to works for all devices I have tested on so far... so I assumed it would be the same for other devices....

Does this mean outlines should be avoided for all large areas at Z14 too?  This would be a problem for my theme as outlines are a key aspect of the emulating the UK OS map style.

Is there any known workaround we could use at Z14? E.g. using delta offsets, etc?

Yes exactly, only at ZL14, and in nature areas.
My screen res. is 1080x2244.
Other themes are also doing it. Elevate... Very bad in OSMap.

Hi Tapio,

In the OSMap theme there is an option "emphasise access land" which allows you to switch off the purple/gold outlines. I suspect this is caused by an issue with the underlying graphic's engine not being able to draw outlines correctly. It also looks like another element is outlining in black too...

does that help?

best regards,
Karl.

I use Notepad+ with a plugin to select rgb colour codes. Transfer to phone using double commander for live testing in app.

New release now available v20210216.

i have updated the first post with the latest release notes and links. I'm now using google drive to release the theme in a shared folder that contains all the releases and the PDF legends.

In this update I have added support for depicting road surfaces and distinguishing between sealed and unsealed roads/tracks. This is applicable to all highway types (including pedestrian and cycle paths) except for motorways.

The attached is a graphical summary (as presented in the map legend) of the new overlay options:

• "dash unsealed roads" to give unsealed roads a dashed outline/casing.
• "road surface/grade textures" to give unsealed roads a textured pattern that represents the type of surface, visible from Z14 onwards.
• "emphasise road surface/grade textures" to highlight roads surfaces at lower zoom levels, visible from Z12.

The second attachment identifies which "surface" and "tracktype" tag values are mapped to the new surfaces.

not all maps support the "surface" tag, but do support the "tracktype" tag. For this reason, the "tracktype" tag is also used to set the road surfaces, albiet at a lesser level of detail (normal, compacted, gravel, dirt). Note that tracks tagged as trackype=grade1, which are also tagged with surface=asphalt, are now "promoted" to sealed roads (solid casing).

I am conscious that I have highjacked a feature of standard OS maps on which they use dashed road casings to represent unfenced roads (in fact a road can be solid one side and dashed the other to show fenced/walled/constrained on just one wide). However, since OAM/LM maps do not (currently) support a tag for fenced roads it seemed a good idea to use the same symbology for sealed/unsealed roads...

These new options are not enabled by default, as the default overlay options are for classic/standard OS map look/feel, and of course OS maps do not have such features.

FYI: Here is an example of unsealed trunk and classified roads in Botswana (both are listed as compacted surface), see attached, rendered with the new road surfaces/grades option I'm working on.

I checked on google maps and OSM data base.... all these roads in the map view are actually compacted earth, including the unclassified road shown as sealed. But this is because the map data does not define any surface/grade for it... so the rendered view (as always) is only as good as the data in the map...

Hi Karl, I notice your theme doesn't distinguish between sealed & unsealed roads. Unfortunately very few Locus themes do, which seems odd as you'd think cyclists would be quite interested in the road surface. Bernard's Desert theme (www.maiwolf.de) is the best for this - his on LHS compared to yours on RHS. Voluntary is the only other one that shows any difference but it is very hard to discern.

for example in my screen cap: https://www.openstreetmap.org/edit#map=16/-42.5113/147.6427
compares surface=unpaved with surface=Asphalt

Hi Andrew,

Attached is a sneaky peek at the road surfaces/grades overlay option I have prototyped for the OS Map theme.
   - 1st image is the default OS map view
   - 2nd image is road surfaces/grades enabled
   - 3rd image is with the emphasise road surfaces/grades enables too

With the road surfaces/grades option selected, if the road is unsealed it will have a dashed casing and the core will have a texture applied based on the type of surface.

The second attachement shows the current road surface/grades renderings and highlight colours.

It is still very much work in progress. I have to say that I have not yet found a real life example of surface="winter"...