Thanks all for such prompt replies. I'll answer all your questions at once.
> Why do you add the kml overlay, then immediately remove it? The map opens up in a view of the whole inner city. The kml looks like an odd funny little smudge because its polygons and lines are so small. So I just remove it after defining it, rather than have it hanging around looking odd. I have a separate checkbox to show (add) it to the map. The checkbox function also centers on the kml, switches to Satellite (the only view in which the kml makes sense) and zooms in to level 22. That's the way to view it. Mike Williams' tutorial says I can't hide and show a GGeoXml overlay the way I'm doing with my marker array categories. If there's a better way to handle this situation, I'd love to know it! >Although it displays the same way in Google Maps: [that is, broken] >feedvalidator thinks it is valid >go to the regular Google Maps page, and >simply paste in the URL of your KML file. >Looks the same as in my browser. [that is, broken] That's a great test! Although, it may still be that there's something wrong with my kml file. I made a new Folder in Google Earth, drew polygons and lines, put them in the folder, styled them, added comments to them and Saved Place as a KML. Several test kmls all show the same broken behavior. >I think your KML is doing what it's told ... are you sure you drew the >shapes in the same coordinate system (WGS84)? Nope. I'm not sure. I drew them in Google Earth and saved a folder of polygons and lines as a KML. I've no idea what projection system GE uses and never imagined --especially for such a tiny area-- it would make a difference. So maybe that's a clue. >It looks liek you're just passing the points to the map... Instead, I >would recommend encoding them. >then use this utility (http://code.google.com/apis/maps/documentation/ >polylineutility.html) to encode a set of points and see if it makes a > difference. Yep, I was trying to use that to create encoded polygons for my map at http://lovebunnies.luckypro.biz/rioni/. That was misery on a stick. It doesn't allow you to reenter the encoded versions, edit them, then re- encode the data. I couldn't find *any* utility in which I could *edit.* So I did the same thing as I'm doing now: made polygons in GE and saved them as KMLs. Then, for the rioni map, I pasted the points into my HTML code for testing. At least that way I could reopen the KML in GE, edit it, resave it, repaste it, etc. Probably the long way around the barn, but with my primitive understanding of the Javascript, it was good for me. The data from those KMLs was fine. But of course I wasn't reading the KMLs themselves in a Google Map. > KML doesn't support poly encoding (yet) So, as a stopgap, I could create polygons as either encoded data or entries of data in an xml file, and create multiple overlays for via Margutta. I had hoped one KML file would handle all that in one fell swoop, as in Mike Williams' example at http://econym.org.uk/gmap/geoxml.htm. But maybe not. > The points in the kml look OK to me: > http://www.geocodezip.com/GenericMapBrowser.asp?filename=viamarguttaA.xml&type=hybrid > Must be something about the way you are using kml. Hmmm. So you, Larry, munged my KML into a simpler XML. How did you do that? And Google Maps API draws my tiny polygons fine if presented the data in an xml. So the problem can't be the size of the polygons, per se. Sigh. I could potentially do the same, although I liked the idea of the clickable polygons. Oh, wait, I could do something like I did on my rioni map. Interesting. That way, I could add sidebar entries for the polygons and lines. Interesting. And yes, there may be something about "the way I use kml," but if so, Google Maps does it too. Or I guess you, Larry, might have meant "there must be something about the way you've broken your kml." Well that's quite possible. But no one seems to know what it is I've done! Could we ask Pamela to ask the technicians to examine my files? It would be good to know the cause of this problem before I try to figure out a way to fix it! I mean, if there's just some little glitch in my kml, it would be a drag to spend hours on an unnecessary workaround. And maybe others would be helped in the future if a fix or a reason or something to avoid is posted here. Thanks guys for looking at this and testing it so thoroughly. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
