Jump to content

VE7RJT

Members
  • Posts

    16
  • Joined

  • Last visited

Everything posted by VE7RJT

  1. I was lead to believe that the reviewers are intentionally NOT local to the caches that they review. I know that the reviewer for this area of British Columbia is located in Georgia. I was told that this was to eliminate the chances that reviewers get FTF on all of the caches that they review and publish.
  2. Sorry to drift O/T.... Reading the OP it seems to me that this was a "question to answer" stage of a multi rather than a physical cache? Can the OP confirm if this is the case? Or is it the case that the cache was still too close to the final co-ords of the multi? Yes, there was no physical component to the other cache itself at the same location. The plaque on the wood carving only provided a clue to the final destination of the cache. It's fine. I've already moved my cache, hidden it again, and re-submitted.
  3. Agreed. Unfortunately, I have no way of knowing which datum the unit uses. I've checked both of the manuals for any instance of 'wgs' 'nad' or 'datum' and came up with nothing. Suppose I'm going to have to get the NAD co-ordinates, and see if I'm able to find a cache I wasn't able to find previously. Guess I just kind of assumed that no one would be using the NAD datum any longer. Thanks.
  4. Not really a way to change the datum on this one. It's pretty limited. But to be safe, I have checked into that myself just to make sure that that wasn't the issue. Thanks for the suggestion, though.
  5. Thanks very much. That's probably what I'm going to have to do. Just a little more work to make things a whole lot better. Appreciate the explanation.
  6. Agreed. Not something I was really considering. Just something I threw out there, though. Thanks for the information. I actually thought of getting someone to check the co-ordinates for me with a 'better' GPS than my own before publishing. Going to have to look up a local, I guess. And start looking at eBay for a different GPSr.
  7. Yes, I'm aware that they can't be any closer than 528 feet. What struck me was that readings taken in the *exact* same location were so vastly different. And based on the fact that I've heard of my co-ords being out before, I'm confident in saying it's probably my GPS rather than the other person's that's got incorrect co-ordinates. So should I just assume that if I hide, my co-ords are going to be out (that's not going to make me particularly popular), or mention in the listing that they could be anywhere in a 20-30' radius of the listed co-ordinates? Or should I just walk away from hiding caches until someday I get a better GPSr?
  8. I'm hoping to get one kind of an answer to this question, but I've got a bad feeling I'm not going to get the answer that I want. I placed a cache that was declined due to being too close to another cache. That's fine - I know the other cacher, and he submitted first. I don't have a problem with that. I placed the cache hidden inside a wood carving on a pedestal. His cache (part of a multi) takes the co-ordinates based on reading the plaque attached to the pedestal. My readings: N 49.06.542 - W 122.38.959 His co-rods: N 49.06.545 - W 122.38.951 I should mention that when I took the readings for my cache, I placed the GPSr *on* the plaque that he got his same readings from. Yet the reviewer rejected the cache reporting that it was only 10m (37 feet) from the other cache. Unfortunately, I've found that on both of my hides, I've gotten reports that the co-ordinates are out. No matter how many times I get readings. Usually by about 10m or so. Evidently it's my GPSr (a Nextar X3-01). Unfortunately, the X3-01 is not the sort of GPSr with the compass/arrow that points directly to the cache. I've got to check the GPS co-ordinates based on how it reports them (in decimal: 49.xxxxx - 122.xxxxx, etc) and then they get converted when I submit the cache for review. Unfortunately there isn't a way to automatically 'average' the co-ordinates that I get. Is there a way to do it manually? My main question (finally) is this: seeing as how it seems to be consistently out by about 10m, is safe to assume that it's going to be out (roughly) the same amount each time and could I add 2-4 points to the north co-ord, and 7-9 on the west co-ord? At this point in time, a new GPSr isn't an option, and I'd really hate to have this issue (which comes into play when finding caches, too) make me have to give up the hobby which I've come to enjoy so much. As I mentioned above, I have a feeling that the answer is going to be "No, you can't assume that it's off the same amount each time," but I thought I'd check anyway. Any advice that anyone could provide would be very greatly appreciated.
  9. Got my answer this morning. Was looking for new caches in the area, and one of the new ones was in the EXACT same location as mine. As part of a multi. It got published this morning. Ah well, that's the chance I take. I know the guy who beat me to the punch for this one, so I've already let him know that I'll be going to retrieve my micro today. Thanks for all of the advice though, folks. Definitely appreciated.
  10. I've found a spot for my next cache, but was wondering if I would be notified when I tried to submit the co-ordinates for it if I would be told that it was too close to an existing cache, or is this something I'll have to wait to hear from the reviewer about? I don't think that it's too close, but I'd rather not take up the time of both myself and the reviewer if I'm just going to be told that the two caches would be too close together. Thanks for any suggestions or feedback.
  11. LOL Expectations can lead to resentments, you dont want that... hehe. JK!!! Glad you found your first cache, fun isn't it, we found ours about a week or so ago... Now we are up to 11 and going out today. UGH! We're addicted! **sigh** oh well Ronney & Bill It is fun. Getting ready to hide my second cache tomorrow (hopefully it'll get approved before my first one, which I'm still waiting on) and I'm determined to pick up find number two this week. Cheers, Rod
  12. Well, I use my ham callsign as my geocaching ID: VE = Canada VE7 = British Columbia I'm actually located about 20 miles east of Vancouver, BC. Cheers, VE7RJT
  13. I finally found my first cache today (GC1YHVF - 100 Acre Wood Cache). It was the second time I'd made an attempt at this cache, the first being made last Thursday, only to find that the batteries on my GPSr died as I arrived at the site. Besides that, there was too much foot traffic. I put the GPS on the charger, and had a few minutes to make an attempt today. Once I found where the cache was likely to be, it was just a matter of 'thinking like someone hiding the cache' and it got a whole lot easier. Just reached right in there and pulled the cache out, with a big smile on my face. I was so happy to just sign the log, writing that it was my very first find. Didn't trade anything as it was such a quick trip that I didn't have anything to trade. It's not really about the swag, anyway. For all of those who hide caches, thank you. I'm now officially hooked on this hobby, especially after getting #1 out of the way. The quest for #2 has now begun. Now I just have to wait for my first hide to be approved (it's been about a week. Should it take that long?) and then I'll feel like a full participant in a great hobby.
  14. Just starting hunting caches in the last little while - haven't found any yet, but those I've been looking for seem to have been micros, which I'm finding might not be the best ones to start with. I'm not giving up, though. Gonna find as many as I can (140 listed within 10km of my house, so...) I just hid my first cache today, and am waiting for approval. One thing that I was wondering, though. Has anyone ever hidden or heard of a cache hidden in a cemetery? I didn't hide my cache in one of the local cemeteries, but with four of them in the area, am wondering if this is something that's somewhat common, or is it frowned upon? Any information that anyone could provide would be very greatly appreciated. Cheers, 7RJT
×
×
  • Create New...