Messages

Sounds like the main issue is now fixed... big thanks!

Also sounds like there are some new tags available to theme creators to control text:
- 'text-wrap-width'
- 'text-align'

Are these available now? What is the syntax? I couldn't find them on the doc page.

What happens if I use these in my theme, and then a user with an older version of LocusMap tries to use the latest theme? will it cause a error loading the theme?

Since the new releases of Locus Map 4.15.1 and Locus Classic 3.66.1, both editions are now text wrapping "long" names.

For really long names this is good, but the algorithm is going g a poor job of wrapping also not very long names. Also the wrapping seems to be left justified, and the placement of symbols "below" are not to the bottom/right.

Seems to be only v4 maps affected.

In the past this would occur rare and then stop, e.g. if change maps or restart. But, I've tried restarting and it seems be permanent now.

Attached is an example.

Worst is the Nottingham Hill. Having a single character word wrapped also looks bad.

Can the text wrapping be made a setting? Or improved to of wrap on non-alpha chars?

@voldapet

Thank you for raising the PR.

Regarding: Point 5

John's JohnThorn maps are raster maps, so there is no theming possible within the LocusMap app...

the OAM maps now include (for UK maps) an additional tag:

<!-- OS_OpenData -->
<osm-tag key='os_open_data' value='crags' zoom-appear='13' />

which renders the OS crag data, so from a theme point of view it is very simple to include... but of course there (presumably) was some considerable scripting effort for the map generation to merge in the OS open data.

Attached is an example of using OAM maps before and after OS crags were included.

Some initial thoughts from me:

Point 1:

I see bicycle=designated is added.

Could we include the following?
   - bicycle=no|yes|designated|permissive
   - foot=no|yes|designated|permissive
   - horse=no|yes|designated|permissive


Point 2:

In the UK we have footpaths and bridleways that are legally protected and signed along their routes - these are known as Public Rights of Way (PROW).

OSM has inluded tagging for these ways (designation):

   https://wiki.openstreetmap.org/wiki/Key:designation

and has the following guidance for usage:

   https://wiki.openstreetmap.org/wiki/Access_provisions_in_the_United_Kingdom

Would it be possible to include this designation tag in LoMap maps?

For the UK, the following values would be useful: public_footpath, public_bridleway, restricted_byway, byway_open_to_all_traffic.
The following values are also used in Isle of Man: access_land, public_cycleway, green_lane.
The following values are also used in Scotland: core_path.

This would provide a massive improvement to be able to indicate footpaths that are of interest to hikers, cyclists and horse riders:
   - bridleways can often be part of a highway=track + designation=public_bridleway - these are currently not displayed in LocusMap but are quite common.
   - bridleways (in the UK at least) are also legally accessible for cyclists - some are sealed and useful to road-bikes but some not and need off-road bicycles.
   - many footpaths in OSM are foot=designated but only because there is a general (Cycle|Foot) signage used by the councils to indicate a shared space footway - these are publicly accessible paths, usually pavements, cyceways, side_walks, combined cycle lanes and footpaths - most are in/around towns. They are not PROW but if rendered as "footpaths" clutter the map with many "additional" paths, resulting in a "can't see the wood for the trees" situation for the walker...


Point 3:

Car parking amenities seem to be growing in OSM over the last year, to the point that the maps are starting to be cluttered with many additional parking=side_street.

Could you include the parking=* tag to help identify which car parking amenties are dedicated off-street parking from the many on-street packing, see:

https://wiki.openstreetmap.org/wiki/Key:parking

This tag is also useful for being able to indicate multi-storey and underground car parks.

When combined with access tag, it allows to identify those car parks that are publicly accessible and likely destinations for people arriving somewhere to park.


Point 4:

I see that many of the appear-zoom levels have been tweaked, some appearing much later...

I noticed when we went from v3 to v4 for OAM that there is a difference in visual scaling between LoMap and v4 maps of the same zoom level.
e.g. zoom=16 in LoMap appears similar in scale to zoom=15 in v4 maps.
This has the effect (for the user) that symbols/ways seem appear much later in v4 maps. When you zoom out in v4 maps you seem to get less information compared to when you switch to LoMap.
...so I was a little surprised to see some appear-zoom levels being increased for some tags...


Point 5:

The OAM maps have recently added OS crag data available from  OS open data. I think Christian did some magic scripting behind the scenes to make this possible for OAM and it is a massive improvement for UK maps.
Is this something that might be considered for LoMap v4?


Point 6:
In OAM maps the map tagging separates out common tag values, e.g. foot=yes and bicycle=yes are transformed into foot=ft_yes and bicycle_bic_yes.
I'm wondering if this is something that is desirable for LoMap v4 maps?
I'm not 100% sure why this was done, but is does mean that you can OR together many tags and check for specific instances of common values like ft_yes or bic_yes.
Perhaps this is now resolved with the bugfix to the double tag issue mentioned earlier?

@menion, no hurry. It would be good if theme creators could access an early beta release of the tag mapping and an example/test map - so we have time to update our themes and provide the user base with working themes as soon as the new lomaps go live...

