Releases: clarisma/geodesk-py
Version 0.2.1
Version 0.2
Breaking changes
-
Features
: Renamed filter methods (to match the naming conventions in
GeoDesk for Java):-
contains()
->containing()
-
intersects()
->intersecting()
-
crosses()
->crossing()
-
Enhancements
-
Support for Python 3.13
-
Support for ARM-based MacOS (experimental)
Bug fixes
-
within
now correctly excludes areas whose edges lie on
the test area's boundary, yet are not inside the test area (#57) -
Removed dependency on pre-Python 3.13 API (#59)
-
Formatting of numeric values in GeoJSON (#60)
-
Fixed floating point conversion for strings that contain
a partially-valid number -
fixed
TagIterator
regression
Version 0.1.11
Version 0.1.10
Enhancements
- New geometric filters:
max_area()
,min_area()
,max_length()
,min_length()
Other
- Upgraded dependencies to GEOS 3.11.3 / Shapely 2.0.3
Version 0.1.9
Version 0.1.8
Enhancements
-
Implemented type hints for improved autocomplete in IDEs
-
lonlat()
andlatlon()
can now create lists of coordinates -
Coordinate()
andBox()
clamp latitude to valid range
Bug fixes
- Fixed regex matching of tag values (#48)
Version 0.1.7
Version 0.1.6
Enhancements
-
from_mercator()
support for shapes (#41) -
lon
andlat
are rounded to 7 digits, conforming to the default precision used by OSM (forCoordinate
andFeature
objects) -
Enhanced support for
Features
metadata:indexed_keys
strings
Tile.size
Bug fixes
Version 0.1.5
Enhancements
-
Formatters now support the following attributes:
id
linewise
precision
pretty
-
Line-by-line GeoJSON is now supported --
.geojsonl
or.geojson(linewise=True)
(#3) -
IDs in GeoJSON can now be customized by providing a formatter function via
id
(#37 partial) -
GeoJSON is now compact by default; for more human-readable (but bulkier) output, use
.geojson(pretty=True)
-
Support for geometry collections
-
Support for anonymous nodes -- e.g.
ways.nodes.geojson
(#36) -
__repr__()
now prints the contents of aFormatter
Bug fixes
-
Area-ways are now in correct format for GeoJSON and WKT (#34)
-
Formatter
: Fixed coordinate rounding bug -
area
,length
andshape
can now be used with feature sets that contain anonymous nodes
Version 0.1.4
Enhancements
within()
: A polygon is now considered to be within itself, which conforms
to the OGC definition
Performance Improvements
- Spatial filters that apply to large areas are now 4x to 30x faster,
thanks to optimizations that short-cut relational tests