> each kml overlay is assigned a unique id (based on the url) and the > server renders the overlays in order of these unique ids (ascii > ordering) instead of displaying them in the natural order in the map. > This looks like a bug with Google Maps.
I wouldn't say it's a bug. There's a lot of asynchronous action within GGeoXml processing. Multiple requests may not arrive at Google's servers in the order they started out ; then there's fetching the KML from the target files of differering sizes, potentially even different hosts ; different amounts of Google-side processing depending on a Google-side decision to render as tile overlays or as regular GOverlay objects ; transmission of all that back to the client. I think if you need fine control of KML rendering you need to look outside of GGeoXml, for a different tool. -- 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.
