[EN/SK] Magic One Click - All chache and TB send logs.

Condor shared this idea 5 months ago
In Progress

(EN)

Bulk send all offline saved logs.

For each cache, perform these operations automatically.


-Read a list of logs (field note)


- open 1. cache detail

- open tab trackable (inventory)

- load TB

- Mark All Visited

- send log (one cache)


- open 2. cache detail

- open tab trackable (inventory)

- load TB

- Mark All Visited

- send log (second cache)

.

.

.

.

.

- open XX. cache detail

- open tab trackable (inventory)

- load TB

- Mark All Visited

- send log (XX cache)


If the error occurs, stop the process

Notice of execution and error list.

+ It would be good to be able to mark the extent of the designated caches for this operation.

(SK)

Magický jeden klick - Všetky keš a TB odoslať logy.


Hromadné odoslanie všetkých offline uložených logov.

Pri každej keš postupne vykonať tieto operacie automaticky.


-načítať zoznam logov (field note)


- otvoriť 1. keš detail

- otvoriť kartu trackable (inventar)

- načítať TB

- označiť všetky ako navštívený

- odoslať log (prvú keš)


- otvoriť 2. keš detail

- otvoriť kartu trackable (inventar)

- načítať TB

- označiť všetky ako navštívený

- odoslať log (druhú keš)

.

.

.

.

.

- otvoriť XX. keš detail

- otvoriť kartu trackable (inventar)

- načítať TB

- označiť všetky ako navštívený

- odoslať log (XX. keš)


Pri výskyte chyby zastaviť proces

Oznam o vykonaní a zoznam chýb.

+ Bolo by dobré mať možnosť označiť rozsah určených keš pre túto operáciu.

_______________________________________________________________

Related themes / Príbuzné témy:


http://help.locusmap.eu/topic/improve-trackable-handling-within-locus-especially-for-offline-logging


http://help.locusmap.eu/topic/templates-for-quick-log-your-visite


http://help.locusmap.eu/topic/mass-logging


http://help.locusmap.eu/topic/automatically-log-trackables-is-already-implemented


And many more....

Comments (25)

photo
1

One more thing.

If you are dealing with TB, so please synchronize time stamp. The current state is that the cache and TB Locus send with different time.

photo
2

(EN)

I found a forgotten feature again.

Geocaching - Logs manager (field_notes_manager).

Me and 99% of people around me do not use this feature.

The reason is that this feature does not contain TB logging.

That's why it's useless for most people.


So this is exactly the function where TB logging needs to be implemented.


(SK)

Našiel som znova zabudnutú funkciu.

Geocaching - Logs manager (field_notes_manager).

Ja a 99% ľudí okolo mňa túto funkciu nepoužíva.

Dôvod je že táto funkcia neobsahuje logovanie TB.

Preto je pre väčšinu ľudí zbytočná.


Takže toto je presne tá funkcia kde treba implementovať logovanie TB.

photo
2

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!

photo
1

Update to Locus BETA 3.30.4.3


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

Add to FN Manager:

It would be good to insert the link after tapping on the "log" in the Field Note Manager - jump to the log edit window.

photo
1

Version 3.31.3

In my view, it is also an unnecessary action - to download a TB list. The list should be downloaded together after the event - log on online. Excluding the unnecessary step and forgetting the TB list. 99% This load list is always followed by an online log event.

Simple, clear, no complications.


This procedure is intuitive and exactly the same after the action to write a log on the GC page. (web)

photo
photo
1

For orderly functioning, ordering and time stamp synchronization of cache logs and TB logs, Sequence of sending is important!

Reason:

Correct sequence of records on the web page. Also to stop the process for any reason. Ensure continuity from the interruption point. Prevent writing TB log in cache for there is no record.

Sequence of sending:

Log first (oldest time) cache,

Pause on feedback time of unsuccessful sending,

Log first TB from list,

Log second, third ...

Pause,

Log second cache,

Pause,

First TB log from list, Second....

etc....

photo
1

For a better understanding of my suggestions.


My goal (all the way to that) is to come home evening (to the hotel), all day in nature, (3 or 100 or xy cache offline note, even TB) press one button in Locus. Go to the shower. After the shower, look at the display and read the "The process was successful" and sleep. Enjoy the next day full of experiences.

photo
1

For a few days we go for a 15 day trip and 15 days of holiday.

So I really believed that this year finally, I will be able to delete the Locus logging from my travel plan. And thereby save two days. (2 hours per day 20 °°-22 °°, add 50-100 km per day. Save two overnight stays in hotels). And also cancel the limit to max cache per day. (Predicting Loging time)

Unfortunately, it did not work again. So maybe a year...

photo
1

New Beta version just published.

Happy testing before vacation Condor ;)

photo
1

Super! Thanks

