Messages

Hi Menione, the new search is great. Very good work. This is the best change in the last year. Personally, I would add the option to view the search directly on the map, but it's not that important. Thanks.

Map is on Dortmund, Nordrhein-Westfalen, Germany. GPS off, device located in the area.

I search for "Halde", those are artificial hills, results of former coal mining. There are quite a few in this federal state, they have "Halde" in their osm name, usually.

Now after pressing enter it shows some inappropriate results. In the south of Germany.

https://youtube.com/shorts/fhv1RJWkurw?feature=share

Zdravím,
Povrch cesty Sett (dlažební kostky) překládá Locus jako Kameny, což je dost zavádějící pojem (ten bych čekal u povrchu Rock).
Ještě bych měl návrh na vylepšení. U každé polní/lesní cesty existuje parametr Klasifikace povrchu (rozmezí 1 až 5 dle typu). Ten je u většiny cest vyplněný. Asi by stálo za úvahu rozdělit polní/lesní cesty ještě podle tohoto parametru - klidně jako podkategorie. Člověk by tak hned získal představu po jak kvalitní cestě se bude pohybovat.
Parametr povrch cesty v tomhle mi moc nepomůže, protože většinou není vyplněný a všechno spadne pod kolonku Neznámé (I když se snažím povrchy doplňovat )

When using the web planner or LM4 route planner using any car profiles: the planners are routing via any OSM way to avoid this secondary road https://www.openstreetmap.org/way/615648056.

There's nothing special about the OSM tags:
highway=secondary
lanes=2
maxspeed=100
name=Tram Road
oneway=no
surface=chipseal

LM web planner with any car profile wrongly avoids the road: https://link.locusmap.app/r/afvn9c - watch the animation!

LM web planner with bike profile is OK: https://link.locusmap.app/r/py4dj4

brouter with road bike profile is OK: https://brouter.m11n.de/#map=12/-43.3832/172.5842/standard&lonlats=172.302704,-43.312773;172.636242,-43.407681&profile=fastbike

brouter with car profile is OK: https://brouter.m11n.de/#map=12/-43.3832/172.5842/standard&lonlats=172.302704,-43.312773;172.636242,-43.407681&profile=car-fast

Google Maps is OK: https://www.google.com.au/maps/dir/-43.3117991,172.3024609/-43.4084211,172.6426318/@-43.33639,172.2820699,11z/data=!3m1!4b1!4m2!4m1!3e0

I don't even live in this country but am interested what may be the issue so I can improve the situation. Any suggestions?

It would be even nicer if the POI is opened directly in the app.  I am thinking here of the POI ID. But for this you would have to have an Api access ? to the app.
Henk van der Spek https://forum.locusmap.eu/index.php?action=profile;u=1680
is a contributor to the app, maybe we would have a possibility here.

I was thinking about editing. Perhaps it would be enough to add a small button with a direct link to editing text via the eight or Wiki website. Depending on where the text is taken from.

There is an app for editing POI in OSM. Its name is: OSMgo
Menion has recently added it to Apps in the sidebar.
https://forum.locusmap.eu/index.php?topic=7975.0
With the app you can change properties of POI very easily. Also the name can be changed.
I often use it to add on the way, opening hours, website, phone number of restaurants.
This app could be added in POI to change.

Hi Radime.
I understand what the problem is, because I often add and correct the data in eight OSM maps. But if I understand it correctly, then the data for lopoints come from two sources. It is quite difficult to find where to fix the data.
I will also write Czech, I'm not very good in English:
Obrázek Sousoší Panny Marie: V OSM je uveden správně, ale v Lopointech je uveden jako památné místo. Měl by se tudíž asi opravit ve Wiki.
Obrázek Laudon: ten byl špatně uveden i v OSM, ale adresa u něj tam uvedena není. Nejspíš tedy pochází z Wiki. Název jsem opravil v OSM na Pomník Generála Laudona, ale měl bych teď jít ještě opravovat data ve Wiki? Je to dost komplikované když data pocházejí z více zdrojů.

Zkuste o tom ještě pouvažovat. Některé názvy jsou opravdu hodně mimo a jaká bude mít databáze hodnotu když bude mít špatná data?

Not all parking spaces are available at the Lopoi. That's why I still use the Oam Poi, there are more parking spaces.
The parking (OSM 783728160) is available at OAM. For Lopoi he is not available online and offline.
There are also differences between Lopoi offline and online. Parking (OSM 688458079) is available as online and not available as offline.
Then I have a parking lot as a permissive (OSM 784802209) this see in the Oam Poi. In the Lopoi he is not available online and offline. Maybe it's on the permissive. You should provide parking as a permissive. But you should display a warning in the POI. That could be a red field with exclamation mark. When I click on it, the note will be displayed to me. This field could be next to the Fee fields.

I can also confirm:

LoRouter's car-routings (both fast and eco) seem to use a fixed speed of 50 km/h for ETA

It's not using BRouter's ETAs from the kinematical model

Hello and thanks

Is the gpx-file, exported from the navigation in Locus, enough? I also added a screenshot that shows the estimated travel time and the distance for the attached gpx-file.

Best regards

One of the most important things when you are outdoors is water. In the screens you can see that even if there are two fountains nearby, selecting the first search result which should theoretically be the closest sends me more than 50km away.

The web planner doesn't work well set to walking, but does OK set to hiking. I screen recorded the issues which you can see in this video: https://www.dropbox.com/s/g88qnkugianhn1w/Locus%20Map%20web-based%20planner.mp4?dl=0

Hi,

hmm I see post from sbojuju but without any (my?) reaction, sorry. Not sure if this is still valid.

Anyway, Radim, to your question. Locus Map loads coursePoints from FIT file and based on defined action, map this action to something known to Locus.

In the case of mentioned two segments-types, these types are simply ignored because I had no better idea what to do with them.

It is possible to set them some icon or mark them as "via points" for navigation. Not sure if any from this may be useful ...