Thanks. Not likely to get any support under my current contract. I'm
not sure if there is an abstract SQL way to do this, but with postGIS
something like
select st_geometryType(the_geom) as gts from xxx group by gts
should be reasonably quick. The good thing is that this is not a run
time
On Sat, Apr 30, 2022 at 8:14 PM wrote:
> You nailed it (as usual), with one caveat. In the postgres DB the column
> type is geometry, but when I use the 'Guess geometry type and srid' from
> the SQL view for the layer, it is filling in the type as LineString. This
> is a bit odd since the
You nailed it (as usual), with one caveat. In the postgres DB the
column type is geometry, but when I use the 'Guess geometry type and
srid' from the SQL view for the layer, it is filling in the type as
LineString. This is a bit odd since the table contains a mix of both
LineString and
Given the behavior, I'm guessing you have multi-line string data in a
database column
that's declared to be LineString instead.
GeoServer follows a strict type system (based on its WFS heritage) and
will convert a MLS into a simple linestring in one of the possible ways,
connecting the bits.
If
It is using a LineSymbolizer. If needed I can post the SLD, a data
sample, and some snapshots of the result.
On 4/29/2022 1:47 AM, Ian Turton wrote:
With out seeing the data and the sld it's hard to say exactly, but it
sounds as if you've used a PolygonSymbolizer instead of a
LineSymbolizer
With out seeing the data and the sld it's hard to say exactly, but it
sounds as if you've used a PolygonSymbolizer instead of a LineSymbolizer to
style the geometry.
Ian
On Thu, 28 Apr 2022 at 18:44, wrote:
> I am hitting a problem with the rendering of a MultiLineString (MLS) and
> hope
I am hitting a problem with the rendering of a MultiLineString (MLS) and
hope someone can
1) Determine if it is a bug that should be reported, and
2) Provide any options for getting the desired result
The issue is simple - I have a MLS with three lines - A->B, A->C, and A->D
When rendered
