palmetto
-
Posts
1492 -
Joined
-
Last visited
Posts posted by palmetto
-
-
https://www.geocaching.com/hide/report.aspx?guid=f1d3b703-bc6b-4fb4-88a1-daec145ff398
Link above for the edit page on your event. This can be built with the guid, which you supplied.
I can see the edit page, but I'm reluctant to fool with it. Only cache owner will be able to make use of this link.
If this listing were mine, I'd kill ALL the html, and have plain text.
We are some people of the organisation team of GeoNord 2016 Mega Event and we are spending some days in the area to attend the Hoorn Cache Mega Event and we want to meet some local or international geocachers. It's a good time to meet other geocachers and share some geocaching adventures or to share where are the most amazing places, but most of all, to taste some good chese or beers!
From 8:00 p.m to 9:00 p.m (AT NIGHT AFTER THE HOORNS MEGA EVENT)
See if making that change works. If it does, great. If not, then staff will have to intervene.
I note some html that I've never seen before, what's a "widow"? "widows:1"
-
As a reviewer, the only time I've followed up on permission has been on caches in U. S. National Wildlife Refuges and National Parks (permission for these areas is rare).
RE Earthcaches, I don't review them. Your local reviewer typically has familiarity with local land manager policy. The GeoAware accounts cover huge chunks of the world, they need for you to explain local policy, or preferably, state explicitly that permission exists. If you can show a particular land manager has a published "place caches freely" policy, that might be sufficient.
-
The Geocaching.com listing guidelines do not define listing coordinates for Wherigo.
On Wherigo.com all carts have "Start at:" locations, either "Play Anywhere", or a set of coords.
When reviewing, I do this:
If the cart is a Play Anywhere cart, then on Geocaching.com, the final physical cache should be within 2 miles of the listing coords, as for Mystery caches. Staff at appeals has agreed with this.
If the cart has "Start at:" specific coords on Wherigo, then those should be the listing coords on Geocaching.com.
Edited to add that I have NOT handled a Wherigo listing on Geocaching.com where the cache owner wanted different listing coords than the Start at: specific coords on Wherigo.
-
My thanks for tackling the numbered list problem.
-
Thanks for pointing this out, I didn't know it was available. I do see it working, as you say, provided there's a line of text and a space above it.
Highlight the block, hit Tab+ Tab and I get indented text with a font change (Lucida Console).
Applying Bullet formatting to the block brings the font back to normal output. Just an observation.
2) If a log is edited to change the Markdown, the changes are not rendered when the edited log is postedI mostly see editing the Markdown does work, except every once in a while, the original Markdown seems to persist, still formatting the output after it's been removed. For me this has been rare.
Possibly if there's a fix for, "loss of spacing when the Code Block is the first line", that will address the font change as well.
-
Preformatted Code Block does not work unless the code block is preceded by a line of text and a blank line
You're getting it work at all? It's not one of Markdown widgets being offered.
The Markdown offered is bold, italic, a unique Quote function, link, horizontal line, 3 Headers, numbered and bullet point lists.
In the log text box, if you Tab, text in the box will show as shifted over. But the preview doesn't show indention, because it's not supported. I noticed that sometimes text behind the Tab will have a font change as rendered. I think it switches from Verdana to Lucida Console.
-
It has ever been thus.
The current CSP forces you to see your coords on a map, too. Admittedly, not a terribly good map. Street view and out some zoom distance. Still, you'd think people would notice sometimes that what the map is showing is might poor match for their hide.
I used to see caches in the deserts of Algeria. This from transposing the longitude (W 08, instead of W 80).
I rarely see that with the current CSP. Instead I see E80, E81 - this puts caches into north India and Nepal. Even the somewhat simplified map on the CSP looks pretty funky relative to anything you'd expect to see in Florida. And it generates the "far from home" warning.
Oddly, I don't recall ever seeing N latitude as S. Why one and not the other? I dunno.
-
As a cache owner I should simply mark the travel bug as missing?
Yes, no point in having it in your cache's inventory if it's not there...
-
The log could have been deleted by the log owner, often in attempt to fix a logging error. ( Deleting the log does NOT reverse the action. A dropped trackable remains dropped, a disabled listing remains disabled.)
Sometimes they'll delete a "drop" log because they realize they logged the drop into the wrong cache.
Unfortunately, this will usually be a dead end for them. Once they've "dropped it" as log type, it's not in their Inventory.
Now, to straighten out the problem, they need the tracking code to "grab" it again, and then correctly drop it in the cache where they actually placed it.
And they don't have that tracking code anymore, because they dropped the trackable into a cache - just not your cache.
If they posted a note to the trackable page, the trackable owner could do this, but generally they don't realize that.
-
but am I allowed to do this at all / by more than a certain distance?
You can shift the listing coords by something less than 528ft yourself. Larger movements will require a reviewer. Please do NOT "walk" the coords, ie make a series of small changes to accomplish the larger change you want.
When you update the listing coords on a Mystery, those coords and the actual cache coords (Final) must remain within 2 miles of each other. No point in requesting a change that doesn't meet that requirement.
"....changing the northings by 10.000". 10 minutes has got to be something in the 10 - 11 mile range. The largest possible move of bogus coords is ~ 2 miles.
Last time I contacted the reviewer he didn't get back to me
Reviewers get a lot of email. Updating Mystery bogus coords may have been low on the to do list, and then simply got forgotten (especially if the coords you sent were outside of 2 miles from you final, reviewer may have intended to tell you, "no" and why, but time passed....) Sorry, but it does happen ;-)
I suggest that you try again.
Send something like, I'd like to update the "bogus" listing coords so that the map icons are clearer on these caches:
GC CODE, update listing coords to N XX XX.XXX W/E XX XX.XXX (original coords are N XX...)
I have checked and these bogus coords are within 2 miles of the final @ N XX XX.XXX W/E XX XX.XXX
repeat as needed.
Check the distance from your proposed listing coords to the actual final using the Boulter website
-
I can edit in some parts the of the Help Center.
I'm not writing phone apps. ;-) You might add your suggestions re the app documentation on Trackables to those particular threads.
-
"collectible means the finder can keep it. "
Collection means a PERSON can keep it, moving it into their Collection; a "Collection" is bookkeeping widget. This removes from their Inventory, so it's not in the way when they log finds on caches.
I'll look at the Help Center article; see if I can describe it without twenty-seven 8 x 10 colored glossy pictures with the circles and arrows and a paragraph on the back of each one.
----
http://support.Groundspeak.com/index.php?pg=kb.page&id=647
I've made some edits, there's no longer anything about "keep it".
-
Hello BearTerritory, the cache that was archived to allow the publication of GC69DBG is in a City of Milpitas Park.
-
Fizzy, I think there's some confusion about the dog park, which is a city park within a county park.
You'll find that info on both the county and city park pages.
I had nothing to do with these reviews; I don't what went on between cache owners and the GeoTour - what I do see is 4 cache owners who shifted hides to accommodate the tour, two instances where the tour shifted their own hides relative to existing caches, and 3 archived caches (all in city parks).
-
I've assisted as reviwewer on 3 Florida GeoTours. The GeoTour hiders will have the same difficulties that many other hiders have, particularly not avoiding existing staged caches.
Generally, where those older caches have explicit permission, that permission will be honored and the GeoTour caches shifted, or there will be cache saturation exemptions. The owners of the older caches placed without permission are contacted about options to move their caches.
Sometimes they do, and sometimes they choose to archive.
At first cachers we're excited about it coming but they aren't now.
Some cache owners and some of their friends will complain and be less than thrilled, for sure. But the larger community will enjoy the tour very much.
I do have sympathy for those who have been placing caches on a "no permission needed" basis, and later find out that not having permission = no protection if the land manager wants to place.
-
I'm aware of several multis that cross the Atlantic - US to Europe, and vice versa.
I have seen finds where all stages were found by a cacher who did the travel.
-
The closest Mystery cache is 1.6 miles away.
I believe you mean, the listing coordinates of the nearest Mystery cache are 1.6 miles away.
The FINAL of that Mystery, or of some other Mystery, is within 528ft of the newly submitted cache.
I see you've found no Mystery or Multi-caches. That makes this harder to understand, but the PHYSICAL stages of the Mystery cache are not (usually) at the listing coords. The cache report form isn't going to warn you about "hidden stages" of other caches. It can only show you the publicly available information. Which won't include the Final locations of Mystery caches, or stages of Multi-caches.
To know where those physical stages are, you have to find them.
-
So I'm wondering, if you would happen to figure out there was an archived virtual nearby, can you log it if you do all the requirements?
Can you? sure, usually you can log archived caches of any type. Sometimes cache pages will be locked to prevent further logging. All the Locationless are locked.
A cache can be locked on owner request, or if an admin notices logging abuse.
What are your opinions on this situation?I'm not a fan of seeking out archived boxless caches, Virts, Webcams, Earthcaches, for logging. If you find one that gets archived between your find and your logging, fine. (I did an Earthcache that was archived by the time I got home to log it. I was thinking of emailing the Geoaware account that published it that it needed to be significantly altered, but someone beat to it.)
I have mixed feelings about hunting physical caches where the container remains. In player mode, I'm rather attracted to the idea. As a reviewer, I see some of the problems it raises.
Is there a way to keep an archived cache from being logged?See answer above; listings can be locked such that they accept no logs.
-
I see your cache is published! congrats.
I'll leave my original response below on how to see the question and to respond, as this comes up often.
You receive all logs to your cache page as email, this includes the Reviewer Note posted yesterday.
After publication all logs to all your caches will come as email as well.
These logs are sent to the address you have on file here, and will come from noreply@geocaching.com
https://www.geocaching.com/account/settings/emailpreferences
Many times people use a junk email account to set up their Geocaching.com account, and don't check it. So check it!
Also, some ISP will automatically spam email from "noreply@geocaching.com". Be sure that you can receive that. Check spam folders.
Finally, the log itself is ON your cache page. Log onto your account, and onto the cache page, and scroll down. There it is.
Respond as directed please ;-)
-
Your cache was read by a reviewer on the 4th; a question has been asked.
Further review and possible publication await your response to that question.
I can't tell tell if that happened before or after you posted here.
Good luck!
-
What's up with the ugly oversized default font?
-
If you've hunted for a cache and not found it, log a Did Not Find.
If quite a few people have already logged DNFs, this could indicate that the cache is missing - though if the cache has a higher difficulty rating, it may be present, and people are simply not finding it.
If many people have already logged DNFs with no cache owner response, especially on a cache that was being found with no DNF logs previously, log a Needs Archived. That log will be seen by a local reviewer, who can decide what action to take.
-
I offer this URL as the place to see all your lists.
http://www.geocaching.com/my/lists.aspx
I hope this helps.
-
Going sideways here re Offset caches, apologies for the thread diversion. As the term is still in use, I'd rather clarify for those reading this thread. Offset caches as defined in the listing guidelines from late 2003 through early 2011 - multis with virtual stages.
Offset Caches
Offset caches are a variation on multi-caches. They are listed as a multi-cache when selecting a cache type. They are not found by simply going to some coordinates and finding a cache there. With the offset cache the published coordinates could be of an existing historical monument, plaque, or even a benchmark that you would like to have your cache hunter visit. At this spot, the hunter looks for numbers or information already appearing on the marker or on some part of the marker or site (geocachers NEVER deface public or private property). The geocacher is then able to manipulate these numbers using instructions posted on the cache page to continue the hunt.
https://web.archive.org/web/20101216075003/http://www.geocaching.com/about/guidelines.aspx
Dead bug button! (Feature Request)
in Website
Posted · Edited by palmetto
Hi KirkwoodCacheCrew, you might want to eyeball this thread on similar idea.
http://forums.Groundspeak.com/GC/index.php?showtopic=284690
If any such thing is to be done, it should be on the Trackable page, not on a cache page.
Site admins can post a Mark Missing log on trackables. That log automatically generates an email. But no one is "having to email owners".