Nice tip Pil. However, this is not really an acceptable situation. Taking into account that work has been undertaken by Google to improve coverage in Europe, notably in France, this should not occur. Our users will not have the reflex to do this kind of manipulation - which will give a bad image to our sites, even if it is out of our control.
The user will not make the difference between our sites and Google, they only see our site. Do we need to open a bug report ? Do we need to send a problem report to Thor Mitchell ? On Oct 10, 3:54 pm, Pil <[email protected]> wrote: > Try > > Orange, Orange, fr > > (An old trick seems still working in this case.) > > On Oct 10, 11:07 am, Andy Newby <[email protected]> wrote: > > > > > > > > > Hi, > > > I'm using Geo-Coding to grab a lat/lng value for a place name entered, and > > then searching our external DB. However, it doesn't seem to wanna find a > > place called "Orange" in France, which I can find fine on the main site: > > >http://maps.google.com/maps?q=orange&hl=en&ie=UTF8&ll=44.128014,4.965... > > > Here is the place it gives an error: > > >http://www.chambresdhotes.org/cgi-bin/links/page.cgi?g=Google_Maps&t=... > > > I'm making sure I pass in lang=fr to force it to use french spellings > > (otherwise we have weird errors, like other place names not being found). > > > This issue also applies to GMaps v2 API (I havn't updated this page yet to > > the v3 one) > > -http://www.chambresdhotes.org/Google_Maps/?q=orange&radiusSelect=30&s... > > > Anyone got any suggestions? > > > TIA > > > Andy -- 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.
