Also, OGR can be used to spatially index a shapefile (command: shptree), which enables faster shapefile rendering in Mapserver.<br> <a href="http://mapserver.gis.umn.edu/cgi-bin/wiki.pl?ShpTree">http://mapserver.gis.umn.edu/cgi-bin/wiki.pl?ShpTree
</a><br> <a href="http://ogr.maptools.org/drv_shapefile.html">http://ogr.maptools.org/drv_shapefile.html</a><br><br>Aaron<br><br><div><span class="gmail_quote">On 12/12/06, <b class="gmail_sendername">Gregor Mosheh</b>
<<a href="mailto:gregor@hostgis.com">gregor@hostgis.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Ask for the details you need to help me if you need some more ...
<br><br>Actually, it's usually the other way around. ;)<br><br><br>> What is the better way to get mapserver generating map faster !<br>> Is POSTGIS optimizing the way that mapserver build the map ?<br><br>Typically, shapefiles are faster; or at least that's what I've
<br>consistently been told is true for the majority of cases.<br><br>If your PostGIS performance is slow, make sure you have indexes! Nothing<br>affects performance as much as indexes, and they're an easy thing to<br>forget to do. Ensure that there's a GiST index on your geometry column, as
<br>well as on on your oid column. If the indexes are missing, generate them<br>as follows:<br><br> create index tablename_the_geom on tablename (the_geom) using gist;<br> create index tablename_oid on tablename (oid);
<br> analyze tablename;<br></blockquote></div><br><br clear="all"><br>-- <br>+-------------------------------------------------<br>| Aaron Koning<br>| Information Technologist<br>| Prince George, BC, Canada.<br>+-------------------------------------------------
<br>| Flexible Internet Spatial Template:<br>| <a href="http://fist-mapping.org">http://fist-mapping.org</a><br>+-------------------------------------------------