Messages

Latest version now available from link below.
Changes: Hide obtrusive gates that are not on paths, tracks etc at low zooms. Improved logic on access restrictions on paths. Improved rendering and legibility of suburb and farm names. Removed a number of persistent bugs.

Latest version now includes cattle grids and police or military checkpoints. The rendering of pedestrian areas and ways is now clearer, with a hatched pattern.

@Zajdlik Josef Sorry I missed your post until just now. I see your problem and I'll look into it. In earlier versions of Locus I had to start the street name close to the start of the road to get it to display reliably but that problem has gone I think.

Diese App könnte Ihnen helfen: https://play.google.com/store/apps/details?id=org.aospstudio.files
Sie öffnet einfach die native App ,,Files by Google" auf Ihrem Telefon, die sonst möglicherweise von Ihrem Telefonhersteller blockiert wird.
Alternativ müssen Sie möglicherweise mit einem geteilten Fenster für die App ,,Files" arbeiten.
Es scheint, als ob es vom Hersteller abhängt.

You may find this app helps: https://play.google.com/store/apps/details?id=org.aospstudio.files
It simply opens the  native Files by Google app on your phone, which may otherwise be blocked by your phone manufacturer.
Alternatively, you may find you need to work with a split window for the Files app.
It does depend on the manufacturer, or so it seems.

With the latest Locus Pro classic, attempting to go to a LoPoint after a search crashes Locus and causes a restart. It was OK not so long ago!
This has also been reported by a German speaking user in the OAM forum.

With some routes I have imported (around 400 track points) Locus Classic crashes when I attempt to Re-route direct from the map screen. If I attempt to Re-route from the track detail screen or track manager ît  pauses then reloads track manager, restarts Locus or reports a crash.

On my phone, at least, I have to get that app into split screen mode on order to copy or move files. But it works.

.de = deutsch (?)

The visibility of the small squares that indicate OSMC marker colour has been significantly improved, and a couple of bugs discovered and dealt with.

Bike parking is currently in the POIs for both Lomaps and OAM, which seems quite reasonable to me.

@Zajdlik
I decided not to do that as it would vastly inflate the size of the theme. The code required to display just one marker is a large proportion of the theme already. Thanks for your understanding.
Edit: It does look like the colours of the small squares could be modified to make them more visible. I'll add that to my list.
Edit2: The visibility of the small squares has now been significantly improved.

@Andrew
Do I see in another post that bicycle parking is not included in the offline maps themselves, so it can't be displayed in any offline theme?

Latest update removes a workaround that is unnecessary with the latest maps. This now gives a better display if a bike or hike route runs along a major road.
Download and install from https://voluntary.nichesite.org

But, my OP was concerned with why LoMap and OAM render differently.

OAM does a lot of preprocessing on cycle tracks and lanes to attempt to make sense of the various ways of mapping them. Lomaps does minimal preprocessing.

@karlchick
To be honest, I can't quite recall exactly what was unreliable. It's not the direction of drawing the way because that would make the one-way incorrect. The theme allows for "reverse one ways".
I think the "unreliability" was simply that there are quite a few different ways of mapping this situation and OAM maps can't pick then all up.
I do recall there was one particular junction in Cambridge with bike lanes and turning filter lanes that looked like a dogs dinner and left me unsatisfied with the result in Voluntary.
But also, l purposely keep the number of options to a minimum and thought that "drive on left/right" choice for just one particular scenario was too much.

@karlchick
Embedded within my code for Voluntary, there is an option for drive on the left or drive on the right for cycle lanes.
It seemed a good idea at the time but I left it as a hidden option (read the beginning of the theme XML file) as the mapping was not reliable enough to make it worthwhile. I decided in the end to treat the marking as symbolic, rather like the pylon markings on a power line don't indicate where the individual pylons actually are.
I also don't like the fact that the lack of radio buttons for either/or choices means you have to rely on the user to turn off one option and turn on another.
Cycle lane mapping is complex and has too many different ways of mapping the same thing to be able to achieve a truly satisfactory solution.

1. Do you think your colour coded menus ought to reflect the colours of Explorer/Landranger? (See my previous post)
2. I don't know how OS marks the boundaries of parks but in general for woods,
Explorer: line if fence etc, nothing if unfenced
Landranger: line if fence etc, dashed if unfenced (but varies)
You cannot view this attachment.
OS-Style

You cannot view this attachment.
Explorer

You cannot view this attachment.
Landranger

3. Buildings appear to have rounded corners in your style
You cannot view this attachment.
OS-Style