the 4 kml files are rendered by GGeoXml as a single tile layer on the server.
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. kml ids (obtained with FireBug) WFS: cFzPlkNSRPi2xIFN1qzQ315oEhplAtnklJbFZIOeUX3UiKkN8-k8pzFny4Q97Ag WMS: cFzPlkNSRPi2xIFN1qzQ315oEhplAtnklJbFZIOeUX3UiKkN8-k8pzNnx4Q97Ag because the WFS id is less than the WMS id, the WFS will always display first, and be hidden underneath the WMS. as a hacked workaround, you could create different urls for the same kml, reverse engineered from the google unique ids. There would be a different url for each kml depending on the order you'd like it displayed. So you'd need 4 urls for each kml. see the following map for a demonstration of this hack: http://www.william-map.com/20100322/1/geoxml.htm -- 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.
