Thanks @jobs, I figured it out eventually. Turned out to be a Google Geocoding bug

1 Like