Accuracy (Wellington) Porirua East, North Island, New Zealand
By Outward Bound on 04-Jun-08. Waypoint GC1CZ3B

I am regretfully archiving this cache since there's been no response from nor action by the cache owner within the time frame requested in the last reviewer note.

I think it's about time this cache was archived. This is not a virtual cache and there has been no cache here for as long as I have been a cacher (that's 7 years now and no I have never logged a find for that reason). I don't understand all the false finds - just because the CO says you don't need to sign a log that's not how geocaching works for unknown caches.

Hi Outward Bound

All physical caches must have a physical cache container and a logbook.
https://www.geocaching.com/play/guidelines#logbook

Please replace the cache within 30 days or I will archive the listing.

Regards
TheCoddiwompler

On a day caching around Porirua.
Did this with an iPhone. Left it on the pin for 5 minutes before checking coordinates which were:
S41 8.224 E174 49.691.
Thanks!

I remember a number of classes at training where we had to plot the accumulative answers from our lab results, it worked well when plotted on graph paper, and the occasional odd ball variant we could easily blame on Nigel, or someone else who happened to be absent on the day. Great concept for a cache, I had 041 08.221 and 174 49.697 after several readings, TFTC

Fun! Look how many things are around that we never knew existed! I love this game and I love how in-accurate it is!

So...Done with phone with excellent intentions of Garmin having batteries working...bummer but was excited anyway. I also did a quick check in with the internet for fun but that was so out it was embarrassing!

I came up with 041 08.221 at every reading on my phone gps
I averaged out 174 49. 696 after several readings putting me about 174 49.698 and 174 49.694

Thanks for working the brain today!

(# 6893) Did this after a walk up the big hill. Weather was overcast and I couldn't let the GPS settle for any amount of time due to a muggle mowing the grass right at the GZ. Thanks for bringing me here.

An interesting exercise. I got coordinates S41 08.223 E174/49.696. I took two readings over a couple of minutes with the same result using a Garmin Etrex 20. I am not very familiar with the satellite fixes but have included a photo of the screen. TFTC

Stood for what felt like ages in the freezing cold and the best accuracy I could get was 3m. New to using GPS so could in fact be user error.

Hmm not sure why the photo won't upload. Co-ordinates are S41 08.223 E174 49.695

Overcast and raining, I stood at the spot for five minutes with my iPhone 8. Got the following coordinates according to Google Maps: 41.1370084 174.8282875

Completed this exercise as part of a walk up through Porirua Scenic Reserve on a very pleasant afternoon. Included a photo of my GPSr after seven minutes.

Straddled the marker with my phone which has a GPS app. Screen shot included.

Found this one a while ago but failed to get the image necessary to log the cache. Thanks CO for the interesting cache.

After getting into camp and getting my tent all set fir the night it was time to relax or so I thought.
Then I noticed this cache ok time to spear so let's have a go at a puzzle
But not what I was expecting so shoe's back on and away I walk.
Found the location easily and after 3 min my ph had settled in nicely.
So down to .4 m
Not bad as it was overcast and humid .
I have found it a case of just giving you devices time to settle and give a set of cords that are pretty good.
Now back to feet up in my tent .
S41 08.233 e174 49.696

Living life one foot steep at a time as i walk from cape reinga to bluff and caching my way home as I walk the
Te Araroa and discover the hidden treasures new Zealand has to offer.
From the beach of the north to the forest and lakes of the south
Blùff here i come
Thanks for the hide

tftc

Have been past this way many times while going up Colonial Knob but never stopped to try out this accuracy exercise before. Today after completing a multi-cache up the hill I found I had some extra time and stopped to give this a go. I usually cache with my android (Huawei) phone but sometimes use an etrex 10 so I thought I'd check out both for comparison. The map on the cache page was helpful in locating the pin (I'd not come across this type or position before, had only ever noticed circular ones in the footpath). I sat myself down on the grass behind the pin and added a waypoint using the geocaching app - surprised that the phone gave my current location exactly the same as the posted coordinates: S41 08.224 E174 49.696 at 12.39pm. I then marked a waypoint using my etrex which gave my location as S41 08.223 E174 49.696 at 12.40pm. I then took a waypoint average on the eTrex and let it sit for 5 minutes, which adjusted the coordinates 1m to S41 08.223 E174 49.697. I don't usually look at the satellite information but I thought it would be good for this exercise, it looked like the satellites in use were numbers 1, 7, 8, 11, 17, 19, 21, 28, 30 and I guess the 3m in the top right hand side of the screen is the estimated position error? I have included some photos showing the coordinates marked on my phone and the satellites on the etrex (hard to get a good photo with the sun glare). So today it looks like my phone and GPSr only differed by a couple of metres, I've noticed sometimes when I've been caching that there's been up to about 7m difference. I didn't look for the cache as the last finder said it was missing and I didn't see Jellybean the Donkey. I did pat the very cute little pony though. Thanks for the interesting cache.

