• Resolved miwamediatack

    (@miwamediatack)


    Hallo Zusammen,

    in der aktuellen Plugin Version 2.2.241 werden die Geokoordinaten (Latitude/Longitude) anhand der Adresse ungenau berechnet, so dass im Frontend die Marker in der Karte von der eigentlichen Adresse abweichen. Mal sind es wenige hundert Meter, aber vereinzelt auch Kilometer. Wenn im Store-Eintrag die “Wegbeschreibung” angeklickt wird und man zu Google Maps weitergeleitet wird, wird bei Google der korrekte Standort der Adresse angezeigt. Wir haben recherchiert, ob es an ungew?hnlichen Angaben im Stra?ennamen oder dem Ort liegt, aber da ist keine Unstimmigkeit festzustellen, da auch bei einfachen Adressangaben die Berechnung der Geokoordinaten abweicht.

    Beispiel:
    Suche PLZ “09120”; Umkreis “10 km”; Store “Stephan Gro?mann”
    Adresse: Elsternwinkel 4, 09125 Chemnitz
    Abweichung: ca. 600 Meter

    Bei aktuell 1918 Store kann das nicht manuell geprüft werden und die Stores werden w?chentlich importiert.

    Vorab vielen Dank für Ratschl?ge und Tipps zur Problembehebung.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter miwamediatack

    (@miwamediatack)

    ### TRANSLATION ###

    Hello everyone,

    in the current plugin version 2.2.241 the geocoordinates (latitude/longitude) are calculated inaccurately based on the address. This causes the markers in the map to be placed differently from the actual address in the front end. Sometimes it’s just a few hundred meters, but sometimes it’s kilometers. If you click on “Directions” in the store entry and you are redirected to Google Maps, Google will display the correct location of the address. We have investigated whether this is due to unusual information in the street name or the location, but there is no discrepancy. This is because the calculation of geocoordinates differs even for simple address details. With the test function (Geocode API Response) of the plugin, the geocoordinates are calculated correctly based on the address.

    Example comparison

    Google Maps coordinate
    adresse: Brücker Str. 120, 14547 Beelitz
    Lat: 52.24399482786793
    Long: 12.956775385470591

    Calculation of the plugin when creating or importing manually
    entered address: Brücker Str. 120, 14547 Beelitz
    calculated values: Lat = 52.311807 / Long = 13.029697
    results in address: Potsdamer Str. 51A, 14552 Michendorf ?

    Test function of the plugin
    entered address: Brücker Str. 120, 14547 Beelitz
    calculated values: Lat = 52.2378413 / Long = 12.9575279
    results in address: Brücker Str. 120, 14547 Beelitz ?

    With currently 1918 stores, this cannot be checked and corrected manually and the stores are re-imported on a weekly basis.

    Thank you in advance for any advice and tips on how to solve the problem.

    farroyo

    (@farroyob)

    Hi there, thanks for writing.

    You can do some simple checks with a tool that we include in the plugin settings page. If you scroll near the end you will see a button labeled “Input location details” where you can search for an address and see the raw response from the Google Maps API.

    I did just that with the address “Brücker Str. 120, 14547 Beelitz” and I obtained the following coordinates (52.2378413, 12.9575279), which are identical to the ones you propose as valid. See the following screenshot of the tool I mention.

    Please try it yourself and double check that you are getting the exact same coordinates.

    Also, please check that you have the right map region in the settings, as it can influence the accuracy of the geocoding results. It should be set to “Germany” in your case.

    Let me know what you find out.
    Best regards,

    Thread Starter miwamediatack

    (@miwamediatack)

    Hi there, thanks for your reply.

    We have found the cause. It was not a faulty behavior of the plugin, but we had entered a store name in the WPSL Fields “address” (mandatory field) and only the address in the WPSL Fields “address2” (address suffix optional). This meant that the calculation could not work correctly.

    We have corrected this and the correct geocoordinates are now also determined.
    So the fault lay with us. We apologize for the inconvenience.

    Thank you very much for your efforts.

    Best regards

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.