<div dir="ltr">Another technique designed to meet this requirement is UTFGrid:<div><br></div><div><a href="https://www.mapbox.com/foundations/an-open-platform/#utfgrid">https://www.mapbox.com/foundations/an-open-platform/#utfgrid</a></div>
<div><br></div><div>OpenLayers apparently has support for UTFGrids:</div><div><br></div><div>Doc: <a href="http://dev.openlayers.org/apidocs/files/OpenLayers/Control/UTFGrid-js.html">http://dev.openlayers.org/apidocs/files/OpenLayers/Control/UTFGrid-js.html</a></div>
<div>Example: <a href="http://openlayers.org/dev/examples/utfgrid.html">http://openlayers.org/dev/examples/utfgrid.html</a> </div><div><br></div><div>The tricky part is generating the UFTGrid! Not sure what tools there are out there for doing this. It would be nice if there was a map server which could generate these on-the-fly...</div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 25, 2014 at 3:35 AM, Rob Marjot <span dir="ltr"><<a href="mailto:rob.marjot@gmail.com" target="_blank">rob.marjot@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Dear list,<div><br></div><div>I'm in the quest of developing a performant webmapping application involving large, complex vector objects (pipelines) originating from CAD. In the application, these objects need to be interactive.</div>
<div><br></div><div>Whether complex or not: the vectors will only be (possibly partly: clipped by the map extents) rendered to a limited number of pixels. In OpenLayers 3, this idea is exploited: before rendering vectors are pre-processed by quantizing (and removing duplicate / co-linear) coordinates. (<a href="http://tschaub.net/blog/2014/03/04/topology-preserving-simplification.html" target="_blank">The algorithm has been implemented by Tim Schaub</a>).</div>
<div><br></div><div>Applying quantization (and clipping) dramatically reduces the serialized (GeoJSON) size of the geometries. Yet, since my coordsys is in meters, exchanging pixel coordinates will reduce the size even further...</div>
<div><br></div><div>My question: is there a layer type that takes pixel coordinates, relative to a map corner? Effectively, this would allow me to create hotspots on a map that was rendered purely serverside.</div><div><br>
</div><div>I fully understand (and tend to accept) the downside of required traffic upon each panning / zooming. It will be acceptable to request a refresh of hotspots with a delay of a 1 sec or so.</div><div><br></div><div>
Otherwise, I'm open to any suggestion taking another approach :))</div><div><br></div><div>Thank you in advance!</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Rob</div></font></span></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.osgeo.org">Users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/openlayers-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/openlayers-users</a><br></blockquote></div><br></div>