> Well actually XY2 19AB is invalid. Postcodes only have one digit in > the second half, so it's always possible to insert the space correctly > as the fourth character from the right.
Sure, we know that, but if the geocoder is presented with a string that is not a valid postcode format, results could be unpredictable. Should we expect it search for XY2 or XY21 ? If it is looking for a non-existent XY21, should it consider XY20 a closer match than XY2 ? Should it treat it as a postcode at all, and instead find a building address, 19A or even 219A ? Its just a variant of GIGO. -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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/google-maps-api?hl=en.
