Improve Trackable Handling within Locus especially for offline logging.

konsumschaf shared this idea 3 years ago
In Progress

First of all, keep track of the TB inventory in offline mode as well. Keep it in sync every time Locus goes online, like loading PQs, upload logs etc.


While logging a cache ask what happened to the TBs in your inventory, store the last action as default (handy for tracking TBs). Store the TB actions in offline logs as well. Log TBs when performing the bulk log (will not work with uploading field notes just like pictures, I know).


Optional ideas:

If it runs out of sync (for example someone grabbed a TB from you) ask to agree to the change, finish the old logs first or stop the process and ask to fix this online using the groundspeak site and offer a "sync my TBs" option to continue.


Optional (extra tab in the logging dialog) ask what happened to the TB that are listed in a cache. Ask for the code to discover or take them, write a note on the TB page if the TB is missing.

Comments (40)

photo
1

Oživení témy - Go Up

photo
1

Hi guys,

what exactly is a problem with current system? As I see, in top toolbar is visible option to set "Dopped off" or "Visited" to all loaded trackables. So it is only two taps to mark all trackables as visited.

With this system, I'm trying to prevent possible problems when "Visited" should be set as default option, but you won't have trackables with you.

photo
2

Menion

Žiadny problém s tým ak nemáme TB veď sa to týka iba tých ktoré si Locus načíta s aktuálneho inventára. Čiže len tie ktoré má. Nejedná sa o nejaké trvalé nastavenie konkrétneho čísla TB.


Nie sú vo len dva kliky ;-)

Narolovať na kartu TB, načítať, vybrať akciu, označiť všetky ako navštívený, vrátiť sa na inú kartu k pokračovaniu zápisu alebo odoslať log.

Tejto otravy sa chcem mať možnosť zbaviť.


Chcem mať možnosť niekde raz označiť v nastavení "automaticky zapísať TB" a tým pádom systém vždy pri voľbe online zalogovať urobí celú túto činnosť automaticky.


Kartu predmetov TB by som navštívil iba vtedy ak raz za čas niektorý predmet nechávam v keš tak v tom prípade zájdem daný predmet zmeniť na vložiť - drop off. Ak nič nenechávam tak túto kartu ani nepozerám a neriešim a systém to urobí automaticky.


Je to fakt otrava to robiť dookola za každým to isté. Hlavné pri viacerých keš na trase ak hneď posielam log. A ešte horšie ak si celý deň nechám na doma a potom posielam tak túto činnosť za každým dookola.....


Ideál by bol a úplná fantázia sen a total luxus za ktorý by som bol ochotný aj zaplatiť naviac by bolo tlačidlo "Odoslať zalogovať všetko" a nechať mobil položený nech si to postupne všetko urobí a ísť do sprchy alebo sa venovať inej zmysluplnej činnosti.


Áno existuje taká možnosť cez field notes ktorá je ale NEPOUŽITEĽNÁ práve preto že to nezapisuje TB! Takže použiteľná len pre toho kto nemá vlastné, mená žiadne cudzie a proste TB ho nezaujíma. Takých je nás fakt málo.


Takže keď urobiš možnosť automaticky zapísať TB pri online odosielani logu tak budeš už len jeden malý krok od toho ÚŽASNÉHO ZÁZRAČNÉHO tlačidlá odoslať všetko jedným klikom ;-)


Raz sa nám tento sen určité splní!

photo
2

I would like to have the possibility to default certain TBs to "visited" especially for offline logging. This is a standard use case for tracking coins or car travel bugs.

photo
1

I would like this feature too ... because one of my TBs visit every cache.


Maybe the default value could be changed in an inventory?

photo
1

I agree with konsumschaf, this is a most welcome feature both for online and offline logging.

photo
1

Two years has passed and there is still no good offline TB handling. Is Field Notes add on source code available in git or somewhere? I work as a software developer and could perhaps implement offline TB handling in the field notes add on.

photo
4

Hello,

I'm aware of need to update functionality of trackables in Locus Map and it definitely has higher priority. I believe that I'll focus on it during first months of next year so really hope it will be ready to use for next season.

Also thanks for offer. As I know, add-on source code is not public, but even if so, all this functionality is mainly stuck on Locus Map itself and it's needed to be updated in Locus, not just an add-on. Thanks for understanding.

photo
1

And we have a new year here :-)

photo
1

Is there anything new to show us eager customers?

