IssueTracker

We are geocoding location data for one of our customers, the police department in Worcester MA where the locations are coming from public safety incidents.

QUESTION 1:  Why in the past when we have left out zip and lat / long did addresses that contain the string "MAIN ST" get geocoded correctly and no longer do?

QUESTION 2: Can you update your system so when we send "MAIN ST" as the street name (as opposed to "MAIN STREET") and WORCESTER MA      as the city and state, that it will ensure that what is returned is a location actually in Worcester?  Read on for the full story.

DETAIL:

Their system does not record a zip code or geo coordinates for their addresses so we can't send that along for geocoding.  

Locations are not geocoded correctly when the address spells out the street as it shows in their system "Main St".

This seems to only be happening for addresses on Main.

For locations geocoded before Feb 2024, they were geocoded correctly when sending the street name as "Main St".

For locations geocoded after Feb 2024, they were geocoded incorrectly when sending the street name as "Main St".

Locations are geocoded correctly when we query their system, and then change "Main St" to "Main Street" before sending it to get geocoded.

Here are 3 examples of what we are sending (SOURCE),
what we are getting back (GOOGLE),
and what we expect it to be (ACTUAL).

SOURCE:  826 MAIN ST WORCESTER MA
GOOGLE: 826 MAIN ST SHREWSBURY MA 01545 (incorrect)
ACTUAL: 826 MAIN ST WORCESTER MA 01610 (correct)

SOURCE:  1038 MAIN ST WORCESTER MA
GOOGLE: 1038 MAIN ST SHREWSBURY 01456 (incorrect)
ACTUAL: 1038 MAIN ST WORCESTER MA 01603 (correct)

SOURCE: 1504 MAIN ST WORCESTER MA
GOOGLE: 1504 MAIN ST BOLTON MA 01740 (incorrect)
ACTUAL:  1504 MAIN ST WORCESTER MA 01603 (correct)