Geocaching Australia

It seems to work now. And it's relatively quick as well. This idea first came up almost 10 years ago and was dismissed due to been too slow, what changed to make it feasible now?

The request: Add ability for "NOT=Tag" in My Query function so as to ignore things like cache race entrants. The result: You may now select the Excludes Geocache With Tags on your MyQuery to exclude all geocaches that have one or more of the supplied tags. Note that using wildcard searches is slow ...

I've noticed this issue to. It seems rather difficult to reproduce consistently. Use the map (and move it around) for long enough and the false yellow stars seem to appear somewhere eventually.

I noticed this about a week ago to. But then an hour or so later it was all working again.

Here's the ones that I have from your missing list: http://laighside.com/geotalk/

Hope that helps complete the collection.

I have 65 though to 90 and happy to share them.

If anyone has the others, I'd like to get the rest of them.

There was a proposal a year or two ago to host them on the GCA website but nothing ever came of it.

This appears to be a pretty minor bug but for some reason we have to spend 3 days arguing before anything is done about it. First you blame Groundspeak with no evidence. Then you insist there is no bug and everything is fine even though several caches clearly don't have names. (I acknowledge the bug...

Ok then, if you insist, let's have caches without names. It's not useful to anyone but at least it meets some ill-defined specs from years ago.

It's a bit all over the place but this seemed to be the conclusion in the thread from 2016: Long term: I think we should update to UTF8MB4 but that requires the new server and some time. Short term: Strip the emoji on input and avoid the garbage from GC. Neither of these things seemed to have actual...

Our instance of MySQL/Mariah uses utf8 , however there is a utf8mb4 format that extends, however I don't know what the ramifications are if we change our encoding Ah, that makes sense. Looks like MySQL only started supporting 4 byte UTF-8 in 2010. I guess we should probably think about upgrading at...

Are we using an old version of UTF-8 or something?

Every reference I look at says UTF-8 can go up to 4 bytes per character. Which suggests that the GPX file meets the standard.

Are you sure? The first character in the example above appears to be a valid UTF-8 character to me. The 4 bytes in the GPX file are: f0 9f a6 84 Which is exactly how U+1F984 is supposed to be encoded (according to https://en.wikipedia.org/wiki/UTF-8) Can you explain which part of that you think does...

Caches with names containing non-ASCII characters still seem to be causing us problems. For example, see https://geocaching.com.au/cache/gc7xan2 The name starts with a non-ASCII character but for some reason, the rest of the name is missing to. The individual GPX file from Groundspeak shows the enti...

The dates for most GC events are out by one day on GCA. Not exactly sure why this is, but possibly because Groundspeak are now including the event start time in the GPX file (in the <time> tag) whereas previously this was set to 00:00:00 It is caused by GC failing to fix some issues when they intro...

On a similar vein when I do imports to help keep the db up to date, I often see messages saying Updated date of log or similar. Whether this is because they have previously been imported and since amended by the finder on the other site I haven't been able to work out. This caused me some confusion...