photo
1

OK, so this is collecting votes or something? This, "I believe that I'll focus on it during first months of next year so really hope it will be ready to use for next season.", statement from menion above --- does collecting votes mean it will not be ready this spring?

photo
1

Collecting votes means that I'm not yet working on it so idea still "collecting votes", simple :).

I've already started work on some geocaching stuff, anyway before I rewrite geoaching logging system, I firstly needs to change screen with detail of point (cache). So work in progress ... so this task completed during this Spring? 50/50 ...

photo
photo
1

Hi guys,

I do not like promises that I cannot fulfil. That's why I rather not write "I promise" here on helpdesk. Anyway, I gave myself promise that this year I want to invest more time into Geocaching.

So first bigger update is here. New Beta version is just generating and will be available today.

News to test:

  • completely new screen for logging with an easier one-page interface
  • offline logging of trackables supported
  • re-using state of trackables from the previous logging (all "VISITED" trackables will be added automatically to next log)
  • and of course option to log all offline logs with trackables over "Field note manager" at once

Because there may be a huge number of non-standart situations, it definitely needs a lot of testing in the field. Please report me any unexpected situations that may happen, thanks.

photo
photo
1

New card for logs is nice.

But ... there is more.

Offline storage of TB can become complicated.

1. TB list is stored offline - badly

2. Reload manually? Well ... OK, think about it at change.

3. What action does it take to send TB that is not in the GC-site inventory? Abort process? Ignore error?

4. If I get another TB during the trip? Edit the subsequent logs again.

5. The same on leaving.


This is the first theoretically at first glance.


These 5 issues solve my proposed solution to the link above.


Of course, great thanks for this function! Finally ...


I think the feature will still need repairs and improvements.


+edit

All this activity for each record individually is totally useless and still anticipates problems.


This whole activity is enough to do it only once!

At the moment of online connection and sending a batch of all caches.


Saving time and no problems.


I will add...

I think this "TB-section" for a single cache log can remain for each log posting. It's comfortable and fast. I recommend automatic updating if the connection is. Or remember autoreload (add a check box).


For bulk upload via FN manager, apply my suggested variation. (Ignore the "TB-section" setting for each log)

photo
1

Thanks for a feedback.

  1. there is no list of items stored offline. The system is based on simple fact, that logs of items in the previous cache will be used in new one. So all items that are logged as "visited", will be added automatically to next cache with preselected "visited" log.
  2. ... needs test if useful or not
  3. ... good point. Adding new found item directly during logging should be useful
  4. same as above
  5. if you drop item to cache during logging, it won't appear in next cache

The idea here is to simplify logging flow in the field. When you move from one cache to another, you may simply online/offline logs trackables that you carry with. All is done automatically when you create a log and not separately in some hidden "Logs manager" as you suggest. All on one place in right moment.

photo
1

I do not know if we understand each other well.

Basically, offline TB is unnecessary.

Extreme example: Some TB someone else grab during my trip and offline log? OK...


The only right time to work with TB is when sending online! This is the only faultless work without problem solving.


It does not need to save 50x with uncertain results.

Just save your current status and result once without any problems.


The philosophy of this feature is not intended for one cache.

The intention is to simply send all logs to one click and ensure that the current TB inventory is automatically written to all records.


What is extra fun with offline TB storage with unpredictable results?

Do we understand? :-)

photo
photo
1

Basically, offline TB is unnecessary.

Maybe for you but not for me.

A good example how offline TB handling can work is the offline logging Dialog of GSAK, including TBs. OK, it is "semi-offline" because GSAK uses the api for each cache to determine the current "TB-State".

If Locus could handle this in a similar way I can stop importing the fieldnotes from Locus to GSAK and the do the offline logging stuff in GSAK. Locus would be enough .... but until than GSAK is there as a very good workaround for me.

But Condor is right when he says that there have to be some error handling. I. e. the TB is no longer in the cache when i want to log it, I noted a wrong tb-number, that not exist, ....

c.s.g.

photo
1

You still do not understand ...


Field Note Manager will do this automatically at the moment of sending. It's a GC page or export to a 3rd party app.

At the moment of sending (internet connection) the current TB inventory status is detected. Mark event to visit for each TB.

The Field Note Manager applies this setting for the entire batch.


This is done only once for the whole dose!

Not 100x manually with each cache separately.

photo
photo
1

Condor, it looks like you did not tried latest version :).

