Pleu

A suggestion regarding the language issue: If I could add an English version of my text it might be easier to use for tourists. Both with just logging the AL in general and to use this new feature. I'm thinking a tab to click to get the English text instead of the original text. I'm thinking as an "add by the CO", not automatically generated text.

Great feature, glad to see some accessibility work on the AL-app!

I'm glad that you're consistent with misinterpreting my words across all forums and languages but I'll be leaving this discussion here. Cheers!

If people bother to make a separate OAR/RAR-log they usually bother to include the reason of the log. It worked perfectly fine for years before the automatic versions were introduced.

These were two separate logs for many, many years before the "all in one"-solution that you like was introduced. As a CO I hate the automatic NM-log in the players language so much because it's a standard log that tells me nothing about the issue and half the time it's in a language I don't even understand since some of my caches are in tourist-y locations. Forcing the player to write a OAR-log that actually makes sense is a big improvement. Specially since one of the standard options was often read by newbies as "this makes sense to click anytime I can't find a cache" which actually caused a lot of extra work for COs for no reason.

Only relevant as long as X and/or Y is calculated by counting something in the field. If X and Y are just numbers in the description it's not a multi-cache, it's a mystery.

Since the "report a bug"-topic says it's preferred to bump a old thread with the bug report instead of making a new one I'll just bump this 2.5 years old topic that the trackable log is still always set to yesterday. It's getting frustrating having to edit these logs to get the correct date and as a user it's hard to understand why this is such a hard fix it hasn't been solved in the multiple years since it was first reported. There's also a report about this here (which is almost 3 years old), I dunno maybe the threads should be merged:

Jag vet inte om det här är aktuellt längre men mitt första tips är att fråga på facebook istället då det är där den mesta av aktiviteten finns när det gäller det svenska geocachingcommunityt: https://www.facebook.com/groups/9967440491 Generellt tycker jag att ni ska fundera över om fysiska geocacher verkligen är det bästa för ert projekt. Vem kommer att underhålla dom? Har ni någon lokal kontakt i Kosovo som kan sköta det? Annars kommer ni att få problem redan från början. Min erfarenhet är att den här typen av projekt blir mer lyckade om man involverar någon erfaren utläggare så det är mitt nästa tips.

I have not yet recieved an email like this, but some of my friends have. I have a concern about the "further reports may result in additional administrative action being taken with your adventure", it has already been mentioned here in the thread that this new feature is sometimes used even when the actual issue is that the player just can't find the answer. All ALs aren't easy, some of them have intentionally been created to be harder to solve. The fact that one can't log a "DNF" on a AL means some people will use this feature in such cases. Combined with the mention that Geocaching HQ might take action on the AL if it has to many reports there is a risk here that AL-owners will need to "dumb down" their ALs to be allowed to keep them. For me the USP of geocaching is the variety. Not every cache is for every cacher. It's the variety that makes it good. This should include ALs, there should be allowed to be variety in ALs. Not every AL will be D1 and it shouldn't be either. I really appreciate the ability to report issues with AL-Locations, I just fear that people will use it for more than it's intended for and the multiple examples of this in this thread seems to confirm this.

You're not allowed to name a cache "Biltema-cache" in Sweden since Biltema is the name of a store so that would be against the commercial guidelines. Generally they ar marked as a bit of higher T (3+) and have the combination "special tool required" and "no tree climbing required", but there are no guranteed search to find them all. They are referred to as "fiskecacher" or "spöcacher" locally, but it's not guranteed to be included in the name or description.

Same bug in the Swedish version too!

That should not be presumed because it will depend on your area. If you're in the US, sure probably. If you're in Canada or the UK it's unlikely to be the same borders. Generally the answer for if they will match will be "it depends". For some countries, like Sweden were I live, we don't seem to be getting any county-lines at all on the Geocaching.com map, even though they are fetched from OSM at Project-GC.

I came here to report the same issue.

There are different builders with different levels of "user-friendliness", but I would look into intercaching as geoawareUSA9 suggested. It's a more "mobile friendly experience" and by that it's automatically easier to understand, even without programming skills. You've placed caches at multiple spots I've had plans for so it would be fitting if you would place the first intercache in Uppsala. I've just been thinking about it since 2017 and haven't got around to it yet.

Jag använder inte den appen själv så jag har ingen koll på den. Om du har ett facebook-konto så rekommenderar jag att ställa din fråga i gruppen Geocaching Sverige på Facebook, där finns det många som har bra koll på den appen.

Jag tror inte att det finns någon site med sån funktion längre.

The privacy controls do not have any affect on challenge checkers. Project-GC uses the API, it's not looking at your profile. Opting out of the API means you don't get to run checkers and CO can't run your name either, how you solve the issue with challenges is between you and the CO of the challenge (and HQ if you can't agree on a solution for it). My guess would be that the overlap between people wanting to log challenges and people opting out of the API so they can't use challenge checkers is pretty small.

Vart exakt är det du ser olika information? Generellt när jag säger "i loggboken" så menar jag i den fysiska pappers-loggboken och där är det ju ingenting som kommer att uppdateras automatiskt. Men det ska inte vara någon skillnad på cacher du loggade idag eller cacher du loggade för fem år sedan när det kommer till vad för information du kan se om andra spelare som har loggat cacherna.

Just to clarify: I just answered @ChriBlis question about if the field was manually or automatically populated, it was not intended as a an answer to your initial problem.

"Yes and no". For caches in some countries, like the US, the region is automatically deduced from the coordinates when the cachepage is created. It can still be changed manually and as Bl4ckH4wkGER mentions the region isn't automatically changed if the coordinates are updated. In Sweden the region is always set manually by the user, there's no automatic deduction based on coordinates.

Funny, I thought from the title that this was going to be about making the calculation more correct, not less correct. The calculation should be (Number of FPs)/(Number of Premium Member logs + number of Basic Members that left an FP). Currently a cache can have 100% FP even tho a number of premium members did not leave FPs. Why? Because if somebody leaves an FP and then stops being a PM their FP is counted but their PM status is not counted, so +1 above the / and +0 under the /. On the other hand I guess the current calculation in some way evens out the issue you're having were some PMs just don't leave FPs at all.

Came here to report this, also seeing this on recently published caches.

I've also noticed this bug! I picked up a trackable the 31 october and it got logged on 30 october. It can't be timezone related IMHO because this was about 18.00 in UTC+1, the time zone would have to be "UTC-17" fot this to be a timezone issue and there is no such thing.

Cachly should be allowed, they use the official API so they are "good guys". I think it's only unathourized apps that are not allowed. You did some good testing, I hope HQ can check on this because there seem to be a bug in how the drafts are handled.

I found this thread because a similar issue was raised in a swedish facebookgroup. The best idea there is that this might be related to the standard format of the iphone's camera that changed a while back and that the official app might be handling this format differently (maybe something changed in a update of the app?). I don't have a iPhone so I can't test this to see if it helps, but here are some article about the thing with suggestions for how to change the format in settings or use different ways to convert the picture to a format that should work in the app: https://www.techgeekandmore.com/change-default-image-format-iphone-ipad/ and https://www.iosappweekly.com/change-photo-format-on-iphone-jpeg-png-tiff-heic/