Hmm. Not looking good: 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>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. 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. Jason On 5 November 2010 06:43, Jackie Ng wrote: [snip] > So here's the problem: > > The meters-per-unit value is calculated by: > > MgCoordinateSystem.ConvertCoordinateSystemUnitsToMeters(1.0) (as seen in > the > mapframe.aspx/php/jsp of the AJAX viewer) > > Unfortunately, the code being purely client-side (and Maestro API being > 100% > managed), I do not have access to the official MapGuide API and thus the > MgCoordinateSystem class. > > So is there a purely managed way to calculate this value? > >
_______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
