Geocaching Australia

Posted: **21 November 10 8:54 pm**

You use the GCA tokens.
http://wiki.geocaching.com.au/wiki/Logg ... log_tokens

Posted: **21 November 10 9:10 pm**

Posted: **23 November 10 6:29 pm**

I just discovered Caches per sqkm/population, however I'm not sure that it's calculating quite correctly.
http://geocaching.com.au/stats/graphs/a ... population

(In addition, there is a typo, that the table heading says 'Cachers'.)

State: ACT
Caches per 1,000sqkm: 677.00
Caches per 1,000 head of population: 0.40

Based on 1354 active caches from http://geocaching.com.au/stats/graphs/a ... s_by_state,
that gives the ACT an area of 2000sqkm (which is roughly correct), however, 0.4 caches per 1000 people would give a population of 3.385 million which is obviously incorrect.

I note also that the same data is given whether GCA Only or All Sources is selected (or indeed what other options are selected at all).

Cheers

Mark

Posted: **23 November 10 7:31 pm**

3,402,000 actually.
Fat finger syndrome.
Strangely no-one has noticed this before

I think I've fixed it.
Oh and made the source selector work.

I only cared about Australia, so the other selectors don't do anything but I'm lazy

Posted: **23 November 10 7:36 pm**

caughtatwork wrote:3,402,000 actually.
Fat finger syndrome.
Strangely no-one has noticed this before
I think I've fixed it.
Oh and made the source selector work.

I only cared about Australia, so the other selectors don't do anything but I'm lazy

Awesome speed as always.

Thanks!

Posted: **25 November 10 1:44 pm**

I use <http://forum.geocaching.com.au/syndication.php?> to feed my RSS reader. Every so often - most recently at some time between 09:16 and 09:51 Perth time - the feed gets errors and posts look like this:

Code: Select all

div class=bb-wrappertable border=0 cellspacing=0 cellpadding=0 class=bb-table width=100%trtd width=4 height=4 class=bb-left-topimg src=images/spacer.gif width=4 height=4 border=0 alt= //tdtd width=100% class=bb-topimg src=images/spacer.gif width=4 height=4 border=0 alt= //tdtd width=4 height=4 class=bb-right-topimg src=images/spacer.gif width=4 height=4 border=0 alt= //td/trtrtd class=bb-leftimg src=images/spacer.gif width=3 height=4 border=0 alt= //tdtd class=bb-content bb-quote width=100%div class=quotetitlebubbles_baby123 wrote:/divdiv class=quotecontentARRRRRRRRRRRGH.br /br /br /br /br /br /br /br /i just broke one of my gnomes. No, seriously. The arm just snapped off.br /br /br /Photos and midnight virgils to come wheni'mnotrunninglatetoworkarrgh!/div/tdtd class=bb-rightimg src=images/spacer.gif width=3 height=4 border=0 alt= //td/trtrtd width=4 height=4 class=bb-left-botimg src=images/spacer.gif width=4 height=4 border=0 alt= //tdtd width=100% class=bb-botimg src=images/spacer.gif width=4 height=4 border=0 alt= //tdtd width=4 height=4 class=bb-right-botimg src=images/spacer.gif width=4 height=4 border=0 alt= //td/tr/table/divbr /br /We had a gnomish incident last weekend. Went into the shed to get the lawnmower out and found one on the floor and the other looking down. Just like he'd been pushed img src=http://forum.geocaching.com.au/images/smilies/icon_eek.gif alt=:shock: title=Shocked / br /br /The gnome was foam filled and while his arm broke off where the foam hadn't filled, the rest of the gnome was cracked but still held together with the foam. We decided to retire him and bought a replacement, but in the field, with a bit of tape to cover the sharp spots, he would have been fine.br /br /Now we keep them separate to avoid another gnomish incident.

I'm guessing the <> are being hidden by disgruntled faeries

When this happens, all the broken posts show up as undetectable duplicates of already seen posts - and they are hard to read if they are new

It would be handy if I saw more than the most recent 10 posts in the feed as well, sometimes a burst of posts in less time than the feed check interval means some get missed ...

Thanks for all your efforts.

Posted: **25 November 10 6:39 pm**

NFI

That code is from the HTML of the page, not the data in the database so I have no idea how it got out there.
I'll look more, but that one is weird.
Please continue to report it as we may be able to spot a pattern if we get enough examples.

Add count=nn (where nn is a reasonable number please) to get more than the default 10.

Posted: **27 November 10 4:20 am**

Looking back recently, I see the same stripped <> issue at the following times:

Code: Select all

Good messages upto  |--| Last broken message |--| Message rcvd okay again after
2010-11-17 09:19:28 |--|            09:35:09 |--| 09:38:18
2010-11-20 16:08:08 |--|            18:11:53 |--| 18:48:50
2010-11-21 18:16:40 |--|            18:22:24 |--| 18:26:17
2010-11-23 05:51:42 |--|            07:02:02 |--| 07:43:00
2010-11-25 09:16:50 |--|            09:51:55 |--| 10:43:04

ie. message "A" was posted on the forum at 09:19:28, I polled shortly after that (certainly before 09:35:09) and got message "A" fine. At least one poll sometime between 09:35:09 and 09:38:18 got at least one broken message, then a poll after 09:38:18 got unbroken messages again.

I think the RSS reader was checking about every 20 minutes.

Might correlate to server load and a script timing out?

Thanks for the count= tip.

Cheers.

Posted: **02 December 10 7:00 am**

RE: GC Caches by Hidden Date Range (500 caches per query) for WA.

Noted that WA hasn't been updated since 18 July 2010?? while the rest of some other states has updated to Sept, Oct, Sept variously.

Posted: **02 December 10 7:24 am**

That's not the last updated time, just the date you need to get the most from your query.

Posted: **07 December 10 1:49 am**

CraigRat wrote:That's not the last updated time, just the date you need to get the most from your query.

http://geocaching.com.au/stats/range/

Re: WA Range:

17 July 2010 to 27 Nov 2010 456 caches
28 Nov 2010 76 caches

It was previously stated 17 July 2010 - without update from that said date and now it has been updated to 28 Nov 2010. That's what I am trying to mention about it.

Thanks for that.

Posted: **07 December 10 3:45 pm**

http://geocaching.com.au/dashboard/au/wa/
Dashboard for Western Australia

Scroll down to "Awaiting First Find"

There are only new caches namely "The Albany 100: 1 to 65 (placed 28 Nov 2010) were shown up and there are missing caches: 66 to 100 (placed 28 Nov 2010) were not published in the list in "Awaiting First Find" as yet.

Is there any problem with them?

Thanks in advance

Posted: **07 December 10 4:08 pm**

The WA feed needs some tweaking, it should come right over the next week.

Posted: **09 December 10 9:43 am**

Hmmm, did the recent RSS dupe log fix break something else? I receive two duplicate logs on two separate moveable caches today. They were both "Found" logs. One had the new coordinates (i.e. should've been a Moved log), the other was a regular Found log.

See here:
http://geocaching.com.au/cache/ga2646
http://geocaching.com.au/cache/ga2644

Has this happened to anyone else?

Posted: **09 December 10 10:35 am**

They are duplicate logs in the system, someone's got a bit Click happy

RSS fix had nothing to do with the logging subsystem

Geocaching Australia

Report GCA Site issues here [closed]

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here

Re: Report GCA Site issues here