Hunting out geocaches previously solved or has high FP count, or is part of an unfilled grid. Or in this case bugged me since I didn't find it July last year when I was stopped at Camp Elsdon for a couple of days.
Lat/Long: S 41°08.224 E 174°49.696.
GPSr make: Samsung S5 running a couple of apps.
Time & Date: 14:00 01/02/2020
EPE: +/-1.3m; Averaged over 101 readings
Sats in use: 17/31 as per screen grab
The actual cache appears to be missing, but Thanks for an interesting cache.

We found the pin easy, and my XR iPhone finally narrowed our co-ordinates down to 0m after placing my phone on the pin for a few minutes. We took a quick screenshot of this. The co-ordinates bounced around a lot though, & we managed to get perfect coordinates by using a phone! Great exercise!

Visited the area thisafternoon
At first was not sure what I was looking for as we had parked the car in front of the plaque. Once found I got a reading off my Samsung 8s although seemed to be jumping around a little bit

An interesting exercise. Visited at 10:30pm, and sat my phone (Andriod Nokia 7+) on top of the marker. Let it sit for a minute and it read S41 08.225 E174 49.695. Pretty close really. TFTC

Some of us use a smartphone, so not all the details were readily available through C:Geo, but I tracked down the bench mark, and took a reading whilst standing almost on top of it! Things looked promising initially, with a reading of under 1m , but the distance gradually climbed, then settled down at 2.86m out with coordinates of S41.08.223, e174 49.697. Thanks for an interesting challenge which made me think!

S41° 8.224 E174° 49.696 on my etrex 20, a single snapshot with accuracy reading +/- 4m. A reading which seems to be identical to the posted coordinates.

We visited the Benchmark this afternoon to test the Accuracy of our GPS unit. We are using a Garmin Etrex 30 running the Patched version 3.90 software.
The time of our visit was 3.55pm, and we had left the GPS to settle for 3 min 30 sec before taking the reading. The GPS had taken 230 samples.
Our reading of the co-ords was S 41.13706 E 174.82826
The satelites that were fixed by the GPS were ID nos 1, 7, 8, 11, 13, 17, 18, 19, 28, and 30.

Thanks for an interesting and educational cache.

Difficult to find at first but the map helped a great deal.

For my purposes I've used this exercise to determine in broad terms whether under clear sky condition my S5 mini smartphone can get a fairly accurate fix within say a couple of thousandths of a minute The screenshots seem to show that this is possible However I have found that repeatability is not consistent Sometimes I can move the phone several metres and the coordinate readings do not alter That can be frustrating when trying to zero in on a difficult cache I waited for about 4 min before recording the values TFTC A favourite from me

Visited this cache with Red Roaming as we travel around New Zealand to celebrate me taking 'Retire and Return' option at work. what an interesting, different cache to do. we spent about 15 minutes here taking various photos and adjusted GPS readings.
my GPS is a Garmin Oregon 650. It read 7 to 8 feet out the GPS accuracy was 10 feet. Long lat reading S 41 08.223 E 174 49.687 which is almost exactly the same as the cache page. MTFTC

Logging as found having visited gz and uploaded details as required. Many thanks

I use my iPad mini for geocaching with the excellent Cachly app.
At gz the iPad was reading 14' with 16+/- accuracy after 5 minutes.
The iPad coords were S41 08.222 E174 49.696 - (given gz S41 08.224 E174 49.696) = not much difference!
Please see photo of my iPad reading at gz and the plaque and bolt

Favourite point - I really found this interesting and informative, as have often felt that my iPad at times wasn't as good as a GPS - but now I know that it is VERY GOOD!

Travelling around the world with Dartmoor Deliverer helping her celebrate having taking early retirement!

NB Dont forget our Devon UK Mega 2017 GC6JZNY this August in the beautiful East Devon area of our county. UK Megas are over one week full of events and geocaching - a wonderful way to enjoy our county!

Interesting.
My pin was was VERY close to the mark on the.map.

Just logging this as done at the moment, pics will be added asap.

Garmin Etrex20 Decimal degrees (DD) readings averaged;
S 41.13707 E 174.82826 ±4m alt. 37.3m
Satellites 2, 5, 6, 9, 12, 17, 19, (25)

Garmin Etrex20 Degrees and Decimal minutes (DDM) readings averaged;
S 41° 08.226 E 174° 49.695 ±4m alt. 33.3m
Satellites 2, 5, 6, 9, 12, 17, 19, (25)

