Messages

Noch ein Tipp, den ich gerade heute in einem anderen Post gelesen habe: Bei der Anzeige eines Standardwegpunktes das Symbol für die Geocachinformationen lange gedrückt halten!

Hallo,
leider kann ich nicht mit einer konkreten Lösung aufwarten.
Aber ich habe etwas recherchiert.
Mein Kollege kennt die API von GPSies leider auch nicht, er nutzt sie auch nur von seinem Android-Handy (Maverick und Endomondo) und es funktionieren Umlaute.
Die GPX-Datei eines Tracks aus Locus enthält korrekt in UTF-8 codierte Zeichen, so wie es im XML angegeben ist: <?xml version="1.0" encoding="utf-8" standalone="yes"?>
...
<name><![CDATA[äöüßÄÖÜ_name]]></name>

Ich habe mich extra bei GPSies angemeldet und mal ein wenig probiert.
Ein GPX-File mit Umlauten bekomme ich nicht korrekt von Locus in GPSies (über den Export).
Ein GPX-File mit Umlauten bekomme ich korrekt von GPSies zu Locus (als Datei und mit Import der Datei Lokal in Locus). Gleiches File mit Umlauten wird beim Export zu GPSies wieder dort nicht korrekt angezeigt.

Es könnte sein, dass Locus an der API zu GPSies nicht korrekt codiert oder bei der Übertragung eine andere Codierung angibt als verwendet wird (oder es könnten im Envelope/Headerdaten der REST-Übertragung andere Codierungen/Codierungsangaben stehen).

Meine Einschätzung der Lage in englisch (@menion):
There is a problem with exporting data (tracks) to GPSies with german special characters like äöüß.
It seems that when giving the data to the API of GPSies, the coding of the characters is not propper UTF-8 at some point.
It could be Locus or it could be GPSies.
Could you verify this behavior and maybe get into contact with the developer of GPSies (Klaus Bechtold).
Thanks in advance and greetings,
druki

Perfect! Thanks, menion!

Hallo, ich kann das auch reproduzieren: Locus 2.1.0 auf Motorola Defy+.
Interessant ist, das das Ausblenden beim Beenden "verloren geht". Und zwar
- beim Verbergen aus der Karte als auch beim Haken entfernen in der Trackliste
- spielt die Art des Tracks (recorded Track oder manuell erstellte Route) keine Rolle
- unabhängig von der Anzahl der vorher angezeigten Tracks (1,2,viele)

Mein persönlicher Workarround: Einen "unwichtigen" Track zum anzeigen auswählen.

Das ist sicher ein Codierungsfehler bei der Übertragung. Es sollte herausgefunden werden, welche Zeichencodierung gesendet und welche erwartet wird. Evtl. könnte der Fehler mit einem REST Client an die Schnittstelle von GPSIES reproduziert werden. Ich frage mal einen Geschäftskollegen, der auch GPSIES nutzt und sich mit Codierungen auskennt.

Hello Menion,
first about the new feature: Sorry I forgot this late at night. I like the chart with display of selected x-axis and the colored points! Thank you!

Setting altitudes offline:
I made similar expirience...
After recording the track on my way home, which was more accurate than the last days (improvement in release?!), I selected to set the altitude offline for this track. Locus crashed (just disappeared after standard crashpopup). I was able to try it a second time with offline altitude and it crashed again. Next I tried with setting altitude online: Worked. And after this, even setting offline altitude worked again.
And also a new track works with setting altitude offline now (so problem not reproduceable any more).

Time of routepoints:
The manual edited routepoint in troute has its time from last edit. I edit by selecting the routepoint in the route and click on the tools-symbol, choose "new" at the coordinates and select it from map. I can reproduce it that way. Even after setting altitudes, this times stay as they are. So in the chart I see then an altitude curve (for this one point).
My workarround for the "time-equalizing" is to set times manually (second by second) in the gpx file and reimport in Locus again. Then I get my fine altitude-chart of the created route. I'm glad I'm not having much routes to create ;-)

Greetings, Druki.

Thank you for the new release!
Yes, "Market" sounded more proffessional...

Averaging works again, now the planning of my first (owned) multi-geocache can go on with perfect measurements.

I tested creating a route and missed the display of the altitude-curve. Is it intended to set all routing points to the same time at saving? If I edit single points afterwards, they keep their editing time.
?

Thank you Menion!

About 2b: With a straight testroute manually crated from east to west I found out, that the order of the pounts is correct, but the first routepoint has a wrong time. Seems that it's set to the time of saving the route.
Maybe this was the thing you fixed (because this could have been the cause of negative duration of the route?).

Greetings,
Druki.

Hello, while playing arround with Locus, I found some issues that seem to be some kind of strange to me:

1.
I record a track and during record I set Trackpoints. After saving and viewing this track as a chart, in the bottom axis the information for time and trackpointname overlap. Is it possible to separate these information?

