shapely 2.2.0rc1__tar.gz → 2.3.0.dev0__tar.gz

{shapely-2.2.0rc1 → shapely-2.3.0.dev0}/CHANGES.txt

@@ -1,7 +1,7 @@
 Changes
 =======
 
-2.2.0 (unreleased)
+2.2.0 (2026-10-07)
 ------------------
 
 Shapely 2.2.0 is a feature release with various new functions,

{shapely-2.2.0rc1 → shapely-2.3.0.dev0}/CITATION.cff

@@ -2,8 +2,8 @@ cff-version: 1.2.0
 message: "Please cite this software using these metadata."
 type: software
 title: Shapely
-version: "2.1.1"
-date-released: "2025-05-19"
+version: "2.2.0"
+date-released: "2026-10-07"
 doi: 10.5281/zenodo.5597138
 abstract: "Manipulation and analysis of geometric objects in the Cartesian plane."
 repository-artifact: https://pypi.org/project/Shapely

{shapely-2.2.0rc1 → shapely-2.3.0.dev0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: shapely
-Version: 2.2.0rc1
+Version: 2.3.0.dev0
 Summary: Manipulation and analysis of geometric objects
 Keywords: geometry,topology,gis
 Author: Sean Gillies

shapely-2.3.0.dev0/_version.py

@@ -0,0 +1,4 @@
+"""Module to show version information for the installed package."""
+
+__version__ = "2.3.0.dev0"
+__git_version__ = "93c894ed95e0fcfc7c29d4eec78781ab2045b3bd"

{shapely-2.2.0rc1 → shapely-2.3.0.dev0}/docs/conf.py

@@ -12,7 +12,7 @@ os.environ["SPHINX_DOC_BUILD"] = "1"
 # -- Project information -----------------------------------------------------
 
 project = 'Shapely'
-copyright = '2011-2025, Sean Gillies and Shapely contributors'
+copyright = '2011-2026, Sean Gillies and Shapely contributors'
 
 # The full version, including alpha/beta/rc tags.
 import shapely

{shapely-2.2.0rc1 → shapely-2.3.0.dev0}/docs/environment.yml

@@ -5,12 +5,9 @@ dependencies:
   - python=3.12
   - geos=3.13
   - numpy
-  - cython
   - sphinx-book-theme
   - sphinx-remove-toctrees
   - numpydoc=1.1
   - matplotlib
   - pip
   - pkg-config
-  - meson
-  - meson-python

{shapely-2.2.0rc1 → shapely-2.3.0.dev0}/docs/installation.rst

@@ -115,13 +115,13 @@ modules happens in editable mode, add ``-Ceditable-verbose=true`` to the command
 Conda environments
 ^^^^^^^^^^^^^^^^^^
 
-Development within conda environments requires additional packages installed
-with the ``conda`` command, including pre-built distributions of GEOS.
+When developing within a conda environment, it is recommended to install the
+development dependencies using conda, including a pre-built distribution of GEOS.
 For example:
 
 .. code-block:: console
 
-    $ conda create -n shapely-dev cython meson meson-python pkg-config ninja numpy geos pip pytest
+    $ conda create -n shapely-dev c-compiler cython meson meson-python pkg-config ninja numpy geos pip pytest
 
 Activate the environment and install shapely in editable mode using ``pip``:
 

{shapely-2.2.0rc1 → shapely-2.3.0.dev0}/docs/manual.rst

@@ -318,7 +318,7 @@ Coordinate values are accessed via `coords`, `x`, `y`, `z`, and `m` properties.
   >>> point.y
   0.0
 
-Coordinates may also be sliced. `New in version 1.2.14`.
+Coordinates may also be sliced.
 
 .. code-block:: pycon
 
@@ -386,7 +386,7 @@ The defining coordinate values are accessed via the `coords` property.
   >>> list(line.coords)
   [(0.0, 0.0), (1.0, 1.0)]
 
-Coordinates may also be sliced. `New in version 1.2.14`.
+Coordinates may also be sliced.
 
 .. code-block:: pycon
 
@@ -566,8 +566,6 @@ the :func:`shapely.geometry.box()` function.
   Makes a rectangular polygon from the provided bounding box values, with
   counter-clockwise order by default.
 
-  `New in version 1.2.9`.
-
 For example:
 
 .. code-block:: pycon
@@ -592,8 +590,6 @@ To obtain a polygon with a known orientation, use
   oriented counter-clockwise and the interior rings (holes) will be oriented
   clockwise.
 
-  `New in version 1.2.10`.
-
 .. _collections:
 
 Collections
@@ -979,8 +975,6 @@ example will be shown for each.
   region with positive signed area). This method applies to `LinearRing`
   objects only.
 
