Messages

The proper way is to update the map database on the https://openstreetmap.org  ( OSM )
via their online editors or extra OSM editing applications like JOSM (java) or Vespucci (Android).

The very important thing is being compliant with their  site and data policy.

This would provide map update available for any map application using OSM data.

If you want to create your own private maps, it is possible, but much more complicated. For this, I would rather recommend to stay with trails being recorded tracks, independent on the map.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

In contrary to profiles, extra specification does not make much sense. I have spoken  for specification for common users, not experts. For the stats to be really useful, not just bells and whistles.

Whatever will be Menion's final decision, I will be fine with that. I have just wanted him to hear various opinions.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Effective category should be more important than formal category.

eh'...
I'm out.

Well, formally paved road  surface=asphalt|paved with tracktype=grade3 and  smoothness=very_bad can put one out. :-)


Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

I am well aware of cobblestones  being archetype of paving. But surface quality is the most important to fast or trekking bikes, not to MTB or cars. Effective category should be more important than formal category.

I agree with to be careful where to put cobblestones. STONES  surface category is fine to me. A bike rider could prefer to push his bike across short cobblestone patches, unless sett is incorrectly tagged as cobblestone. Even car drivers may prefer gravel if it is rainy, as wet cobblestones are dangerous ( and sett too ).

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

I an well aware cobblestones are not loose, compared to gravel or pebblestones. But it is often disadvantage.

When you rode across the true cobblestones ( not sett nor flattened cobblestones ), you  immediately realize you would rather prefer near any unpaved surface, including gravel, which is kind of soft due its looseness.

Effectively, assigning cobblestones to paved surfaces is an insult to the term paved.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

I'm not sure about "cobblestone" - so you think rather "gravel" then "stones"?

Well, current usage of cobblestone in OSM is ambiguous. I have read recently there is recommended using sett or unhewn_cobblestone or cobblestone:flattened
what applies the best.

cobblestone in sense of unhewn one is like gravel, even worse, as gravel slides away.
It could be STONES or GRAVEL, probably former .

flattened one is somewhere between unhewn one and sett. But still probably STONES.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Zooming in "slides": I was thinking more about adding them also to segments. When you tap on the segment, there already is a chart just for this particular segment, so why not to have a way types/surface here as well.

I guess segments could be good enough. If a profile fits your preferences really good, ( non round ) routes have often none or rather just few route segments, which may be quite long. OTOH, I can always make an extra segment just for sake of having stats, cannot I ?   

About the elevation + way type + surface chart, it may be good if they were somehow, even if not exactly, zoomed together with the map.

E.g.  a route is 120 km long, but the map is zoomed in to show just a 5 km long route section between 20 and 25 km. The charts should not show all 120 km, but just the relevant section, possibly with some padding.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Hmm, for bicycles, it would be good if similar surface qualities had the same category/colour. Too  many options is hard to remember and the bar chart could be too much scattered.

E.g.

• cobble stones and pebble stones are much closer to gravel than to sett
• sett is effectively close to concrete, both make you little jumping up/down.
• finegravel is quite far from gravel. considering smoothness and convenience.
• paved almost always means asphalt and should probably have the same colour/category.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

LM4 is not in Play store yet.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

It seems the rule "never update before a trip, but after it." has paid off for me, leaving for hiking weekend. :-)

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Even if I had such a feature available for my Xiaomi MI band 4, I would still prefer the voice based on the BRouter hints, as it provides more information like the shape and the distance.

Vibrations could get easily confused with other sources of vibration events plus it may be challenging to remember which is which.

Note that the band allows to define vibration patterns, but for all events from a particular application, not distinguishing further, AFAIK. There could be option to implement in LocusMap hint notification messages, but except of hiking/walking, it would not be a wise idea for security reasons.

But I think your idea so that you can also color the section of the route on the map is very good.

+1 :thumb up:



Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

I mean some minimalistic phone friendly version, possibly on demand only.
Note also mentioned  track grades are there listed  among surfaces.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

[@poutnikl]

@poutnikl
The fill color below chart may be better. I was playing with it and it does not look too good because the chart can't be interpolated (at least the library I use does not have this option). I'll try another alternative with a simple line below chart.
Thanks for the info about grades!

What about summary statistics, like can be displayed in the recent BRouter-web versions under the pie chart icon on the right ?

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk