Jump to content

rediguana

+Premium Members
  • Posts

    142
  • Joined

  • Last visited

Posts posted by rediguana

  1. I tried posting a note on one of my archived caches with today's date mid morning here (NZ) and it was still logged as the previous day (=American time).

     

    KiwiNomad is correct. All logs are still showing the wrong time when submitted from this part of the world (New Zealand).

     

    I've just created two test logs from here.

     

    1. Field Note. Created at 2013-03-12 16:51 UTC+13. Shows in Field Notes on website as 12 March 2013 08:51:04 - somewhere a whole 8 hours got lost. This method at least gets the day correct, but the field note timestamp on the website is out by eight hours. Hence early morning logs will get posted to the incorrect day. I've now published this log as well. http://coord.info/GLADC9VR

     

    2. Found Log. Created a few minutes later. Shows as 2013-03-11 on the website - a whole DAY out, it should be logging as 2013-03-12. http://coord.info/GLADC9JB

     

    My account settings on the website are: Time Zone: New Zealand : Auckland, Wellington and Show Daylight Savings Time

     

    The iPhone application + website combination are still showing this timezone bug, which has been reported many times in the past, and continues to remain unfixed. This is very frustrating for Australian and New Zealand users of the application. Please fix it.

     

    I also use CacheSense on Android, and it log as found, and creates fieldnotes with correct dates and times, so it is definitely the iPhone (and apparently Android) versions of the app where the issue lies.

  2. The attribute WOULD be helpful...if you are paying attention.

     

    That was my point above - many people don't/won't pay attention to attributes, and you only really get the tools to manage attributes with Premium membership

     

    nor do I feel any sympathy for someone who ends up at the base gate without knowing where they were going in the first place.

     

    You perhaps forget that sometimes, military bases do not show up on online and on GPS maps - particularly in troublesome regions such as the Middle East. These sort of military bases are quite different from military bases at home. ;)

     

    It's not an issues where I live (but even if it were), I would be taking steps of my own to remedy my problem and not expect Geocaching.com to do it for me.

     

    Yeah, see if I was to 'remedy my own problem', it would probably involve "Needs Archiving' logs on all the caches with a direct reference to placement guideline 1.6.4: "The cache is problematic due to its proximity to a public structure, including and not limited to, highway bridges, dams, government buildings, schools, military installations, hospitals, airports and other such locations." They also don't meet guideline 1.1: "This refers to both the placement of the geocache and the journey required to reach it. Geocachers must not be required to cross any land with "No Trespassing" signs, or locally-defined markers that prohibit access."

     

    Not to mention the extended reading of the Fundamental Placement Guidelines.

     

    Geocaches are not placed on school properties or military installations. Generally, schools and the military do not allow geocaching on their property. Further, you should not place geocaches near schools or military installations, as the borders shown on a map may be inaccurate. A cache and geocachers searching for a cache around schools or military installations are likely to arouse suspicion, which may result in a military or local law enforcement response. The costs of any such response are entirely the cache owner's responsibility. See more about other inappropriate placements here.

    I would much prefer that if geocaching.com is going to continue to allow reviewers to list caches on military bases, that Groundspeak implement a global system to opt-in/opt-out of them. Unlike many other geocachers, I have no problems asking for caches to be archived if I think they are in contravention of the guidelines, and that option still remains open to me.

  3. Not sure we would - if cachers are able to access caches on one country's base, they may be able to access other countries bases as well e.g. coalition bases. If a military cacher was opting in, they would be opting in to seeing all MBCs. But it should remain simple for the majority (all non-military cachers) to opt out of them all, in a single, simplified manner.

  4. First Up: This feature request is not in any way meant to be a discussion topic as to the pros/cons of whether caches on military bases outside of the US should exist. It assumes that they will exist. What I am interested in discussing are what changes can be made to the website so that both the US Military cachers, and everyone else is given reasonable tools to manage them. I would ask any forum moderators to delete posts that discuss whether MBC should/shouldn't exist. All I want to discuss is tools that allow the US Military cachers, and those of us that can't, better manage these caches.

     

    Some assumptions:

    • Military Base Caches will (MBC) continue to exist and grow in number
    • Tools to manage MBC should rely on free functionality (e.g. Premium membership must not be a requirement)
    • The massive majority of geocachers (we must be talking 98-99%) will never be able to attempt MBCs.

     

    Option 1 - Ignore Lists (not practical)

    I don't see the Ignore cache functionality being useful. It means that the majority of geocachers have to manually add each and every MBC to their own Ignore list. This may be practical for local geocachers, but it isn't practical for travellers, such as myself, as I may not be aware that the cache is a MBC until I turn up at the gate (remember not every geocacher reads the description before turning up at the listed coordinates) - this could be a very Bad Thing particularly if you're in the Middle East as I currently am. As a traveller, I can't be expected to identify each and every US military base, find all the caches, and add them to my Ignore list before travelling. Ignore lists are just plain inefficient for handling MBCs.

     

    Option 2 - MBC attribute (not free)

    Another option is to create a MBC attribute (when I looked last week, I couldn't see one). At an absolute minimum, every MBC should have a MBC attribute assigned to it - not only for new listings, but also applied to all existing listings. However, attributes are only really useful to Premium Members, as they are the only ones able to filter PQs based upon them, but it isn't possible to filters standards searches or map views based on attributes. This means that this doesn't present a fee solution to managing MBC caches.

     

    Option 3 - a MBC 'membership'

    My thought is that Groundspeak should consider adding functionality that is a little like Premium Membership, except it is a US Military 'membership' - it is, of course, free. (Technically it may be based on having an MBC attribute - something for the hamsters to decide on if they decide to implement this feature).

     

    All caches have a new MBC flag created. It would probably fall to the reviewers to initially flag relevant caches in their reviewing coverage. All caches being listed in future would need the cache owner to tick a box - 'this cache is being placed on a military base, and significant access restrictions apply' (or similar). At some point a one-off database pass would need to be done - any geocacher that has found a MBC as identified by reviewers, would automatically be assigned to the MBC membership. By default, a geocacher does not have US Military 'membership'. This means that MBCs do not appear in any search, map or pocket queries. Any geocacher that has not done a cache classified as a MBC would not be assigned to the notional 'military membership'.

     

    Any geocacher can step into their profile, tick a 'Show me Military Base Cases' box, and become a member of the new group.

    Any geocacher with the MBC box ticked, would then be returned the MBCs in addition to normal caches.

    Of course the My Finds query would ignore this setting, as a cacher may no longer be able to access MBCs, but has found MBCs in the past during their working career, for example.

     

    Then the updated website code would be turned on, and overnight, MBCs would disappear for those that are likely to never be able to find them (remember, this is probably in the high-90%'s), and all those that have found at least 1 MBC would still see MBC's as per normal.

     

    Again, I don't want this to be a discussion of whether these caches should exist or not. But I believe that as they are likely to continue to exist, and that they represent a very asymmetrical usage (I have no idea of the figures, but I'm guessing that only a handful of % of geocaching.com accounts would ever be able to access these caches, yet they are displayed to 95%+ geocachers that will never have the opportunity to find them), that there should be functionality create (that is both free and fair in its use) to enable those that are able to hunt them, to do so, and for those that will never be able to hunt them, to have them simply ignored.

     

    I'm posting this from Qatar, in the Middle East, and found caches within a few km of military base caches. I was most disappointed that I couldn't go cache that nice little cluster on the map :) It is probably a good thing that I haven't had a rental car, and just decided to drive up to the gates without researching that the caches were on military bases ;) I've talked about this issue with local geocachers that live near one or more of these bases, and there is frustration that it isn't easier to ignore/opt-out of these caches.

     

    Again, I'm not wanting to debate whether they should exist or not. However, if they are going to continue to be in place, I think that Groundspeak should at least provide more appropriate tools to Opt-In or Opt-Out of Military Base Caches.

     

    Cheers Gav

  5. It was great meeting everyone at the event last night, and sorry I was a bit late getting there, the weather impacted the flight plans just a little ;)

     

    I managed to get a handful of Postbox caches after the event on the way to the hotel. Yes, very much looking forward to the safari, and the niggling travel cough has nearly gone! :)

     

    Also looking forward to caching with cincol in Doha - still amazed at how small a world geocaching can make it! :D

  6. OK, that's not a train smash as we have an event on the 6th :) I am sure we can organise a few hours of caching in the Doonside area on either the Thursday or the Friday, and possibly also a lift to & from the event if you are stuck for transpoirt. Watch this space :D

     

    Oh, this sounds like it could even work for the event. My flight lands at 1800 on the 6th. I won't have my own transport on Thu/Fri, so if there is any chance of a ride, that would be awesome. I have bribes available ;)

     

    And I've just had an 'awww crap' moment. Not only is the Mega in Pretoria, but it is also the same weekend that the ABs are playing the Springboks in J'burg. That is just cruel! :)

  7. Without knowing where you will be based, it is difficult to give accurate advice :) ... Please post your dates and where you will be staying - perhaps we can even organise an event so that you can meet the locals - some local cachers may even be keen to take you out for a day of caching.

     

    I will be spending a couple of nights down at Doonside, Thu/Fri this coming week, after that I'm on an organised safari. I've been pretty busy up till now to get onto any planning. Unfortunately that means it will be well inside the 2 week guideline for listing event caches.

     

    The best opportunity to meet local cachers is unfortunately going to be a weekday, this coming Friday 7 SEP. I'd love to go caching with some locals, but also understand that it is a workday :)

  8. I'm going to be visiting South Africa for a few days in the near future. I'll be staying near Durban for a couple of nights, and then will be doing a short 3 day safari before flying out (alas unable to spend more time in SA this trip). This will be my first time to Africa and South Africa. I'm keen to try and grab a cache or two. I have done a little reading on security in South Africa, and so am aware of most of the risks.

     

    Any tips or advice would be most welcome! :)

  9. When I'm urban caching, for example, I like to find paths between houses that lead to greenspaces where caches are located. OpenStreetMap often doesn't show those paths, but I usually can spot them with the satellite map.

     

    And here is why OpenStreetMap is cool - one cacher has found the path, they can edit OSM, add the path, and the next cacher will be able to find it. Without using the satellite imagery. So if OSM doesn't show them, you can add them fairly easily.

  10. OK. The best reason I can think of is that the concept of Nearest changes over time based on how many caches one has done. If one is starting off in a cache-dense city, it may make a lot of sense to be able to set a starting nearest distance of only 5 or 20km, for example. Over time, as the near caches are found, the cacher should be able to expand the distance, e.g. to 50 or 100km depending once they've cleared out the nearer caches.

  11. As someone that travels a fair bit, I had been looking forward to being able to download the caches via email whilst on the road. As a traveller, downloading via email is often the quickest and easiest means of getting new caches.

     

    I can see the download system working fine for caching around home when you've got time and guaranteed internet access, but this isn't always easy when travelling in another country. A direct-connect GSAK is fine at home, but may not work as well when on the road - sometimes you just want to dump the GPX file directly on the GPS. Being able to retrieve the PQs along with other email is still the easiest approach - especially for those of us that have some email scripts set up to automate our workflow :D

     

    So, sorry to other cachers, but I'm probably going to be sticking with twice as many 500 cache PQs so I can still easily receive caches on the road with a simple email download.

     

    Cheers Gav

  12. I'm currently planning a trip to the US for a few conferences and meetings, and the first day I've got available to go caching looks like being Thursday the 15th of October in Cleveland, OH. I'd like to meet some local cachers, and go out caching with them, and was wondering if anyone felt like doing some caching in and/or around Cleveland on that day? I'm coming all the way from Christchurch, New Zealand - yes, I do have a funny accent :)

     

    I've got a three day conference at JCU Friday-Sunday, that includes drinks at 8pm on Thursday night, so would have to be back in town by 7pm or so.

     

    I don't mind whether it is a casual or slighly more numbers-focused day. And if you want to have some (small) trackables brought back to be released in New Zealand, I might just be able to arrange that as well :D

     

    Cheers Gav

  13. I'm personally glad to see ALR caches go. I have always argued here in NZ that if you get your name in the logbook - you can log the cache. If you want me to do something additional, then you better weave it in on the way to finding the container and logbook.

     

    My only minor concern now is that of changing an ALR from a unknown to a trad once the ALR has been removed. Surely that is unfair on all cache finders that have found the cache as an unknown, as it will be converted back to a trad, when in reality it was more than that when it was found?

     

    I'd suggest that the ALR caches be left in their current state, or archived and relisted as a trad. Much as a puzzle that has had the puzzle removed and now just has the final coords listed.

  14. Nice. Great to see an 'official' app that is able to use the website.

     

    The two biggest things I would like in an iPhone app are...

     

    1. Multi/Puzzle aware - one that can be used for recording notes, adding waypoints and navigating to them whilst out in the field.

     

    2. An ability to upload GPX files so that the device can still be used in out of range areas. You don't have to go far places in NZ to lose coverage. And not all of us actually have data plans either.

     

    Cheers Gav

  15. Wow - great effort getting the US maps off the ground. I got pointed to this thread a New Zealand project that does similar (our maps are already auto-routing - you've got that to look forward to at some point).

     

    I wanted to just pop up a couple of ideas for those that are doing the hard work behind the scenes building these maps.

     

    If you can, look at using OpenStreetMap as your repository. As a previous poster mentioned, they have imported TIGER data already (although it may not be 2008 yet, I imagine they'll update it soon). OSM also has excellent processes and tools for people to update the raw map data by uploading GPX tracklogs, and improving the data themselves. This will provide you with a massive infrastructure for sharing the maintenance of the map data. Also, OSM is improving tools for producing Garmin map files, from OSM data.

     

    I think over time that OSM is going to become a natural worldwide repository for mapping data.

     

    Cheers Gav

  16. Yellow Seahorse - Rediguana

     

    Wow, how completely random and an unexpected surprise! Certainly brought a smile to my day! Thanks to Cheesy Pigs for nominating me!

     

    Congratulations to everyone else that got nominated and those that were lucky like me.

     

    Finally, thanks to Dorkfish for running the contest!

     

    Cheers Gavin

  17. If someone is interested in following this up, go to the website (hosted on an offical gov.au domain), and make a phone call to the CFA to check it out. If you don't trust that, then look the number up in a phonebook or online directory...

     

    Compare

    http://www.cfa.vic.gov.au/contact.htm

    to a search on http://www.whitepages.com.au/ for country fire authority, state victoria

    for example

     

    You should also be able to crosscheck with URISA - http://www.giscorps.org/ as I believe the project is being organised by them. It fact it may even be better to donate the GPS directly through URISA GISCorps.

     

    I'm not suggesting that someone should donate in this case with no research, heck I wouldn't. But given our interests in GPS, I can at least post a lead for others to follow up on if they so choose. Thanks for the friendly reminder though Kermode.

     

    Cheers Gav

  18. One of the lists I belong to just had an email come across where a GIS analyst is going to Sri Lanka to help with the recovery from the tsunami. They are looking at getting 80 GPSR's to create a local capability to collect spatial information for including in the GIS to be developed. Twenty have been donated to date.

     

    If anyone is looking at getting a new GPS and wants a very worthwhile home for their old GPS, I can think of few more deserving uses. It is quite a donation to make however.

     

    The contact email is r.shamir at cfa.vic.gov.au - this is the Country Fire Authority in Victoria, Australia for those curious.

     

    2005.02.01

     

    Ron Shamir

     

    CFA

     

    Dear Mr. Shamir,

     

    The Survey Department would very much like to take advantage of your services as a volunteer GIS coordinator, working between all the government, UN and NGO agencies currently involved in the post Tsunami assessment and reconstruction activities in Sri Lanka. This will help us continue the valuable work begun by the UK-based MapAction team, who left Sri Lanka a short while ago.

     

    There is a considerable amount of work to do in harmonizing GIS information, coordinating the collection of GPS data, and in the use of air photography and remote sensed imagery for different applications. We will be very happy to provide you with office accommodation at the Survey Department and look forward to working closely with you. We understand that you will be available for up to 3 months.

     

    We understand that you may be able to bring a considerable number of handheld GPS units, kindly contributed by Australian organizations, and we would appreciate this very much as we have insufficient for our needs in the field.

     

    Yours sincerely,

     

    B.J.P. Mendis

    Surveyor General

    Survey Department of Sri Lanka

     

    PS: Ron has secured 20 GPS units of the target of 80 needed for the project.

     

    Jim

     

    Cheers Gav

×
×
  • Create New...