> Try this "1, Ringel Taube Street, Nagercoil" > in:http://koti.mbnet.fi/ojalesa/boundsbox/geocode_basic_3.htm > &http://code.google.com/apis/maps/documentation/javascript/examples/pl... > > Former can at least detect "Nagercoil", but the Google's example > can't.
Yes, they work in different ways. The geocoder knows nothing of Ringel Taube Street. So the Autocomplete example gets lost at "1, Ringel T" and has no suggestion to offer to complete the address, as it knows no address beginning with that. That's how it is supposed to work. The 'buttonless geocoder' example works in a different way, it tries to do a simple geocode of the whole address typed in so far. It also has no at all suggestions for "1, Ringel T" But when you get to "Nagercoil" the placename part is recognised, and can be geocoded. Note that the Ringel Taube part is completely ignored. We can get the same end result with "99, Banana Alley, Nagercoil" Geocoding an address that may contain some unrecognised parts is _not_ the same task as offering autocomplete suggestions for an unrecognised address. The most simple geocoding example at http://code.google.com/apis/maps/documentation/javascript/examples/geocoding-simple.html demonstrates the same result > > Can this behavior be fixed in Google's API or any patch to fix > Google's example to behave like the above? TIA > > -- > <?php echo 'Just another PHP saint'; ?> > Email: rrjanbiah-at-Y!com Blog:http://rajeshanbiah.blogspot.com/ -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
