As others have said you really should be doing the following:<div><br></div><div>1) Reproject the geometries on the server so that the web browser will not need to do this for each geometry. Your geometries range from around 10,000 points to nearly 14,000 points.</div>
<div>2) If at all possible run a simplification on the geometries so that you do not have so many points as that alone is an issue for most web browsers. It actually made even Google Chrome feel sluggish when dong the hover events. This can be done in PostgreSQL/PostGIS as well as a slew of desktop software packages.</div>
<div>3) Try rounding your decimal places to 5 or 6 instead of going to 9, this will at least help you on your download sizes so that the initial page load occurs quicker.<br clear="all">--<br>Nathan Gerber<br>
<br><br><div class="gmail_quote">On Sat, Jul 10, 2010 at 5:32 PM, Rossko <span dir="ltr"><<a href="mailto:rossko@culzean.clara.co.uk">rossko@culzean.clara.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
><br>
example:<a href="http://www.myethiopia.org/KililisandWoredasandZones/Kilil/Kilil.html" target="_blank">http://www.myethiopia.org/KililisandWoredasandZones/Kilil/Kilil.html</a><br>
(shouldn't take more than 14 sec :))<br>
<br>
Took three minutes and a "script running slow" prompt in IE ; in Firefox<br>
about the same time and eight prompts. Not all PCs or browsers are alike.<br>
<br>
The javascript file here is "only" 2Mb ... you've got to simplify. Just<br>
taking out whitespace would help. Do you really need both google and yahoo<br>
maps? Can you simplify the projections in use? Would another data format<br>
work quicker than WKT? Do your points really need to be specified to better<br>
than 1mm precision?<br>
<br>
Seperating the data from the script is good practice, and should allow you<br>
to at least show some kind of map while all the crunching is going on,<br>
instead of the nothingness that currently greets visitors to your page.<br>
<font color="#888888">--<br>
View this message in context: <a href="http://osgeo-org.1803224.n2.nabble.com/openlayers-and-css-error-tp5271709p5278670.html" target="_blank">http://osgeo-org.1803224.n2.nabble.com/openlayers-and-css-error-tp5271709p5278670.html</a><br>
</font><div><div></div><div class="h5">Sent from the OpenLayers Users mailing list archive at Nabble.com.<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openlayers.org">Users@openlayers.org</a><br>
<a href="http://openlayers.org/mailman/listinfo/users" target="_blank">http://openlayers.org/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>