geo-polygonize 0.36.2 → 0.39.2

package/README.md

@@ -9,10 +9,10 @@ A native Rust port of the JTS/GEOS polygonization algorithm. This crate allows y
 - **Robust Polygonization**: Extracts polygons from unstructured linework.
 - **Robust Noding**: Implements **Iterated Snap Rounding (ISR)** to guarantee topological correctness on dirty inputs (self-intersections, overlaps).
 - **Hardware Acceleration**: Uses **SIMD** instructions (via `wide` crate) for critical geometric predicates like Point-in-Polygon checks.
-- **Wasm Optimized**: Tailored for WebAssembly with `talc` allocator and Zero-Copy data support (`geoarrow`).
+- **Wasm Optimized**: Tailored for WebAssembly with `talc` allocator and binary GeoArrow support.
 - **Performance**: Competitive with GEOS/Shapely (C++), outperforming it on random sparse inputs and scaling well on dense grids.
 - **Geo Ecosystem**: Fully integrated with `geo-types` and `geo` crates.
-- **GeoArrow Support**: Zero-copy data transfer via Arrow C Data Interface and Arrow IPC (Wasm).
+- **GeoArrow Support**: Arrow C Data Interface and Arrow IPC integration with GeoArrow metadata.
 
 ## Engineering Roadmap
 
@@ -110,7 +110,7 @@ for p in polygons:
     print(p.area)
 
 # 2. Using High-Performance Flat Arrays
