How would you handle this James?<div><br></div><div>The spatial intersection that MapGuide performs with the current viewport's extents is critical to performance when you are dealing with large amounts of data, and many of the FDO data sources are optimized using R-Tree (or similar) indices to return only the data which is currently in view.</div>
<div><br></div><div>I guess you could conceivably fetch an over-post of the current extents by some factor, but that would only work for a subset of point symbols (those where the maximum dimensions of the theming is < half the expanded extent dimension, and it would mean that everyone has to live with the decreased performance of the over-fetch.</div>
<div><br></div><div>A few options:</div><div> - Make the over-fetch percentage or distance configurable per server, per map, or per-layer</div><div> - Only apply the over-fetch to points (there are actually cases where the same problem happens with lines and polygons, so I don't think this is valid)</div>
<div><br></div><div>I personally feel that the current behaviour is generally OK, but there are definitely cases where you wouldn't want features missed just because their mid-point isn't in the current view extents.</div>
<div><br></div><div>Regardless of the solution, I think this would take some work, so might require some funding or somehow making it important to one of the developers.</div><div><div><br></div><div>Jason</div><div><br><br>
<div class="gmail_quote">On 16 February 2010 12:06, JamesDudden wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I understand how it happens and it does make sense but it renders the<br>
theming of points useless if they are going to be anything larger than a few<br>
pixels.<br>
<br>
I think it would be good to see future versions of Mapguide become more<br>
intelligent and be able to cope with theming of points.<br>
<div class="im"><br></div></blockquote></div></div></div>