(PointSymbolizers had a filter restricting their use to points, but I
would expect a renderer would be smart to realize that
PointSymbolizers are for points)... Unless there are crazy situations
where one could have multiple geometry types within the same feature
type.
SLD defines behavior for what to do if you're rendering something like a
polygon with a PointSymbolizer. For example, section 11.3.1 says:
>The Geometry element is discussed in Section 11.1.2. In this case, if
a line, polygon, or raster geometry is used with this symbolizer, then the
>semantic is to use the centroid of the geometry, or any similar
representative point.
section 11.1.2 (LineSymbolizer) says:
>Geometry types other than inherently linear types can also be used. If
a point geometry is used, it should be interpreted as a line of
> “epsilon” (arbitrarily small) length with a horizontal orientation
centered on the point, and should be rendered with two end caps. If a
> polygon is used (or other “area” type), then its closed outline is
used as the line string (with no end caps). If a raster geometry is
used, its
> coverage-area outline is used for the line, rendered with no end caps.
You can certainly have multiple geometry types in the same feature type.
You can have multiple geometry 'columns' in a feature - each with
different types. I dont think there is a necessary restriction on the
geometry type within a featuretype - feature 1 can be a POINT, feature 2
a LINESTRING, feature 3 a POLYGON, etc...
dave
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
