The <iframe> is a modified version of a Google embedded map. If you go
to maps.google.com and look for your location, then click on the "Link"
link, you'll see a "Paste HTML to embed in website" box that contains
code that will embed the map into your website. You don't need an API
key for that.
I guess there's something that crawls through your HTML and replaces
"{Location}" with the actual value entered by the user. [Unless you're
using {Location} metalinguistically to indicate that the actual address
is placed there.]
The way an <iframe> works is that the code inside the frame is
effectively running in the maps.google.com domain, rather than running
in your domain, and maps.google.com doesn't need an API key. The
location gets passed to the <frame> in the same sort of way that it
would if you call maps.google.com/maps?q=Chicago.
The Terms don't specifically say how far you're allowed to tweak the
embedded map parameters. I suspect that you're supposed to either use
the "Paste HTML to embed in website" as provided, or to use the API. If
you use the "Paste HTML to embed in website" code exactly as provided,
then it's futureproof - Google aren't going to change the syntax in a
way that breaks thousands of embedded maps - but if you tweak it as you
have (e.g. by removing the &ll) then Google could possibly change
things at some point such that your tweaked version doesn't work.
To be certain of being legal and futureproof, ditch that code and do it
properly with the API.
--
Mike Williams
http://econym.org.uk/gmap
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
