There certainly are ways to interpret self-intersecting polygons in a consistent manner. But is there a use-case for this in the realm of CF? For self-intersecting lines, this seems clear (any kind of route, for instance, from ships, planes, etc.), but for polygons, I struggle. Hence my intuition would be to at least discourage their use.
For a better understanding, I would rather look to other geo packages and standards than to inspiration from the world of graphic design. Starting points might be [Shapely](https://urldefense.us/v3/__https://shapely.readthedocs.io__;!!G2kpM7uM-TzIFchu!idhAoQ76_ui8lY2teNnycaX33NT7fBg4C2u4JKx1kuasbE4jZwXtJtlmIkPoubWnl7OBjzfFja0$ ), [GEOS](https://urldefense.us/v3/__https://libgeos.org/__;!!G2kpM7uM-TzIFchu!idhAoQ76_ui8lY2teNnycaX33NT7fBg4C2u4JKx1kuasbE4jZwXtJtlmIkPoubWnl7OBI5FEIHc$ ), or the OGC's [Simple Feature Access](https://urldefense.us/v3/__https://www.ogc.org/standards/sfa__;!!G2kpM7uM-TzIFchu!idhAoQ76_ui8lY2teNnycaX33NT7fBg4C2u4JKx1kuasbE4jZwXtJtlmIkPoubWnl7OBYYQPP4U$ ). -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/354*issuecomment-1033792476__;Iw!!G2kpM7uM-TzIFchu!idhAoQ76_ui8lY2teNnycaX33NT7fBg4C2u4JKx1kuasbE4jZwXtJtlmIkPoubWnl7OB30-khCg$ You are receiving this because you are subscribed to this thread. Message ID: <cf-convention/cf-conventions/issues/354/[email protected]> This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
