concavewrap-geo 0.1.0__tar.gz

concavewrap_geo-0.1.0/CHANGELOG.md

@@ -0,0 +1,9 @@
+# Changelog
+
+## 0.1.0 — 2026-10-01
+
+- Add polygon-safe concave hull construction with explicit ratio semantics.
+- Add global, grouped, and disconnected-component scopes.
+- Add hole, invalid-geometry, and convex-fallback policies.
+- Add GeoPackage output, JSON diagnostics, CLI, Python API, and synthetic tests.
+- Add executable forest-patch, large-gap, narrow-neck, and hole-policy examples.

concavewrap_geo-0.1.0/CITATION.cff

@@ -0,0 +1,8 @@
+cff-version: 1.2.0
+message: "If you use concavewrap-geo, please cite this software."
+title: "concavewrap-geo"
+version: 0.1.0
+authors:
+  - family-names: Nikitina
+    given-names: Alena
+license: Apache-2.0

concavewrap_geo-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,5 @@
+# Contributing
+
+Please open an issue before a large change. Geometry behavior must include tests
+for coverage, validity, convex bounds, and deterministic grouping. Use synthetic
+or openly licensed data only.

concavewrap_geo-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

concavewrap_geo-0.1.0/MANIFEST.in

@@ -0,0 +1,3 @@
+include CHANGELOG.md CITATION.cff CONTRIBUTING.md SECURITY.md
+recursive-include docs *.md *.svg
+recursive-include examples *.py

concavewrap_geo-0.1.0/PKG-INFO

