Messages

v1.3.6 (accidentally skipped 1.3.5 😂)

• Fine tuning to city/suburb name sizes
• Slight pink coloring for residential area town masses
• No more residential roads in zoom level 12
• Some fixes to width of mtb routes
• Several small fixes

@AndrewHeard haven't yet looked to that cycle relations issue, but will do.

[OS Map v20231203 Draft1.zip]

Had a busy evening, managed to draft fixes for all the issues reported so far.

I've loaded a draft version with fixes here:

    OS Map v20231203 Draft1.zip

I've not updated the legends or release notes yet, will do that for a proper release.

Changes made are:
- reduced heavy pylons at high zoom levels.
- fixed issues causing Oruxmap to not display many elements correctly.
- added option enabled by default "show symbols earlier" to allow reduced clutter in cities.
- fixed dynamic view of footpath dashes green/black out of sync
- moved surface highlights to below the highways to avoid obscuring the surface texture and street names.

BTW, the issue with Oruxmaps was down to case sensitivity of filenames in theme vs actual filenames. Seems Windows likes to capitalise the first letter by default. Have renamed all files to lowercase now.

Please try out the new draft and I'll all be very grateful of any feedback, thanks in advance.

Thank you everyone for feedback and bugs found so far, I very much appreciate it and will work on these to get a fixed release out ASAP. Attached is my fix list so far.

I will look at it. What I instantly see is, Karl draws two lines, left and right from roads. I draw one - hiking relations are drawn on the other.
I think it's this: depending how mappers draw the ways, the  relations sometimes interrupt and skip to the other side. So what we see may be a drawback from using an offset to only one side of the way. Sigh. If I draw it later it would appear on top of the main road. EDIT: which it usually does and should to. I will find it. A priority issue maybe.

... the new PROW highlights are drawn below the highway... I should do this for these highlights too.

Attached is a quick test of doing this, think I like it...

Andrew,

Strange, the previous version v20210216 and the new version v20231013 seem to behave the same regarding surface highlighting. Attached is a comparison of v20210216, v2023101, and v2023101 modded to highlight all roads with asphalt.

Currently only tracks, raceway and cycleways highlight asphalt. Looking at the modded version I can see why I might have avoided other highways which are usually sealed anyway. With the dash unsealed roads option enabled it would be obvious when main roads are not sealed.

I agree with your ~rant about the highlights being too intrusive, they are drawn over the highways (like a real highlighter pen). I changed the way the hike/cycle routes are highlighted in this release and the new PROW highlights are drawn below the highway... I should do this for these highlights too.

Thanks Andrew, I made a mistake with the release notes, fixed it now.

I'll take a look at the surface highlights and see what's going on.

I noticed Tapio's signature earlier, will do something similar too I think.

Hi Everyone,

Finally the wait is over. After 2.75 years of tweaking in my spare time, I have finally completed the update to the OS Map theme.

The links to the theme are in the first post, which has also been updated with the latest release notes, comparison screenshots and links to the latest PDF legends (also bundled in the theme itself).

The theme now works as a ZIP theme, so no need to unzip anymore.

I am a little worried about the size of the theme files now, they have doubled in size... so please let me know if this causes performance issues... I am considering splitting the theme into 6 separate files: 1:25k, 1:50, Dynamic and again for night theme... but would prefer not to...

If you are wondering why the release date on the ZIP is 20231013, this was the original planned release date and I was about to upload when LocusMap switched from v3 to v4 LoMaps and I realised I needed to update the theme to cope with the new map and its tags etc...

The theme has a lot of improvements regarding footpaths, including with the change to v4 LoMap maps a massive improvement, especially if you are a fan of the original Ordnance Survey Maps, as LoMaps now support tags to distinguish between the different types of public rights of way, which in the UK, are not always as simple as access yes|no:



Some of the map features can be disabled using the options for non-OS content or accessible/designated paths, as they are not in the original Ordnance Survey maps, but are (I think) very useful additions that enhance the maps.

In the UK these different types of public rights of way (PROW) which define restrictions on who/what can use them:



There is a new option in the theme to highlight PROW and this uses the same colour scheme as the UK waymakers shown above.

I realise that in other countries you do not have the same waymarkers, restrictions or even possible tagging yet in your country's OSM data. But please remember that this theme is aimed as emulating the Ordnance Survey maps and so is largely aimed at users of the OS maps, which obviously will be located in the UK.

I am planning to upload the OS map theme into the LocusMap store, but I would like to identify any teething issues first as I have made a massive number of changes/improvements. So please provide feedback if you find anything wrong. Thanks in advance, Karl.

Hi Everyone,

Finally the wait is over. After 2.75 years to I have finally completed the update to the OS Map theme.

Please check the main OS Map theme sticky post for more details.

[@jonny.blue]

@jonny.blue
firstly, please merge multiple posts in a row into a single one, or create a separate topic to your problem. This only complicates the readability of the whole, very important, topic. Thanks

Then, as balloni wrote .. are you using the latest app version 4.20.0 (1118)? Also, can you estimate how many points & tracks were visible? When hidden, no problem at all, right?

@Andrew Heard
"Locus Map has stopped" > This does not look like a system dialog and the app can't display such dialog when stopped . Hmm, full system log right after this will be necessary I'm worried ...

No, I love to forget to change version inside the xml. You can use https://github.com/TapioOfTapiola/oam_theme_tapiola/blob/main/Tapiola.xml
- Has some few changes.

[new version 4.20.0 (code 1118)]

Oki, the new version 4.20.0 (code 1118) just published also on Google Play (second attempt to pass verification).

Minor fixes along the way ...

@Andrew Heard
these are not some minor versions, but regular release versions. Better should be 4.20.0 RC1, RC2 etc, but because I also publish them on Google Play, all are simply named 4.20.0.

Dashboard resize issue ... hmm, will look at it.

[App version regenerated 4.20.0 (code 1117)]

App version regenerated 4.20.0 (code 1117)
Available in the "release" directory.


"App stop" problem, probably got it, thanks!

@jonny.blue
thanks for the testing and sorry for the complications.
BRouter error > do you use an unsupported combination? We made a bunch of big improvements (due to new system of customization + route warnings) so internal LoRouter profiles are no longer compatible with routing data provided by the BRouter application itself. There is also an opposite "problem". BRouter now introduced a few parameters that are not (yet) compatible with offline LoRouter, so profiles from the original BRouter repo may report an error when used with offline LoRouter.

So:
- use "public brf profiles for BRouter" only with the Google Play BRouter app. Offline LoRouter currently does not support all BRouter features (this will change in the near future), but if you don't see any error, it should work fine.
- use "LoRouter profiles" only with offline LoRouter. They most probably won't work with BRouter app

Thanks for understanding.

Installation of the older version is more complicated because it requires un-install the current version first. Suggest waiting a day (or in the worst case two) till a new update is generated/published.

What settings do you want to modify for BRouter? All are available in the Route planner directly.

@Tapio
Intent problem > this is unfortunate. The plugin uses a hardcoded name of the starting screen, but this has changed in the latest version and this old screen no longer exists.

Problem with recording > problem with the start may be connected to the crash at start. The worst is "action: stop".

@Andrew Heard
Plan visible after closing planner > grrr, so another try, even more aggressive plan removal in the next version.

Aspect colored by slope > I've had this prepared, but wasn't satisfied with the colors ... so later.

tapio - the download page still only has 1.3.3?

Thx, please retry. After I clicked "publish" nothing happened, now I see it was just saved as a draft.

Most recent xml has SAC Scale captions and traffic lights ("public transport, traffic" category).

Hi guys, the new version brings a lot of interesting changes and even more on the background. I have to thanks a lot for tests most of you made during last weeks. It really helped a lot!!

Version 4.20.0 was uploaded to the Google Play, but was rejected because of some missing info in subscription screen. It will take some time to fix it, so I've at least uploaded APK to the public Google Drive directory. If anyone wants to test and use this version, feel free to do it.

Have a nice weekend!