HTC One X+ using GPS Satellie Viewer app. from S.F.Applicality Ltd. V.2.0.2 DD readings averaged;
S 41.13707755 E 174.82824949
GPS satellites 2, 5, 6, 9, 12, 17, 19
GLONASS satelites 67, 82.

Didn't see the four-legged onlooker, neither did I find the physical cache.

Thanks for the exercise.

Out with Spider-Bite back in October (12th) and only Just realized this hadn't been logged

IPhone 5S - still for 2 to 3 min, stated accuracy got no better

Reading at Plaque S41.137073 E174.828199 and a stated accuracy of 31 meters

Reading taken with Spyglass compass - photo attached.

Using Geocaching app I was approx 5 meters away from plaque when app said 1 meter to go

Wellington has been appalling today - rain, no trains, traffic jams everywhere. As a result this emergency cache came into play to maintain my streak, but other constraints limited the time I had available at GZ, so only a partial log. Sorry!

Date: 15 November 2016 @ 15:30 (Groundspeak will log this on 14th - so be it!)
Coordinates: S41.13706 E174.82828 (Yes - really 82828!) averaged over two samples, about 5 minutes.
Equipment: Garmin GPSMap 62sc

Didn't note the satellites in use or any other data.

Didn't find the cache, did pat the Shetland pony that trotted up to say hello, no donkey today.

Photos attached.

{Edit} The listing speaks of decimal degrees so that's what I posted. Only later did I notice that the legend on the plot reads 'Decimal seconds'. Too late now! {/edit}

My coords very close to given, at (decimal minutes with extra digit) S41 08.2223 E174 49.6973. iPhone SE, using MotionX-GPS. 5 m accuracy, great reception. No change over few minutes. Cool idea for cache, thanks!

Found this one while out caching with CanuckNZ.
The plaque was where it should be, but no sign of the physical cache.
The location (at the plaque) from the Garmin Dakota 20 GPS was:
S 41.13707 E 174.82826
S 41 08.224 E 174 49.696
The GPS had 9 satellite locks (7, 8, 9, 11, 16, 23, 27, 28 & 30), with reported GPS accuracy of 3m.
You can see the satellite reception strengths in the photo.
The GPS was stationary for about 5 minutes before the readings were taken.
Thanks for a really interesting & different cache

Found with TregearP this afternoon. The car park was quite busy with some young petrol heads appearing to be checking out a Mitsi Evo for possible purchase/sale.

Whilst they were checking tyres and under the hood we found the geomarker and set about recording the data needed to log the find.

The GPS is a Garmin Montana 650, 3:04 p.m. on Saturday 17 October 2015. The weather was overcast, still a blustery Northerly with a Southerly change expected (and arrived) about 90 minutes later.

We let the GPS settle for around 5 minutes for readings of S41.13708333° E174.8283000°. The precision shown is on the basis of the last significant digit in 0.001' which our GPS displays, and the number of decimal places that corresponds to for degrees.

The photo attached to this log shows the satellites and their strength, which according to the posted coordinates had us within 3m of the GZ.

We had a look for the physical cache but nothing found and given the comment we didn't linger. Jellybean appears to have a new paddock-mate and they were both happily munching at the other end of the field and didn't seem overly interested - or perhaps it was from the engine testing / revving of the petrol heads that prompted them to stay away.

An interesting and enjoyable cache.

Found with SJT_NZ and details included in SJT_NZ's log. A clever idea for the cache, couldn't find a physical cache despite a good fossick and no donkey but there was a little shetland in the paddock. It had sufficient grass to keep it happy so had little interest in a couple of people taking lots of photos.

I'm not exactly a Luddite, but I don't have a proper GPS handset. Rather, I use an iPhone and an iPad. The iPhone's Geocaching.com (Groundspeak) application is considerable less accurate than the iPad's after a recent iOS update I also have a basic compass app on the phone but it doesn't give decimal seconds. So, knowing I was going to be in the area today and might have time for a crack at this cache, I downloaded Spyglass and a satellite locator app. The locator was a dud - at least I didn't pay for it! Or maybe I just don't know how to operate it? Anyway, there are no satellite readings. But Spyglass was pretty efficient: I got 41.137065 S 174.828293 E (60GUV1772943754). Elevation was 42m. The numbers didn't change at all over four minutes, from 4.29pm. It was pretty cold (snow on the mountains!) so I forgot to use the iPhone and iPad Geocaching apps to double-check my readings. Also, I didn't see the donkey But I am very pleased with Spyglass - it looks like it has some very interesting functions, so I shall investigate now! TFTC

