JeremyR

That sounds a touch arrogant to say the least. I'll hold my tongue until I've considered my thoughts a little more though. Minor bug report: something may be amiss with HTML Tidy - I can't seem to insert <br/> elements in TB pages at the moment.

I wasn't confused when I opened this thread but I sure am now! So, what you're saying is that a puzzle cache with multiple stages can't end more than 2 miles from it's published coords? What if it's a long one? That could mean that the listed coords are well over 2 miles from the starting location. Surely in the case of a multi-puzzle cache, the most common sense solution is that the listed coords should be at or near the first stage ('near' if the puzzle part is to work out the first location), in the same way that multi caches are handled? Do reviewers have any case-by-case discretion on this one, as with the 160m rule?

I see what you mean but I think they're 'unblown' 500ml Coke bottles?

Are they back again? There are no attributes in the PQ I ran just a few minutes ago... What attributes are you speaking of? Markwell's post implied cache attributes were included in the PQ GPX. That was briefly true for a couple of days after the last code release but Groundspeak rolled it back quite quickly because it caused issues with <ahem>certain applications</ahem>. Last time I checked (last night), the attributes were not back in the GPX files.

Are they back again? There are no attributes in the PQ I ran just a few minutes ago...

The last time I encountered a mouse was only a couple of weeks ago - when I saved the poor little blighter from the claws of my cat

Oh, and don't forget, if you have a camera and you're not a terrorist then you must surely be a paedophile...

I've been thinking more about this. Adding identifiers to the type would be excellent, and while we are tearing off the band-aid, maybe well-defined identifiers should be added elsewhere also. Cache size and log type are the most obvious, but it would also be nice to have two-letter identifiers for the US states, as well as 2- or 3-letter standard identifiers for country. So the new code might look like this: <Groundspeak:type id="4">Unknown Cache</Groundspeak:type> <Groundspeak:container id="1">Regular</Groundspeak:container> <Groundspeak:country id="USA">United States</Groundspeak:country> <Groundspeak:state id="TX">Texas</Groundspeak:state> What do people think? I like!! Me too! Proper coding of textual info in GPX files would be a godsend and make parsing a whole bunch easier Don't forget the log types! Eg: <Groundspeak:log id="12345"> ... <Groundspeak:type id="1">Found it</Groundspeak:type> ... </Groundspeak:log>

Shhh! Don't put 'em off! <whispers>2000 posts! 2000 posts! 2000 posts!</whispers>

Indeed.

GeoAngst FTW!

IMHO this thread is starting to make a mockery of the forum's moderation. It's been stuck in a loop going around and around in circles for hundreds of posts now. It's clear that Groundspeak are not going to respond beyond what they have already said so the people still arguing it out need to agree to disagree and let it go... For goodness' sake, it's just a game.

Not a chance. The Government/OS will never release the data into the public domain. Increased access != unrestricted access. OSM on the other hand is restricted only by CC Attribution-ShareAlike, meaning you can essentially use the data in any way you please so long as you attribute the source and make your version available under similar terms. The OS mapping data may become more available and usable (and that will be a great thing... if it ever happens) but OSM will always have a less restrictive license so there will always be a use for it.

Are you guys rabbiting on about courts and law actually serious? I mean come on, it's tupperware in the woods. Get some perspective

When was the last time some meaningful input about the *actual* circumstances was made in this thread?

Ta Dave

I'm a little confused about the supposed compatibility between Galileo and GPS. Are they compatible to the extent that their signals are analogous and once up there, they'll essentially become part of a larger constellation of satellites or are there enough differences that firmware upgrades and/or new GPS units will be needed to use the new system once it's online? I suspect the latter but only because I'm a cynic and when I hear talk of international government cooperating with each other for the benefit of the masses, I think O RLY?

It wasn't off topic, merely a pictorial description of my thought that the discussion has run it's course and interesting as it was this thread is just going around and around in circles, maintained by people who keep making the same points over and over again because they can't just agree to disagree.

