Hello,
We are experiencing a bug where some of the regions defined for our map are "disappearing" after zooming. The following screenshots illustrate the problem.
I can provide the xaml/C# if necessary, though the C# is 600+ loc. Any assistance would be greatly appreciated.
Hi,
This is actually expected behavior. There is an auto-culling routine that removes shapes that are "too small" to aid perfomance for shapefiles that have a lot of geometry that isnt necessarily important when you are zoomed out. You can effect this behavior by adjusting the Resolution property on the map layer. Let me know if this helps!
-Graham
I don't think my previous screenshot correctly represented the behavior we're seeing. I managed to get a better representation:
As you can see, the majority of the map has been culled. I will do some testing around the Resolution property, but right now we aren't setting that explicitly.
Thank you for your quick response!
Hi merklemmo,
The issue you're observing was fixed in our previous service releases, so if you update to the latest version of the product, it will be gone.
Thank you for pointing this out and sorry for any inconvenience caused.
Best regards,Milana Zhileva
I have attached a zip of a test project that exhibits the unpredictable behavior. After the map loads, all you need to do is click and drag it around a little and it will very quickly crash.
All the sample does is create an XamMap, add a layer, import a shapefile, and then create a tooltip on each element that is a TextBlock. You'll find that if you replace the textblock with a simple string, the crashing behavior disappears.
Glad you got it figured out. If you can share a sample that recreates the issue you were seeing, hopefully we can get to what the root of your problem was.
In the end, we discovered that the problem stems from us setting our tooltips to TextBlocks. When we changed them to regular strings, all of our issues disappeared. We had also been encountering a period crash issue while zooming, and this solved that problem as well.
I'm not sure what inside the control could have been causing this, but it seems like a fairly serious issue.
Did you try a resolution of 1? I'm not sure 0 is a valid value, in this case. Is that with the USA shape file we use in the samples? If you share the setup for the map, (its size, etc), I'll see if I can see what else might be going on.