entering coords for a new geocache waypoint always gives me the red ! signs as shown in the screenshot. Removing the space behind the ° sign helps. Could someone please fix the underlying regex, such that ° sign becomes optional as in previous versions. Same as ' sign at the end. This bug drives me nuts...
yes, I (and some friends) can reproduce this problem. What we do is: - on the map click on a geocache icon and choose guide to - now the line with distance and bearing appears - since the latest version of Locus also a new bar showing D/T rating etc. appears - on the new bar (or on the geocache icon on the map) choose "log your visit" - save a (find) log to the fliednotes (offline)
Then the logs gets written to the database and Locus restarts, always.
sorry to bother you again with GPX stuff but there is still a bug in Locus leading to data loss.
I have a local geocache database and add a waypoint to a geocache. As prefix for this waypoint I choose "L0" because I know that Locus starts creating waypoints with prefixes from "L0" onwards. I export a GPX file from the database and import it to Locus. Everything is fine. Locus shows the geocache with its attached waypoint. I go outdoors and add multiple new waypoints while completing the geocache. Back at home I want to store the waypoints locally to have a full documentation in my database. I export a GPX file from Locus and import it in the database. And now here comes the bug... The very first waypoint I created locally is gone...
I had a look at the GPX file. It contains two waypoints with the prefix "L0" and therefore the same name. The one I created locally and the first waypoint Locus created. Locus does not make sure that the waypoint prefixes / names are unique what they should be.
not logs but waypoints. I import a GPX file. Then I import it again and when the window pops up I choose overwrite existing points. Afterwards I have the same number of geocaches in the database but all waypoints underneath are listed twice. Btw.: A third time doesn't give me three times as many waypoints...
thanks for the answer. My intention was to have this behavior for "traditional" mysteries only. But not for caches with more than one stage. I think I'll get used to it.
Even if off topic in this thread I wanted to ask why the duplicate check for waypoints does not get applied to imported waypoints within a geocache. Is this a bug or a feature? I just noticed that all geocache related waypoints are shown twice after importing a GPX file a second time.
I have a question and couldn't find an answer using the forum search...
I know there is the possibility to mark a geocache as "computed" so it shows up on the map with a red star added to the icon. But is there a possibility to mark multiple geocaches at once? Especially when working with an offline database and exporting geocaches via .gpx file this would be helpful. Or is there even an "undocumented" tag I could use in my .gpx files to mark geocaches directly while importing them into Locus?
When uploading fieldnotes Locus uploads so fast that the API rejects new requests after around 30 fieldnotes for a certain time frame. Instead of waiting Locus resumes the upload with the next fieldnote, marking the previous (failed) fieldnote upload as being successful. If deletion indicator is set the fieldnote gets deleted from local storage resulting in data loss since the fieldnote was not transferred to the website.
Is there any chance of adjusting the upload speed or detecting the API reject?