Messages

... Currently, I'm working with Radim on our own BRouter data generator that will be integrated directly into the app, probably in a similar way to downloading elevation HGT files. ...

Will it include incremental updates similarly as  the Brouter app does ? ( or my Android termux Linux bash script for power users, calling BRouter  as java application brouter.jar  for the processing of the downloaded incremental download   )

(If the prior square update is not older than 7 days, incremental update downloads typically just 2-5% of the full size, very useful e.g. for frequent/daily updates of home square a/o neighbourhood, especially for data limited cases. )


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

@john_percy  Menion could implement location dependent LocusMap behaviour...   

I have created some multisegment test route in the Route planner, going to play with segment way/surface stats. I have not created segments sequentionally, but by cutting original single segment by dragging the segment icon.

When I then clicked on the logical 1st route segment icon, the selection dialog displayed at the top "Part 3 of route" ( probably created as the third ), but then the altitude stats chart correctly displayed "Route segment 1".

Later I created the 4-segment route sequentially and realized the selection dialog numbering ( "Part n of route") was 3-2-4-1, instead of 1-2-3-4. I think the numbering could be more consistent. :-)

BTW, have I got the message right, that the segment based way/surface stats are planned, similarly as the segment altitude chart is already in place ?

@John Percy In UK context, you are right.

In CZ context, they are in some sense alike, grouping them in similar manner as are grouped similar surfaces in incoming LM4  surface statistics.

I agree it is rather controversial and perhaps it should not be marked so.

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

New beta still shows highway=footway as residential not path in route planner chart.
As far as I can see path and footway are used pretty well interchangeably in UK mapping.


Sent from my moto g(6) plus using Tapatalk

I think there is general OSM trouble with proper mapping usage of
highway=footway and highway=path.

Some regions or  mappers prefer  =footway over =path for narrow single track path for pedestrians, mostly out of urban areas. Or they take them like  interchangeably.

OTOH, other regions a/o authors, like in Czech Republic, use mostly =path for them, using =footway rather for sidewalks and similar way in the urban area, often paved. Personally, I am not sure if I have ever encountered usage highway=footway e.g. for a hiking path in Czech countryside.

Considering the photos from the OSM Wiki....... they seem rather to support the Czech way ( what may include Menion :-) ) than the UK way.

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

It seems that mysterious update is not the same as the explicit update from the GP.

I was always able to overinstall the LM4v960 over the mysteriously installed LM4free/beta. Recently, for whatever reasons, I have explicitly demanded update of LM3 free/beta and since then, LM4 960 cannot be installed.

Perhaps it may play roles this is an ad supported free version, not unlimited beta version.

Something like that happened to me before, sometimes it is related to LM being set as a system manager application, which has to be turned off. But I guess it did not help me that time and I had to uninstall LM3 free/beta before being able to install LM4 alpha.

And exactly this I had to do now, importing then previously saved LM4 backup.



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

Locus did, what it had been told, not what you had really wanted, as any good obedient computer does  :-)

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

@freischneider  +1

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

Thanks for version clarification.
Regarding surface categorisation, it seems very fine to me.

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

I have tested the hypothesis it may be an issue of beta tester program of GP.

I have noted yesterday the current version of Podcast Addict, the other app I am subscribed as a beta tester. I have updated manually all applications but these 2 applications ( LM3 free + PA ) where both have listed an available update.

Today, at the usual morning hour, I have noticed the regular unsolicited LM3 free update happened again. The PA app has stayed not updated.

I guess it is either an issue specific to LM, either it has something to do with LM4 being side-loaded in parallel with GP app with the same App ID ( a kind of system protection? )



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

Well, not really. I got used to LM4. Also, I have set updating via WiFi only, but this is  ignored here. Probably GP issue.

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

A trial question is free.  :-) I guess you are right, John, he said it. The updating ping-pong is very annoying.

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

Would it be possible to manage LM4 alpha/beta to have formally ALWAYS higher version number, so Google Play would not try to update LM3 over LM4 ?

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

I have thought it was just me.

I have as well turned off automatic updates ( on Android 10 ). I had to manually reinstall latest LM4 beta after 3-4 times seeing LM3 beta/free magically appeared installed over the LM4  in last days.

I also confirm it looks like LM specific issue ( or possibly more generally an issue of applications subscribed in beta tester program ? )

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

I confirm that. OTOH, moving to  other maps while on high zoom level often does not work, perhaps because of typical large overlapping of OAM maps. LoMaps are said to have more precisely and explicitly defined boundary.