a ŠJ5d‚ã@sVdZddlZddlZddlmZmZddlmZdgZ Gdd„deƒZ e ej j d<dS)z#Line strings and related utilities éN)Ú BaseGeometryÚ JOIN_STYLE)ÚPointÚ LineStringc@sfeZdZdZgZddd„Zedd„ƒZddd „Zed d „ƒZ d e j d fdd„Z dd e j d fdd„Z dS)ra A geometry type composed of one or more line segments. A LineString is a one-dimensional feature and has a non-zero length but zero area. It may approximate a curve and need not be straight. Unlike a LinearRing, a LineString is not closed. Parameters ---------- coordinates : sequence A sequence of (x, y, [,z]) numeric coordinate pairs or triples, or an array-like with shape (N, 2) or (N, 3). Also can be a sequence of Point objects. Examples -------- Create a LineString with two segments >>> a = LineString([[0, 0], [1, 0], [1, 1]]) >>> a.length 2.0 Ncs¶|durt d¡St|tƒr4t|ƒtkr,|S|j}nLt|dƒrHt |¡}t|tj ƒrft  |j tj ¡rfndd„‰‡fdd„|Dƒ}t |ƒdkr–t d¡St |¡}t|tƒs²tdƒ‚|S) NzLINESTRING EMPTYZ __array__cSs&t|tƒr|jdSdd„|DƒSdS)NrcSsg|] }t|ƒ‘qS©)Úfloat©Ú.0ÚcrrúW/var/www/html/django/DPS/env/lib/python3.9/site-packages/shapely/geometry/linestring.pyÚ @óz7LineString.__new__.._coords..)Ú isinstancerÚcoords)Úorrr Ú_coords<s  z#LineString.__new__.._coordscsg|] }ˆ|ƒ‘qSrr)r r©rrr r Br z&LineString.__new__..rz/Invalid values passed to LineString constructor)ÚshapelyZfrom_wktrrÚtyperÚhasattrÚnpZasarrayZndarrayZ issubdtypeZdtypeÚnumberÚlenZ linestringsÚ ValueError)ÚselfÚ coordinatesZgeomrrr Ú__new__&s(     ÿ    zLineString.__new__cCsdt|jƒdœS)Nr)rr)Útupler©rrrr Ú__geo_interface__NszLineString.__geo_interface__çð?cCsV|jr dS|dur |jrdnd}|dur,d}d dd„|jDƒ¡}d  |d |||¡S) aàReturns SVG polyline element for the LineString geometry. Parameters ========== scale_factor : float Multiplication factor for the SVG stroke-width. Default is 1. stroke_color : str, optional Hex string for stroke color. Default is to use "#66cc99" if geometry is valid, and "#ff3333" if invalid. opacity : float Float number between 0 and 1 for color opacity. Default value is 0.8 zNz#66cc99z#ff3333gš™™™™™é?ú cSsg|]}dj|Ž‘qS)z{},{})Úformatrrrr r er z"LineString.svg..zSg@)Zis_emptyZis_validÚjoinrr")rZ scale_factorZ stroke_colorZopacityZ pnt_formatrrr ÚsvgRs ÿ ýzLineString.svgcCs|jjS)zÓSeparate arrays of X and Y coordinate values Example: >>> x, y = LineString([(0, 0), (1, 1)]).xy >>> list(x) [0.0, 1.0] >>> list(y) [0.0, 1.0] )rÚxyrrrr r%ks z LineString.xyég@cCs6|dkrtdƒ‚nt |¡s$tdƒ‚t |||||¡S)aòReturns a LineString or MultiLineString geometry at a distance from the object on its right or its left side. The side is determined by the sign of the `distance` parameter (negative for right side offset, positive for left side offset). The resolution of the buffer around each vertex of the object increases by increasing the `quad_segs` keyword parameter. The join style is for outside corners between line segments. Accepted values are JOIN_STYLE.round (1), JOIN_STYLE.mitre (2), and JOIN_STYLE.bevel (3). The mitre ratio limit is used for very sharp corners. It is the ratio of the distance from the corner to the end of the mitred offset corner. When two line segments meet at a sharp angle, a miter join will extend far beyond the original geometry. To prevent unreasonable geometry, the mitre limit allows controlling the maximum length of the join corner. Corners with a ratio which exceed the limit will be beveled. Note: the behaviour regarding orientation of the resulting line depends on the GEOS version. With GEOS < 3.11, the line retains the same direction for a left offset (positive distance) or has reverse direction for a right offset (negative distance), and this behaviour was documented as such in previous Shapely versions. Starting with GEOS 3.11, the function tries to preserve the orientation of the original line. gz3Cannot compute offset from zero-length line segmentz$offset_curve distance must be finite)rrÚisfiniterÚ offset_curve)rÚdistanceÚ quad_segsÚ join_styleÚ mitre_limitrrr r(ys "  zLineString.offset_curveÚrightcCs"|dkr|d9}|j||||dS)a› Alternative method to :meth:`offset_curve` method. Older alternative method to the :meth:`offset_curve` method, but uses ``resolution`` instead of ``quad_segs`` and a ``side`` keyword ('left' or 'right') instead of sign of the distance. This method is kept for backwards compatibility for now, but is is recommended to use :meth:`offset_curve` instead. r-éÿÿÿÿ)r*r+r,)r()rr)ZsideÚ resolutionr+r,rrr Úparallel_offset¡süzLineString.parallel_offset)N)r NN)Ú__name__Ú __module__Ú __qualname__Ú__doc__Ú __slots__rÚpropertyrr$r%rÚroundr(r0rrrr r s" (   û +úé) r4ÚnumpyrrZshapely.geometry.baserrZshapely.geometry.pointrÚ__all__rÚlibÚregistryrrrr Ús 1