You do not have to do it 100x for 100 caches. You do it only once and then it's done automatically for all other caches you will log!

*** New Beta version 3.30.4.3 *** just finishing.

System of Trackables rewrote a lot also since last Beta version. I'll try to describe major points:

  • when creating a new log, "visited" trackables from the previous cache are automatically loaded and set to visited
  • it is possible to "Load inventory" during logging. This automatically upload all trackable logs to server and after all went well, new fresh inventory is loaded
  • logging of trackables is possible in all three "log modes", even offline!
  • logs manager will notify at top of screen in case, there will be any un-send trackable logs
  • any "Online log / Upload draft log" will automatically upload all trackable logs to keep inventory synced
  • any possible problems with upload of trackable logs will be visible as error dialog with an option to retry or simply discard invalid log

Really a lot of changes on background (as I see around 50 hours of work) so it definitely needs a field testing!

photo
1

Menion yes tried!

Condor ● 1 day ago New card for logs is nice.

But ... there is more........

And all I'm saying is about it Beta version 3.30.4.3 3.30.4.2

Do I really write that incomprehensible?


 Condor ● 2 weeks ago

Implementation:

(EN)

In Field note manager, the implementation was easier.

Just add the option to load TB inventory. (similar to TB cards in cache details)

In it, allow each TB to be labeled as being visited. (other options are irrelevant for bulk log - take, leave, etc.)

Use this setting for the entire dose.

This feature saves one to two hours per day!

Of course, it is also of great importance to save battery!

We search for and optimize ON / OFF display, GPS, etc. and you are trying to save minutes. Here are hours!

This is totally simple :-)

Another possibility:

This implementation is also lucrative for adding FieldNotes (paid Pro version).

A good reason to finally buy it ;-)

I've been fighting for this feature for nearly 3 years. I do not give up!

(SK)

Vo funkcii Field note manager by implementacia bola jednoduhšia.

Stačí doplniť možnosť načítať inventár TB. (obdoba karty TB v detaile keš)

V ňom povoliť označovanie každého TB ako navštívený. (ostatné možnosti sú pre hromadný log irelevantné - zobrať, zanechať atď.)

Toto nastavenie použiť pre celú dávku.

Táto funkcia ušetrí denne jednu až dve hodiny!

Samozrejme obrovský význam aj pre úsporu baterie!

Hľadame a optimalizujete ON/OFF displej, GPS atď. a snažíte sa ušetriť minúty. Tu sa ponúkajú hodiny!

Toto je uplne jednoduché :-)

Iná možnosť:

Táto implementácia je lukratývna aj pre add FieldNotes (platenú Pro verziu).

Dobrý dôvod si ju konečne zakúpiť ;-)

Za túto funkciu bojujem (a priatelia) skoro 3 roky. Nevzdávam to!
http://help.locusmap.eu/topic/ensk-magic-one-click-all-chache-and-tb-send-logs#comment-56010

photo
1

Nope, probably all is clear. I just can't perfectly imagine, how it all may work over "Logs manager" and I believe that new system is perfectly clear and useful for "common user".

Anyway give it a try in the field during weekend if possible and then we may ... maybe "skype", it will be faster and easier ;).Wish you nice weekend guys and suggest to backup your fieldNotes database (do full backup in app) because previous and also latest Beta modify database system. I really hope, it won't be necessary to change it.

photo
1

Hi, just a question ...

Is there a way to upload an image to a trackable log in the new beta?


Many trackable owners like to see photos of their TB at the cache location. 🙄

photo
1

Interesting idea, not yet.

photo
photo
1

I want to remind you of the long-standing cache-log time and TB-log time synchronization problem (including bad day - morning to 7-8 AM)


I assume that in the new system (BETA) this problem will be more pronounced.

photo
1

I have been testing offline tb handling on the latest 3.31.0 RC version.


1. Always log offline in settings is turned on

2. I log a visit an cache A

3. I press LOAD on trackables in the log editor, select visit for a TB and finally confirm

4. I realise I have logged wrong cache and open the details for cache A and select Delete for the existing (local) fieldnote.

5. I confirm it is deleted in logs manager. It states "nothing here yet.

6. I log a visit for cache B

7. I press the LOAD button for trackables


And at this point a log is sent to groundspeak logging a visit of the TB on cache A

photo
1

Just to make it clear - I expect all visit logs for trackables on a cache will be deleted when a visit to a cache is deleted.