-  `New in version 1.2.10`.
-
 .. code-block:: pycon
 
   >>> LinearRing([(1,0), (1,1), (0,0)]).is_ccw
@@ -1854,8 +1848,6 @@ transform (`rotate`, `scale`, etc.). The functions can be used with all
 geometry types (except `GeometryCollection`), and 3D types are either
 preserved or supported by 3D affine transformations.
 
-`New in version 1.2.17`.
-
 .. function:: shapely.affinity.affine_transform(geom, matrix)
 
   Returns a transformed geometry using an affine transformation matrix.
@@ -2060,85 +2052,159 @@ Other Transformations
 Shapely supports map projections and other arbitrary transformations of
 geometric objects.
 
-.. function:: shapely.ops.transform(func, geom)
+.. function:: shapely.transform(geom, func, include_z=False, interleaved=True)
+  :no-index:
 
-  Applies `func` to all coordinates of `geom` and returns a new
-  geometry of the same type from the transformed coordinates.
+  Apply a transformation `func` to all the coordinates of `geom`, and return
+  a new geometry of the same type from the transformed coordinates.
 
-  `func` maps x, y, and optionally z to output xp, yp, zp. The input
-  parameters may be iterable types like lists or arrays or single values.
-  The output shall be of the same type: scalars in, scalars out;
-  lists in, lists out.
+  By default, `func` maps a single 2D array of coordinates to a new 2D array
+  of transformed coordinates (``func([[x1, y1], [x2, y2], ...])``).
 
-  `transform` tries to determine which kind of function was passed in
-  by calling `func` first with n iterables of coordinates, where n
-  is the dimensionality of the input geometry. If `func` raises
-  a `TypeError` when called with iterables as arguments,
-  then it will instead call `func` on each individual coordinate
-  in the geometry.
+  If your function works on separate arrays of x, y, and optionally z
+  coordinates, set `interleaved=False` (``func([x1, x2, ...], [y1, y2, ...])``).
 
-  `New in version 1.2.18`.
+  Full reference: :func:`shapely.transform`
 
-For example, here is an identity function applicable to both types of input
-(scalar or array).
+For example, here is a simple function that returns shifted coordinates:
 
 .. code-block:: python
 
-    def id_func(x, y, z=None):
-        return tuple(filter(None, [x, y, z]))
+  def shift_xy(coords):
+      # NumPy applies this addition element-wise to all coordinates
+      return coords + 2
 
-    g2 = transform(id_func, g1)
+  g2 = shapely.transform(g1, shift_xy)
 
+or that swaps the x and y coordinates:
 
-If using `pyproj>=2.1.0`, the preferred method to project geometries is:
+.. code-block:: python
+
+  def swap_xy(x, y):
+      return y, x
+
+  # specify interleaved=False to pass separate x and y arrays to the function
+  g3 = shapely.transform(g1, swap_xy, interleaved=False)
+
+To reproject geometries using ``pyproj``:
 
 .. code-block:: python
 
     import pyproj
 
-    from shapely import Point
-    from shapely.ops import transform
+    from shapely import Point, transform
 
     wgs84_pt = Point(-72.2495, 43.886)
 
     wgs84 = pyproj.CRS('EPSG:4326')
     utm = pyproj.CRS('EPSG:32618')
 
