Jump to content

Loki-84

+Premium Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by Loki-84

  1. No, the changed coordinates stay changed when you open the listing of a cache you already found. It is only displayed at its original location on the map.
  2. I included the new GS checker as well as an 3rd party checker in my new cache. I just wanted to see what it is like. In its current form I will not use the GS version for any upcoming caches as the disadvantages outwheigh the advantages. Must-haves for me to include the checker in future caches would be: Stats: Successes and fails (at least for the CO) and entered coordinates (CO only) Success page: I'm not sure the 'unhidden Waypoint' solution would suffice because I think most people wouldn't even look at the information displayed there. But it would be better than nothing. A real success page (or maybe a pop-up) could also include an option to correct the listing coordinates or not. Fuzzy matching and checker coordinates =/= final coordinates: My first cache actually uses both, you have to find a specific intersection (fuzzy matching) in order to see the cache coordinates that are somewhere else. Nice-to-haves would be: Checkers for letterboxes (since most of them are actually mysteries with a stamp in them, at least in my area). For multis I would prefer a system that facilitates the coordinate calculation. Something like: go to stage 1, find A, enter A in the app, the app puts A into the formula for stage 2 and displays the resulting coordinates (without verification) but that's another topic and much more difficult to implement. optional single-field entry: It can be more convenient in some cases but I also use the multi-field entry on geocheck.org Get rid of the reCAPTCHA Make it smaller What I like about it: Easy to integrate Easy to maintain Automatic coordinate correction (I use coordinate correction a lot but it would be fine with me, if it can be opted out).
×
×
  • Create New...