Remembered this M@ style cache in Auckland. Its a good indicator of how different readings can be.
Today we got decimal degrees 41.13702/174.82826 and 41.08.221/174.49.695 for the Lat/Long. GPS is a Garmin 64s, Time was 1.19 pm, 16 August 2015.

EPE 3 m, but 15 satellites counted. Time to read was 1 minute, but we messed around for about 10 mins. Fine day with scattered cloud.

Off home for lunch! Thanks for this one.

#852. Out at Porirua for some shopping with the family so we stopped off afterwards to do some local caches. The girls fed grass to the ponies and donkey while I mucked around with the datum point that Mrs GSEL spotted with her sharp eyesight. I put the GPS next to the pin and photographed it after one minute and again after 2 minutes. The GPS is a Garmin GPSMAP 64s and photos taken at 12.57 pm and 12.58 pm on 17 May. See attached photo taken at 2 minutes. There were 14 satellites available and altitude was apparently 33m. The position was initially S41 08.223, E174 49.695 and latitude changed to .224 after 1 minute. I also took a waypoint after 2 minutes using decimal degrees. It was -41.13706, +174.82826. GPS accuracy was supposedly +/- 3 m at the time. I did have a brief look for the cache checking posts around 20-30m away on either side of the road but nothing seen. TFTC

Heading North from Blenheim today and into the eye of the storm as the heavens flashed and crashed and the rain came down. A pleasant ferry ride and saw dolphins and seals so that was nice and was on the earlier ferry to hopefully surprise the family. Little did I know what was waiting though with flooded roads, closed roads and silt and vegetation lying around after flood waters had ebbed and flowed.
Had identified a couple of potential puzzle caches with user names beginning with differing letters of the alphabet an O was missing from my healthy sized list. After solving " " my dear Watson and seeing it had been adopted out I focussed my attention on this one. Arriving at G Z and the little stream just up past the car park had burst the bank and was forging a new path. Likewise the grass alongside was very wet and small streams were running all around, the power of nature is amazing.
Found the pin readily enough and proceeded to take readings using my Garmin Etrex 20.
Coordinates at the pin were;
S41 08.226 E174 49.698 Elevation 49m
Accuracy was 2 metres out of sync, cloudy, overcast, raining, 5 satellite bars.
Saw the donkey but he didn't come over to me
T F T C Outward Bound

S41° 08.224 E 174° 49.696
Average over five readings, walking away in a different direction and figure of eight between readings, left gps to settle for 30 seconds or so between samples.
Device is a Samsung galaxy s3 running android 4.3 a d using c:geo as my gps utility.
accuracy was +\- 6m with 12/12 satellite's visible.

note cords I screen capture were part of the averaged results

TFTC Stopped by on the way home one night to grab this one. Found the little pin and then LCBuilder and I used our Magellan 510 to obtain the coordinates. It was a bit of a cloudy day but we let the GPS settle for about 2 minutes and got a reading of:
S 41 08.222 E 174 49.693

Neat Puzzle thanks for the cache done with Wafflekitties

Obtained the following with the Magellan 110, with accuracy 5m, today at 2:30pm:

S 41 08.225
E 174 49.695

Nice clear conditions too. TFTC

Have been meaning to do this one for a while and was out and about today with work.

Overcast conditions today and allowed the Garmin 62s to settle for five minutes before taking the following readings:

S 41 08.222
E174 49.694 +/-4mtrs

TFTC

A quick find. Having only ever used c:geo for geocaching, I'm probably not as well educated with the technical details.

However, I can provide the following information regarding my find:
Lat/Long: S41 08.225 E174 49.696
GPSr: Nexus 5 (LG)
Time/Date: 11:26NZDT 2014-10-04
EPE: 3m
Waypoint time: ~30s
Satellites in use: 12/20

Too many muggles around to bother trying to find the physical. TFTC

#1189 This is such a neat idea- today I took along my phone (which I mainly use for caching) and my Magellan 710 which I use under any tree cover or as the big guns when I need more accuracy. It was a clear day and as a bonus, I got to meet both little ponies and the donkey. They supervised the whole thing

Magellan 710 Coords: S41 08.225 E174 49.697 (41.137083 174.828283)
HTC Desire phone coords (c:geo): S41 08.226 E174 49.692 (41.137100 174.828200)

This entry was edited by Skaga on Wednesday, 24 September 2014 at 10:20:26 UTC.

Quick find of required mark. Donkey and two little ponies stood at far away fence. They didn't want to say hello today.

My Coords were S 41.13709 E 174.82826 using Magellan 110. For some strange reason didn't want to get any more accurate than 22m this morning even though clear skies overhead. Satelite coverage seemed okay and I have added a picture for this. TFTC.