I am currently on the MEGA event and the data is very bad here and time is not.

On Monday, I see ☺

photo
1

Is offline logging of travel bugs included in this beta?

photo
1

Nope, did I mentioned it? :)

I "only" enabled mass online logging of trackables over "Logs manager". In case of offline logging, I firstly need to be sure, that this new online system (which on background store data into the database for later re-send in case of problems) works correctly. Then we should start experiment with offline logging. Thanks for understanding.

photo
1

So this mass logging will send in a visit (if that is selected) on all marked logs?

photo
1

Yes, exactly ... (for a found logs) online. Or better, it firstly creates all trackable logs in the database and then try to send them online. In case of the problem, in logs manager at the top will be a visible number of unsend trackable logs with an option to send rest again.

photo
photo
1

Ok, I have installed the beta version with a shared folder with the pro version and will do more testing in the future

photo
1

@Menion

BETA 3.31.4

Nevydržal som a teraz som to skúsil na ostro na 3 keš. (Vyrábať sekvenciu na test a potom ju mazať by bolo zbytočné)

Celá sekvencia (dávka) odišla úplne zlé takže ma čaká v pondelok kopec mazania a opravné logy poslať znova. Čo už.... Táto funkcia stojí za tu prácu ;-)

Zadanie 3 keš a tuším 6 TB

Výsledok

Všetky TB odoslalo 3 krát ale do jednej poslednej keš dávky!

Ostatné nič bez záznamu.

Log found odoslalo len do prvej keš.

Ostatné 2 keš nič bez záznamu.

Vo FNM zostali všetky záznamy v zozname tak ako pred odoslaním.

Oddelené odosielanie najprv TB po načitani je zlé riešenie. Nesprávne.

Očakával som načítanie zoznamu TB a následne výber akcie zalogovať keš. Po tejto akcií má nasledovať odosielanie keš aj TB.

Vyšie je presne popísaný postup a následnosť odosielanych dát celej sekvencie záznamov keš a TB.

Toto je nevyhnutné dodržať z viacerých dôvodov. (Nebudem ich znova písať)

Ešte raz ďakujem že si sa do tejto funkcie pustil.


(Pre nedostatok času a zrozumiteľnosť text v Slovenčine.)

photo
1

Ah damn, sorry, you are correct.

Thanks for a test! Issue will be fixed in next version.

photo
1

OK

Som zabudol ešte. Tiež foto prešlo len jedno! Čo boli viac priložené.

photo
1

Ďalša vec je že pridelenie FP (označenie) bude nutné presunúť na Offline kartu pod log aby to bolo možné spracovať hromadne.

photo
1

Teď moc nerozumím ...- Foto? Bavíme se stále of "Trackable logs"? Asi ne, takže u běžného online logování se ti neodešle více jak jedna fotka?

- Přesunutí FP? Nerozumím proč a kam, doporučuji samostatný nápad, jelikož to nevypadá jako záležitost na 5 minut

Díky

photo
1

Všetky pripomienky v tejto téme sa týkajú výhradne tejto funkcie.

Takže odoslalo v hromadnom logu keš pri ktorej boli 3-4 fotky ale odoslalo len jednu.

Označenie do obľúbených čiže FP je dostupné až na karte pre online log. Pre hromadné spracovanie je toto označenie nutné presunúť na offline kartu. Aby sa dala označiť keš a následne neskôr to bolo spracované pri odosielani cez FNM. Uvedomil som si to až pri pri práci na ostro že toto chýba.

photo
1

I apologize for the contributions in the Slovak language.

I can not write more complicated technical issues in English.

Or for lack of time on the road.

Thank you for understanding.

photo
1

*** 3.31.3.2 BETA ***


I tried...

Trackable can not be separated by a separate feature - sending action. Basic bad design functionality.


The resulting problems:


- to exclude sending a TB record without an existing record cache (log)


- synchronize the time stamp (TB / cache) - the sequence of logs on the GC Web


- Exclude changes in related and other logs


- the ability to stop the process (forced by the user and accidentally for any reason)


- the ability to proceed exactly from the process stop point


Based on these assumptions, this feature will not work correctly.


P.S.

The exact sequence of the sequence is described above.


Suggestion:


The FNM should be constructed exactly like the Online log one cache. Load the TB list, automatic mark the visited action (keep the option to change without action)

Subsequently, the send log button sends (As one cache) the entire sequence in the correct order (see above).


Sequence of sending:

Log first (oldest time) cache,
Pause on feedback time of unsuccessful sending,
Log first TB from list,
Log second, third ...
Pause,
Log second cache,
Pause,
First TB log from list, Second....
etc....
That is all.

photo
1

There are no reliable basics of working with logs geocaching individually.

In this state (currently), it is not possible to consider bulk processing of records.

Thank you for the votes for this functionality.

photo