-    project = pyproj.Transformer.from_crs(wgs84, utm, always_xy=True).transform
-    utm_point = transform(project, wgs84_pt)
+    transformer = pyproj.Transformer.from_crs(wgs84, utm, always_xy=True)
+    # specify interleaved=False because the pyproj transform function expects
+    # separate x, y arrays as input
+    utm_point = transform(wgs84_pt, transformer.transform, interleaved=False)
 
 It is important to note that in the example above, the `always_xy` kwarg is
 required as Shapely only supports coordinates in X,Y order, and in PROJ 6 the
 WGS84 CRS uses the EPSG-defined Lat/Lon coordinate order instead of the
 expected Lon/Lat.
 
-If using `pyproj < 2.1`, then the canonical example is:
+.. function:: shapely.transform_coordseq(geom, func, include_z=False, interleaved=True)
+   :no-index:
 
-.. code-block:: python
+   Apply a transformation `func` to the coordinate sequences of a geometry.
 
-    from functools import partial
-    import pyproj
+   Similar to :func:`shapely.transform`, the transformation function can
+   accept a single 2D array of coordinates or separate x, y, and optionally
+   z arrays (depending on the ``interleaved`` keyword).
 
-    from shapely.ops import transform
+   The difference is that in case of :func:`~shapely.transform_coordseq`,
+   the transformation function is called separately for each coordinate
+   sequence (and thus only receiving the coordinates of one sequence at a
+   time), instead of being called once for all coordinates. For polygons, this
+   means per ring.
 
-    wgs84 = pyproj.Proj(init='epsg:4326')
-    utm = pyproj.Proj(init='epsg:32618')
+   As a result, the number of coordinate pairs per coordinate sequence is
+   allowed to change.
 
-    project = partial(
-        pyproj.transform,
-        wgs84,
-        utm)
+   Full reference: :func:`shapely.transform_coordseq`
 
-    utm_point = transform(project, wgs84_pt)
+For example, reducing a linestring to only its first 2 points:
 
-Lambda expressions such as the one in
+.. code-block:: pycon
 
-.. code-block:: python
+  >>> import shapely
+  >>> line = LineString([(2, 2), (4, 4), (6, 6)])
+  >>> shapely.transform_coordseq(line, lambda coords: coords[:2])
+  <LINESTRING (2 2, 4 4)>
 
-    g2 = transform(lambda x, y, z=None: (x+1.0, y+1.0), g1)
+The :func:`~shapely.transform` function is the more performant option, so
+whenever your transformation function can be applied to all coordinates
+element-wise at once and does not change the number of coordinate pairs, we
+recommend using that.
 
-also satisfy the requirements for `func`.
+Finally, there is a third `transform` function, which existed before the
+options described above, and is kept for backwards compatibility but is
+deprecated:
 
+.. function:: shapely.ops.transform(func, geom)
+
+  Applies `func` to all coordinates of `geom` and returns a new
+  geometry of the same type from the transformed coordinates.
+
+  `func` maps x, y, and optionally z to output xp, yp, zp. The input
+  parameters may be iterable types like lists or arrays or single values.
+  The output shall be of the same type: scalars in, scalars out;
+  lists in, lists out.
+
+  `transform` tries to determine which kind of function was passed in
+  by calling `func` first with n iterables of coordinates, where n
+  is the dimensionality of the input geometry. If `func` raises
+  a `TypeError` when called with iterables as arguments,
+  then it will instead call `func` on each individual coordinate
+  in the geometry.
+
+  .. deprecated:: 2.2.0
+
+  **Updating to use** :func:`shapely.transform` **or** :func:`shapely.transform_coordseq`
+
+  If you are currently using ``shapely.ops.transform``, consider whether your
+  transformation function can be applied to all coordinates at once
+  independently. If that is the case, replace:
+
+  .. code-block:: python
+
+    geom2 = shapely.ops.transform(func, geom1)
+
+  with :func:`shapely.transform`:
+
+  .. code-block:: python
+
+    geom2 = shapely.transform(geom1, func, interleaved=False)
+
+  If your function has custom logic per coordinate sequence or changes the
+  number of coordinate pairs, use :func:`shapely.transform_coordseq`.
+
+  If your function only works on scalar coordinate values, you can define
+  a small wrapper function that accepts an array of coordinates, and
+  applies your scalar function to each coordinate pair individually:
+
+  .. code-block:: python
+
+    import numpy as np
+
+    def func_scalar(x, y, z=None):
+        if x < 0:
+            x += 360
+        return x, y
+
+    def func_wrapped(coords):
+        return np.array([func_scalar(x, y) for x, y in coords])
+
+    geom2 = shapely.transform(geom1, func_wrapped)
+
+  Note: this scalar function is only for illustration purposes, and this
+  specific operation can also be re-written to use vectorized array operations.
 
 Other Operations
 ================
@@ -2183,8 +2249,6 @@ Sequences of touching lines can be merged into `MultiLineStrings` or
   form part of polygon. Invalid ring lines form rings which are invalid
   (bowties, etc).
 
-  `New in version 1.2.18.`
-
   .. code-block:: pycon
 
     >>> from shapely import polygonize_full
@@ -2233,8 +2297,6 @@ within a rectangle.
     not guaranteed to be valid. No exceptions will be raised for topological
     errors.
 
-    `New in version 1.7.`
-
 .. code-block:: python
 
   >>> from shapely import clip_by_rect
@@ -2404,8 +2466,6 @@ a second geometry with a given tolerance.
    The `tolerance` argument specifies the minimum distance between vertices for
    them to be snapped.
 
-   `New in version 1.5.0`
-
 .. code-block:: pycon
 
   >>> from shapely import snap
@@ -2431,8 +2491,6 @@ linear geometries.
    inputs. The second element is a MultiLineString containing shared paths with
    the opposite direction for the two inputs.
 
-   `New in version 1.6.0`
-
 .. code-block:: pycon
 
   >>> from shapely import shared_paths
@@ -2564,8 +2622,6 @@ Diagnostics
 
   Returns a string explaining the validity or invalidity of the object.
 
-  `New in version 1.2.1`.
-
 The messages may or may not have a representation of a problem point that can
 be parsed out.
 
@@ -2640,13 +2696,6 @@ Polylabel
   Finds the approximate location of the pole of inaccessibility for a given
   polygon. Based on Vladimir Agafonkin's polylabel_.
 
-  `New in version 1.6.0`
-
-.. note::
-
-  Prior to 1.7 `polylabel` must be imported from `shapely.algorithms.polylabel`
-  instead of `shapely.ops`.
-
 .. code-block:: pycon
 
   >>> from shapely.ops import polylabel
@@ -2672,8 +2721,6 @@ cannot add or remove geometries.
 
   References to these geometric objects are kept and stored in the R-tree.
 
-  `New in version 1.4.0`.
-
   .. method:: strtree.query(geom)
     :noindex:
 
@@ -2864,8 +2911,6 @@ The GeoJSON-like mapping of a geometric object can be obtained using
   counterclockwise, and interior rings (holes) clockwise with
   :func:`shapely.orient_polygons`.
 
-  `New in version 1.2.3`.
-
   For example, using the same `GeoThing` class:
 
 .. code-block:: pycon

{shapely-2.2.0rc1 → shapely-2.3.0.dev0}/docs/release/2.x.rst

@@ -4,7 +4,7 @@ Version 2.x
 
 .. _version-2-2-0:
 
-Version 2.2.0 (2026-09-xx)
+Version 2.2.0 (2026-10-07)
 --------------------------
 
 New features
