jeremyp

Actually I'm maintaining *all* the scripts. The reason the custom stuff isn't available yet is because the cgi will need some minor changes to make it work in the new location and I just haven't got around to doing it yet. Unfortunately, Mark is away for the weekend so they probably will not get posted to his web site until afterwards. However, if there is demand I'll try and get them on my own web site *temporarily* until the official version is up. BTW: if anybody has any suggestions for new features, you can mail them to me or the address on the UK stats page. BTBTW: A big thanks to Rob and Lisa for all the work they have done on this. I'm sure everybody agrees that their page is one of the most useful private geocaching pages there is, especially the bits I haven't got working yet Thank you for your patience, normal service will be resumed shortly ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

The trig points were set using the OSGB36 datum. I don't know what the accuracy is, but it is probably higher than the accuracy of a handheld GPS. So as long as you set your GPS to OSGB36, then you can use them. Note that the OSGB36 datum is designed for the UK and so it is fixed wrt the British landmass. WGS84 - the datum used by the GPS satellites - is designed so that the average movement of the whole Earth's crust wrt it is 0. This means that the UK is actually moving slowly North East although the rate of movement is insignificant wrt the accuracy of a handheld GPS unit. Anyway, in the end the trig points will have moved far enough so that the conversion from WGS84 to OSGB36 is wrong, but I assume that firmware upgrades and new GPS units will adjust the conversion. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

The OS has (or had) two sets of benchmarks: the trig points used for triangulating horizontal position and another set of benchmarks for determining height above sea level. The trig points are usually situated on the tops of hills and so many of them will be in good locations (if you like locations with a good view). Several existing caches have trig points near them. They could be used to make virtual caches with quite easily. Some would be good and some not so good, but you can say that about normal caches anyway. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

1. LE/Jo'G 2. DoB first game 3. First goal scored - with L/JoG it could take weeks anyway 4. Caches created before kickoff. Only other requirement - the "ball" must fit in it. 5. KISS ----------------- el10t _mobilis in mobili_ ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

It's Dan and Pid and one of their friends looking for a cache. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

I volunteer to maintain the Perl scripts for you. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

By "techie" I assumed you meant "person who makes his living in a computer related job". I thought of other splits like|"boys v girls" which is a non-starter - well my impression is that most forum posters are boys. Also, nerds against non-nerds but there again.... Well to get the thing off the ground, we should go for something simple like birthdays or if you want to introduce some rivalry, look at the date everybody logged their first cache then find the median and put everybody who logged a cache before then in the "oldsters" team and everybody who logged their first cache after that date is a "newbie" ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

My web site allows me to do perl cgi, so I'd be happy to take it on if the new uk site turns out to be unsuitable. I also know how to hack perl, so would be willing to help maintain the code if your stuff does end up on a different web site. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

You could make it a virtual cache. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

You could make it a virtual cache. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

OK, it resolves now. You are going to get flamed about the forum as we already have one here. I think you should concentrate on putting UK specific resources on there such as info about access rights, where to get maps, GPS units from, UK caching links, a geocaching photo album would be nice, etc etc. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

OK, it resolves now. You are going to get flamed about the forum as we already have one here. I think you should concentrate on putting UK specific resources on there such as info about access rights, where to get maps, GPS units from, UK caching links, a geocaching photo album would be nice, etc etc. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

Congratulations ECM. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

Congratulations ECM. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

quote:Originally posted by SimonG: The only necessary element I can see missing from your proposed rules is something to stop one team from grabbing the bug and taking it straight to its goal, stopping at caches along the way. I think the easiest solution is to say the same person can't move it twice in a row (but not the same team - if they have to take it in turns to move it becomes too much like chess). Yes, I agree. I thought of this flaw myself late last night and was going to amend the rules in more or less the way you suggest here. quote: Secondly, the name. I suggested, in jest, that we call it bugger (bug + rugger). It later occurred to me that this isn't far from a decent name - bug + rugby = bugby! Come to think of it, I kinda like my original idea. Yes, I like that name. There might be some censorship issues though. quote:Bugger, anyone? I'd join in. I'd have to be on the techies team (I assume you mean computer techies). It would be quite fun because there might be caching partnerships where one person is a techy and the other isn't. e.g. if I go out caching with el10t things could get interesting. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

