Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| 21f5a11b | 2025-11-01 08:04:25 | geo/pygeoif: update to 1.6.0 | ||
| e9132643 | 2025-10-23 13:19:51 | remove MODPY_COMMENT from PLISTs, no longer needed | ||
| 017ab3fd | 2025-01-06 10:47:05 | geo/py-geoif: update to 1.5.1 | ||
| cd2ca3dc | 2024-12-21 11:38:05 | handle py3.12 switchover in geo | ||
| db161a09 | 2024-05-19 13:44:58 | geo/py-geoif: update to 1.5.0 | ||
| f3d8779e | 2024-05-06 12:23:30 | bump REVISION for py3.10 -> py3.11 switch | ||
| 90687a71 | 2024-04-17 14:44:25 | geo/py-geoif: update to 1.4.0 | ||
| 0ade68f9 | 2023-02-19 11:24:03 | geo/py-geoif: update to 1.0.0. | ||
| 15f221b9 | 2022-12-19 10:50:57 | Import geo/py-geoif 0.7. PyGeoIf provides a GeoJSON-like protocol for geo-spatial (GIS) vector data. You may think of pygeoif as a shapely ultralight which lets you construct geometries and perform very basic operations like reading and writing geometries from/to WKT, constructing line strings out of points, polygons from linear rings, multi polygons from polygons, etc. It was inspired by shapely and implements the geometries in a way that when you are familiar with shapely you feel right at home with pygeoif. Not porting 1.0.0 since pygeofilter isnt compatible with it yet, cf https://github.com/geopython/pygeofilter/issues/57 ok sthen@ |