You'd be better off taking a MapGuide render of a few different geometry types options (extrusion, etc) and running them through the Galdos KML Validator to see what MapGuide is doing wrong.
http://kmlvalidator.com/home.htm The GeoREST generator outputs KML geometry to spec, and the rest is up the the individual template author to get right; it's just as likely to be non-compliant as anything. If the validator doesn't catch it, then it's likely that MapGuide is getting the KML winding order wrong. Here's one of mine that validates if it helps: http://maps.nanaimo.ca/data/property/115545.kml In my opinion, the MapGuide KML implementation will take more than a geometry fix to be truly functional. A bandaid solution would be OK for current users, but IMO what it really needs is a complete overhaul or deprecation. Jason On 20 March 2012 18:46, Jackie Ng wrote: > It would be nice to have some test cases where the KML generated by > MapGuide > differs from the KML generated by GeoREST so we can see where the KML > renderer in MapGuide is doing it wrong. > >
_______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
