<html>
<head>
<title></title>
<meta name="GENERATOR" content="MSHTML 8.00.6001.18876"></meta>
<meta name="SKYPE_FRAMEID" content="HBROAMAKDT"></meta>
</head>
<body>
<div>Hallo</div>
<div> </div>
<div>Now postgisonline.org handles geometry collections and return all different tyoes in the collection. It also handles if a table has different types in different rows.</div>
<div> </div>
<div>Everything thanks to the new function ST_CollectionExtract</div>
<div> </div>
<div>What I do is to send every geometry to three layers in the map-file in mapserver , one with point symbol, one with line and one polygon.</div>
<div>Then I split the geometry like this for the polygon example:</div>
<div> DATA "the_geom FROM (select ST_CollectionExtract(ST_Force_Collection(the_geom),3) as the_geom, idmap1 from userdata.%relation%) as a USING UNIQUE idmap1 USING SRID=%srid%"<br />
</div>
<div> </div>
<div>it seems to work.</div>
<div> </div>
<div>I didn't see any simple solution for handling geometry collections in mapserver on the net, but with PostGIS 1.5 it is no big deal :-)</div>
<div> </div>
<div>THis approach give som overhead since the query has to be evaluted 3 times instead of one even for cases that isn't collections. But I think it's worth it in this case because I also catch special cases like different types on different rows.</div>
<div> </div>
<div>But the alternative of course is to make collections a special case and send those to special map-file layers.</div>
<div> </div>
<div> </div>
<div>About the firefox-problem I mentioned the other day it was of course me who had done things wrong. ow it should work.</div>
<div> </div>
<div>/Nicklas</div>
</body>
</html>