2.
a) If i manually create a route by setting routingpoints on the map, the routes sumary time is negative. b) If saved as GPX, the order of the routingpoints in the file seems to be the coordinates. I would expect that the time is the order.

3.
The feature of the external app for averaging waypoints is not accessible from Locus any more (it worked some time ago in an older release). If started external, the avaraging app works and can give the coordinates to Locus successfully.

Hiho,
Wegpunkte zu existierenden Geocaches kann man folgendermaßen anlegen: In der Ansicht für den Wegpunkt die GC Details aufrufen (Symbol unten links) und dann dort die zusätzlichen Wegpunkte aufrufen (das Symbol unten "Punkt Pfeil Pfeil Punkt" ). In der Ansicht für die Zusatzwegpunkte kann wieder unten mit "Hinzufügen" einen neuen zusätzlichen Wegpunkt anlegen. Richtiges Symbol nicht vergessen, denn standardmäßig ist das "Final" Symbol ausgewählt.
Die Koordinaten kannst Du über den Button "Neu" bestimmen über die Auswahl mehrerer Quellen. Der Vorteil, wenn Du statt "Neu" dann "Bearbeiten" wählst ist, dass Du das einzugebende Koordinatenformat wählen kannst.

Ein schnelles Anlegen von Zusatzwegpunkten aus der Kartenansicht heraus habe ich leider noch nicht gefunden (wenn es das tatsächlich noch nicht gibt, neues Feature über https://getsatisfaction.com/locus/ anfragen?!).
Locus müsste dann nur wissen, zu welchen Cache es Zusatzwegpunkte anlegen soll. Bei der App GeOrg fand ich das elegant gelöst über die Auswahl von Geocaches in der Nähe (nach Entfernung sortiert).

Hallo,
verschieben geht schon indirekt: Vorhandenen Trackpunkt in der Karte wählen und bearbeiten (bei den Koordinaten auf NEU klicken). Die neuen Koordinaten "aus Karte holen" und gewünschte Stelle in der Kartenansicht wählen und bestätigen.

Neue Trackpunkte manuell setzen geht wohl (noch) nicht.

Hi tommi62, thanks for the link.
There they discuss about altitude correction and believe they get this information from NMEA (although it´s not proved that the altitude information is comming from NMEA). IMHO, in some devices, the altitude is given from internal GPS, but not by NMEA.
I played arround with internal GPS (with 3 different Apps and Locus) and bluetooth GPS hardware (Jentro BT-8), even with a bluetooth GPS-App:
With external GPS, I can record NMEA, with internal GPS of Defy+: no way
:-(

Now with the Version 2.0.2 a lot of my questions are answered and wishes are fulfilled - thank you!

I have one little bug and a wish left:

The new feature of altitude information by SRTM is great and also seems to work for aditional waypoints of geocaches. But the information is not saved permanently (if I look at the waypoint later, the altitude information is gone). Is there a chance to fix it?

The wish is to be able to update the geocache-information within the geocache detail view by the geocaching addon or (alternative) be able to go back to general waypoint view of the geocache with one click (where I call the geocaching addon there).
My workarround now is to jump from geocache detail view back to the map, search the waypoint and recall it again to update with the geocaching addon.

Hello,
there seem to be several devices (mobile phones) that doesn't support NMEA output from their built in GPS. Often the hardware could handle it, but the software (ROM) of the phone manufacturer doesn't use it.
Unfortunately my Motorola Defy+ (MB625) is one of this.
After trying to get NMEA data with other apps ("NMEA Recorder" and "Simple NMEA Monitor" - both as free available), I found this in my research:

http://community.developer.motorola.com ... td-p/14374

http://www.kowoma.de/gpsforum/viewtopic.php?f=3&t=3138
(at the end some interesting informations about the GPS chip in the Defy)

So sadly I have no possibility with my internal GPS yet. Maybe I give it a try with my bluetooth GPS receivers. Or I pray for motorola to activate this in an update.

Hello, thank you for explaining, now I see more preciesly.
Here my comments about the suggestions:

a)
Scrolling (by swiping in the window title) could change the display views like with the tabs. In the window itself, it would "disturb" the scrolling and zooming features in the chart view (which I love the way it is). Or is there an other way to have both functionalities?

b)
IMHO displaying aditional information is a good idea, but maybe the overview could become messy if the fields carry very long information (only show one line? scrollable?). And how can I figure out that html code should be displayed? With the complete code or interpreted?

c)
also a good idea for the suggested fields. Other fields are calculated from the trackpoints and shouldn't be editable.
As I see in the edit area, there are several other information for a track (displaying settings etc.). This edit window (with all editable fields) could be integrated in the track information area. The amount of clicks (2) to get there from the map would be the same.

d)
Copying is a good idea. As I understand, you would paste in an other aplication. Editing/Pasting in fields of calculated values should IMHO not be done in Locus.

We have Maps in Locus and can see tracks with trackpoints there (and select trackpoints for editing). I think this should stay as it is, as editing of trackpoints in an other view doesn't make sense to me.

Let's see what other users and the master think about it.