@@ -41,9 +41,9 @@ vectorized functions:
   of a geometry (#2313).
 - :func:`.coverage_clean`, which returns a cleaned version of geometries
   forming a polygonal coverage (#2454)  (requires GEOS >= 3.14).
-- :func:`.split` to split a geometry by another geometry (uses GEOS>=3.15,
-  falls back to the existing :func:`shapely.ops.split` implementation
-  otherwise) (#2477).
+- :func:`~shapely.split` to split a geometry by another geometry (uses
+  GEOS>=3.15, falls back to the existing :func:`shapely.ops.split`
+  implementation otherwise) (#2477).
 
 In addition, two other functions have been added to the top-level namespace:
 
@@ -67,25 +67,36 @@ Other improvements
   reused through a thread-local GEOS context (#2343).
 
 - :func:`.Polygon.from_bounds` now builds the ring in counterclockwise order,
-  consistent with :function:`shapely.box`, so the result satisfies the GeoJSON
+  consistent with :func:`shapely.box`, so the result satisfies the GeoJSON
   right-hand rule (#2396).
 
 - Added return values to :func:`.prepare` and :func:`.destroy_prepared`. They
   now return whether something was done; calling `prepare` twice on a geometry
   will first return `True`, and then `False` (#2359).
 
-- The :func:`.split` and :func:`shapely.ops.split` functions now support
-  splitting a (Multi)Polygon by another (Multi)Polygon, by using the boundary
-  to split to with (similarly as was already done for splitting a
+- The :func:`~shapely.split` and :func:`shapely.ops.split` functions now
+  support splitting a (Multi)Polygon by another (Multi)Polygon, by using the
+  boundary to split to with (similarly as was already done for splitting a
   (Multi)LineString with a polygon) (#2505).
 
 API changes
 ^^^^^^^^^^^
 
-- The :func:`shapely.ops.transform`` is deprecated. Use the more specific
+- The :func:`shapely.ops.transform` is deprecated. Use the more specific
   :meth:`shapely.transform` (when your function works independently on all
   coordinates) or :meth:`shapely.transform_coordseq` (when your function works
-  on the coordinate sequence directly) instead (#1902).
+  on the coordinate sequence directly) instead. See
+  :func:`the manual with update advice <shapely.ops.transform>` for more
+  details (#1902).
+
+- The ``multithreading_enabled`` decorator is deprecated, and is also no longer
+  used internally. This decorator added overhead to each function call, while
+  only providing minimal and incomplete safety guarantees around multi-threaded
+  usage of shapely (#2338).
+  When sharing NumPy array of geometries between threads, it is the responsibility
+  of the user to ensure those geometries are not modified at the same time.
+  See the `multithreading section <https://github.com/shapely/shapely#multithreading>`__
+  for more details.
 
 Bug fixes
 ^^^^^^^^^
@@ -95,6 +106,8 @@ Bug fixes
   passing a sequence of non-polygons (#2461).
 - Fix a crash in :func:`.coverage_invalid_edges` on invalid (non-geometry)
   input (#2483).
+- Fix keyword argument forwarding in :func:`shapely.line_interpolate_point`
+  and :func:`shapely.line_locate_point` (#2480).
 
 Packaging
 ^^^^^^^^^

{shapely-2.2.0rc1 → shapely-2.3.0.dev0}/pyproject.toml

@@ -2,7 +2,7 @@
 requires = [
     # keep in sync with a subset of [dependency-groups.build]
     "Cython",
-    "meson-python>=0.15.0",
+    "meson-python>=0.15.0,!=0.22.0",
     "numpy>=1.26,<3",
 ]
 build-backend = "mesonpy"
@@ -46,7 +46,7 @@ build = [
     # keep in sync with a superset of [build-system.requires]
     "Cython",
     "meson>=1.2.1",
-    "meson-python>=0.15.0",
+    "meson-python>=0.15.0,!=0.22.0",
     "ninja",
     "numpy>=1.26,<3",
 ]
@@ -184,7 +184,6 @@ ignore = [
 
 [tool.ruff.lint.isort]
 combine-as-imports = true
-extra-standard-library = ["packaging"]
 
 [tool.ruff.lint.pydocstyle]
 convention = "numpy"
@@ -197,3 +196,11 @@ allow-dunder-method-names = [
     "_repr_svg_",
 ]
 max-positional-args = 8  # TODO: revise with deprecate_positional changes
+
+[tool.versioneer]
+VCS = "git"
+style = "pep440"
+versionfile_source = "src/shapely/_version.py"
+versionfile_build = "shapely/_version.py"
+tag_prefix = ""
+parentdir_prefix = "shapely-"