Suggestion: Add info on OpenCageData key to plugin description page

  • Hey,

    Thank you for sharing this nice plugin with the WordPress community and thanks for the time and effort for maintaining and enhancing it.

    I suggest to add some information on the access key of OpenCageData.com to the plugin’s description page. It seems that the key is required to make OSM maps work in the backend? That could add some transparency for users and help them understand what the key of this third party is required for. What are your thoughts on this?

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Stonehenge Creations

    (@duisterdenhaag)

    Hi @sankari,

    First of all, thank you for your kind words about that plugin. I really appreciate it.

    It just so happens that I am about to release an update for EM – OpenStreetMap (version 5.0.0) and in the new version I have added several help texts.
    Here’s a screenshot of the new info in the Plugin Options Page:
    https://snipboard.io/T63RKO.jpg

    Please let me know what you think about this new introduction.

    About the OpenCage API key requirement.
    Before releasing the very first version of this plugin I tested many geocoding providers, because there had to be some way to determine the coordinates, of course.
    I finally decided to use OpenCageData, because not only were their search results the fastest and the most accurate, they also seemed to be the only geocoding service that returns the result in your website’s locale. Another reason was that OpenCageData offers a free key with a daily limit of 2500 calls.

    When you are creating a new Events Manager Location, this plugin will only call the OpenCage Geocoding API with a full search query when you click the “Find Coordinates” button (formerly labeled as “Search Address”). That click is counted as one credit.
    Events Manager then saves the retrieved coordinates to the wp_em_locations database table. By reducing the search queries to just one (instead of by keystroke) the free limit of 2500 calls is hard the reach. ??

    I will take your advise and include an explanation about the OpenCage API key requirement in the plugin description for the upcoming release, because I agree that could use a little more transparency.

    Thread Starter sankari

    (@sankari)

    Thank you very much for your friendly and fast support ?? …and for the screenshot of the next release.

    It looks good to me and the new intro makes things more clear.
    (Just an insignificance, bare with me: I don’t know if I would write “Locations” with an upper or lower case “L” in that case. Maybe lower case? Not sure.)

    The call saving method is smart – I like it! <3

    What also crosses my mind: Your plugin is attractive for privacy-aware people, so transparency is key. If data is called from a third party provider people might want to know if/what data is exchanged and if – by using an OpenCage API key – the plugin is still GDPR compliant. Could it be declared in the FAQ section?

    Looking forward to your reply. Have a great evening!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Suggestion: Add info on OpenCageData key to plugin description page’ is closed to new replies.