Hmm. Not looking good:<div><br></div><div><a href="http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Web/src/HttpHandler/HttpResourceStrings.cpp#L338">http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Web/src/HttpHandler/HttpResourceStrings.cpp#L338</a></div>
<div><br></div><div><a href="http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Web/src/HttpHandler/HttpResourceStrings.cpp#L338"></a>That seems like a pretty important/useful function to have available though. I guess you could extract the units from the WKT and transform yourself, but that's painful.</div>
<div><br></div><div>I wouldn't be surprised if you find other mismatches in the functionality between web and client APIs. I remember DMSG running into this a few times in initial Fusion development, and I've seen it myself in some of the print output stuff.</div>
<div><br></div><div>Jason</div><div><br></div><div><div class="gmail_quote">On 5 November 2010 06:43, Jackie Ng wrote:<br><div><br></div><div>[snip]</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
So here's the problem:<br>
<br>
The meters-per-unit value is calculated by:<br>
<br>
MgCoordinateSystem.ConvertCoordinateSystemUnitsToMeters(1.0) (as seen in the<br>
mapframe.aspx/php/jsp of the AJAX viewer)<br>
<br>
Unfortunately, the code being purely client-side (and Maestro API being 100%<br>
managed), I do not have access to the official MapGuide API and thus the<br>
MgCoordinateSystem class.<br>
<br>
So is there a purely managed way to calculate this value?<br><br></blockquote></div></div>