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.<div><br></div><div><a href="http://kmlvalidator.com/home.htm">http://kmlvalidator.com/home.htm</a>
</div><div><br></div><div>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.<div>
<br></div><div>Here's one of mine that validates if it helps: <span style="color:rgb(102,102,102);font-family:Arial;font-size:14px;text-align:left"><a href="http://maps.nanaimo.ca/data/property/115545.kml">http://maps.nanaimo.ca/data/property/115545.kml</a></span></div>
<div><br></div><div>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.</div>
<div><br></div><div>Jason</div><div><div><br></div><div><div class="gmail_quote">On 20 March 2012 18:46, Jackie Ng wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It would be nice to have some test cases where the KML generated by MapGuide<br>
differs from the KML generated by GeoREST so we can see where the KML<br>
renderer in MapGuide is doing it wrong.<br><br></blockquote></div></div></div></div>