geojson-rewind
A Python library for enforcing polygon ring winding order in GeoJSON
The GeoJSON spec mandates the right hand rule:
A linear ring MUST follow the right-hand rule with respect to the area it bounds, i.e., exterior rings are counterclockwise, and holes are clockwise.
This helps you generate compliant Polygon and MultiPolygon geometries.
Note: Co-ordinates in the input data are assumed to be WGS84 with (lon, lat) ordering, as per RFC 7946. Input with co-ordinates using any other CRS may lead to unexpected results.
Installation
pip install geojson-rewind
Usage
As a Library
Enforce RFC 7946 ring winding order (input/output is a GeoJSON string):
>>> from geojson_rewind import rewind
>>> input = """{
... "geometry": { "coordinates": [ [ [100, 0],
... [100, 1],
... [101, 1],
... [101, 0],
... [100, 0]]],
... "type": "Polygon"},
... "properties": {"foo": "bar"},
... "type": "Feature"}"""
>>> output = rewind(input)
>>> output
'{"geometry": {"coordinates": [[[100, 0], [101, 0], [101, 1], [100, 1], [100, 0]]], "type": "Polygon"}, "properties": {"foo": "bar"}, "type": "Feature"}'
>>> type(output)
<class 'str'>
Enforce RFC 7946 ring winding order (input/output is a python dict):
>>> from geojson_rewind import rewind
>>> input = {
... 'geometry': { 'coordinates': [ [ [100, 0],
... [100, 1],
... [101, 1],
... [101, 0],
... [100, 0]]],
... 'type': 'Polygon'},
... 'properties': {'foo': 'bar'},
... 'type': 'Feature'}
>>> output = rewind(input)
>>> output
{'geometry': {'coordinates': [[[100, 0], [101, 0], [101, 1], [100, 1], [100, 0]]], 'type': 'Polygon'}, 'properties': {'foo': 'bar'}, 'type': 'Feature'}
>>> type(output)
<class 'dict'>
On the Console
# Enforce ring winding order on a GeoJSON file
$ rewind in.geojson > out.geojson
# fetch GeoJSON from the web and enforce ring winding order
$ curl "https://myserver.com/in.geojson" | rewind
Versioning
geojson-rewind follows semantic versioning. For this project, the "API" also includes:
- CLI flags and options
- CLI exit codes
In line with common practice in the python community, geojson-rewind will drop compatibility with unsupported python versions without incrementing the major version.
Acknowledgements
geojson-rewind is a python port of Mapbox's javascript geojson-rewind package. Credit to Tom MacWright and contributors.
Metadata
Release files for geojson-rewind 1.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| geojson_rewind-1.2.1.tar.gz | 4.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| geojson_rewind-1.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.2 kB
Release files / geojson_rewind-1.2.1.tar.gz
| Download URL | geojson_rewind-1.2.1.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1b7b8b3714eb1f0cfccdba023444f0073be2c9ce148d72c69fd097ea7743da60
|
|
BLAKE2b-256 checksum How to use checksums |
1fbb6f9ca8311baad6e2111101ff1625a46d66fc46ffe828126d06fd314d22ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2025.
Transparency logRelease files / geojson_rewind-1.2.1-py3-none-any.whl
| Download URL | geojson_rewind-1.2.1-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0336c1940d070686edf254d8783fe7c9acc5c6b107a0a87b8c628cd28c0651d1
|
|
BLAKE2b-256 checksum How to use checksums |
c73aa8eec7f3288b485c1b679f5f83a8e2be756748137f99a656f2669bf16159
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2025.
Transparency log