See the original thread posted earlier by el10t for a *very* full discussion of why or why not have a yahoo group. Oh, I've just reviewed the original thread and it says a lot about "insular" americans and arsenal but actually very little about yahoo groups - sorry. To be honest, I agree with you. I only joined the original group to make sure I didn't miss out on anything. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching [This message was edited by jeremyp on July 31, 2002 at 02:24 AM.]

Or you can get a tube from Paddington or a bus. The London tube is pretty safe generally. I would have no worries about travelling on the central bit at any time of day or night. Once you get out of the centre it might be different, I don'y know. PS don't believe anything Pid says, he is a danger magnet and therefore has a biased opinion about what is dangerous and what isn't. He's one of only two cachers to nearly get shot in this country ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

Or you can get a tube from Paddington or a bus. The London tube is pretty safe generally. I would have no worries about travelling on the central bit at any time of day or night. Once you get out of the centre it might be different, I don'y know. PS don't believe anything Pid says, he is a danger magnet and therefore has a biased opinion about what is dangerous and what isn't. He's one of only two cachers to nearly get shot in this country ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

Didn't think of that possibility. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

Yes. I joined the original group and either it's very quiet or they expelled me without telling me. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

If it's a non-profit organisation, you should have registered geocacheuk.org, or better geocache.org.uk. BTW it still doesn't resolve from my name server. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

If it's a non-profit organisation, you should have registered geocacheuk.org, or better geocache.org.uk. BTW it still doesn't resolve from my name server. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

This is getting too complicated. For the first attempt let's keep the rules very simple. That's why I suggested you can only move the bug to a cache on the first page of nearest caches to the one it came from. It makes it very easy to check if a move is legal. My proposed rules would be: - Two teams. - Designate two caches a long way apart as the goals. - Designate a third cache as the centre spot where the bug starts from. - Anybody can pick up the bug and place it in a cache that was on the page of nearest caches to that cache on the day before the bug was picked up. The last rule is worded like that to avoid arguments about whether a move was legal if a new cache is posted on the same day as the bug was moved. All you have to do is print out the nearest caches before going out in the morning and you are guaranteed to be placing it in a legal position. - The bug must be replaced the same day (prevents hoarding) - An infringement of the rules results in a "free kick" to the opposing team. The bug is placed back in the original cache and the team causing the infringement may not make the first move. - In the event of the bug being lost for any reason (cache pillaging etc) a replacement will be placed in the same cache (or the next nearest one which is not a goal if the cache has been destroyed) and a "drop ball" occurs. - In the event of a team member archiving a cache which has the bug in it, this is a free kick to the opposing team from the next nearest cache. The last rule prevents potential abuse. The rules may not be perfect, but after the first game we can refine them based on experience. For teams I would suggest Manchester United supporters against the rest of us, except there are very few ManU supporters in the Manchester region which could be a problem if we put one of the goals there ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

This is getting too complicated. For the first attempt let's keep the rules very simple. That's why I suggested you can only move the bug to a cache on the first page of nearest caches to the one it came from. It makes it very easy to check if a move is legal. My proposed rules would be: - Two teams. - Designate two caches a long way apart as the goals. - Designate a third cache as the centre spot where the bug starts from. - Anybody can pick up the bug and place it in a cache that was on the page of nearest caches to that cache on the day before the bug was picked up. The last rule is worded like that to avoid arguments about whether a move was legal if a new cache is posted on the same day as the bug was moved. All you have to do is print out the nearest caches before going out in the morning and you are guaranteed to be placing it in a legal position. - The bug must be replaced the same day (prevents hoarding) - An infringement of the rules results in a "free kick" to the opposing team. The bug is placed back in the original cache and the team causing the infringement may not make the first move. - In the event of the bug being lost for any reason (cache pillaging etc) a replacement will be placed in the same cache (or the next nearest one which is not a goal if the cache has been destroyed) and a "drop ball" occurs. - In the event of a team member archiving a cache which has the bug in it, this is a free kick to the opposing team from the next nearest cache. The last rule prevents potential abuse. The rules may not be perfect, but after the first game we can refine them based on experience. For teams I would suggest Manchester United supporters against the rest of us, except there are very few ManU supporters in the Manchester region which could be a problem if we put one of the goals there ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching

quote: Anyone been mugged for your GPS? It's something I have thought about in the past actually, particularly when caching in London. My GPS is actually worth considerably more than my phone. ------- jeremyp The second ten million caches were the worst too. http://www.jeremyp.net/geocaching