Kind of related, I'm really disappointed at Google Maps's inability to deal with my country's addressing scheme. We practically have two parallel systems in use: the usual street+number, and district+number. Almost without exception, the latter is used only for blocks of flats and other residential buildings built under the former communist regime. Each building only has an actual address in one of these systems, i.e. either it's directly on a street and given a number, or it's offset from the main street with a small unnamed side street going to it and given the next sequential number for the district, or it is on an actual street, but the street doesn't have numbers or a name posted. This does mean that buildings in the district+number scheme are practically plopped at random and there is no guarantee that N will be next to N+1 and sometimes a building gets an extension and the extension's number is N-A. Sometimes you have a pair of buildings planned and N-A and N-B allocated for them, but then N-B gets cancelled and you only have N-A...<p>Paper maps work by having a reference on the back telling you at which rough coordinates building N in district X is and our homegrown online maps simply have all the GPS coordinates for every building.<p>However, in Google's case, half the time it fails if I write "City, district number". It knows, say, building 219, but not 220, even though they're right next to each other. It seems to treat the entire "district number" string like a property name, like if you have a property called "the awesome steakhouse" and type "the awesome steakhouse" in maps, it shows you where the awesome steakhouse is in the city.<p>/rant