On May 1, 4:17 pm, "[email protected]" <[email protected]> wrote: > Andrew, you misunderstand what I wrote. I was quoting > "sensor=true_or_false" because that is how it's specified in the > example, but self-evidently one is expected to select one or the > other, ie sensor=true OR sensor=false. > Seehttp://code.google.com/apis/maps/documentation/introduction.html. > > My own code has sensor=false as I'm not using one. The correction I > quoted, replacing "&" by "&" fixed the problem. I did not need to > change anything else in the code.
OK, I just did a test with an API key specified with and without converting the ampersands (&) to entities (&). I borrowed Mike's first example page, and posted one version with '&' and another with plain '&' (no quotes); Makes NO difference. See for yourself: http://www.mapfolio.org/map/test/map_amp_test_no_entities.html http://www.mapfolio.org/map/test/map_amp_test_w_entities.html Just to be sure, here's one using '&' EXCEPT for '&sensor=...' http://www.mapfolio.org/map/test/map_amp_test_mixed_entities.html Of course this isn't an argument for not using '&' for '&', or for not encoding URLs. There are good reasons for doing that, but not doing it doesn't explain Maps API errors. HTH. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
