Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - poutnikl

Pages: [1] 2 3 ... 32
1
The record track has to be examined in very high details, in range of meters, in sense how the recorded GPS positions are placed.

Note that Locus has no idea about the proper length about the route, as,in opposite of OSMAnd proprietary solution, the Mapsforge vector map libraries do not expose such information, AFAIK.

Try to check the length on online tools by uploading the GPX, what hey say?


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


2
You can always throw the device out, if it became useless.. :-)

Is the recorded track path perfectly straight, or, does it have a little of zig-zag-ness originated from GPS fluctuation ?

As recorded track length calculation is based on GPS path, not the map way length.

You may try to set (stronger ) GPS filtering, that would straighten the GPS path
in Settings /GPS and sensors / advanced settings.

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

3
@keitsi Have you check it on https://www.openstreetmap.org
the master data the LoMaps+their indexes are based on ?

As the fix should be done there if wrong as well.

If OSM is OK then it is the Lomaps issue.

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

4
I am attaching the development version of the sedbatch script, I do not want to add it to the github, as it is not finished yet.

There is another scope option locus, that is currently implemented just for for profile option bike ( my bike profile generation ) and mtb (your ). It creates just 1 universal profile for both dry/wet condition.

It replaces function
Code: [Select]
function mtbexec {

replaceone is_wet 0 0 $src     mtbzoss-dry
replaceone is_wet 0 1 $src     mtbzoss-wet

replaceone mtb_hard_factor 0 1 mtbzoss-dry    mtbzoss-hard-dry
replaceone mtb_hard_factor 0 1 mtbzoss-wet    mtbzoss-hard-wet
 
}

by

Code: [Select]
function mtbexec {

replaceone is_wet 0 0 $src     mtbzoss
replaceone mtb_hard_factor 0 1 mtbzoss   mtbzoss-hard

}


5
Well, I guess that is addressed by the development script version. I may post it to the forum later today.


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


6
It is already in Brouter-profiles repository, at least last RC version.

Perhaps, zip may need to be installed as well.

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

7
Troubles & Questions / Re: Information missing from LoMaps
« on: September 11, 2019, 08:10:28 »
Sorry for wrong info about LoMaps. :-)

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


8
Troubles & Questions / Re: Information missing from LoMaps
« on: September 11, 2019, 04:56:32 »
..... no way to use it with the same comprehensive map contents as OSM or OSMAND.
.......
So what is the solution for me?

For your complains to be constructive, you should provide the particular place, map and themes for Locus team to evaluate if missing map details are  issue of LoMaps or of the themes not telling Mapsforge libraries to display them. Or it can be an issue of libraries themselves.

LocusMap and OSMAnd work with OSM based maps at very different conditions, so it is not reasonable to expect similar behaviour.

You had presumptions what LocusMap is like, or what it should be like, so the disappointment is the fault of making opinion before getting familiar with.   :-)

Use OSMAnd :-) What is wrong with it ?

I used it in past and now I use LocusMap or Mapsfactor navigator. Or local Czech application, that has its own POI index, using OSM based maps for non Czech locations.

Both Locus and OSMAnd have their strengths and weaknesses. Deal with that. Use an application which fits your requirements better for what you are going to do.

E.g. OSMAnd will probably never have the great integration with BRouter as LocusMap has, or off-road, non routing features. It has better following of GPX route.  It's maps need not extra files nor plugins for isolines.....


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

9
Troubles & Questions / Re: Information missing from LoMaps
« on: September 10, 2019, 20:25:47 »
You should be aware of the major difference between OSMAnd and its OBF maps on one side, and Locus maps and Mapsforge compatible MAP maps.

Osmand uses its own map format and, AFAIK, generates internally the map index for POIs, allowing POI search and other operations over vector map objects.

Locus uses external Mapsforge libraries to display maps and to manipulate with them. It does not allow for now POI search or other operations, unless extra Locus POI index for LoMaps is provided.

And even the explicit index  may contain just subset of POIs with basic info, so it is pretty possible a bus stop is not "clickable", but is just a displayed feature of vector map.

@Menion or @Petr Voldan may provide more insight to this.

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


10
Troubles & Questions / Re: Information missing from LoMaps
« on: September 10, 2019, 13:55:08 »
Try to download the Locus compatible map from OpenAndroMaps.org, together with their elevate/elements theme if that help.

Check also, if somebody accidentally deleted the buildings from OSM.

Sent from my Xiaomi MI A2 via Tapatalk

11
Troubles & Questions / Re: Information missing from LoMaps
« on: September 10, 2019, 13:34:10 »
Displayed map features are controlled by the used Mapsforge compatible map theme/style, that is usually configurable subset of the map data ( that is subset of  OSM data , plus some extra data, like isolines ).

Try to search for, install and try some external themes, e.g. on this forum or on other sites ( openstreetmaps.org, osm.paws.cz )

Sent from my Xiaomi MI A2 via Tapatalk


12
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 10, 2019, 12:28:45 »
@poutnikl
describe it please little more. When I open route planner, then hide the app by "home" button and then again over hope button display list of apps and choose Locus Map, I'm back in route planner. Same does not happen to you?

Prerequisite: Having the Beta Locus icon on the Home screen.

Actions to reproduce the issue:
Launch Locus Beta
Open the Route planner ( in my case from the poping up side bar )
Press the Home button
Press the Locus Beta icon again
The route planner is gone.

I confirm if I do it your way, bringing back from the task list, it works OK, i.e the Route planner has stayed open.

Perhaps pressing icon of already launched application makes some initialization. But, it works OK for the Locus Release.

Sent from my Xiaomi MI A2 via Tapatalk

13
Well, it was a false alarm.

I know 4 %X% parameters have been implemented in Locus some 2 years ago, but I kind of thought it was hardcoded to internal embedded variants of my car and bike profiles.

I remember recent discussion in the forum or BRouter Github repository about enhancing the implementation.

I have originally tested the %X% parameters on the Locus beta only.

Now, I have tested it on Locus release version, and it works as well.

But I still think only is_wet, avoid_unpaved and 2 other car related parameters ( avoid_toll?, avoid_motorways?) have been implemented.

Sent from my Xiaomi MI A2 via Tapatalk

14
Attached set of the generated Locus-aimed development profiles for testing, involving previously implemented  %is_wet% and %avoid_unpaved% Locus dialog parameter.

There are no -dry and -wet versions anymore*), as it is addressed by the dialog settings.

There remains Trekking-Dry just to distinguish itself from the original BRouter profile.

Works already for Locus release version.
(originally thought beta is needed).

*) For BRouter-web and other application, full set including wet profiles will be generated.

http://cloud.tapatalk.com/s/5d74b87471208/BR-Bike-Profiles-develop-locus.zip

Sent from my Xiaomi MI A2 via Tapatalk

15
I have currently modified the development not yet submitted script and the bike template.

Code: [Select]
assign   is_wet     0 # %is_wet% Wet_conditions
If there is used the scope parameter "locus" instead of "all", the script does not generate both dry and wet profile variants, but just the universal version.

The %is_wet% parameter ( original iswet was not recognized ) is switchable in Locus ( tested in beta ).

I will do the same for generation of other bike profiles.

Full generation is kept for Brouter-web uploads ( for now?) and for other applications.

I have experimentally added another parameter, recognized by the Locus dialogue, to the bike template:

 %avoid_unpaved%

as the stronger version of %is_wet%.


Sent from my Xiaomi MI A2 via Tapatalk

Pages: [1] 2 3 ... 32