This object is in archive!
geocache logs are doubled after resfreshing a cache
Solved
got a problem refreshing a cache in order to get the newest logs.
After refreshing the cache, the new logs are availabe ... But it doesn`t grab only new logs. It grabs the last 10 logs (if availabe) and adds them. So sometimes this results in doubled log-entries.
hope, this description is comprehensible ,)
The same problem 
hmm interesting. Are names and dates equals in duplicate logs? I`m trying to simulate it on data from PQ files and later updated by GC4L add-on, but no success
hmm interesting. Are names and dates equals in duplicate logs? I`m trying to simulate it on data from PQ files and later updated by GC4L add-on, but no success
I experienced the same. From time to time I update the geocaches in my home zone via pocketqueries and live api. But when I afterwards update single geocaches by GC4Locus, I get doublets.
The old ones stay in correct order, the doublets with older date are inserted above till the actual date. They doublets are exactly the same content.
I try to do some research if possible.
I experienced the same. From time to time I update the geocaches in my home zone via pocketqueries and live api. But when I afterwards update single geocaches by GC4Locus, I get doublets.
The old ones stay in correct order, the doublets with older date are inserted above till the actual date. They doublets are exactly the same content.
I try to do some research if possible.
hmm problem discovered
there is different time in logs from Pocket Query and logs received in addon by API ... nice groundspeak, nice. So logs cannot be simply marked as same, and that`s why locus add them twice. We`re already working on solution so in next version it will be ok. Thanks for report
hmm problem discovered
there is different time in logs from Pocket Query and logs received in addon by API ... nice groundspeak, nice. So logs cannot be simply marked as same, and that`s why locus add them twice. We`re already working on solution so in next version it will be ok. Thanks for report
Could the solution be to use
groundspeak:log id="247940938"
for conrrelation?
I found values in:
- data from query via live api
- data in gpx file
but not in
- data from addon with download of nearest
- data from addon with livemap
Maybe addon can get the ID?
Greetings, Druki.
Could the solution be to use
groundspeak:log id="247940938"
for conrrelation?
I found values in:
- data from query via live api
- data in gpx file
but not in
- data from addon with download of nearest
- data from addon with livemap
Maybe addon can get the ID?
Greetings, Druki.
yes that`s exactly what we did. Author of add-on added ID to data that send to Locus and Locus will use ID for comparing logs. So both add-on and Locus needs to be updated and then this will works correctly
yes that`s exactly what we did. Author of add-on added ID to data that send to Locus and Locus will use ID for comparing logs. So both add-on and Locus needs to be updated and then this will works correctly
Great! Thank you both for your excellent work!
Great! Thank you both for your excellent work!
Replies have been locked on this page!