An address didn't geocode
What to do when Routelink can't place a stop on the map, or places it in the wrong spot.
Geocoding turns a written address into map coordinates. When it fails, the stop can’t be planned, because Routelink doesn’t know where to send the driver.
Why it fails
Most failures come down to one of these:
- The address is incomplete: no suburb, city, or postal code.
- It’s internal shorthand rather than an address (“Depot 2”, “the usual place”).
- The street name exists in several suburbs and there’s nothing to tell them apart.
- It’s a new development that isn’t in map data yet.
- Typos, or a unit number written where the street number should be.
How to fix it
Complete the address. Adding the suburb and postal code fixes the large majority of cases. On the Plan screen, click the task to open it. Under Address, start typing the full address in the search box and pick the right match from the list, then click Update Task. If the spreadsheet upload flagged the row, correct the address in the upload grid and import again.
Pick from several matches. If Routelink found more than one possible address, the task shows a warning above the address. Click Select Address… and choose the right one.
Search for a nearby place. For places that won’t geocode (farm gates, informal addresses, a loading bay round the back), search for the nearest address or landmark that does. The task’s Notes are a good place for the extra directions.
Send coordinates. If you know the exact location, add latitude and longitude columns to your spreadsheet. Routelink then places the task exactly there and skips the address lookup. See Importing tasks from a spreadsheet.
Fix it at the source. If the same bad address arrives every week from your store or ERP (business management software such as Sage or SAP), correcting it there saves you doing this again. Otherwise it comes back with the next import.
Wrong location, not a failure
A stop that geocoded successfully but landed in the wrong place is more dangerous than one that failed, because nothing flags it. Scan the map after importing. A pin sitting far away from the rest of the cluster is almost always a mismatched suburb.
Still stuck
If an address looks correct and still won’t resolve, email it to [email protected] and we’ll take a look at why.
Still stuck? Email [email protected] and we'll help you out.