I am working on loading KML files into a map using Google Maps API v3. The KML loads fine and the markers are seen. But the marker info (pop-up when the marker is clicked) never shows up in a consistent manner. A few work some times, some others don't. This is really peculiar. To see the page, check-
http://www.sobitabraham.com/teawap/NEW_kml.html
The KML file is here-
https://sites.google.com/site/teawapdata/home/kml-files/TEAWAP.kml
The KML file is 990 KB in size, so it is not some file size ceiling problem. It could have something to with the caching of KML, I am not sure. The KML file was exported from Google Earth.
The frustrating thing is that this marker behavior is erratic, the error is not consistent. This problem is seen even when I paste the URL of the KML file into maps.google.com. Any help in sorting this out will be appreciated.
Thanks.
Related
I working on a website that utilizes a Google Map (V3). What I'm looking to do is apply KML layers, provided by the National Weather Service (NWS) at http://radar.weather.gov/ridge/kmzgenerator.php. I am able to get "single images," or still KML files to work, but I want to have the radar animating over time. The NWS provides KMZ loop files, and I've tried just simply adding those, but that doesn't show any KML Layers at all. Thanks in advance for any help
I have made a map with a series of overlays of old maps that I created using MapTiler and the coordinates were definitely correct when I plotted them in Google Earth, but when I load the KML files in Google Maps they are roughly in the correct area but are far from accurate.
As the same error is replicated in all the layers can someone suggest what it is that I am doing wrong?
http://www.southdevonaonb.org.uk/cordialemapping/kmzdata/withtiledoverlays/19x/doc.kml
http://www.southdevonaonb.org.uk/cordialemapping/kmzdata/withtiledoverlays/20x/doc.kml
The other KML files can be found by changing the URL to 21x, 22, 23x, 25x, 26x, 27x (I am unable to post more than two links).
I'm converting recorded GPS tracks to KML/KMZ files and they show up correctly in Google Earth. However, opening the same KML file in the Google Maps website I get weird straight lines that are a few thousand km long.
KML download:
http://www.indunet.it/stackexchange/test.kml
Direct link to Google Maps website:
https://maps.google.com/maps?q=http:%2F%2Fwww.indunet.it%2Fstackexchange%2Ftest.kml&hl=de&sll=37.230328,-95.712891&sspn=52.421131,114.169922&t=h&z=4
This is what the KML file looks like on my computer:
I get identical results with FF, Chrome and IE, so I guess it's somethign related to the generated KML file, but I have no clue what's wrong..
Oddly, zooming in to the correct area (upper-left end of the line, i.e. northern Italy) shows some outline that's similar to the original track:
Correct display in Google Earth (same KML file):
Any ideas?
PS: I get similar results with all tracks I export. However, markers always show up correctly.
Your kml has the coordinates specified:
11.30968602,46.35330003,
If I add a third coordinate it works:
11.30968602,46.35330003,0 [on google maps]
or if I remove the comma at the end it works:
11.30968602,46.35330003 [on google maps]
I am using Google Maps JavaScript API v3 with a KML layer to display a map with custom markers.
My map links to the KML file I published as a Google Site attachment. Once loaded, the map shows each of the PlaceMarks from the KML file correctly, but will not display the popup balloons.
Rarely when I click a pin it shows the balloon (5% of the time), then none of the other pins work. When I zoom in and out my custom pin images sporadically revert to the default pin image.
I added the layerOptions to explicitly set clickable to true and suppressInfoWindows to false. It didn't change the balloon behavior.
I have tested with Chrome v19, Firefox v12, and IE8.
Update 1:
I found a typo in my KML, (bal*l*oon). Still not working right. Something is making the pins buggy.
Update 2:
v3 is now working. Google's caching made this difficult to test. Added '?nocache=0' to KML URL to prevent caching. BaloonStyle was the problem, but caching caused the typo to remain. Migrating KML to personal server.
Live HTML Map Page (Fixed)
Live KML Download (Fixed)
My references:
http://developers.google.com/maps/documentation/javascript/reference
http://ge.images.alaska.edu/workshop/advanced.htm
Google is caching your KML on purpose. The workaround is to append something like the current time to the end of your URL so that it is different every time:
var kmlFile = 'http://www.myserver.com/my.kml?'+(new Date()).getTime();
var kmlLayer = new google.maps.KmlLayer(kmlFile);
kmlLayer.setMap(myMap);
My problems:
A typo in my BalloonStyle tag
A stale cache of my KML file
This would have been easier if:
Google Maps JS threw errors when parsing KML
Google caching was reasonably fast
I started testing on a server
Update:
I moved the KML file to my server, but the cache remained stale after the first change. It seems the caching occurs when my Google Map object loads the KML overlay. I made sure it was not my system or my server caching.
The pins start acting buggy if I make a change to my KML and the cache doesn't update. All my pins show in the correct location, but one of the pins won't have a balloon. Changed the file name, works fine!
Update 2:
I reported this caching behavior as a bug on Google Maps JS API.
http://code.google.com/p/gmaps-api-issues/issues/detail?id=4196
Conclusion:
I wrote the ASP.NET/C# class to geocode addresses and build the KML doc in less time than it took to find this error.
Stop caching so hard Google!
Your KML is invalid. <Name> is not part of the spec. Change it to <name> and you should be good to go.
I need to draw routes in my android app's MapView and to do so I'm using the coordinates listed in the KML output file of Google Maps.
The problem is: when I add a waypoint to a route, the KML file doesn't contain the complete route details and only shows the coordinates/directions from the source to the waypoint.
Here is an example. As you can see, the route is drawn correctly and all the directions are shown, but the KML output only has the details from the source to waypoint.
A solution is making two requests, one for source->waypoint and other for waypoint->destination, but I would like to avoid that if possible.
Thanks.
Multistep routing is only supported in google maps directly.
See
http://groups.google.com/group/kml-support-advanced/browse_thread/thread/1d57c9f0bc879141
and
http://groups.google.com/group/kml-support-getting-started/msg/e3d15213ac4ae9ed