Messages

Hi John,

the theme available for download in the Locus Store is not compatible with Locus Map Classic. I've attached the older theme that works with LM Classic. Please copy it manually if possible.

Thanks,
Petr

What app are you using, please? Are you still on Locus Map Classic?

Hi,
would you please delete message in notify center and try to download it again?
Thanks, Petr

Hi,

Thank you for the report!
The node numbers are really missing and it's definitely an issue in the latest version. We'll prepare a fix for the next release.

Thanks, Petr

Děkujeme za report, chyba opravena
S Díky
Petr

[General notes]

Hi,

thank you for the feedback - it's very helpful.

If you don't mind, I'll comment only on the map content here. I'll forward the ideas or issues related to specific web planner functions to my colleagues, who know the roadmap and current state much better.

General notes

Shading is now less pronounced and no longer covers regular paths.

@alang

Disappearing peak names

- please check again; this should already be improved.

Are you intending in future to provide other maps, like OAM, OS Maps, etc.?

OAM maps are available only as offline maps for Android, so it cannot be displayed directly in the web planner. I know that @Menion  intended to create a system where the web planner could display maps stored on the mobile app, but to be honest, I'm not sure about the current state of that system.

What I can say is that there are plans to support at least some paid online maps, such as the French IGN.

The road number captions are not properly displayed in the vector map - there is a blue information box icon obscuring the road number.

This is fixed now.

at zoom levels 7 and 8 many of the captions overlay themselves

A fix is currently being deployed. But because of cached data, CDN propagation, etc., it may take a little while before the change becomes visible.


Thank you!
Petr

[Can raw Mapterhorn data be imported directly into Locus Map?]

@hudsson
thank you for your message and for the detailed comparison - and also for being a long‑time Locus Map user :-)

We have actually started using Mapterhorn data as well in our web planner https://web.locusmap.app
However, we simplify the data quite heavily, because of data size, server load and bandwidth requirements. This is the main reason why the rendering in Locus Map currently looks less detailed than in gpx.studio.
But we do not rule out using a more detailed version in the future.

Regarding integration on your side:

Can raw Mapterhorn data be imported directly into Locus Map?
Unfortunately no - the raw data downloaded from Mapterhorn cannot be used directly in Locus Map.
They must first be converted into one of the supported formats:

• HGT (elevation grid)
• or a raster map (e.g., GeoTIFF → MBTiles)

For both alternative, you can use tools such as: Rasterio, GDAL

However, both require some work with the command line and basic knowledge of geodata processing. So I'm  not sure if suitable for you.

Petr

@Andrew Heard
you might still be seeing an older version of the web planner. Would you please try refreshing the page.

@Graf Geo
Thank you for testing and reviewing it.
Regarding the option to turn layers on/off - I can't give a definitive answer, as this is more of a product‑level decision. I can imagine a simple toggle similar to what we have for offline LoMaps on Android (like mentioned hillshading or cycling/hiking routes).

Hi,
the specification for this route was changed about six months ago - you can see the change here: https://www.openstreetmap.org/way/508064043/history/4

Previously, the route was mapped as highway=path, which is why it was rendered as a dashed line.

About six months ago, it was changed to a climbing route, and therefore it is now rendered only with climbing symbols.

Petr

[LoMaps V2 (raster)]

Hi everyone,
we've just released a brand‑new generation of LoMaps on our web route planner. This is the first step in introducing our new map technology, based on the look and feel of classic offline LoMaps.

The new map is fully vector‑based, offering smoother zooming and support for map rotation on mobile platforms. Because vector rendering requires more device performance, we're rolling it out gradually - starting on the web, where we can test and fine‑tune it more easily.

Map options
LoMaps V2 (raster) - uses the same data as the vector map, but is pre‑rendered on the server for faster and more stable performance on all devices.
LoMaps Vector Map BETA - fully vector‑rendered version with smoother zoom and map rotation support, but with higher performance demands.

Both maps contain identical data - the difference lies only in how they are rendered. Based on your feedback, we'll later decide which map should become the default, as both approaches have their own advantages and disadvantages.

Let us know how the new map performs on your device and whether you encounter any issues. Your feedback will help us refine the map before the full release.

Thanks!

Hi,

I'm sorry - there was an issue in the script that caused that the system encoding was used by default. This will be improved in an upcoming update.

So I've converted your theme. By the way, several line strokes were defined as stroke-width="1,3" (with a comma instead of a dot), so I corrected them to stroke-width="1.3".

The converted theme is attached.

Regards
Petr

Ahoj,

máte pravdu – aktuálně je možné přidávat fotografie pouze k jednotlivým bodům zájmu, které jsou zobrazené v mapě. Není bohužel možné umístit fotografii na libovolné místo mimo existující body. Tuto funkci jsme už několikrát zvažovali, ale zatím nemáme konkrétní plán její realizace.

Co se týče editace mapových dat – naše mapy vycházejí z OpenStreetMap (OSM). Naprosto rozumím, že nechcete trávit čas mapováním či úpravou existujících prvků. V takovém případě stačí vytvořit tzv. OSM Note: https://docs.locusmap.app/cs/doku.php/manual:user_guide:maps_tools:osm_notes
Jde o jednoduchý způsob, jak upozornit komunitu a ostatní mapery na problém v mapě.

Díky a přeji hezký den,
Petr

@WildWortWechsel - You're right. For cities, both the local name and the English name are often displayed, which is particularly helpful for non-Latin scripts (and vice versa). However, the English names depend on the data source we use for map rendering (Thunderforest), so we don't have control over which cities include an English name.

Exactly, and we can't fill forest areas that are also designated as protected areas. The best solution might be duplicating the protected areas under a different key, such as ls_boundary=protected_areas, but that would invalidate all existing themes. Difficult decision...

Ah, I hadn't noticed your last post and went ahead editing my post from yesterday
Problem is caused because of combination natural=wood and boundary=protected_area. In LoMaps is the protected area  processed with force-polygon-line="true" (to correctly display the dashed green border). For this reason is polygon represented as line or several lines in the map file and isn't closed.