How do I fix the geolocation of an address?

EasyRoutes uses Google Maps to geocode a stop address to a latitude and longitude. While Google Maps' accuracy is generally high, there can be occasional edge cases where the address does not validate correctly. EasyRoutes will also attempt to flag some of these cases directly on a route:

Do you have an order or stop where Google Maps is returning a pin in an unexpected location? Try the recommendations below.

Recommendation #1: See if removing the second address line fixes things

A common case we've noticed is customers entering additional details in the second address line that confuses Google Maps. You can also use this approach for other address geocoding issues beyond the second address line.

  1. Edit the stop.
  2. Check the "Display the following as the address on route instead" check box.
  3. Clear the second address line.
  4. Click Preview at the top of the page to see if the pin is now in the correct location.
  5. Click Save.

Recommendation #2: Use manual latitude / longitude

If manually editing the address is not getting the result you desire, you can switch to manual latitude / longitude mode.

  1. Edit the stop.
  2. Under Geocoding, select the "Use the latitude and longitude values below for your stop coordinates" option.
  3. Enter latitude / longitude in the form or click on the map at the top of the page to set the latitude / longitude to a new pin.
  4. Click Save.

Recommendation #3: Use Plus Codes

Some regions of the world may find using Plus Codes easier. You can find out the Plus Code by clicking a location on Google Maps or looking up the address in Plus Codes Maps.

  1. Edit the stop
  2. Clear all existing address fields.
  3. Determine the Plus Code for the location in question:

  1. Enter the Plus Code into the Address field.
  2. Enter the associated city and province or state into the City and Province or State fields.
  3. Click Preview at the top of the page to see if the pin is now in the correct location.
  4. Click Save.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.