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.

Show posts Menu

Messages - chbla

Is this the selection menu in the settings, or where do you chose that? (Don't have locus here right now to check)
Thanks! I'll give it a try
Can anyone please comment on:

QuoteIf I use openandromaps, or another OSM map, is it somehow possible to filter the POIs/features by type? I think Osmand can do this - or is this a matter of the theme supporting it? (as for Openandromaps I can switch on/off certain things, although on a higher level).
If I use openandromaps, or another OSM map, is it somehow possible to filter the POIs/features by type? I think Osmand can do this - or is this a matter of the theme supporting it? (as for Openandromaps I can switch on/off certain things, although on a higher level).
Thanks jonh_percy, I'll have a look.
I noticed that you can also extract the points from openstreetmap, see links at the bottom:

@voldapet: where do I get the offline POI db? it's empty in my Locus. I understand the reason, but I think that parking lots are one of the most used POI searches usually :)
If I understand correctly they are included in the offline vector maps, right? I'm satisfied with openandromaps and I don't really buy them for POIs. Are they based on OSM?
I've tried it - but that's mainly for the UK it seems, for my region (Austria, Switzerland, Italy) there is not much ..
Hi there,

I'm right now looking for 2 types of POIs:

a) Parking Lots
b) drinking water sources (while hiking)

I noticed that OSM (I'm looking at openandromaps at the moment) includes those already partially. However, those points are only selectable through the theme and are not imported as waypoints.

Is there a something so I can hilight parking lots or other particular points if they are features of the map? Or how does this work?
Is it possible to extract these OSM pois somehow so I can filter them in the POI list?
Or does anyone have POI sources for parking lots and water sources?

Thanks a lot,

Ich wuerde das feature gerne pushen :) Brouter mit instructions waere fuer mich die beste Routing Loesung die ich mir vorstellen kann - vorallem wegen den Profilen.

Laut Menion kocht da wirklich jeder sein eigenes Sueppchen, das ist ziemlich schade. Die Moeglichkeiten laut seiner Aussage sind:

Quote1) extending export from BRouter by same tags and system as is used in MapQuest, Google or other service (every has own solution!)
2) extending GPX by Locus private tags (in this case, it will be export for Locus-only)
3) it should be also possible to use Locus API which allows directly create track with navigation commands anyway this will require import of Locus API and again, result will be Locus-only

Allerdings sollte so etwas meiner Meinung nach nicht Locus-spezifisch sein.

Bisher plane ich meine Routen mit brouter online und fuege dann in bikeroutetoaster Abbiegehinweise hinzu (TCX Courses File). Ich bin nicht sicher ob das TCX Schema da Sinn macht, aber es ist das einzige was halbwegs funktioniert.

Aufgrund von anderen Diskussionen frage ich aber eben mal bei den GPX Leuten nach, obs da keine einheitliche Loesung fuer sowas gibt..
For me it seems we don't really get anywhere with the current automatically generated instructions - partially because Locus cannot compute certain things and because it's difficult to implement.

However, therefore I do not really understand why the tickets regarding TCX are not paid more attention to. If it's not automatically possible but we already have partial functionality for the interpretation of coursepoints - isn't it natural to extend this? It would be a lot less effort implementation wise than this automatic stuff. You just extend the functionality for coursepoints by allowing additional elements such as 0709 and Ingo suggested in their tickets, eg:

In essence it is just a coursepoint with an arbitary name or type that can be used for whatever a users wants and is displayed at distance X before the point. That's it, no magic no nothing, I don't understand why the whole thing is complicated so much.

I've tested the new features yesterday for the first time during a 4h mountainbike ride.
I noticed the following when using Navigation (with a predefined track):

1. Automatic turn commands are useless in this scenario. Usually you are following a path and 90% of people are not interested in turn information, you just follow a path. This would only be relevant to rallye drivers, which I think we can exclude. What is needed are turnpoints/coursepoints at junctions - that's the only info that is relevant. If I come to a junction I need to know which way to go. So the screen should pop up at a specified distance and show me which path to take.

I've suggested a separation between turn points and junction points before, but I think Locus cannot recognize junctions (from what I've read) is this right?

One point where I could see turn points helpful is when you follow a rather unmarked path.

2. Screen-On modes with automatically generated commands drains battery. I used the default settings first, with generated commands and the screen turned on so often (and in 99% of the cases where it is not necessary because there is no other way to go) and my Nexus 5 would last maybe 2.5 hours. So I had to disable this.

I ended up oldschool, manually switching on/off the display when I was at junctions and did not know where to go - then just had a look at the track.

So right now what this means for me is: It would be best to push the TCX file support again and turns vs junctions. For future rides I will get back to creating my own coursepoints with bikeroadtoaster.
Quote from: michaelbechtold on April 11, 2015, 19:04:26
Ich denke die SRTM-Daten der Satelliten sind genauer als alles was das Smartphone messen und/oder berechnen kann. GPS ist bzgl. Höhe teilweise ziemlich wild, da habe ich genug Beispiele erlebt. Druckmessung habe ich nie praktiziert, kann aber m.E. nicht mit Radarmessungen konkurrieren, da eine akkurate Normierung fehlt.
Die Funktion Höhe eintragen nutzt SRTM.

Da muss man sehr gut aufpassen - es ist naemlich genau umgekehrt: Barometer > GPS, SRTM.
Ein barometrischer Hoehenmesser ist das genaueste was uns zur Verfuegung steht. SRTM Daten sind interpoliert, und die die zur Verfuegung stammen teilweise von alten Karten. Das ist dann alles im 25m Raster. Fuer Oesterreich gibts demnaechst ein 5m Raster da diese Daten frei zugaenglich sind (Radar).

Interessant fuers Smartphone waere eine App die fuer das Barometer entweder automatisch (GPS) die Hoehe am Ausgangspunkt korrigiert (wie zB Garmin Uhren) oder man das manuell beim losgehen einstellen kann.
Other features / Re: Mapsforge 0.5
May 06, 2015, 16:07:39
Well that's just a matter of abstraction. You can always separate things into default and advanced mode.
For me, the benefits outweight simplicity.
Maps / Re: Question about Swisstopo maps
April 28, 2015, 11:40:01
"competetive"?  ;D

Well the difference would allow to renew it for 18 years
Since the benefit of the swiss topo is it's detail, it's mainly used to look up things.
For navigation/guidance/calculation you might as well use OSM and not notice a big difference.

So for me it's kind of hard to justify this price.
Maps / Re: Question about Swisstopo maps
April 28, 2015, 11:07:10

For 38 swiss francs, complete map, 1 year
So in essence we are paying 683 EUR only to have the map in locus instead of the swiss topo app?
I hope I missed something..
Quote from: menion on April 24, 2015, 09:54:36
@chbla: I beleive there is already 3+ topics that discuss about navigation in Locus. Well, I have quite mess it all these requirements ..

Sorry, I didn't know where to post it :)

I added it here:
as this ticket seems almost mandatory with the new navigation