@@ -0,0 +1,185 @@
+Metadata-Version: 2.4
+Name: concavewrap-geo
+Version: 0.1.0
+Summary: Auditable concave hulls that cover complete polygon areas
+Author: Alena Nikitina
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/NikitinaAD/concavewrap-geo
+Project-URL: Repository, https://github.com/NikitinaAD/concavewrap-geo
+Project-URL: Issues, https://github.com/NikitinaAD/concavewrap-geo/issues
+Keywords: gis,geospatial,polygon,concave-hull,shapely
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: Programming Language :: Python :: 3
+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.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: geopandas>=0.14
+Requires-Dist: shapely<3,>=2.0
+Requires-Dist: pyproj>=3.6
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Requires-Dist: pytest-cov>=5; extra == "test"
+Requires-Dist: ruff>=0.8; extra == "test"
+Dynamic: license-file
+
+# concavewrap-geo
+
+[![CI](https://github.com/NikitinaAD/concavewrap-geo/actions/workflows/ci.yml/badge.svg)](https://github.com/NikitinaAD/concavewrap-geo/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/concavewrap-geo.svg)](https://pypi.org/project/concavewrap-geo/)
+[![Python](https://img.shields.io/pypi/pyversions/concavewrap-geo.svg)](https://pypi.org/project/concavewrap-geo/)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+**Build auditable concave hulls that cover complete polygon areas.**
+
+Many concave-hull implementations guarantee that the output contains the input
+vertices. For areal data that is not enough: a hull edge can cut through a source
+polygon. `concavewrap` repairs or rejects invalid input, constructs the hull, and
+then enforces and verifies coverage of every source polygon.
+
+![Polygon patches become a polygon-safe concave hull](https://raw.githubusercontent.com/NikitinaAD/concavewrap-geo/main/docs/demo.svg)
+
+## Quick start
+
+```bash
+python -m pip install concavewrap-geo
+concavewrap build areas.gpkg \
+  --layer areas \
+  --ratio 0.25 \
+  --output hulls.gpkg \
+  --diagnostics hulls.json
+```
+
+The output is a GeoPackage layer named `hulls`. The JSON report records input and
+output areas, added fill area, the convex-hull area, coverage checks, repaired
+features, and any convex fallback.
+
+## Reproducible example
+
+Generate and process four synthetic polygon arrangements, including the failure
+modes that commonly make a single concave-hull setting misleading:
+
+```bash
+python examples/run_examples.py
+```
+
+| scenario | question answered | expected result |
+|---|---|---|
+| `forest-patches` | can irregular areal patches be wrapped without cutting them? | one hull that covers every complete polygon |
+| `large-gap` | should disconnected patches be bridged? | `global` gives one hull; `component` gives two |
+| `narrow-neck` | does a thin connecting polygon remain covered? | one valid hull covering the neck and both ends |
+| `ring-with-hole` | should a semantic hole remain open? | `allow_holes=True` keeps it; the default fills it |
+
+Generated inputs, outputs, and JSON reports are placed under
+`examples/generated/`. To run the standard case through the CLI:
+
+```bash
+concavewrap build examples/generated/forest-patches.gpkg \
+  --layer areas \
+  --ratio 0.25 \
+  --output examples/generated/forest-hull-cli.gpkg \
+  --diagnostics examples/generated/forest-hull-cli.json
+```
+
+Expected audit values are printed and asserted by the script, then saved in
+`summary.json`. No external or real-world data is used.
+
+## Ratio and policies
+
+`--ratio` follows GEOS/Shapely semantics:
+
+| value | behavior |
+|---:|---|
+| `0` | most concave result available from the input vertices |
+| `0.25` | useful starting point for irregular polygon collections |
+| `1` | convex hull |
+
+The ratio is dimensionless. It is not an alpha radius or a distance threshold,
+so values from alpha-shape tools cannot be copied directly.
+
+| option | choices | meaning |
+|---|---|---|
+| `--scope` | `global`, `component` | bridge all polygons in a group, or keep disconnected dissolved components separate |
+| `--group-by FIELD` | any scalar field | build an independent result for each attribute value |
+| `--allow-holes` | flag | retain source holes and permit hull holes; without it all holes are filled |
+| `--invalid` | `repair`, `error` | repair invalid polygonal geometry with GEOS or stop |
+| `--fallback` | `convex`, `error` | use and report the convex hull if the concave operation fails, or stop |
+
+## Guarantees
+
+For every output record, `concavewrap` verifies that:
+
+- the result is valid polygonal geometry;
+- the result covers the complete input polygon area, not only its vertices;
+- the result does not extend beyond the convex hull, within floating-point tolerance;
+- the chosen hole, grouping, component, repair, and fallback policies are recorded;
+- input ordering determines stable group and component ordering.
+
+## Output fields
+
+| field | meaning |
+|---|---|
+| `hull_id` | stable one-based output identifier |
+| `group_value` | text representation of the grouping value, or null |
+| `source_features` | number of input features contributing to the hull |
+| `repaired_features` | number of invalid contributors repaired |
+| `input_area` | dissolved source area in CRS square units |
+| `hull_area` | output hull area |
+| `fill_area` | area added around or between source polygons |
+| `convex_area` | area of the corresponding convex hull |
+| `hull_to_convex_ratio` | output area divided by convex-hull area |
+| `fallback_used` | whether the convex fallback was used |
+| `fallback_reason` | captured failure message, if any |
+| `ratio`, `allow_holes`, `scope` | effective construction settings |
+| `covers_input` | final invariant check |
+
+## Python API
+
+```python
+import geopandas as gpd
+from concavewrap import HullOptions, HullResult, build_hulls
+
+areas = gpd.read_file("areas.gpkg", layer="areas")
+result: HullResult = build_hulls(
+    areas,
+    HullOptions(ratio=0.25, scope="global", allow_holes=False),
+)
+result.hulls.to_file("hulls.gpkg", layer="hulls", driver="GPKG")
+print(result.report())
+```
+
+The stable public interface is `build_hulls(...)`, `HullOptions`, `HullResult`,
+and `HullDiagnostic`.
+
+## Limits
+
+- Input geometries must be Polygon or MultiPolygon.
+- A projected CRS with horizontal units in metres is required so that area audit
+  values are meaningful and comparable.
+- `component` scope dissolves touching and overlapping polygons before identifying
+  disconnected components.
+- Concave hulls are not unique across algorithms. This package uses the GEOS
+  algorithm exposed by Shapely and records its ratio explicitly.
+- A hull is a generalization. Always inspect results for sparse samples, narrow
+  necks, very large gaps, and geometries whose holes have semantic meaning.
+
+Run `concavewrap --help` for all options. Exit code `0` means success and `2`
+means invalid input or a processing failure.
+
+The pre-release and launch checks are listed in
+[`docs/release-checklist.md`](docs/release-checklist.md).
+
+## Development
+
+```bash
+python -m pip install -e ".[test]"
+python -m ruff check .
+python -m ruff format --check .
+python -m pytest
+```
+
+Copyright 2026 Alena Nikitina. Licensed under the [Apache License 2.0](LICENSE).

concavewrap_geo-0.1.0/README.md

@@ -0,0 +1,156 @@
+# concavewrap-geo
+
+[![CI](https://github.com/NikitinaAD/concavewrap-geo/actions/workflows/ci.yml/badge.svg)](https://github.com/NikitinaAD/concavewrap-geo/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/concavewrap-geo.svg)](https://pypi.org/project/concavewrap-geo/)
+[![Python](https://img.shields.io/pypi/pyversions/concavewrap-geo.svg)](https://pypi.org/project/concavewrap-geo/)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+**Build auditable concave hulls that cover complete polygon areas.**
+
+Many concave-hull implementations guarantee that the output contains the input
+vertices. For areal data that is not enough: a hull edge can cut through a source
+polygon. `concavewrap` repairs or rejects invalid input, constructs the hull, and
+then enforces and verifies coverage of every source polygon.
+
+![Polygon patches become a polygon-safe concave hull](https://raw.githubusercontent.com/NikitinaAD/concavewrap-geo/main/docs/demo.svg)
+
+## Quick start
+
+```bash
+python -m pip install concavewrap-geo
+concavewrap build areas.gpkg \
+  --layer areas \
+  --ratio 0.25 \
+  --output hulls.gpkg \
+  --diagnostics hulls.json
+```
+
+The output is a GeoPackage layer named `hulls`. The JSON report records input and
+output areas, added fill area, the convex-hull area, coverage checks, repaired
+features, and any convex fallback.
+
+## Reproducible example
+
+Generate and process four synthetic polygon arrangements, including the failure
+modes that commonly make a single concave-hull setting misleading:
+
+```bash
+python examples/run_examples.py
+```
+
+| scenario | question answered | expected result |
+|---|---|---|
+| `forest-patches` | can irregular areal patches be wrapped without cutting them? | one hull that covers every complete polygon |
+| `large-gap` | should disconnected patches be bridged? | `global` gives one hull; `component` gives two |
+| `narrow-neck` | does a thin connecting polygon remain covered? | one valid hull covering the neck and both ends |
+| `ring-with-hole` | should a semantic hole remain open? | `allow_holes=True` keeps it; the default fills it |
+
+Generated inputs, outputs, and JSON reports are placed under
+`examples/generated/`. To run the standard case through the CLI:
+
+```bash
+concavewrap build examples/generated/forest-patches.gpkg \
+  --layer areas \
+  --ratio 0.25 \
+  --output examples/generated/forest-hull-cli.gpkg \
+  --diagnostics examples/generated/forest-hull-cli.json
+```
+
+Expected audit values are printed and asserted by the script, then saved in
+`summary.json`. No external or real-world data is used.
+
+## Ratio and policies
+
+`--ratio` follows GEOS/Shapely semantics:
+
+| value | behavior |
+|---:|---|
+| `0` | most concave result available from the input vertices |
+| `0.25` | useful starting point for irregular polygon collections |
+| `1` | convex hull |
+
+The ratio is dimensionless. It is not an alpha radius or a distance threshold,
+so values from alpha-shape tools cannot be copied directly.
+
+| option | choices | meaning |
+|---|---|---|
+| `--scope` | `global`, `component` | bridge all polygons in a group, or keep disconnected dissolved components separate |
+| `--group-by FIELD` | any scalar field | build an independent result for each attribute value |
+| `--allow-holes` | flag | retain source holes and permit hull holes; without it all holes are filled |
+| `--invalid` | `repair`, `error` | repair invalid polygonal geometry with GEOS or stop |
+| `--fallback` | `convex`, `error` | use and report the convex hull if the concave operation fails, or stop |
+
+## Guarantees
+
+For every output record, `concavewrap` verifies that:
+
+- the result is valid polygonal geometry;
+- the result covers the complete input polygon area, not only its vertices;
+- the result does not extend beyond the convex hull, within floating-point tolerance;
+- the chosen hole, grouping, component, repair, and fallback policies are recorded;
+- input ordering determines stable group and component ordering.
+
+## Output fields
+
+| field | meaning |
+|---|---|
+| `hull_id` | stable one-based output identifier |
+| `group_value` | text representation of the grouping value, or null |
+| `source_features` | number of input features contributing to the hull |
+| `repaired_features` | number of invalid contributors repaired |
+| `input_area` | dissolved source area in CRS square units |
+| `hull_area` | output hull area |
+| `fill_area` | area added around or between source polygons |
+| `convex_area` | area of the corresponding convex hull |
+| `hull_to_convex_ratio` | output area divided by convex-hull area |
+| `fallback_used` | whether the convex fallback was used |
+| `fallback_reason` | captured failure message, if any |
+| `ratio`, `allow_holes`, `scope` | effective construction settings |
+| `covers_input` | final invariant check |
+
+## Python API
+
+```python
+import geopandas as gpd
+from concavewrap import HullOptions, HullResult, build_hulls
+
+areas = gpd.read_file("areas.gpkg", layer="areas")
+result: HullResult = build_hulls(
+    areas,
+    HullOptions(ratio=0.25, scope="global", allow_holes=False),
+)
+result.hulls.to_file("hulls.gpkg", layer="hulls", driver="GPKG")
+print(result.report())
+```
+
+The stable public interface is `build_hulls(...)`, `HullOptions`, `HullResult`,
+and `HullDiagnostic`.
+
+## Limits
+
+- Input geometries must be Polygon or MultiPolygon.
+- A projected CRS with horizontal units in metres is required so that area audit
+  values are meaningful and comparable.
+- `component` scope dissolves touching and overlapping polygons before identifying
+  disconnected components.
+- Concave hulls are not unique across algorithms. This package uses the GEOS
+  algorithm exposed by Shapely and records its ratio explicitly.
+- A hull is a generalization. Always inspect results for sparse samples, narrow
+  necks, very large gaps, and geometries whose holes have semantic meaning.
+
+Run `concavewrap --help` for all options. Exit code `0` means success and `2`
+means invalid input or a processing failure.
+
+The pre-release and launch checks are listed in
+[`docs/release-checklist.md`](docs/release-checklist.md).
+
+## Development
+
+```bash
+python -m pip install -e ".[test]"
+python -m ruff check .
+python -m ruff format --check .
+python -m pytest
+```
+
+Copyright 2026 Alena Nikitina. Licensed under the [Apache License 2.0](LICENSE).

concavewrap_geo-0.1.0/SECURITY.md

@@ -0,0 +1,8 @@
+# Security policy
+
+Only the latest released version receives security fixes.
+
+Please do not open a public issue for a suspected vulnerability. Use GitHub's
+private vulnerability reporting feature on this repository instead. Include a
+minimal reproduction, affected versions, and the expected impact. You can expect
+an acknowledgement within seven days.

concavewrap_geo-0.1.0/docs/demo.svg

@@ -0,0 +1,23 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="960" height="330" viewBox="0 0 960 330" role="img" aria-labelledby="title desc">
+  <title id="title">Polygon patches converted to a concave hull</title>
+  <desc id="desc">Four polygon patches on the left and a covering concave hull with the source areas on the right.</desc>
+  <rect width="960" height="330" fill="#f8fafc"/>
+  <text x="70" y="42" font-family="sans-serif" font-size="22" font-weight="700" fill="#0f172a">Input polygon patches</text>
+  <text x="610" y="42" font-family="sans-serif" font-size="22" font-weight="700" fill="#0f172a">Verified concave hull</text>
+  <g fill="#60a5fa" stroke="#1d4ed8" stroke-width="3">
+    <rect x="80" y="85" width="90" height="170" rx="3"/>
+    <rect x="170" y="85" width="205" height="50" rx="3"/>
+    <rect x="320" y="135" width="55" height="75" rx="3"/>
+    <rect x="170" y="215" width="95" height="40" rx="3"/>
+  </g>
+  <path d="M585 255 L585 85 L880 85 L880 210 L805 210 L805 165 L675 165 L675 255 Z" fill="#99f6e4" stroke="#0f766e" stroke-width="5" stroke-linejoin="round"/>
+  <g fill="#60a5fa" fill-opacity="0.75" stroke="#1d4ed8" stroke-width="2">
+    <rect x="585" y="85" width="90" height="170" rx="3"/>
+    <rect x="675" y="85" width="205" height="50" rx="3"/>
+    <rect x="825" y="135" width="55" height="75" rx="3"/>
+    <rect x="675" y="215" width="95" height="40" rx="3"/>
+  </g>
+  <path d="M455 165 H520" stroke="#334155" stroke-width="5"/>
+  <path d="M510 150 L530 165 L510 180" fill="none" stroke="#334155" stroke-width="5" stroke-linecap="round" stroke-linejoin="round"/>
+  <text x="303" y="303" font-family="sans-serif" font-size="17" fill="#475569">The output covers every source area and stays inside the convex hull.</text>
+</svg>

concavewrap_geo-0.1.0/docs/release-checklist.md

@@ -0,0 +1,24 @@
+# Release checklist
+
+## Before making the repository public
+
+- [ ] CI passes on Windows and Linux with Python 3.11, 3.12, and 3.13.
+- [ ] `python examples/run_examples.py` reproduces every documented scenario.
+- [ ] Ruff, pytest, wheel/sdist build, Twine metadata, and clean-wheel smoke tests pass.
+- [ ] README commands work from a fresh clone and use only synthetic data.
+- [ ] The repository contains no private data, credentials, unrelated product names, or
+      files without a clear redistribution right.
+- [ ] Version `0.1.0`, changelog, citation metadata, URLs, license, and topics agree.
+
+## Publication session
+
+- [ ] Confirm the PyPI pending Trusted Publisher targets this repository,
+      `.github/workflows/release.yml`, and the `pypi` environment.
+- [ ] Make the repository public and enable required CI on `main`, with force-push and
+      branch deletion disabled.
+- [ ] Publish GitHub Release `v0.1.0`.
+- [ ] Confirm the release workflow publishes the already-built artifacts through OIDC.
+- [ ] Install `concavewrap-geo` from PyPI in fresh Windows and Linux environments and run
+      `concavewrap --version` plus one documented example.
+- [ ] Confirm GitHub and PyPI show Apache-2.0 and correct source, issue, and homepage URLs.
+- [ ] Pin the repository only after the PyPI installation check passes.