photo
1

That seems to be the only option now to delete all (even double) TB records. Delete the entire original entry cache log (off line mode)

photo
1

Hi Hovland, Condor,

by press of "Load" button in inventory, Locus perform full sync, so it sends all TB logs to server and download fresh inventory. Agree that not yet send logs for TB should be deleted.

Anyway based on discussion with Condor in forum, in next version I'll enable online logging of trackables only (as was till now). Offline logging is quite complicated to make it work correctly. To be true, I do not give up this idea, just do not want to risk serious troubles in soon coming new version. So let's make online system working without any issues in first step.

photo
1

Sorry to hear that. Anyway, which forum?

photo
1

Here: http://forum.locusmap.eu/index.php?topic=6071.msg51407#msg51407 ... general discussion about current Beta version.

photo
1

I am sorry to see that offline logging of TB's is removed from the latest beta version. I have been waiting for this functionality since I moved from Maaloo Geocaching on Windows Phone to Locus Map Pro. When this was announced last year that it will arrive before this "season", I was looking forward to this. But it has taken it's time and now it feels like something has been removed from me.


Locus Map Pro is still not usable for me without some work afterwards with my PC and GSAK. I really hope offline logging of TB's could be included in the near future and I can start using my phone and my phone only for all logging activities.

photo
1

We all are working to improve TB work in Locus.


It is necessary to realize that this is a very specific activity.

There are many possible variations of the situation. It is necessary to design a model that will work in every situation.

In my opinion (and my design), it is expedient to resolve mainly recurring activities (typically - the inventory being visited). It most saves work, time and battery. Of course, it will also contribute to the ease of use.


Specific activities that occur occasionally (insert, grab, leave) are difficult to keep for later use (offline) due to the lack of reality to determine the actual real status. These are a great assumption of errors. It would be necessary to address follow-up actions for these errors. This solution brings a problematic situation. For successful resolution, it is necessary to interfere with multiple saved records. I could describe many different situations that may occur. There's a lot ...

These activities are rare and complex. That is why I would keep them in the same condition as before.

photo
photo
1

Expected Problems...

photo
2

Jana, I use Google translate on what ypu wrote and it works well

photo
2

This weekend verified work in the log cache and default setting TB at visited is a great contribution to faster cache log!

Well done! Thanks ☺

photo
1

Indeed, the new interface for logging is much more pleasant to use. I let the people concerned by the discussion on the complex TB log offline, to complete the reflection and possibly improve the functioning.

However, one could add a very simple functionality in offline mode. It would be nice to be able to keep in the TB offline menu the Tracking Number to use and the action to record when online later. The log manager could indicate which log has a TB entry to edit before sending the log. In this intermediate solution there is no synchronization with the API. Simply a memorization of the Tracking Number and the action to be able to carry out the operations later as it is the case for a registration when we are online. Naturally, this solution does not allow a complex TB management like replacing a TB picked up offline in another cache without having previously registered the previous TB log online but my solution would solve the vast majority of situations encountered. It's an idea, you can do whatever you want with it.

photo
1

I have the last couple of days tried the app Looking4cache" for iphone. And this app have some features I wish Locus could pick up.


1. There is no difference in logging online or offline. All features is similar. In the create log section you can mark TB as visited individually and they are store offline until you decide to send them in. The difference regarding Locus is that you don't have to decide beforehand if you want to log offline or online. In Locus you have to select different menues and then write your log. In Looking4cache, you select "Create Log" and if you find out that you want to continue writing later, you can select "store offline" and press save. You don't have to make the desicion before you start writing, but can do so after you have started. The "Store offline" checkbox is persistent so it is remembered on the next log you write.


2. All TB's in your possession can be individually marked as visited, no action or dropped. Looking4cache does not remember the last action, but you can in settings set what action should be default for each of the travel bugs. The advantage with this approach is that you know what state the travel bug is in when creating a new log. In Locus Map you have to browse the list of travel bugs and make sure everything is as wanted because you have probably changed something on the previous log.


3. When sending in offline logs, Looking4cache clearly show what the status is. It has three visible counters and if any errors are happening it is shown. And it has a section where you can resend everything that failed.


197925425c9f5c558ad07b21b1bee1d8


a970a0fe15af1a0cd1351a32ecd50d27

photo
1

Is there any progress at all here?


And no comments on how other apps are doing this as explained in my previous post?