Since Google doesn't support "structured" postal addresses (or name for that matter) so we have to make a guess at what the various fields are. We've spent quite a bit of time on this, and it works pretty well for US and Canadian addresses, but starts to degrade with addresses that are formatted differently, and formatting varies widely from country to country.
If you could post a few examples of addresses that are not parsing correctly (with any private data stripped out) I could see if we could tweak the parser to work with them better. The ultimate solution will be for Google to support structured addresses in their Contacts API, something we and everyone else who uses the API is eager to see. Thanks, Charlie On Mar 7, 9:27 am, Yevgeny <[email protected]> wrote: > Google incorrectly assigns address fields set in Address Book. > > First, I set up an address in Address Book. Then sync it with Google > using Spannig Sync. After Google syncs with my iPhone, I see that > 'country' is in the 'region' field, 'zip code' is placed after the > city name (both are in 'city/town'). > > Then I reassign values on the iPhone: manually select a 'country', > place a 'zip code' where it belongs. Now iPhone syncs through Exchange > with Google. And in my Address Book (updated with Spanning Sync) I see > an address added with incorrect field values: 'city/region' contains > 'country', 'city' is at the end of the 'street', 'country' is unset. > > Any plans to fix this? Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Spanning Sync" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/spanningsync?hl=en -~----------~----~----~----~------~----~------~--~---
