RadMap has a problem with sufficiently large shapes, where if you zoom far enough into the shape it disappears. You can observe this effect in the demo:
http://demos.telerik.com/silverlight/#Map/WktReader
Zoom for example into East Area. When you reach the last 2-3 zoom levels from the bottom there is a high chance that the shape will disappear and you will see the map beneath without white overlay. Sometimes it disappears immediately, sometimes after you do something. For example, if I switch to a different application with Alt+Tab and back to IE the shape disappears with 100% probability.
The larger the shape is the more there are zoom levels from the bottom at which shape disappears.
http://demos.telerik.com/silverlight/#Map/WktReader
Zoom for example into East Area. When you reach the last 2-3 zoom levels from the bottom there is a high chance that the shape will disappear and you will see the map beneath without white overlay. Sometimes it disappears immediately, sometimes after you do something. For example, if I switch to a different application with Alt+Tab and back to IE the shape disappears with 100% probability.
The larger the shape is the more there are zoom levels from the bottom at which shape disappears.
1 Answer, 1 is accepted
0
Accepted
Hello Sergey,
It is a known problem with the Silverlight rendering engine. It has a restriction on size of the standard Silverlight shapes (Rectangle, Polygon and so on). In fact it uses the short type values for them. So, if the shape has a size that becomes larger than max short value while zooming then it could be calculated wrong.
To avoid this problem you can split the original polygon in more polygons with the size smaller than short.MaxValue. Or you can limit zoom level.
All the best,
Andrey Murzov
the Telerik team
It is a known problem with the Silverlight rendering engine. It has a restriction on size of the standard Silverlight shapes (Rectangle, Polygon and so on). In fact it uses the short type values for them. So, if the shape has a size that becomes larger than max short value while zooming then it could be calculated wrong.
To avoid this problem you can split the original polygon in more polygons with the size smaller than short.MaxValue. Or you can limit zoom level.
All the best,
Andrey Murzov
the Telerik team
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.