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 4 ... 33
16


Díky. Není to sice ideální, ale lepší než nic. Mnohem lepší by byla nastavitelná vzdálenost zákazu otočení v možnostech navigace.

Myslíš odchylka od trasy nebo ujetá vzdálenost po sjetí z trasy ? Protože to může být paralelní ulice/cesta pár set metrů bokem.



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


17
Zdravím nazpět.

To vůbec není otázkou profilů, ale Locusu samotného.

Nemá to konkrétní nastavení, jako vzdálenost od trasy pro upozornění sjetí z trasy, přepočítání trasy nebo přepnutí na navádění.

Menion, pokud jsem to správně pochopil, naprogramoval přepočítávání trasy ( pro prioritu trasy, nejsem si jist, jestli i pro prioritu bodu ), že Tě nejdřív 2x pobídne se vrátit ( pokud se mu zdá návrat lepší ), a napotřetí to vzdá a dynamicky návrat zakáže.

Pokud si pamatuji, tak určí nejbližší bod původní trasy a zkoumá, vychazi-li návrat na něj lépe kupředu nebo zpátky. Pokud zpátky, tak tak to na Tebe 2x zkusí, jestli to otočíš, a pak tam interně hodí nogo bod.

Takže to vlastně bude nepřímo souviset se vzdáleností pro varování/přepočet a s frekvencí opakování varování o sjetí z trasy.

Když je nastavíš nakrátko,  Locus se vykašle na návrat o něco dřív.

Matně si pamatuji, že někde je nastavené natvrdo opakování po 30s, možná je to zrovna tady. Takže možná "vzdálenost pro přepočet + 2x30s".

Jinak nezbývá než v Locus ručně přidat nogo na návratovou trasu.

@menion Můžeš upřesnit ?

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

18
[CZ&SK] - diskuze o Locusu / Re: Problemy s GPS na mobile
« on: October 02, 2019, 08:12:06 »
GPS mojí bývalé mašinky Sony Xperia M Dual s Android 4.3 zase po asi 3 letech pravidelně vytuhla asi 1 minutu po GPS fixu, který byl sám o sobě rychlý.

Tvůj problém může být kombinací drobné nekompatibility LineageOS / A9 s daným modelem a  stárnoucího hardwaru, který může být už "nahluchlý" a "unavený, když se zahřeje".

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


19
Troubles & Questions / BRouter profile %parameter% true/false values
« on: September 29, 2019, 23:20:53 »
Some time ago, there have been implemented syntax

assign parameter = 0/1 # %parameter%

for chosen set of parameters of my embedded car/bike/hiking profiles.

is_wet
avoid_toll
avoid_motorways
avoid_unpaved

It works well even for external BRouter profiles.

The problem is, Locus does not detect the parameter, if it's value is defined

assign parameter = false

instead of

assign parameter = 0

Would it be possible to extent Locus profile parsing analysis to Brouter values true/false, that were implemented later?

Current implementations of the new car profiles by Arndt, based on very good kinematic model, prefers true/false for logical values, even if Boolean type is not implemented yet.

BTW, I recommend these car profiles, instead of mine.

See also https://github.com/abrensch/brouter/issues/197


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

20
Another candidate is the Waymark v2a theme. It is together with Elevate
 invaluable for long distance bike trekking along international a/o national cycle route network.

As most themes render cycleroutes  too late and often do not distinguish well the route classes ( ICN,NCN,RCN,LCN).

E.g Native Locus hiking/bicycle touring theme shows routes at zoom 13+ what is too late for big picture with ICN or NCN only. Additionally, all have the same colour.

Elevate cycling renders ICN/NCN at Z8-9, other routes at Z12. Similar for Waymark theme.

Waymark theme has additionally a great feature to turn on/off route classes independently.


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

21
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 26, 2019, 12:42:57 »
Just quick thoughts:

The only idea coming to my mind is error propagation via sums of variances ( squares of standard deviations ).

But to get a model how these propagate via Kalman filtering may be very challenging.

Some info could be extracted from Kalman filtre variance matrices.

Another aspect, that may nullify the above effort would be  nature of position errors.

They are not random either in time, either in space, but there is strong both space and time correlation of errors.

By other words, following a road, there may be e.g. for 10-15 seconds a systematic position bias few meters to the right, and after a short while, a systematic bias to the left. If these biases are long enough, Kalman filtering cannot say difference between the bias and true deviation, as it is designed against random variations.

A filter addressing biases would need a feedback from a real life, like systems evaluating position errors of known positions, what is out of ordinary GPS abilities.

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

22
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 26, 2019, 07:47:12 »
@Žajdlík Josef
Perhaps, it may be related to the recent fixed issue of escaping the route planner if Locus was brought back by clicking on its icon, versus staying in route planner if Locus was restored from the list of recent applications.

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


23
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


24
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

25
@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

26
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

}


27
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


28
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

29
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


30
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

Pages: 1 [2] 3 4 ... 33