I had this problem with using MG with openlayers too. Solution would be a new http method which returns a json config document which covers everything required, MPU, extent scales etc for a given map def
z On Tue, Nov 9, 2010 at 12:18 AM, Jackie Ng <[email protected]> wrote: > > Well that makes the Rendering Service API mostly useless for client-side > created runtime maps :( > > The workaround is of course knowing the actual meters-per-unit value > beforehand when creating the runtime map client-side, but "workaround" is a > far too generous a word to describe that! > > - Jackie > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/Calculating-map-meters-per-unit-without-MgCoordinateSystem-tp5709001p5716813.html > Sent from the MapGuide Users mailing list archive at Nabble.com. > _______________________________________________ > mapguide-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapguide-users > -- Zac Spitzer Solution Architect / Director Ennoble Consultancy Australia http://www.ennoble.com.au http://zacster.blogspot.com +61 405 847 168 _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