#539 Not too sure what I was meant to do for this one. However, took a photo of my GPS with satelites - I have a Magellan 100 series - basic but accurate. Its GPS reading at GZ was S41 08 223 E 174 49 696 and my iphone (as second check) was S41 08 225 E 174 49 697 (accuracy 5m). It was a slightly cloudy day. Couldn't find the actual cache anywhere. Looked for a little while.... And the date was Sunday 27th July.

Dipping Tb

Needed an "O" cacher name mystery for a challenge - so after having done Kevin Andersons cache we heeded for this one and arrived approx 2pm on the 21/07/2014 - we used a Garmin 62s - and the error was approx 3m ( photos of satellites will be on Stretch0's log as he has the fancy phone that takes the pics He did an averaging mark for for approx 6mins - the conditions were overcast with occasional showers - S41 08 223 E 174 49 696 Thanks for the cache

Needed an "O" cacher name mystery for a challenge we are doing - so after having done Kevin Andersons cache we heeded for this one and arrived approx 2pm on the 21/07/2014 - using a Garmin 62s after locating the correct point sat GPS down and left to get an aveage over about 6 minutes with 9 satelites in range on an overcast day will add pic of gps

Got the coords after finishing a walk to Colonial Knob with Belmont Scouts, Jax479, CaliguliaNZ & orrsum4sum TFTC

Coordinates:
S 41 08.225
E 174 49.697

Using S5, allowed to settle over 5 minutes, took a number of readings, noted down the most common Co's.
Taken just after 4p.m, Saturday 5.07.2014. Conditions: Sky clear and sunny.

TFTC!

Stopped off for this one after doing a few hours on the Colonial Knob loop with a small group of Scouts and Leaders.

Coordinates:
S 41 08.224
E 174 49.697

Using i-Phone 4, allowed to settle over 10 minutes, and an average of six readings reported.
Taken at 4p.m, Saturday 5.07.2014. Conditions: Sky clear and sunny.

TFTC!

#35 Cache Found. Coordinates exactly the same as previous cacher used Samsung S2 TFTC

Gutted we couldnt find the cache as we thought we had to. Big thanks to Huntleight for letting us know there hasnt been a container to find for quiet some time now and we could go ahead and log it as a find as long as we took a reading at the marker (which we did!)
Here is the reading we got at the marker: s 41 08.234 e174 49.701 it was taken with a Garmin GPSmap 60SCx

[green]Cache of the Day: 31/31 [/green] | [blue]Cache of the Mega: 31/416 [/blue] | [purple]Our cache find: #1823[/purple]

This entry was edited by gracie7 + Mum on Wednesday, 13 November 2013 at 23:18:35 UTC.

S41 08.222
E174 49.695

This was measured with a 'S3 mini' android phone.

Got a chance to stop on the way home from work today, been meaning to do this one for a while

S 41.08.225
E 174.49.697

Garmin GPSmap 62

Time 17.06 29/8/2013

TFTC Outward Bound

Been meaning to get around to this one for years. The annoying thing is I have been in this car park masses of times and not thought about it.

Took the iPhone and the Garmin etrex venture HC along to compare them. The Garmin has been playing up and has been around 10m out just lately. I don't use it so much since getting a smart phone.

iPhone 5 (geocaching app) S 41 8.224, E 174 49.693 (haven't worked out how to change the units!)
Garmin S41.13699, E174.82817

Left them for about half a minute but I was being watched by a couple in their parked car, and it was cold and dark. I forgot to note the satellites. There was some light cloud.

TFTC!

Out and about with Kjwx and the eldest littlejardisliketardis today. I had heard about this cache from Kjwx, who had done it 3 years earlier...

Lat/long: S41 08.255' E174 49.697'
GPSr: Garmin Etrex H
EPE: +/- 3m
Satellites: 3,6,15,18,21,22,24,26,27,29
Date/time: Sunday 23 June 2013, 2.30pm

Stood on the pin for 30 seconds, observed only the rear end of Jellybean.

TFTC!

3 day weekend? I like the sound of that! What's even better? 3 DAYS OF CACHING!!!
Destination sorted (to Wellington and back again), the bags are packed, the travel bugs are ready to travel and the GPSr is ready to show us the way.

Took a while to figure out what we were looking for to take our readings from. Thought it might be fun to compare three different GPSr systems: the Garmin, Galaxy S3 and Xperia X10. Z-NZ has posted up the screenshots taken from each.

#2 for the day, 64 total for the weekend with a total of 1250 kms.

TFTC

Becsicasa and I decided to do a bit of a caching mission well outside of our area. We left Hamilton early Friday morning and hit the road, Destination: Wellington
Thought it would be cool to get the three devices we use all together!
TFTC!

S 41 08.223
E 174 49.695
3m accuracy
Garmin Colorado 300 (Software version... no idea!)
Date: 30 March 2013
Time: 3.05 pm
GPSr in situ 3 minutes approx.

Donkey in evidence - that's reassuring!
Cache not though. But that seems to be expected perhaps.

A new and different caching experience. Thanks for that.
Undertaken with team cacher Sweet P
The Turtle trikes again!

Lat: 41.13711 S
Long: 174.82831 E
EPE: 7m
GPSr: Sony Xperia Go
SW: Android Gingerbread 2.3.7
App: GPS Status 4.0.1
Sat: 9/10
Time: 11.58am
Hold gpsr in position for about 30s...

TFTC

Fear that everyone will laugh at the accuracy of my lowly i-phone, and it won't even make the graph !

My GPS is an i-Phone 4GS running iOS 6.0.1 (10A523).
Software was MotionX-GPS V20.0 Build 4621 R.

Put the phone on the PIN and waited a little while for it to settle, then managed to come up with;
S 41.137024, E 174.828289.

Date/Time - 19/01/13 at 1:28pm
Accuracy of 5m according to the phone.
I let it sit on the Pin for about 3 minutes.
No satellite information I'm afraid !

No sign of donkey, or the physical cache, but TFTC anyway !

Couldn't resist doing this one as the 16 year old has just left for Outward Bound. Readings as follows:
Oregon 550
Averaged with 100% confidence of 5 minutes
S 41 08.224
E 174 49.495
Accuracy 3m
10 satellites
Clear skies

Garmin GPSmap 62
Unit Id 3809138800
Software Version 3.90

S 41.08.225
E 174.49.695

Elevation 37m - 3m Acc

1100 on Wed 26th December 2012 with clear skies.

Lat/long:
-41.137067
174.828233

ETrex H

Time to waypoint: 2 minutes

Thanks for the cache, i really enjoyed doing this one!

Sunday 9th September 4.15pm

Let GPSr settle at geo pin for 5 minutes. Weather full cloud and rain starting.
Dakota 20 software version 5.30
EPE +/- 3m -41.137067 174.828267

No sign of the donkey. Took Chelle's High horse for a trot in the fresh air.

This entry was edited by Renard & Co on Sunday, 09 September 2012 at 21:36:14 UTC.

TFTC
Buzzing from cache to cache

Lat/Lon: S 41° 08.224 E 174° 49.698
GPSr Make: Garmin GPS MAP 62s
Time / Date: 16:19 28/7/12
EPE: 3m
Waypoint Time: Only long enough to get the screenshot - had just walked around Colonial Knob loop, and was ready to head home.
Satelites in use: See pic.
Extras: none

After camping the night really close to this spot, our morning exercise was measuring how accurate our GPSr was. We came really close:

Lat/Long: S 41 08.224 E 174 49.696
GPSr Make: Garmin
GPSr Model: Extrex 20
software version: 2.70
Time / Date: 13/7/2012 10:18
EPE: 0m
Waypoint Time: 25 seconds

See attached the satellite details.

Drive by on Solstice morning. I'm interested to know how my Galaxy SII measures up, as I've never used a dedicated GPSr unit.

Lat/Long: S 41 08.221 E 174 49.690
GPSr Make: Samsung
GPSr Model: Galaxy SII
software version: Gingerbread
Time / Date: 21/6/12 08:46:13
EPE: 5m
Waypoint Time: 25 sec's
Sats 2, 4, 5, 9, 10, 12, 17, 20, 27

Jellybean not in attendance.

TFTC

using Taybee new Gps to log this Thank's

Lat/Long: S 41 08.225 E 174 49.696
GPSr Make: Garmin
GPSr Model: GPSmap 62s
software version: 3.9v
Time / Date: 04/6/12 14:38
EPE: 3m
Waypoint Time: 31 sec's

Good fun used my Iphone and it told me 041-08-222,174-49-695 so pretty happy with that. Spent about 10 min looking for cache but didnt find -(given message didn't spend too long )

Found today at 14:00, clear and sunny. Donkey and two miniature horses in attendance.
GPS device Garmin GPSmap 62s, ver 3.50.
S 41.13707 E 174.82829
Took about a minute to average.

See screen shot for satellite readings.
Didn't try to find cache.
TFTC

Got this today, not much cloud. We had the livstock watching our every move.GPS: Garmin Etrex v2.14 CoordsS41 13707° E174 82823° EPE: 5m Time: It was sitting here for 5ish minutes Satellites:see picture.
No cache find attempted

I luckily still had the paperwork for this one with me when I unexpectedly had to drop off a colleague at Porirua railway station today.
Lat/Long: S41 13705 E174.82822
GPS: colorado 300
Time: 15.55 29/2/12 (special day)
EPE: GPS said 3m
Satelites: 1,2,4,8,9,17,20,27,28,32,48
I estimate 50% - I tried to take a photo but it really didn't show
up very well with the reflections
Extras: Very overcast grey afternoon

Cheers for the cache and a leap day find #3043

This entry was edited by isis58 on Friday, 02 March 2012 at 10:18:33 UTC.

Coordinates S41 08.223 E 174 49.694
iPhone4
Geocaching App v4.5.9
Accuracy 5m
11.15 am 29/01/12

I suspect that using the iPhone it does not matter much if you are decminal degrees or minutes .

TFTC

Down from Auckland for the day with 10centcoin, on a mission to find some caches around the Wellington region. Found this one while heading north out of Wellington. With my Oregon 550, I measured the coords at the benchmark to be S 41 08.225 E 174 49.696. TFTC!!!

@11:50 23/1/2012 for about 5 mins
Garmin 62s
S41.137083 E147.82826 +-3m
Satellites
3 100%
6 100%
7 100%
8 zip
10 80%
13 80%
16 100%
19 80%
20 zip
23 90%
30 100%

The nearby business was working today (Wgtn anniversary) so didn't attempt to locate the GZ.

"Jellybean" the donkey was present with two miniature ponies. The ponies can be a bit stroppy though.

Coordinates S41 08.224 E 174 49.695
Garmin Nuvi 500
3.20 pm 20/11/11

Coords: S41 08.223, E174 49.696
GPS: Oregon 550
Time/date: 1:05pm, 6th November 2011
Accuracy: 3 m
Time to average: GPS took 30 seconds to say it was 100% confident
Satelites: 12, 14, 20, 25, 30, 31, 32 - average reading 75%
Extra: Nil

No sign of a container

Measured position: S 41.13708 E 174.82825- looks pretty good to me when compared with the decimal conversion of the posted coordinates!
Using a GPSMap 60CX
EPE varied between 3 and 5 metres, was 3 metres when position was recorded. I didn't record over a period or average but only made a quick reading because there were working muggles over the road, plus a few muggles passing close by in vehicles and even without a physical cache my standing there for long could have looked a bit suspect. For the same reason I didn't look for the physical cache (if it still exists!)
Satellites: excellent configuration and reception, approximate percentages as follows:
GPS 20,23,29,30, 31, 32 and 48 at 100 percent
32 and 48 at 90 percent
14 at 80 percent
16 at 60 percent.
Jellybean: 0 percent- not sighted!- is he still around?
In view of the likely absence of a physical cache I won't log all the trackables that visited, however in view of the existence of a geodetic marker here I will record the visit by a geodetic marker geocoin.
TFTC.

Usually have 2 GPSr with me, as the Garmin is more accurate and the Iphone 3gs is a bit dodgy not as good as the Iphone 4, but its good at getting upto date info)

lat long S41 8.230 E 174 49.698
GPRS Garmin etrex 2.14
Time/Date 30/7/2011 14:30
EPE 5.0m
Waypoint time 5 minutes

lat long S41 8.221 E 174 49.699
GPSr Iphone 3gs 4.3.2 (8H7)
Time/Date 30/7/2011 14:30
EPE 7.6m
Waypoint time 5 minutes

Had a quick look for the GC, but no luck finding it.
TFTC

41 08 244
174 49 696
2 2
5 3
26 4
15 4
29 4
21 5
29 4

6m accuracy

Found this with Bkj97 and Lil Blue Hen as part of our big day out. TFTC

Found with Little Blue Hen whose beady little eyes were needed to read the details on the Garmin. Richargr used his identical garmin so it will be interesting to compare. Details
41 08.222 174 49.687 Garmin Nuvi 500 with topo chip inserted in walk mode; 2.30ish pm 25/6/11; GPS said 7 m accuracy;Sat gps on kerb for up to 5mins (didn't actually note with accuracy!); Satelites 2 = 60% 5 = 80/100% 15 = 80% 18 = 100% 21 = 80% 26 = 60/80% 29 = 80/100%
Have generally found the nuvi very accurate in city/high buildings locations eg London but Richargr and I noted some discrepencies earlier in the day between our identical units. We recorded these today independently.
Didn't disturb donkey or trinkets. Thanks for an interesting diversion on the way to Yeetrees event.

With Bkj97 so details identical to his log. Without my eyesight he would have been lost in space. Interesting check of the equipment as being a luddite I usually rely on chicken intuition rather than these new fangled devices. T4TC

Garmin GPSMap 62s - Software version 2.80
Approx 5 minutes at site at 1920 hrs
S41 13709 E174.82828
See screen print for satelite and gps error details.
Given the previous logs I didn't bother looking for the physical cache.
TFTC

After the previous logs, we didn't even try to look for the cache.
Readings (using StreetWalker's Garmin 60CSx - I didn't think my yellow Etrex was quite up to the job)
co-ords: 41.13709 174.82826 (accuracy 4m)
satelittes: 4,9,17,20,24,27,28,32
date/time: 10:34 14 May 2010
TFTC

#2233.Readings from a Garmin 60CSx:
co-ords: 41.13709 174.82826 (accuracy 4m)
satellites: 4,9,17,20,24,27,28,32
date/time: 10:34 14 May 2010
TFTC

No luck with the cache either, but here are the rest of the statistics.

Lat/Long: 41.13705, 174.82828
GPS: Garmin etrex, version 2.14
Time/Date: 16:23, 1 May 2011
Accuracy: 7m overall - Fluctuated between 1.52 m and .76 m from actual site when there.
Waypoint time: approximately 5 minutes
Satellites in use - 4, but no way on this GPS to get more details than that.

Thanks for an interesting cache/exercise!

Found the pin but not the cache.

Used a Garmin etrex Vista HCx

Coordinates S 41.13705 E 174.82828
Accuaracy 3m

Sattelites 7,8,11,17,24,26,28

TFTC.

Found the pin but not the cache. Used a Garmin 60c.
Co-ords were:
41.13707
174.82826
accuracy: 4m
Sattelites were: 26, 17, 80, 7, 11, 24, 28
TFTC!

Quick stop while driving north out of the city, using a rubbish Garmin Dakota 20.

GPS Make & Model: Garmin etrex Vista HCx
Device Software:
Time / Date: 02/10/2010 13:21
Reported Location: S41° 08.224' E174° 49.696'
Reported Accuracy: 3m
Waypoint Time: 2 minutes

See the attached photo for satellite details

What an interesting idea. While we didn't find the cache, we did successfully measure and record the ambient conditions and our location. Considering I got my iPhone 4 delivered a few days ago, we figured it was the perfect time to complete this cache and see just how accurate this device is.

GPS Make & Model: Apple iPhone 4 Black 32GB
Device Software: iOS for iPhone 4.0.2 (not jailbroken)
GPS Software: Geocaching by Groundspeak 4.0.2
Time / Date: 0848 28.8.10 Saturday
Weather: Sunny & north-westerly breeze with scattered high cloud
Reported Location: S41° 08.224' E174° 49.694'
Reported Accuracy: 5m (pretty darn good for a Assisted GPS)
Waypoint Time: 2 minutes

We will hopefully revisit this site again when we receive our Garmin Oregon 550. TFTC!

Liked this one.

I was using a brand new Garmin GPS62.

Screen shot displays the rest of the info,

TFTC

Decided to take an averaged reading like we do when cache placing and so averaged it over 200 readings as that is what we are normally happy with. Averaged accuracy was 2.4m when finished and the co-ords were S41 08.225 E174 49.696 on our Garmin 60 CSx
Eight satellites locked on including 09 14 18 19 21 22 24 27 Accuracy of gps read +/-3m

Great cache concept, thanks for setting it up. +/- coin

no actual cache in evidence - our GPS (Garmin Dakota 10) brought us to within a metre of GZ and showed 1m on the screen so i guess that's not too bad - couldn't get it to 0m tho. Waypoint reading was S41 08.225 E174 49.697 - it was an interesting experiment TFTC

Visited this cache location last week and noted the details on pointy device but didn't get the opportunity to look for the actual cache. Returned today to find the actual container, poked around the base of a number of poles with no luck.
Lat / Long: 41deg 08.224S 174deg 49.694E or -41.137067 174.828233 (used the LINZ Detailed Online Converter to convert the points - http://www.linz.govt.nz/geodetic/conversion-coordinates/online-conversion-service/converter/index.aspx?advanced=1 )
GPSr Make: eTrex H
Time / Date: 15 June 2010 at 12.08pm
EPE: 2.5m
Waypoint Time: Approx 1 minute. No averaging
Satellites in Use: (refer photo)
02 - 100%
04 - 100%
05 - 100%
09 - just reading
10 - 80%
12 - 100%
13 - just reading
17 - 60%
23 - just reading
27 - just reading
30 - 70%
48 - just reading
Extras: none

This entry was edited by SAROC on Monday, 21 June 2010 at 04:25:35.