Ok this is something that may need a bit of discussion. This is not only a bug in the CREATERUNTIMEMAP implementation, it's also a bug in the spec (xml schema).
A client application like Fusion tests for the absence of the ScaleRange property in order to determine if it's a non-vector layer. If I fix this "bug", the raster layers will have a scale range, but there will still be no practical way to differentiate between a vector layer and a raster layer. This is because there is nothing in the runtime map schema that tells us whether a layer is a vector/raster/drawing layer. If I fix the implementation, if you need to test for the layer's type you would have to test for the following: - Drawing: The FeatureSource is a resource id ending with "DrawingSource" - Raster: The ScaleRange is not null, but it only has a minscale/maxscale set, the FeatureStyle will be an empty array (the XML schema prevents us from setting this to null) - Vector: None of the above. This is the only way I can see this "problem" being fixed without doing a schema revision. Does this sound acceptable? - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Bug-CreateRuntimeMap-returns-scalerange-with-Null-when-using-Raster-or-WMS-layers-in-Map-tp5291469p5291797.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