I'm using Samsung Galaxy A52 with Android 11 and system dark mode enabled. No additional dark mode apps installed, but I am using Chrome flag to force dark mode on websites...

I checked the system developer settings, force dark mode is not set.

With v3.64.1 I sometimes find the UI colours get inverted and menus have white text on white background. See screenshot.

I can 'fix' it by opening quick settings (opens in Black, white, see screenshot) and closing quick settings. After that the UI returns to normal white with black text, see screenshot.

I'm guessing this a bug, but also wondering if perhaps dark mode is being developed for classic but not yet released...

@Menion, any chance of a sneaky peak at the tagmapping file for v4 lomaps? Is it similar to v3?

Ok... I've got the v4/v5 theme into a state ready for release - just need to update the Legend PDFs.
The v3 theme I have not started work on, it will require a lot of rework...

I think I am going to do a release with just the v4/v5 theme updated and leave the v3 untouched for now - that way you can benefit from the latest theme updates on OAM maps right now.

i was wondering if I should split the theme into two separate themes, one for OAM and one for LoMap. But then I thought "Will LoMaps ever upgrade to v5 or higher maps?" @Menion, perhaps an inkling?

John, I think your hosting site is down, I get a bad gateway error when trying to access theme or legends.

Hi J,

Yes, I have noticed. I have added the new OS Crag tag to the new version of the theme I'm slowly working on. It's close to ready for v4/v5 maps. But the v3 of the OS Map theme is in need of major updates to support lomap maps and keep the latest look/feel in line with v4/v5 theme...

I could release just the v4/v5 map theme if people want something for Andromaps now....

I've been working on updating my OS Map theme for LoMaps having improved the OAM version, and discovered that wetland=saltmarsh is not part of the lomap tag mapping. All these areas (quite a lot around the UK coast line) end up as plain natural=wetland.

Another tag I really miss in LoMaps is tidal=yes.

Many footpaths and areas area tagged as tidal and hence only accessible at low tide.

Tidal=yes, is also useful for distinguishing between natural=wetland area that are probably tidal mud flats vs inland peat bogs.

Would it be possible to add wetland=saltmarsh to the wetland tag mapping for LoMaps? And would it also be possible to add tidal=yes

Hi Jeff,

You are correct, the European tag mapping file defines which information from OSM is in the OAM maps and at which zoom level they can first appear. Some of the tags are renamed for various reasons too.

If there are multiple points/nodes to display then they drawn based on the display and priority options, or the order they appear in the theme file. Order is quite important, and sometimes a compromise has to be made, often transparent fills are used to deal with hidden/layerred items, but this is difficult when emulating the OS map theme.

You can request additional items via the OAM forum;

https://www.openandromaps.org/en/oam-forums/forum/maps

You'll see I've requested some things, but not all requests will be accepted, especially if they do not meet the purpose of OAM maps, which is primarily for walking/cycling. Also there is a 15 tags limit per osm item (node/way/area) which if violated causes the whole tile to not be drawn.

If there are any items in the tag mapping that are not in my theme, please let me know and I'll do my best to include them in a future release.

I am planning to rework the summits in a similar fashion to the OutdoorV5 theme which makes summits visible based on their prominence and zoom level. But first I have to formalise all the v5 and tidal features improvements I have prototyped...

Note, some background info: I have two master theme files, one for locusmap/v3 maps and one for OAM v4/5 maps. Each defines both the night and day themes, to make it easier to work on both at the same.e time, but are very large and hence slow to use. So when I release a theme I have a script that splits the day and night parts into separate theme files. Resulting in the four theme files you are looking at.

Generally I am trying to emulate the look and feel of OS maps with this theme. It will be impossible to exactly match OS maps, since not all features of OS maps are supported by either the source data (OpenStreetMap) or the map creators (e.g. LoMap and OpenAndroMaps).

There is also a difference in how map features are used by the map creators, this is defined by a tag-mapping file. Only the tags in the tag-mapping files can be drawn...

OSM maps include a lot more content than OS maps, and I have added options in the theme to allow displaying addition non-OS content, e.g. Post boxes, hedges etc.

In general I have tried to create similar icons and symbology for non-OS content that are hopefully in keeping with the style of the original OS maps.

I'll take a look at Saddles too. Thanks for the feedback, it is always appreciated. I am working on a massive improvement to the rendering, starting with the v4 theme that mainly supports OAM maps, including v5 maps now.  I'll then be looking to update the LM/v3 map theme...

Thanks Jeff, you are correct and mineshaft is missing from the theme. I guess you using a lomap map as oam do not currently support mineshaft tags, only adits.

I suspect this is why it is missing, I added adits for oam (v4/v5) maps first and then updated the v3 map theme.

I'll include mineshafts in the next release. I might also request adding mineshaft to OAM maps too, there are over 10,000 tagged worldwide.

I'm still working on the update for v4/v5 map theme and will also roll back the improvements made to the v3 map theme. Once the v4 updated theme is ready/available, you might want to consider switching to using OAM maps as they have a lot more information in them and are getting rendered closer to OS maps now than lomaps... except for mineshafts, of course.