Navigon MobileNavigator & Navigating to Contact's Address with Apartment Number Fails

[SirWinston]

Has anyone else noticed that when you use the Contacts option (i.e. going through your address book) to navigate to an address, and that address has an apartment number in it, MobileNavigator (MN) fails miserably? (This at least happens with 1.6. I don't know about previous versions.)


Lets say the address is:
71 Avery Rd
#12 (or apt 13, or Unit B, whatever)
Atlanta, GA 30309

MN will respond with:
1) navigate to "Atlanta, GA 30309" (and completely ignore the address), or
2) "The address for this contact was not found in the map database" (even though, a) the house has been there for over 100 years and b) if you type in the address, sans apartment number, through the traditional route it will find it just fine).

 

[ideefixe]

Yes, I've noticed the same thing, drove me crazy.

It will work if you leave no space between APT and the unit number:

71 Avery Rd
APT12
Atlanta, GA 30309

 

[LiquidZed]

Has anyone else noticed that when you use the Contacts option (i.e. going through your address book) to navigate to an address, and that address has an apartment number in it, MobileNavigator (MN) fails miserably? (This at least happens with 1.6. I don't know about previous versions.)


Lets say the address is:
71 Avery Rd
#12 (or apt 13, or Unit B, whatever)
Atlanta, GA 30309

NavAssist in the AppStore will solve this issue. It strips the apartment numbers off (with some basic rules, what you describe above it will handle), but the next version (soon to be released) will work with almost any format and have google mapkit integration (soon to have local search hopefully). Check out http://liquidzed.blogspot.com. The next version will have google maps integration.