Harald Vålerhaugen
Top achievements
Rank 1
Rank 1
Harald Vålerhaugen
asked on 22 Dec 2010, 11:03 AM
After upgrading from Q2 to Q3 we experienced a big accuracy problem with overlays and map markers. Support informed me that there are up to 50 cm offset of items. This is visible from at least level 17.
After filing a support request, I was referred to a not scheduled feature request describing the exact problem: http://www.telerik.com/support/pits.aspx#/public/silverlight/4352
I've attached an image with an overlay on top of my tileprovider, showing that this should not be filed as a "feature request", because it is a bug!
Can you please comment on your plans on fixing this issue?
HaraldV
After filing a support request, I was referred to a not scheduled feature request describing the exact problem: http://www.telerik.com/support/pits.aspx#/public/silverlight/4352
I've attached an image with an overlay on top of my tileprovider, showing that this should not be filed as a "feature request", because it is a bug!
Can you please comment on your plans on fixing this issue?
HaraldV
2 Answers, 1 is accepted
0
Accepted
Hi Harald Vålerhaugen,
We are aware of this problem. We completely redesigned the engine of the information layer for the Q3 2010 release to increase its panning and zooming performance on large data arrays. Now it can handle up to 1000 locations (compared to 150 in previous version) or map shapes with up to 100000 total points (compared to 10000 in previous version).
However, the new engine has some side effects. Our developers have already managed to address some of them and we are currently working on the rest. The accuracy of the element location on the highest zoom levels is one of them -- it occurs because computations made to calculate position on zoom levels 19 or 20 are close to the precision provided by the double value type. The miscalculation on doubles in this case can give up to 50 centimeters difference in object location (in real world dimensions). This is 1-3 pixels on screen. The same is true for zooming and panning on highest zoom levels.
Unfortunately we cannot suggest you a workaround for this problem at the moment but we have planned several enhancements for the information layer for Q1 2011 that will solve this particular problem as well. You can track the progress of this task in our public issue tracking system here: http://www.telerik.com/support/pits.aspx#/public/silverlight/4352
Greetings,
Andrey Murzov
the Telerik team
We are aware of this problem. We completely redesigned the engine of the information layer for the Q3 2010 release to increase its panning and zooming performance on large data arrays. Now it can handle up to 1000 locations (compared to 150 in previous version) or map shapes with up to 100000 total points (compared to 10000 in previous version).
However, the new engine has some side effects. Our developers have already managed to address some of them and we are currently working on the rest. The accuracy of the element location on the highest zoom levels is one of them -- it occurs because computations made to calculate position on zoom levels 19 or 20 are close to the precision provided by the double value type. The miscalculation on doubles in this case can give up to 50 centimeters difference in object location (in real world dimensions). This is 1-3 pixels on screen. The same is true for zooming and panning on highest zoom levels.
Unfortunately we cannot suggest you a workaround for this problem at the moment but we have planned several enhancements for the information layer for Q1 2011 that will solve this particular problem as well. You can track the progress of this task in our public issue tracking system here: http://www.telerik.com/support/pits.aspx#/public/silverlight/4352
Greetings,
Andrey Murzov
the Telerik team
Browse the videos here>> to help you get started with RadControls for Silverlight
0
Harald Vålerhaugen
Top achievements
Rank 1
Rank 1
answered on 23 Dec 2010, 02:42 PM
That's great! I was told that this was scheduled, but your issue tracking system had an issue displaying it as not scheduled :)
HaraldV
HaraldV