-# Perfect for zero-copy integrations or massive datasets
+# Flat buffers avoid Python object-per-coordinate overhead
 coords = np.array([
     0.0, 0.0, 10.0, 0.0, 10.0, 10.0, 0.0, 10.0, 0.0, 0.0,
     0.0, 0.0, 10.0, 10.0
@@ -145,6 +145,12 @@ The default return shape is a stable dictionary with `polygons` as
 `SimplePolygon` values. Use `return_polygons=True` only when you want Shapely
 `Polygon` objects.
 
+`SnapStrategy::Grid` keeps topology and output coordinates on the configured
+precision grid. The CFB profile uses `GeosCompat`: the grid establishes robust
+topology, then output nodes regain deterministic source coordinates to better
+match Shapely `snap` plus full-precision noding. It is not `set_precision`
+emulation, and exact parity is not guaranteed for many-to-one snaps.
+
 For Shapely parity checks, compare report-mode outputs with the built-in
 mismatch helper:
 

package/dist/slim/cjs/bindings/PolygonizerOptions.d.ts

@@ -49,7 +49,7 @@ export type PolygonizerOptions = {
      */
     extract_only_polygonal: boolean;
     /**
-     * The underlying strategy to apply when snapping coordinate geometries.
+     * Controls robust snap noding and output coordinate handling.
      *
      * See `SnapStrategy` for differences between strict `Grid` snapping and
      * Shapely/GEOS `GeosCompat` strategies.

package/dist/slim/cjs/bindings/SnapStrategy.d.ts

@@ -1,25 +1,15 @@
 /**
- * Strategy for snapping coordinates to a grid.
+ * Strategy for robust snap noding and output coordinates.
  *
- * `Grid` applies a standard round-to-nearest integer grid policy `(coord / size).round() * size`.
- * `GeosCompat` attempts to emulate GEOS / Shapely's `set_precision` behavior, which uses
- * C++ std::round (rounding halfway cases away from zero).
+ * `Grid` uses the precision grid for both topology and output coordinates.
+ * `GeosCompat` uses the grid for topology, then restores one deterministic nearest source
+ * coordinate per snapped node. This targets Shapely-style `snap` followed by full-precision
+ * noding and polygonization; it does not emulate `set_precision` output.
  *
  * **Scale Guidance:**
- * Use `Grid` for native Rust applications where absolute topological determinism and
- * intuitive rounding is preferred.
- * Use `GeosCompat` if you are using `geo-polygonize` to replace a Shapely / GEOS pipeline
- * and require exact parity for edge cases at precision boundaries.
- *
- * **Expected Parity:**
- * Rust's native `f64::round()` rounds halfway cases away from zero. This perfectly
- * matches C++ `std::round` behavior, meaning that `Grid` and `GeosCompat` currently
- * map identical values for basic single-coordinate precision points (e.g., `-0.5` => `-1.0`
- * and `0.5` => `1.0`).
- *
- * **Expected Divergence:**
- * The divergence between `Grid` and `GeosCompat` strategies typically arises under complex
- * topological scaling sequences rather than simple single point coordinate rounding, but
- * the option ensures the library remains semantically compatible with Python/C++ GEOS pipelines.
+ * Use `Grid` when an explicit precision model is the desired output contract.
+ * Use `GeosCompat` when the grid is a robustness aid but source-coordinate fidelity matters.
+ * Both strategies are deterministic; exact GEOS/Shapely parity is not guaranteed for
+ * degenerate or many-to-one snaps.
  */
 export type SnapStrategy = "Grid" | "GeosCompat";

package/dist/slim/cjs/index.d.ts

@@ -9,7 +9,6 @@ export * from "./bindings/NodingOptions";
 export * from "./bindings/ProvenanceOptions";
 export * from "./bindings/SnapStrategy";
 export * from "./bindings/TileOwnershipPolicy";
-export * from "./bindings/TilingOptions";
 export * from "./bindings/TouchPolicy";
 export * from "./cfb";
 export default function init(_input?: any): Promise<typeof exports>;

package/dist/slim/cjs/index_slim.d.ts

@@ -9,7 +9,6 @@ export * from "./bindings/NodingOptions";
 export * from "./bindings/ProvenanceOptions";
 export * from "./bindings/SnapStrategy";
 export * from "./bindings/TileOwnershipPolicy";
-export * from "./bindings/TilingOptions";
 export * from "./bindings/TouchPolicy";
 export * from "./cfb";
 export declare function initBest(scalarModule: any, simdModule?: any): Promise<typeof scalarExports>;

package/dist/slim/cjs/index_slim.js

@@ -219,7 +219,7 @@ function polygonize(geojson_str, node_input, snap_grid_size, extract_only_polygo
 /**
  * Polygonizes an Arrow IPC stream containing a GeoArrow LineString array.
  *
- * This zero-copy path avoids JSON serialization overhead and returns a binary
+ * This binary path avoids JSON serialization overhead and returns an
  * Arrow IPC stream containing a GeoArrow Polygon array. Requires the options
  * to be passed as a parsed JS object.
  * @param {Uint8Array} ipc_bytes

package/dist/slim/cjs/index_threads.d.ts

@@ -9,7 +9,6 @@ export * from "./bindings/NodingOptions";
 export * from "./bindings/ProvenanceOptions";
 export * from "./bindings/SnapStrategy";
 export * from "./bindings/TileOwnershipPolicy";
-export * from "./bindings/TilingOptions";
 export * from "./bindings/TouchPolicy";
 export * from "./cfb";
 export default init;

package/dist/slim/es/bindings/PolygonizerOptions.d.ts

@@ -49,7 +49,7 @@ export type PolygonizerOptions = {
      */
     extract_only_polygonal: boolean;
     /**
-     * The underlying strategy to apply when snapping coordinate geometries.
+     * Controls robust snap noding and output coordinate handling.
      *
      * See `SnapStrategy` for differences between strict `Grid` snapping and
      * Shapely/GEOS `GeosCompat` strategies.

package/dist/slim/es/bindings/SnapStrategy.d.ts

@@ -1,25 +1,15 @@
 /**
- * Strategy for snapping coordinates to a grid.
+ * Strategy for robust snap noding and output coordinates.
  *
- * `Grid` applies a standard round-to-nearest integer grid policy `(coord / size).round() * size`.
- * `GeosCompat` attempts to emulate GEOS / Shapely's `set_precision` behavior, which uses
- * C++ std::round (rounding halfway cases away from zero).
+ * `Grid` uses the precision grid for both topology and output coordinates.
+ * `GeosCompat` uses the grid for topology, then restores one deterministic nearest source
+ * coordinate per snapped node. This targets Shapely-style `snap` followed by full-precision
+ * noding and polygonization; it does not emulate `set_precision` output.
  *
  * **Scale Guidance:**
- * Use `Grid` for native Rust applications where absolute topological determinism and
- * intuitive rounding is preferred.
- * Use `GeosCompat` if you are using `geo-polygonize` to replace a Shapely / GEOS pipeline
- * and require exact parity for edge cases at precision boundaries.
- *
- * **Expected Parity:**
- * Rust's native `f64::round()` rounds halfway cases away from zero. This perfectly
- * matches C++ `std::round` behavior, meaning that `Grid` and `GeosCompat` currently
- * map identical values for basic single-coordinate precision points (e.g., `-0.5` => `-1.0`
- * and `0.5` => `1.0`).
- *
- * **Expected Divergence:**
- * The divergence between `Grid` and `GeosCompat` strategies typically arises under complex
- * topological scaling sequences rather than simple single point coordinate rounding, but
- * the option ensures the library remains semantically compatible with Python/C++ GEOS pipelines.
+ * Use `Grid` when an explicit precision model is the desired output contract.
+ * Use `GeosCompat` when the grid is a robustness aid but source-coordinate fidelity matters.
+ * Both strategies are deterministic; exact GEOS/Shapely parity is not guaranteed for
+ * degenerate or many-to-one snaps.
  */
 export type SnapStrategy = "Grid" | "GeosCompat";

package/dist/slim/es/index.d.ts

@@ -9,7 +9,6 @@ export * from "./bindings/NodingOptions";
 export * from "./bindings/ProvenanceOptions";
 export * from "./bindings/SnapStrategy";
 export * from "./bindings/TileOwnershipPolicy";
-export * from "./bindings/TilingOptions";
 export * from "./bindings/TouchPolicy";
 export * from "./cfb";
 export default function init(_input?: any): Promise<typeof exports>;

package/dist/slim/es/index_slim.d.ts

@@ -9,7 +9,6 @@ export * from "./bindings/NodingOptions";
 export * from "./bindings/ProvenanceOptions";
 export * from "./bindings/SnapStrategy";
 export * from "./bindings/TileOwnershipPolicy";
-export * from "./bindings/TilingOptions";
 export * from "./bindings/TouchPolicy";
 export * from "./cfb";
 export declare function initBest(scalarModule: any, simdModule?: any): Promise<typeof scalarExports>;

package/dist/slim/es/index_slim.js

@@ -216,7 +216,7 @@ function polygonize(geojson_str, node_input, snap_grid_size, extract_only_polygo
 /**
  * Polygonizes an Arrow IPC stream containing a GeoArrow LineString array.
  *
- * This zero-copy path avoids JSON serialization overhead and returns a binary
+ * This binary path avoids JSON serialization overhead and returns an
  * Arrow IPC stream containing a GeoArrow Polygon array. Requires the options
  * to be passed as a parsed JS object.
  * @param {Uint8Array} ipc_bytes

package/dist/slim/es/index_threads.d.ts

@@ -9,7 +9,6 @@ export * from "./bindings/NodingOptions";
 export * from "./bindings/ProvenanceOptions";
 export * from "./bindings/SnapStrategy";
 export * from "./bindings/TileOwnershipPolicy";
-export * from "./bindings/TilingOptions";
 export * from "./bindings/TouchPolicy";
 export * from "./cfb";
 export default init;

package/dist/slim/pkg-scalar/geo_polygonize.d.ts

@@ -35,7 +35,7 @@ export function polygonize(geojson_str: string, node_input?: boolean | null, sna
 /**
  * Polygonizes an Arrow IPC stream containing a GeoArrow LineString array.
  *
- * This zero-copy path avoids JSON serialization overhead and returns a binary
+ * This binary path avoids JSON serialization overhead and returns an
  * Arrow IPC stream containing a GeoArrow Polygon array. Requires the options
  * to be passed as a parsed JS object.
  */

package/dist/slim/pkg-wrapper/bindings/PolygonizerOptions.d.ts

@@ -49,7 +49,7 @@ export type PolygonizerOptions = {
      */
     extract_only_polygonal: boolean;
     /**
-     * The underlying strategy to apply when snapping coordinate geometries.
+     * Controls robust snap noding and output coordinate handling.
      *
      * See `SnapStrategy` for differences between strict `Grid` snapping and
      * Shapely/GEOS `GeosCompat` strategies.

package/dist/slim/pkg-wrapper/bindings/SnapStrategy.d.ts

@@ -1,25 +1,15 @@
 /**
- * Strategy for snapping coordinates to a grid.
+ * Strategy for robust snap noding and output coordinates.
  *
- * `Grid` applies a standard round-to-nearest integer grid policy `(coord / size).round() * size`.
- * `GeosCompat` attempts to emulate GEOS / Shapely's `set_precision` behavior, which uses
- * C++ std::round (rounding halfway cases away from zero).
+ * `Grid` uses the precision grid for both topology and output coordinates.
+ * `GeosCompat` uses the grid for topology, then restores one deterministic nearest source
+ * coordinate per snapped node. This targets Shapely-style `snap` followed by full-precision
+ * noding and polygonization; it does not emulate `set_precision` output.
  *
  * **Scale Guidance:**
- * Use `Grid` for native Rust applications where absolute topological determinism and
- * intuitive rounding is preferred.
- * Use `GeosCompat` if you are using `geo-polygonize` to replace a Shapely / GEOS pipeline
- * and require exact parity for edge cases at precision boundaries.
- *
- * **Expected Parity:**
- * Rust's native `f64::round()` rounds halfway cases away from zero. This perfectly
- * matches C++ `std::round` behavior, meaning that `Grid` and `GeosCompat` currently
- * map identical values for basic single-coordinate precision points (e.g., `-0.5` => `-1.0`
- * and `0.5` => `1.0`).
- *
- * **Expected Divergence:**
- * The divergence between `Grid` and `GeosCompat` strategies typically arises under complex
- * topological scaling sequences rather than simple single point coordinate rounding, but
- * the option ensures the library remains semantically compatible with Python/C++ GEOS pipelines.
+ * Use `Grid` when an explicit precision model is the desired output contract.
+ * Use `GeosCompat` when the grid is a robustness aid but source-coordinate fidelity matters.
+ * Both strategies are deterministic; exact GEOS/Shapely parity is not guaranteed for
+ * degenerate or many-to-one snaps.
  */
 export type SnapStrategy = "Grid" | "GeosCompat";

package/dist/standard/cjs/bindings/PolygonizerOptions.d.ts

@@ -49,7 +49,7 @@ export type PolygonizerOptions = {
      */
     extract_only_polygonal: boolean;
     /**
-     * The underlying strategy to apply when snapping coordinate geometries.
+     * Controls robust snap noding and output coordinate handling.
      *
      * See `SnapStrategy` for differences between strict `Grid` snapping and
      * Shapely/GEOS `GeosCompat` strategies.

package/dist/standard/cjs/bindings/SnapStrategy.d.ts

@@ -1,25 +1,15 @@
 /**
- * Strategy for snapping coordinates to a grid.
+ * Strategy for robust snap noding and output coordinates.
  *
- * `Grid` applies a standard round-to-nearest integer grid policy `(coord / size).round() * size`.
- * `GeosCompat` attempts to emulate GEOS / Shapely's `set_precision` behavior, which uses
- * C++ std::round (rounding halfway cases away from zero).
+ * `Grid` uses the precision grid for both topology and output coordinates.
+ * `GeosCompat` uses the grid for topology, then restores one deterministic nearest source
+ * coordinate per snapped node. This targets Shapely-style `snap` followed by full-precision
+ * noding and polygonization; it does not emulate `set_precision` output.
  *
  * **Scale Guidance:**
- * Use `Grid` for native Rust applications where absolute topological determinism and
- * intuitive rounding is preferred.
- * Use `GeosCompat` if you are using `geo-polygonize` to replace a Shapely / GEOS pipeline
- * and require exact parity for edge cases at precision boundaries.
- *
- * **Expected Parity:**
- * Rust's native `f64::round()` rounds halfway cases away from zero. This perfectly
- * matches C++ `std::round` behavior, meaning that `Grid` and `GeosCompat` currently
- * map identical values for basic single-coordinate precision points (e.g., `-0.5` => `-1.0`
- * and `0.5` => `1.0`).
- *
- * **Expected Divergence:**
- * The divergence between `Grid` and `GeosCompat` strategies typically arises under complex
- * topological scaling sequences rather than simple single point coordinate rounding, but
- * the option ensures the library remains semantically compatible with Python/C++ GEOS pipelines.
+ * Use `Grid` when an explicit precision model is the desired output contract.
+ * Use `GeosCompat` when the grid is a robustness aid but source-coordinate fidelity matters.
+ * Both strategies are deterministic; exact GEOS/Shapely parity is not guaranteed for
+ * degenerate or many-to-one snaps.
  */
 export type SnapStrategy = "Grid" | "GeosCompat";

package/dist/standard/cjs/index.d.ts

@@ -9,7 +9,6 @@ export * from "./bindings/NodingOptions";
 export * from "./bindings/ProvenanceOptions";
 export * from "./bindings/SnapStrategy";
 export * from "./bindings/TileOwnershipPolicy";
-export * from "./bindings/TilingOptions";
 export * from "./bindings/TouchPolicy";
 export * from "./cfb";
 export default function init(_input?: any): Promise<typeof exports>;