gbod
-
Posts
182 -
Joined
-
Last visited
Posts posted by gbod
-
-
Just curious how the stats would look if you subtracted all the test posts?
-
does anyone have any idea what RCV_CPO support is?
I was about to ask the same question when I saw this thread. Internet searches have yielded nothing but references to the Garmin download pages!
Anyone know? Anyone?
-
11500 harrison street in omaha
Zoom in full.
Scroll north until you see Tyler street. (a click or two).
Click on Tyler street.
Huh?
Start moving the map and zooming in and out and ask yourself if Brookhaven Park is really there or not.
Wow. Kind of neat! Maybe this is like an Area 51 or something....
-
There is a cache near my house that I drive by several times a day. The first time I saw cachers there I didn't even know a cache had been placed there. I ran home and searched for nearest caches and found out one had been placed under my nose. Since then I haven't seen anyone out looking for it.
-
Ok I'm official now. + No more guilty feelings!
-
Uh oh.. my freeloading is exposed.
Hmmm. Off to sign up for premium membership...?
-
On the bottom of the forums it shows whos logged in. Some of the names have red crosses by them. What do they mean?
-
quote:
Originally posted by Rich in NEPA:I can live with this, and I hope that the same relaxed restrictions (600 pixels wide or less, or 125KB or less) will soon be provided on the benchmarking site.
I guess I should have stated from the beginning that the photos I'm uploading are all benchmark photos. I didn't know there was a difference between the two. (I've never uploaded a photo to a geocache).
Would you be so kind to explain the difference?
Thanks!
-
Thanks for the tips.
My main reason for resizing the photos is because I'm on a slow dial up connection. I have had problems with the image upload server timing out if the image is any bigger than about 400kb. My concern was one that has been raised earlier on the forums about GC.com resizing the photos again, and degrading image quality. I'll look into the programs you have all suggested. I'm sure any of them are better than what I'm using!
Another question: Recently it was worked out here that images would be left alone if less than 600 pixels wide or 125kb. What if your image is less than 600 pixels wide and greater than 125kb? Or less than 125kb but greater than 600 pixels?
Thanks!
-
Hey all- I need some recommendations on what you guys are using to "compress" your photos before uploading them to GC.com. I currently use a Kodak 3 Megapixel digital camera- and at home they look great. I've been using an old shareware program called Lview to resize them, and the results are less than spectacular to say the least. Rich in NEPA- your photos look pretty good- what are your methods?
Also- is it best to increase compression of a large dimension file- or just resize it to smaller dimensions?
Finally- is it best to take "high quality" (more pixels) photos on your digital camera and resize and/or compress them, or is it better to just take "good quality" (less pixels) photos to begin with minimize editing/compression.
I'm kind of new to the digital photo editing world, so I'm sure my vocabulary in the above questions may not be correct.
(I posted this in Benchmarks- since Benchmarkers take more photos than the general Geocacher)
Thanks!
-
Would you be so kind to provide a PID as an example?
-
quote:
I bet over the distance of 30 feet, a 2 degree error is going to only be a few inches off, certainly close enough when geocaching. Perhaps a mathematically gifted person could give a real number...
About a foot actually. A good approximation can be determined by the formula:
H = D * Deg * (pi/180)
Where H= horizontal error (the number you are trying to determine)
D= distance from the cache
Deg= angle of error in degrees
pi= 3.14159..
If you plug in the numbers 30 feet and 2 degrees, the answer is pretty close to 1 foot.
Disclaimer: I'm not a math expert, I just happen to remember these kinds of problems from trig class. Also- this formula actually gives you the arc length. The true horizotal distace is the chord length, which will be a shorter since it is a straight line. For small angles the approximation works fine for most applications.
And yes, certainly close enough for geocaching.
[This message was edited by gbod on October 15, 2003 at 04:00 PM.]
-
Plug in your coordinates, hit "goto", and follow the arrow. It's that simple.
Declination is important only if you will be triangulating the position of your cache with the help of a magnetic compass. It's probably easier, in my opinion if you leave the GPSr to point to true north, and make the declination adjustment on your compass. Even then, I've never had to do that to find a cache.
-
From what I understand (and I may be way off-I'm no expert), GPS satellites orbit at around 12,000 miles above the earth. The shuttle is designed to reach orbits ranging 115 miles to 400 miles high. The space shuttle is always way below the GPS satellites.
-
The maps are very helpful. Sure, there are bugs to be worked out.
One of them: in addition to archived caches, the maps are showing EVENT caches. Some of these events were months ago! (I'm afraid I might show up 6 months late for breakfast
)Besides these minor inconveniences, I am enjoying the new map feature.
Thanks Jeremy for all you do.
-
test... 1 or 2?
-
Quote from the image upload page: Your image can be as large as 4 megs, but the site will resize it into a smaller format. All images will be converted into JPG for viewing.
The limit for uploading seems to be 4 megs. (although they might be resized to 100K).
Oh well, I'll just make 'em smaller and try again.
-
I'm having trouble uploading images to the benchmark pages I have found. I am on a dial-up connection, but I have resized the image files to approx 500 KB. It seems to take forever to upload the images, and I have managed to get a couple through. However, with the last few images I've tried to upload, I keep getting a time out error message, and the image has not been posted. Any suggestions? (Besides getting a cable or DSL connection?) Thanks.
-
Thanks for the feedback. I went searching for a cache during lunch time and could not find it. I did not have a lot of time though, and people were giving me funny looks, so I think I will give it a little more effort before I actually log a DNF. (Unless I find it of course!)
-
I would like to know what the proper logging etiquette is on caches that you do not find, then go back at a later date and find.
Do you?...
A: Log a no-find on day 1, then post a new log as a find on day 2?
or...
B: Log a no-find on day 1, then go back and edit the original no-find log as a find on day 2?
Thanks!
-
I logged it again, and it's there this time. I figured the first one got lost, but I didn't want to double-post. Thanks!
-
I logged a find on Saturday, August 16th around 8:00pm. It is not displaying on the cache page, or on the "my cache" page. Is there a delay on these things showing up, or can I assume it was lost in transmission and post again? I see others here discussing problems with the server the last couple of days.
-
quote:
Originally posted by robertlipe:That's what I get for relying on memory. I'm sure it's one of the government data sets, but I probably guessed wrong and referenced the wrong bookmark. Try this one on for size:
Yes- this certainly could be it! Interestingly, it links to the census TIGER mapping feature if you want to map out your query result.
-
I checked the census site and explored the TIGER files. I don't think it's the data set being used. I was unable to find campsites, radio towers, valleys, etc. that ARE downloaded with the nearest placenames. The census data seems to be more concerened with political and population boundaries, etc. than radio towers or geographic features. Pehaps I'm not looking deep enough though!
Faq?
in Benchmarking
Posted
Try looking at this page first. If you still have questions- come back and feel free to ask them here.