On Dec 12, 2:33 pm, Alireza Kashian <[email protected]> wrote: > > But for us at lilihood, the API provides this > URL:http://mt2.google.com/mt?v=ap.86&hl=en&x=653&y=1582&z=12&s=Gal > (we cann't see this url) > > The thing is that we see 88 in maps.google and 86 in lilihood..which > we have the feeling is the older version. > if you can see the link above, it must be a part of Singapore city. > But for us, this URL returns "not found" message. > > Anyone has any experience on this? why does the Google map API lead > us to version 86?
Does it? In one of my maps, I get a tile at http://mt1.google.com/mt?v=ap.88&hl=en&x=8205&y=5500&z=14&s=Gal [that's not supposed to be Singapore, don't worry] Your function CustomGetTileUrl() creates a Google URL as var address = "http://mt2.google.com/mt?v=ap.86&hl=en&x="; + coordinate.x + "&y=" + coordinate.y + "&z=" + zoom + "&s=Gal"; so you are fixing v86 of the tiles. It looks like you are trying to intercept tile requests in order to substitute your own tiles. If this is not actually contrary to the Terms of Service it's borderline. A better solution would be to use G_NORMAL_MAP tiles so you don't have to worry about where Google is serving its tiles from. Mike does this at http://econym.org.uk/gmap/example_custommap3.htm Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