It's fairly easy to discover them yourself: Descriptive Name ID *** Permissions: Dogs 1 Bicycles 32 Motorcycles 33 Quads 34 Off-road vehicles 35 Snowmobiles 36 Horses 37 Campfires 38 *** Special Equipment Access or parking fee 2 Climbing gear 3 Boat 4 Scuba gear 5 Flashlight required 44 *** Conditions Recommended for kids 6 Takes less than an hour 7 Scenic view 8 Significant hike 9 Difficult climbing 10 May require wading 11 May require swimming 12 Available at all times 13 Recommended at night 14 Available during winter 15 Stealth required 40 Watch for livestock 43 Needs maintenance 42 *** Hazards Thorns 39 Poison plants 17 Snakes 18 Ticks 19 Abandoned mines 20 Cliff / falling rocks 21 Hunting 22 Dangerous area 23 *** Facilities Wheelchair accessible 24 Parking available 25 Public transportation 26 Drinking water nearby 27 Public restrooms nearby 28 Telephone nearby 29 Picnic tables nearby 30 Camping available 31 Stroller accessible 41 Hope this helps.

It's not Groundspeak's game it's their website (distinction). If the cache exists, publish it on one of the other cache listing sites.

Why don't you relist it on <ahem>Another Site</ahem> ?

Not true. I coded a GPX parser about 12 months ago. I've just been back through the source code and it looks for 'Unknown Cache' in the <Groundspeak:type> node to identify puzzles (As an aside, Nate, it would be really nice to have an enum ID for cache types and log types as you've done with attributes! ) To make the point, here's an excerpt from a GPX generated on October 13th (before the attribute rollout): <Groundspeak:name>The Triple Hat Trick</Groundspeak:name> <Groundspeak:placed_by>.ichydr</Groundspeak:placed_by> <Groundspeak:owner id="400605">.ichydr</Groundspeak:owner> <Groundspeak:type>Unknown Cache</Groundspeak:type> <Groundspeak:container>Regular</Groundspeak:container> <Groundspeak:difficulty>5</Groundspeak:difficulty> <Groundspeak:terrain>5</Groundspeak:terrain> <Groundspeak:country>United States</Groundspeak:country> <Groundspeak:state>Georgia</Groundspeak:state> And here's one from November 7th (post attribute rollout). Same cache (GC1R2K9) which was the first puzzle in the PQ with attributes set: <Groundspeak:cache id="1229905" available="True" archived="False" xmlns:Groundspeak="http://www.Groundspeak.com/cache/1/0/1"> <Groundspeak:placed_by>.ichydr</Groundspeak:placed_by> <Groundspeak:owner id="400605">.ichydr</Groundspeak:owner> <Groundspeak:type>Unknown Cache</Groundspeak:type> <Groundspeak:container>Regular</Groundspeak:container> <Groundspeak:attributes> <Groundspeak:attribute id="41" inc="0">Stroller accessible</Groundspeak:attribute> <Groundspeak:attribute id="13" inc="0">Available at all times</Groundspeak:attribute> <Groundspeak:attribute id="24" inc="0">Wheelchair accessible</Groundspeak:attribute> <Groundspeak:attribute id="19" inc="1">Ticks</Groundspeak:attribute> <Groundspeak:attribute id="18" inc="1">Snakes</Groundspeak:attribute> <Groundspeak:attribute id="17" inc="1">Poison plants</Groundspeak:attribute> <Groundspeak:attribute id="39" inc="1">Thorns</Groundspeak:attribute> <Groundspeak:attribute id="8" inc="1">Scenic view</Groundspeak:attribute> <Groundspeak:attribute id="4" inc="1">Boat</Groundspeak:attribute> </Groundspeak:attributes> <Groundspeak:difficulty>5</Groundspeak:difficulty> <Groundspeak:terrain>5</Groundspeak:terrain> <Groundspeak:country>United States</Groundspeak:country> <Groundspeak:state>Georgia</Groundspeak:state> A mass of text (sorry!) but as you can see, the <Groundspeak:type> element is unchanged. The only difference is the addition of the <Groundspeak:attributes> node (and it's children).

I bet it's an instant notification problem? Check here and see if any of your notifications have "Didn't find it" in the log types list. If DNF is enabled for any of your notifications, you'll get an email every single time somebody DNFs any cache of the type specified inside that radius. If you live in a cache-dense area and the notification is for traditional caches, you'd be flooded with 'em . Click the edit link to the right of the notification, turn off Didn't Find It and save the changes.

A quick and slightly dirty solution is to use style attributes rather than class attributes. Rather than: <p class="mytext">text here</p> This should work (assuming your visitor has that font, of course): <p style="color:crimson; font-family:papyrus; font-size:x-large;">text here</p> You can drop the <style> element if you do it this way. Some CSS directives are filtered out by the server (the positioning ones, IIRC) but the ones you're using should be OK.