Ok chaps, I've come up with a 'solution'. I simply wrote a java servlet this exists on my web server in the root directory called 'mapsatt'. This servlet grabs the query string, makes a request of "http://maps.google.com/mapsatt"; with the same query string and pipes the result back out. Not ideal, but as a work around, it does the job.
On Oct 22, 3:05 pm, Mark <[EMAIL PROTECTED]> wrote: > OK, I've been looking into this further and something somewhere > doesn't make sense. > > The marker icons are also loaded directly from within the KMZ file and > they load when using the demo Google Maps API, yet the images that > should go in the balloons don't. > > For example the url in the generated page on Google Maps for the > marker icon and for one of the photos are > /mapsatt?id=http://www.dcs.shef.ac.uk/~mark/blog/blog_files/journeys/ > to_work.kmz&f=camera.png > /mapsatt?id=http://www.dcs.shef.ac.uk/~mark/blog/blog_files/journeys/ > to_work.kmz&f=p13.jpg > > When using the demo app the two urls are the same. > > The problem seems to arise in that the resolution of these URLs is > done differently. On Google Maps they both get expanded > tohttp://maps.google.com/mapsatt?id=http://www.dcs.shef.ac.uk/~mark/blo...http://maps.google.com/mapsatt?id=http://www.dcs.shef.ac.uk/~mark/blo... > > yet when using the GGeoXml demo they get expanded > tohttp://maps.google.com/mapsatt?id=http://www.dcs.shef.ac.uk/~mark/blo...http://gmaps-samples.googlecode.com/mapsatt?id=http://www.dcs.shef.ac... > > So for some reason the marker icon is being resolved correctly to load > from the KMZ file referenced through the google maps servers where as > the image is being resolved against the server hosting the API demo. > I'm guessing that this is definitely a bug in the Google Maps API > code. As I haven't played around too much with the API yet (read some > of it but not tried writing any code), is it possible to access the > html generated by GGeoXml? If so a script could be run to fix these > URLs after the KMZ file had been loaded. > > I might start digging in and writing some code to see if this is > doable until a permanent fix appears in a later version of the API. > > Hope that sheds some light on the problem for other people. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
