shapely 2.0.7__tar.gz → 2.1.0rc1__tar.gz

{shapely-2.0.7 → shapely-2.1.0rc1}/CHANGES.txt

@@ -1,6 +1,89 @@
 Changes
 =======
 
+2.1.0 (unreleased)
+------------------
+
+API changes:
+
+- Equality of geometries (``geom1 == geom2``) now considers NaN coordinate
+  values in the same location to be equal (#1775). It is recommended however to
+  ensure geometries don't have NaN values in the first place, for which you can
+  now use the ``handle_nan`` parameter in construction functions.
+
+Bug fixes:
+
+- Prevent crash when serializing a number > 1e100 to WKT with GEOS < 3.13. (#1907)
+- Ensure ``plot_polygon`` does not color the interiors of polygons (#1933).
+- Fixes GeoJSON serialization of empty points (#2118)
+- Fixes `__geo_interface__` handling of empty points (#2120)
+- Fixes ``GeometryCollection()`` constructor accepting an array of geometries (#2017).
+
+Improvements:
+
+- Add a ``handle_nan`` parameter to ``shapely.points()``,
+  ``shapely.linestrings()`` and ``shapely.linearrings()`` to allow, skip, or
+  error on nonfinite (NaN / Inf) coordinates. The default behaviour (allow) is
+  backwards compatible (#1594, #1811).
+- Add an ``interleaved`` parameter to ``shapely.transform()`` allowing a transposed call
+  signature in the ``transformation`` function.
+- The ``include_z`` in ``shapely.transform()`` now also allows ``None``, which
+  lets it automatically detect the dimensionality of each input geometry.
+- Add an ``include_m`` keyword in ``to_ragged_array`` and ``get_coordinates`` (#2234, #2235)
+- Add parameters ``method`` and ``keep_collapsed`` to ``shapely.make_valid()`` (#1941)
+- The ``voronoi_polygons`` now accepts the ``ordered`` keyword, optionally forcing the
+  order of polygons within the GeometryCollection to follow the order of input
+  coordinates. Requires at least GEOS 3.12. (#1968)
+- Add option on ``invalid="fix"`` to ``from_wkb`` and ``from_wkt`` (#2094)
+- Add a ``normalize`` keyword to ``equals_exact`` (#1231)
+- Handle ``Feature`` type in ``shapely.geometry.shape`` (#1815)
+- Add support to split polygons by multilinestrings (#2206)
+- Add an ``m`` attribute on the Point class and an ``has_m`` attribute on the base Geometry class.
+
+New functions:
+
+- Add ``disjoint_subset_union`` and ``disjoint_subset_union_all`` as an optimized
+  version of union and union_all, assuming inputs can be divided into subsets that do
+  not intersect. Requires at least GEOS 3.12.
+- Add function ``minimum_clearance_line`` (#2106)
+- Add function ``maximum_inscribed_circle`` (#1307)
+- Add function ``orient_polygons`` (#2147)
+- Add function ``constrained_delaunay_triangles`` (#1685)
+- Add function ``coverage_simplify`` to allow topological simplification of polygonal
+  coverages (#1969)
+- Add function ``coverage_is_valid`` and ``coverage_invalid_edges`` to validate
+  an array of geometries as valid topological coverage (#2156)
+- Add function ``equals_identical`` (#1760)
+- Add function ``has_m`` (#2008)
+- Add function ``get_m`` (#2019)
+
+Breaking changes in GEOS 3.12:
+
+- ``oriented_envelope`` / ``minimum_rotated_rectangle`` changed its implementation
+  in GEOS 3.12. Be aware that results will change when updating GEOS. Coincidentally
+  the implementation is similar to the shapely 1.x approach. (#1885)
+- ``get_coordinate_dimension`` / ``has_z`` now considers geometries three dimensional if
+  they have a NaN z coordinate. (#1885)
+- ``voronoi_polygons`` changed its output from a LINESTRING to a MULTILINESTRING in case
+  ``only_edges=True``. (#1885)
+- The WKT representation of a MULTIPOINT changed from for example "MULTIPOINT (0 0, 1 1)"
+  to "MULTIPOINT ((0 0), (1 1))". (#1885)
+
+Deprecations:
+
+- The ``shapely.geos`` module is deprecated. All GEOS-version related attributes are
+  available directly from the top-level ``shapely`` namespace as well (already since
+  shapely 2.0) (#2145).
+- The ``shapely.vectorized`` module is deprecated. The two functions (``contains and
+  ``touches``) can be replaced by the top-level vectorized functions ``contains_xy``
+  and ``intersects_xy`` (#1630).
+
+Packaging:
+
+- Require GEOS >= 3.9, NumPy >= 1.21, and Python >= 3.10 (#1802, #1885, #2124)
+- Binary wheels are now built for musllinux (Alpine) x86_64 platforms (#1996).
+- Upgraded the GEOS version in the binary wheel distributions to 3.13.1.
+
 2.0.7 (2025-01-30)
 ------------------
 
@@ -46,6 +129,7 @@ Bug fixes:
 - Fix bug in ``to_wkt`` with multiple empty Z geometries (#2012).
 - Fix bug in ``to_ragged_array`` for an array of Points with missing values (#2034).
 
+
 2.0.3 (2024-02-16)
 ------------------
 
@@ -55,6 +139,7 @@ Bug fixes:
   therefore a ``numpy<2`` upper pin was added to the requirements (#1972).
 - Upgraded the GEOS version in the binary wheel distributions to 3.11.3.
 
+
 2.0.2 (2023-10-12)
 ------------------
 
@@ -66,11 +151,16 @@ Bug fixes:
 - Fix ``minimum_rotated_rectangle`` (``oriented_envelope``) to always return
   the minimum area solution (instead of minimum width). In practice, it will use the
   GEOS implementation only for GEOS 3.12+, and for older GEOS versions fall back to the
-  implementation that was included in Shapely < 2.
+  implementation that was included in Shapely < 2 (#1670).
+- Fix ``from_ragged_array`` to work with read-only array input (#1744).
+- Fix the handling of z coordinates ``shapely.ops.substring`` (#1699).
 
 Wheels are available for Python 3.12 (and still include GEOS 3.11.2). Building
 from source is now compatible with Cython 3.
 
+For a full changelog, see
+https://shapely.readthedocs.io/en/latest/release/2.x.html#version-2-0-2
+
 2.0.1 (2023-01-30)
 ------------------
 
@@ -91,12 +181,13 @@ Improvements:
 For a full changelog, see
 https://shapely.readthedocs.io/en/latest/release/2.x.html#version-2-0-1
 
+
 2.0.0 (2022-12-12)
 ------------------
 
 Shapely version 2.0.0 is a major release featuring a complete refactor of the
 internals and new vectorized (element-wise) array operations providing
-considerable performance improvements. 
+considerable performance improvements.
 
 For a full changelog, see
 https://shapely.readthedocs.io/en/latest/release/2.x.html#version-2-0-0

{shapely-2.0.7 → shapely-2.1.0rc1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: shapely
-Version: 2.0.7
+Version: 2.1.0rc1
 Summary: Manipulation and analysis of geometric objects
 Author: Sean Gillies
 Maintainer: Shapely contributors
@@ -16,21 +16,19 @@ Classifier: Operating System :: Unix
 Classifier: Operating System :: MacOS
 Classifier: Operating System :: Microsoft :: Windows
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.7
-Classifier: Programming Language :: Python :: 3.8
-Classifier: Programming Language :: Python :: 3.9
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Scientific/Engineering :: GIS
-Requires-Python: >=3.7
+Requires-Python: >=3.10
 Description-Content-Type: text/x-rst
 License-File: LICENSE.txt
-Requires-Dist: numpy<3,>=1.14
+Requires-Dist: numpy>=1.21
 Provides-Extra: test
 Requires-Dist: pytest; extra == "test"
 Requires-Dist: pytest-cov; extra == "test"
+Requires-Dist: scipy-doctest; extra == "test"
 Provides-Extra: docs
 Requires-Dist: numpydoc==1.1.*; extra == "docs"
 Requires-Dist: matplotlib; extra == "docs"
@@ -143,11 +141,11 @@ See the documentation for more examples and guidance: https://shapely.readthedoc
 Requirements
 ============
 
-Shapely 2.0 requires
+Shapely 2.1 requires
 
-* Python >=3.7
-* GEOS >=3.5
-* NumPy >=1.14
+* Python >=3.10
+* GEOS >=3.9
+* NumPy >=1.21
 
 Installing Shapely
 ==================

{shapely-2.0.7 → shapely-2.1.0rc1}/README.rst

@@ -103,11 +103,11 @@ See the documentation for more examples and guidance: https://shapely.readthedoc
 Requirements
 ============
 
-Shapely 2.0 requires
+Shapely 2.1 requires
 
-* Python >=3.7
-* GEOS >=3.5
-* NumPy >=1.14
+* Python >=3.10
+* GEOS >=3.9
+* NumPy >=1.21
 
 Installing Shapely
 ==================

shapely-2.1.0rc1/docs/coverage.rst

@@ -0,0 +1,11 @@
+Coverage operations
+===================
+
+.. currentmodule:: shapely
+
+.. autosummary::
+   :toctree: reference/
+
+{% for function in get_module_functions("_coverage") %}
+   {{ function }}
+{% endfor %}

{shapely-2.0.7 → shapely-2.1.0rc1}/docs/design.rst

@@ -27,4 +27,3 @@ In sum, Shapely's stack is 4 layers:
 .. [1] John R. Herring, Ed.,
    “OpenGIS Implementation Specification for Geographic information - Simple
    feature access - Part 1: Common architecture,” Oct. 2006.
-

{shapely-2.0.7 → shapely-2.1.0rc1}/docs/geometry.rst

@@ -53,8 +53,8 @@ or WKB (Well-Known Binary) representation:
   >>> from_wkb(b"\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\xf0?\x00\x00\x00\x00\x00\x00\xf0?")
   <POINT (1 1)>
 
-A more efficient way of constructing geometries is by making use of the (vectorized)
-functions described in :ref:`ref-creation`.
+A more efficient way of constructing geometries is by making use of the
+(vectorized) functions described in :ref:`ref-creation`.
 
 Pickling
 ~~~~~~~~
@@ -181,9 +181,9 @@ Canonical form
 When operations are applied on geometries the result is returned according to
 some conventions.
 
-In most cases, geometries will be returned in "mild" canonical form. There is no
-goal to keep this form stable, so it is expected to change in future versions of
-GEOS:
+In most cases, geometries will be returned in "mild" canonical form. There is
+no goal to keep this form stable, so it is expected to change in future
+versions of GEOS:
 
 - the coordinates of exterior rings follow a clockwise orientation and interior
   rings have a counter-clockwise orientation. This is the opposite of the OGC
@@ -194,9 +194,9 @@ GEOS:
 - the order of geometry types in a collection can be changed, but the order is
   undefined
 
-When :func:`~shapely.normalize` is used, the "strict" canonical form is applied.
-This type of normalization is meant to be stable, so changes to it will be
-avoided if possible:
+When :func:`~shapely.normalize` is used, the "strict" canonical form is
+applied. This type of normalization is meant to be stable, so changes to it
+will be avoided if possible:
 
 - the coordinates of exterior rings follow a clockwise orientation and interior
   rings have a counter-clockwise orientation

{shapely-2.0.7 → shapely-2.1.0rc1}/docs/index.rst

@@ -29,9 +29,11 @@
    set_operations
    constructive
    linear
+   coverage
    coordinates
    strtree
    testing
+   plotting
 
 Indices and tables
 ==================

{shapely-2.0.7 → shapely-2.1.0rc1}/docs/installation.rst

@@ -25,6 +25,15 @@ Shapely is available on the conda-forge channel. Install as follows::
 
     $ conda install shapely --channel conda-forge
 
+Installation of the development version using nightly wheels
+------------------------------------------------------------
+
+If you want to test the latest development version of Shapely, the easiest way
+to get this version is by installing it from the Scientific Python index of
+nightly wheel packages::
+
+    python -m pip install --pre --upgrade --extra-index-url https://pypi.anaconda.org/scientific-python-nightly-wheels/simple shapely
+
 
 Installation from source with custom GEOS library
 -------------------------------------------------
@@ -45,16 +54,17 @@ On macOS::
     $ brew install geos  # skip this if you already have GEOS
     $ pip install shapely --no-binary shapely
 
-If you've installed GEOS to a standard location on Linux or macOS, the installation will automatically
-find it using ``geos-config``. See the notes below on GEOS discovery at compile time
-to configure this.
+If you've installed GEOS to a standard location on Linux or macOS, the
+installation will automatically find it using ``geos-config``. See the notes
+below on GEOS discovery at compile time to configure this.
 
-We do not have a recipe for Windows platforms. The following steps should enable you
-to build Shapely yourself:
+We do not have a recipe for Windows platforms. The following steps should
+enable you to build Shapely yourself:
 
 - Get a C compiler applicable to your Python version (https://wiki.python.org/moin/WindowsCompilers)
 - Download and install a GEOS binary (https://trac.osgeo.org/osgeo4w/)
-- Set GEOS_INCLUDE_PATH and GEOS_LIBRARY_PATH environment variables (see below for notes on GEOS discovery)
+- Set GEOS_INCLUDE_PATH and GEOS_LIBRARY_PATH environment variables (see below
+  for notes on GEOS discovery)
 - Run ``pip install shapely --no-binary``
 - Make sure the GEOS .dll files are available on the PATH
 
@@ -62,8 +72,8 @@ to build Shapely yourself:
 Installation for local development
 -----------------------------------
 
-This is similar to installing with a custom GEOS binary, but then instead of installing
-Shapely with pip from PyPI, you clone the package from Github::
+This is similar to installing with a custom GEOS binary, but then instead of
+installing Shapely with pip from PyPI, you clone the package from Github::
 
     $ git clone git@github.com:shapely/shapely.git
     $ cd shapely/
@@ -72,8 +82,8 @@ Install it in development mode using ``pip``::
 
     $ pip install -e .[test]
 
-For development, use of a virtual environment is strongly recommended. For example
-using ``venv``:
+For development, use of a virtual environment is strongly recommended. For
+example using ``venv``:
 
 .. code-block:: console
 
@@ -101,9 +111,10 @@ Shapely can be tested using ``pytest``::
 GEOS discovery (compile time)
 -----------------------------
 
-If GEOS is installed on Linux or macOS, the ``geos-config`` command line utility
-should be available and ``pip`` will find GEOS automatically.
-If the correct ``geos-config`` is not on the PATH, you can add it as follows (on Linux/macOS)::
+If GEOS is installed on Linux or macOS, the ``geos-config`` command line
+utility should be available and ``pip`` will find GEOS automatically.
+If the correct ``geos-config`` is not on the PATH, you can add it as follows
+(on Linux/macOS)::
 
     $ export PATH=/path/to/geos/bin:$PATH
 
@@ -113,8 +124,8 @@ header files using environment variables (on Linux/macOS)::
     $ export GEOS_INCLUDE_PATH=/path/to/geos/include
     $ export GEOS_LIBRARY_PATH=/path/to/geos/lib
 
-On Windows, there is no ``geos-config`` and the include and lib folders need to be
-specified manually in any case::
+On Windows, there is no ``geos-config`` and the include and lib folders need to
+be specified manually in any case::
 
     $ set GEOS_INCLUDE_PATH=C:\path\to\geos\include
     $ set GEOS_LIBRARY_PATH=C:\path\to\geos\lib
@@ -129,13 +140,15 @@ Common locations of GEOS (to be suffixed by ``lib``, ``include`` or ``bin``):
 GEOS discovery (runtime)
 ------------------------
 
-Shapely is dynamically linked to GEOS. This means that the same GEOS library that was used
-during Shapely compilation is required on your system at runtime. When using Shapely that was distributed
-as a binary wheel or through conda, this is automatically the case and you can stop reading.
+Shapely is dynamically linked to GEOS. This means that the same GEOS library
+that was used during Shapely compilation is required on your system at runtime.
+When using Shapely that was distributed as a binary wheel or through conda,
+this is automatically the case and you can stop reading.
 
-In other cases this can be tricky, especially if you have multiple GEOS installations next
-to each other. We only include some guidelines here to address this issue as this document is
-not intended as a general guide of shared library discovery.
+In other cases this can be tricky, especially if you have multiple GEOS
+installations next to each other. We only include some guidelines here to
+address this issue as this document is not intended as a general guide of
+shared library discovery.
 
 If you encounter exceptions like:
 
@@ -143,17 +156,21 @@ If you encounter exceptions like:
 
    ImportError: libgeos_c.so.1: cannot open shared object file: No such file or directory
 
-You will have to make the shared library file available to the Python interpreter. There are in
-general four ways of making Python aware of the location of shared library:
-
-1. Copy the shared libraries into the ``shapely`` module directory (this is how Windows binary wheels work:
-   they are distributed with the correct dlls in the ``shapely`` module directory)
-2. Copy the shared libraries into the library directory of the Python interpreter (this is how
-   Anaconda environments work)
-3. Copy the shared libraries into some system location (``C:\Windows\System32``; ``/usr/local/lib``,
-   this happens if you installed GEOS through ``apt`` or ``brew``)
-4. Add the shared library location to a the dynamic linker path variable at runtime.
-   (Advanced usage; Linux and macOS only; on Windows this method was deprecated in Python 3.8)
+You will have to make the shared library file available to the Python
+interpreter. There are in general four ways of making Python aware of the
+location of shared library:
+
+1. Copy the shared libraries into the ``shapely`` module directory (this is how
+   Windows binary wheels work: they are distributed with the correct dlls in
+   the ``shapely`` module directory)
+2. Copy the shared libraries into the library directory of the Python
+   interpreter (this is how Anaconda environments work)
+3. Copy the shared libraries into some system location
+   (``C:\Windows\System32``; ``/usr/local/lib``, this happens if you installed
+   GEOS through ``apt`` or ``brew``)
+4. Add the shared library location to a the dynamic linker path variable at
+   runtime. (Advanced usage; Linux and macOS only; on Windows this method was
+   deprecated in Python 3.8)
 
 The filenames of the GEOS shared libraries are:
 

{shapely-2.0.7 → shapely-2.1.0rc1}/docs/io.rst

@@ -9,4 +9,3 @@ Input/Output
 {% for function in get_module_functions("io") %}
    {{ function }}
 {% endfor %}
-