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 that's not the case, then yes, please do share a minimal data set to
reproduce.

Cheers
Andrea

On Thu, Apr 28, 2022 at 8:36 PM <tom-sourcefo...@tomsaul.com> wrote:

> 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 with the standard line SLD this manifests as a collection
> that include A->B, (B->A)**, A->C, (C->A)**, A->D, (D->A)**
>
> where the items tagged with ** are straight lines between these points,
> and should not really be present in my opinion.  Why is the rendering
> adding these 'end-to-start' connectors?  Is there a way to tell it not to?
>
> My current workaround is an overly complex SQL query that splits the MLS
> into its respective lines - so in this case the result is three rows
> with the respective individual Lines (and all other columns from the DB
> the same).
>
>
>
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>


-- 

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  333 8128928

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to