Messages

Nice to have map themes now included.

For me, it would be nicer to have map styles as well as themes included.

Because each preset can have own independent set of settings I imagine could cause user confusion. Seems user will generally need to have settings identical in each preset (for example I am testing with 3 presets Cycling/ Driving/ Default). There is not going to be large number of settings to choose from so could the initial choosing of set of settings be removed - each preset just has all possible settings? User simply decides on the value of each setting.

That change would need a three-position switch (on | off | no change) for each setting which is what the present arrangement achieves.

My feedback regarding the presets-feature:

I'm ok with the way it's implemented now. This way the settings currently in use are consistent with what the main settings menu shows (at this time). You (the user) just have to keep in mind that some settings can be changed from what you set up in the main settings when a preset is "executed".

I must admit, I first was confused about how to set up a preset, even to the point I thought it didn't work on my phone (or maybe it actually wasn't in the first version?). It took me a while to realise that it's a two-step process of first selecting which settings should be available in the preset, and then the actual setting. But I think this is only a matter of headline/description/help texts...

So I'm looking forward to also having themes, dashboard activation, permanent display on and display activation settings available. Also, preset execution when starting track record with a specific recording profile would be nice!

For me these "presets" are really setting "overrides". It seems to more accurately describe the new feature. Would you consider renaming presets to overrides?

Currently there doesn't appear to be a way to disable a selected preset. Could there be a checkbox at the top of the main dialog?

It seems for each available boolean setting there are 3 possibilities: don't override, force true, force false. Similar for more complex settings. Maybe if the overridden value is same as default value it is displayed in normal font, and if  overridden value is different to default value it is displayed in stronger font?

At present there are two steps to creating a new preset - 1) select list of settings from list 2) decide on overridden value (which may be same as default value anyway). To make it more obvious to user what "is going on here" could there be just a single dialog/ list. I think Wolfgang commented this was confusing too? For each setting there is an "override" checkbox, and if override=true then value control is enabled, and can be modified, and will be in strong font if different to default value.

If list is ever opened subsequent time for further editing, the overridden values are sorted to/ displayed at top of list to save user scrolling through whole long list.

Maybe in the "top level" selection list of presets below each icon, there can be a list of overridden abbreviated or acronym setting names in small font for quick glance. I imagine for each preset there will only be short list of settings that user would override. A long list would suggest user has misunderstood the purpose of presets.

Just my 2 cents of thoughts after some further usage and reading other forum comments.

Die .rd5-Dateien sind kein darstellbares Locus-Kartenmaterial, sie dienen ausschließlich zur Berechnung des Weges bei der Routenplanung und Navigation. Wählst Du bei der Locus-Navigation/Routenplanung BRouter als Routingservice, übernimmt BRouter die Routenberechnung und greift dabei auf die .rd5-Dateien zu.

For global info: http://www.locusmap.eu/everything-you-always-wanted-to-know-about-elevation-in-locus-but-were-afraid-to-ask/

I do not have a pressure sensor so when I found that altitude data of the recorded track with just gps are crazy I tried to solve.

First you need a good accuracy of recorded track points:
settings -> track rec -> choose your profile settings --> requested accuracy set a strict value (for me 30mt)

Second you can have better SRTM values using HGT files with 1" arc insted of 3"
http://help.locusmap.eu/topic/hgt-elevation-data-display-if-both-1%E2%80%9D-and-3%E2%80%9D-resolution-hgt-files-are-present-in-the-srtm-directory
http://www.viewfinderpanoramas.org/Coverage%20map%20viewfinderpanoramas_org1.htm
http://www.viewfinderpanoramas.org/dem3.html

and if you want a costant application of srtm data and bypass the "fill data.." after track recorded use this:
in settings -> gps and position -> altitude manager -> settings -> srtm data -> replace gps values

Except really rare cases (except some tasks around downloading of maps), Locus always used device time ...

With the present user interface, changing overlays is rather complicated. The current overlay has to be removed with the "Remove" button , then a new one has to be selected with the "Select" button. As the overlay can be simply switched on and off, either with the eye icon on the map Layers slide-out menu or the switch on the Map Overlays pop-up screen, the "Remove" button is someone superfluous. I suggest either (a) click on the overlay name to change to a different overlay or (b) change the "Remove" button to "Change overlay" button. That reduces clicks by one.

@gynta: hmm not sure I understand. Topics are marked as read when you tap on them to open in browser or when you tap on an eye in top right corner of post.

@Bucky Kid: I've already read about similar problems, have to check it, thanks.

@michaelbechtold: thanks for test with rings. Generally they are all incorrect. These rings should be on normal online/vector maps elipses, and not real circles. It is not visible for small distances, but for distances more then100km , this should be visible a lot. Also because of this, I see no sense in values above 100km. I've anyway added at least 200m ring.

@cokeman: not sure how may I help you. I've downloaded attached gpx file and filled values with SRTM 3'' downloaded over Locus and values are in range -5% / +2.5% , so it looks a lot better. MAybe a source of your 1'' isn't as accurate as you think? .

Hello. I note a small shortcoming when adding a new track or waypoint. The suggested folder seems to be choosen quite randomly. Should be pre-selected either last used folder from previous add or user preference for default category for new track and waypoint.

Sent from my phone by Tapatalk

3.20.0 release notes has this very interesting new feature:

