Jump to content

H_M_A

+Premium Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by H_M_A

  1. What can I do or whom can I adress if my communication to an earthcache reviewer (geoawareUSA2) seems to fail?

    He/she does not respond to any logs in the unpublished listing nor does he/she answer onto my email letters. So again:

    - What can I do to overcome this bad situation??

    - Whom can I adress to get my earthcache published (it's already in the queue since early january and we already cleared several misunderstandings. Now a single point had to be changed to get the earthcahce published, it was changed by me 2 weeks ago, but nothing happened)

    • Upvote 1
  2. I had found out how to use field notes to pre-log found geocaches in some situations. This Feature is very useful in my opinion. My question now is if this works also with logging TBs/GCs in the different situations.

    - If YES which entries are needed and how is the expected format?

    - if NO is there any reason for not to allow it??

    Would be great to get an answer, my situation - as told above - is when visiting certain caches with my >10 geocoins and having to write the logs after these visits.

  3. I have found a simple Format Problem when using your 3 most interesting searches (Events, oldest geocaches, geocaches with favorite Points). The Problem is that my home coordinates (something near 48.xxxx 10.yyyyy) are used in a "wrong" Format will say it is used with a delimiting comma instead of a decimal Point. This Looks like 48,842266, 10,100942 (this is a direct copy out of the search window) and - of course - it leads to a DNF. When I correct the given coordinates by simply entering a decimalpoint after the 48 and 10 the search works, but unfortunately not the 3 given most favorite searches. Please try to correct - I'm sure These searches are also if interest for me!

    Thanks in advance H_M_A

     

    What browser are you using? Sounds like the browser is providing that format of coordinate. Or if your computer's localization settings say to use "," instead of a period for decimal values, Groundspeak can't change that.

     

    But, they could add a check on their end to see - if a coordinate can't be determined - if replacing commas with periods makes a difference.

     

    Hi thebruce0, I am using IE11. May be the browser provides that Format of coordinates, but where do These values come from? I was sure that the search function uses the values stored and found in my personal Profile on geocaching.com. But - of course - this is stored in a format like N nn° mm.xxx' and NOT as used in the search function which looks like N nn.mmmm°. So I am not sure where my home coordinates are coming from when being used in the search window. Normally all windows dealing with my home coordinates in the geocaching.com environment are working perfect. Why is there a difference now?

    When you propose a check at Groundspeak's end - if a coordinate can't be determined - that would be a great help!

  4. Read the previous release notes

     

    We're excited to announce that the new Search tool is now available to all Geocaching members. It's faster, easier to use and helps you find the exact adventure you want—and it's all thanks to the geocaching community. Geocaching Premium members took a sneak peek at the new tool and we appreciate all the feedback and suggestions we've received to date!

     

    Go ahead and take it for a spin by searching for Pi Day events and Mystery Caches near you so you can earn your Pi Day souvenirs on March 14.

     

    While you’re at it, be sure to test drive some of our favorite searches:

     


    •  
    • Find the Mystery Caches you have solved, but not yet found.
    • Plan a geocache outing with your geocaching buddies.
    • Find the most Favorited geocaches in your area.
    • Find geocaches in your state with the D/T combination that you need to complete your Fizzy Grid.

    And don’t worry. We know you’re excited to download these powerful searches to your GPS device and/or sync them with the Geocaching app. (We are 100% with you there!) Our team will be working hard on building this functionality into the Search tool in the near future.

     

    Visit this FAQ to learn more about Search (including how-to’s for all our favorite searches).

     

    And speaking of new upgrades to Geocaching.com, check out the new Hide a Geocache page. It’s designed to be more helpful for new geocache hiders and streamlined for seasoned geocachers.

     

    I have found a simple Format Problem when using your 3 most interesting searches (Events, oldest geocaches, geocaches with favorite Points). The Problem is that my home coordinates (something near 48.xxxx 10.yyyyy) are used in a "wrong" Format will say it is used with a delimiting comma instead of a decimal Point. This Looks like 48,842266, 10,100942 (this is a direct copy out of the search window) and - of course - it leads to a DNF. When I correct the given coordinates by simply entering a decimalpoint after the 48 and 10 the search works, but unfortunately not the 3 given most favorite searches. Please try to correct - I'm sure These searches are also if interest for me!

    Thanks in advance H_M_A

  5. Hello,

    your problem is caused by the API. In PQs the "corrected coordinates" are submitted to your device. But your application (GC-app, c:geo, cachebox etc.) searches for updates (for example new logs) and uses the API. Unfortunately the API wasn't changed until now, it returns always the original coordinates.

    see FEATURE

    Best regards

    Andreas

    Hi there,

     

    is there a chance to get the API being corrected? All the discussed workaround require action long time ago when seen form the actual find tries. I will try out the given solution by using a PQ - but to be honest - this is not what I really expect.

    Kind regards,

    Herwig aka H_M_A

×
×
  • Create New...