@trackunit/geo-json-utils 1.12.1 → 1.12.3

package/index.cjs.js

@@ -740,12 +740,14 @@ const mapWestOverflowPolygon = (poly) => {
  *
  * - **Center longitude:** Map inputs may be outside [-180, 180] (e.g. 540°). The center is folded once by
  * whole 360° turns into that range—same meridian on the ground; only the number used for math changes.
- * - **Sampling the ring:** Each vertex is `lonCenter + offset` along the loop. We do not normalize every
- * vertex to [-180, 180] by itself; that would turn a short step across the dateline into a long wrong chord.
- * Instead, the ring can use longitudes past ±180° until clipping splits it into valid pieces. The western
- * piece is adjusted so the ±180° edge is short, which `mergeAntimeridianFeatures` expects when merging halves.
+ * - **Sampling the ring:** Each vertex is `lonCenter + offset` along the loop. Vertices use **continuous**
+ * longitude (no per-point normalization to [-180, 180]) so the planar ring does not self-intersect at the
+ * dateline; each hemisphere is clipped separately. We do not normalize every vertex to [-180, 180] by
+ * itself; that would turn a short step across the dateline into a long wrong chord. The western overflow
+ * piece is repaired so the ±180° seam is a short edge, which allows consumers such as
+ * `mergeAntimeridianFeatures` to merge halves for rendering.
  *
- * - Returns **null** when the polygon crosses the antimeridian but both hemisphere
+ * Returns **null** when the polygon crosses the antimeridian but both hemisphere
  * intersections yield zero polygons (e.g. very small polygons near the
  * dateline). In that case, returning the original coordinates would produce
  * invalid geometry per RFC 7946 Section 3.1.9.

package/index.esm.js

@@ -738,12 +738,14 @@ const mapWestOverflowPolygon = (poly) => {
  *
  * - **Center longitude:** Map inputs may be outside [-180, 180] (e.g. 540°). The center is folded once by
  * whole 360° turns into that range—same meridian on the ground; only the number used for math changes.
- * - **Sampling the ring:** Each vertex is `lonCenter + offset` along the loop. We do not normalize every
- * vertex to [-180, 180] by itself; that would turn a short step across the dateline into a long wrong chord.
- * Instead, the ring can use longitudes past ±180° until clipping splits it into valid pieces. The western
- * piece is adjusted so the ±180° edge is short, which `mergeAntimeridianFeatures` expects when merging halves.
+ * - **Sampling the ring:** Each vertex is `lonCenter + offset` along the loop. Vertices use **continuous**
+ * longitude (no per-point normalization to [-180, 180]) so the planar ring does not self-intersect at the
+ * dateline; each hemisphere is clipped separately. We do not normalize every vertex to [-180, 180] by
+ * itself; that would turn a short step across the dateline into a long wrong chord. The western overflow
+ * piece is repaired so the ±180° seam is a short edge, which allows consumers such as
+ * `mergeAntimeridianFeatures` to merge halves for rendering.
  *
- * - Returns **null** when the polygon crosses the antimeridian but both hemisphere
+ * Returns **null** when the polygon crosses the antimeridian but both hemisphere
  * intersections yield zero polygons (e.g. very small polygons near the
  * dateline). In that case, returning the original coordinates would produce
  * invalid geometry per RFC 7946 Section 3.1.9.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trackunit/geo-json-utils",
-  "version": "1.12.1",
+  "version": "1.12.3",
   "repository": "https://github.com/Trackunit/manager",
   "license": "SEE LICENSE IN LICENSE.txt",
   "engines": {

package/src/GeoJsonUtils.d.ts

@@ -19,12 +19,14 @@ export declare const getBboxFromGeoJsonPolygon: (polygon: GeoJsonPolygon | GeoJs
  *
  * - **Center longitude:** Map inputs may be outside [-180, 180] (e.g. 540°). The center is folded once by
  * whole 360° turns into that range—same meridian on the ground; only the number used for math changes.
- * - **Sampling the ring:** Each vertex is `lonCenter + offset` along the loop. We do not normalize every
- * vertex to [-180, 180] by itself; that would turn a short step across the dateline into a long wrong chord.
- * Instead, the ring can use longitudes past ±180° until clipping splits it into valid pieces. The western
- * piece is adjusted so the ±180° edge is short, which `mergeAntimeridianFeatures` expects when merging halves.
+ * - **Sampling the ring:** Each vertex is `lonCenter + offset` along the loop. Vertices use **continuous**
+ * longitude (no per-point normalization to [-180, 180]) so the planar ring does not self-intersect at the
+ * dateline; each hemisphere is clipped separately. We do not normalize every vertex to [-180, 180] by
+ * itself; that would turn a short step across the dateline into a long wrong chord. The western overflow
+ * piece is repaired so the ±180° seam is a short edge, which allows consumers such as
+ * `mergeAntimeridianFeatures` to merge halves for rendering.
  *
- * - Returns **null** when the polygon crosses the antimeridian but both hemisphere
+ * Returns **null** when the polygon crosses the antimeridian but both hemisphere
  * intersections yield zero polygons (e.g. very small polygons near the
  * dateline). In that case, returning the original coordinates would produce
  * invalid geometry per RFC 7946 Section 3.1.9.