<add: option (in config.cfg) to pan & zoom in track chart in vertical axis as well>

In 3.20.0.1 when I click on About > Release Notes > ">" to get more info for this topic I get error "Application for selected feature is missing...". It seems half the topics with links back into Locus website are valid/ working, but other half also give this error - mistyped URL?

New setting gui_track_screen_chart_vertical_scale=0|1.

My first experience with setting=1 and tap the chart + button: not very useful because X and Y zoom at same time. Pinch/zoom seems quite unreliable. Could the Y axis have own +/- zoom buttons when setting=1, or why not forget special setting, and just have Y axis buttons +/- zoom buttons always displayed?

Prima, dass es jetzt besser klappt!  Daran wurde in den letzten Wochen auch viel gearbeitet. Und ist sicher noch nicht fertig, ...weil noch nicht gänzlich perfekt.
Ein Gedanke zu den automatischen Neuberechnungen mit Endpunkt-Priorität: 
Wie wäre es, wenn Locus beim Beginn der Navigation Startpunkt, Zwischenziele und Endpunkt der Route ausliest, in gesetzter Reihenfolge intern erfasst und konsequent bis zum Erreichen des Routenziels verwaltet (passiert/noch nicht passiert). Bei notwendiger Neuberechnung wird auf diese Daten zugegriffen und immer der erste, noch nicht passierte Punkt anvisiert. Bei Navigationsstart, also zum Zeitpunkt des Erfassens der Punkte, werden alle Punkte auf "noch nicht passiert" gesetzt.
Das heißt dann, egal von wo ich die Navigation der Route starte, es wird in jedem Fall zuerst zum Startpunkt der Route navigiert. Wurde dieser passiert (bei beispielsweise ca. 30m Annäherung), wird er intern als ,,passiert" gesetzt und wird somit bei einer nächsten Neuberechnung nicht mehr berücksichtigt. Durch diese Arbeitsweise würde bei Abweichung von der Route kein Zwischenziel mehr verloren gehen.
Auch das kommt unter Umständen vor: Wird ein Einstieg (Startpunkt) inmitten der Route gewünscht, könnte das beispielsweise durch Langdrücken auf den gewünschten Punkt der Routenlinie umgesetzt werden (Navigation ab hier?).

[Digital Terrain Models (DTMs)]

Dear Locus map creators and users!

I want to tell you, that I've created several Digital Terrain Models (DTMs), which are based on precise Opendata LiDAR-elevation data of the country's Geographical Institutes.
You can find all infos and download links on the following Website:

https://sonny.4lima.de

The improvements in accuracy, quality and fine details of my model's elevations compared to those of the popular SRTM-datasets are enormous. Especially in mountainous terrain.

You can use these new DTMs to create improved, more accurate contour lines in maps. Or you can copy the files for the area of your interest into the correct folder of Locus to improve dynamic elavation values and the shading of the maps in these areas.

Yours, Sonny

@lor74cas: I'll try to improve it little bit and allow to hide this button

@Bucky Kid: you see a raster map as background of this feature? Surprise, because only vector maps should be used here! And with chart > I'll try to do something with it, thanks.

Thanks for an email Michale (btw, please change your support email to locus.map@asamm.com . Email you used is not longer used).

Seems you were a victim of one small issue on previous version. On the end of recorded track is one single invalid point. Exported file looks like:

Code Select Expand


    ....
    </trkpt>
    <trkpt lat="49.985613" lon="9.138136">
    </trkpt>
  </trkseg>
</trk>
</gpx>

Last point is without a time and other values. I'll try to fix it on Locus side, thank you.

Anyway if you will wants to use format I use in Locus, less work for me, anyway it's not clear solution I think.

Hi Menion,

sorry for the long delay, but here's what I came up with.

You can use the latest version (1.4.) of BRouter from it's homepage (not yet on Google Play):

http://brouter.de/brouter/revisions.html

use the apk there'in, and also update the routing profiles (they are not automatically overwritten by an APK update. Simplest way is to just delete the "profiles2" directory, it will be re-created on next brouter app start)

After careful consideration, I decided to go with the native turn-instruction formats used by Locus and OsmAnd.

3 ways to generate an GPX, so 3 ways to make sure that Locus format is used:

- when creating a GPX via the BRouter app, nothing special to do. The profiles are configured to "turnInstructionMode = 1 = auto, which means it generates Locus format when using a Locus waypoint-database.

- when creating the GPX by requesting it via the AIDL interface, you must send an additional parameter
  "turnInstructionFormat" with value "locus".(Just the same way you are sending "lons" and "lats", but with a String value)

- when creating a GPX via the Web-Interface ( http://brouter.de/brouter-web/ ) you have to modify the profile to contain turnInstructionMode = 2 (use the "upload" button the upload the modified profile)

I tested the voice hints by manuelly importing them into Locus, and that works fine. So I really wold like to be able to use them also when using BRourer via the AIDL-Interface...

What you have to change for that is:

- send turnInstructionFormat = locus as secribed above

- evaluate the locus extensions containing the turn-instructions the same way you do it when importing with "merge waypoints into track"

What you should also do is look at a bug I encountered when using the "roundabout" hints:
the first instruction after a roundabout that is not a roundabout is announced as the last roundabouts exit count ("third exit") instead of the actual next instruction ("turn left").

Thanks in advance for looking into this,

regards, Arndt