Mapbox-vector-tile

Latest version: v2.0.1

Safety actively analyzes 619456 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 4

2.0.1

-------------

*In development*

2.0.0

-------------

* Drop Python 2 support
* Usage of `tox` for tests
* Add GitHub Actions
* Add pre-commit tool
* Regenerate the vector tile protobuf Python code to solve
[113](https://github.com/tilezen/mapbox-vector-tile/issues/113)
* Support for Python 3.11
* Delete the `round_fn` argument as Python 2 has been dropped
* Use `pyproject.toml` and Poetry to replace the `setup.py` file
* Use `geom_type` property instead of deprecated `type`
* Add the possibility to give a coordinates transformer
* Add a `geojson` option. See [107](https://github.com/tilezen/mapbox-vector-tile/issues/107)
* Refactor the options using the `per_layer_options` and `default_options` dictionaries.
* Add the option `max_geometry_validate_tries`.

1.2.1

-------------

* Add the trove classifiers to the setup.py

1.2.0

-------------

* Performance focused release, including:
* Enable Shapely speedups, when available
* Skip inners which cause exceptions
* Union inners in blocks when making valid
* Make benchmark script python3 compatible
* Fix test to support different versions of GEOS

1.1.0

-------------

* Include LICENSE & CHANGELOG.md in sdist tarballs
* Refactor geometry encoding logic, including skipping tiny geometries
* Decoded geometry is now geojson-ish dict
* Winding order is now optional
* Add benchmarking around round function and document how to improve performance
* Document performance tip for protobuf encoding with C bindings for Debian

1.0.0

-------------

* Generate more valid polygons and multipolygons using [pyclipper](https://pypi.python.org/pypi/pyclipper) library for v2 MVT compliance (but we're still not fully v2 compliant for [other](https://github.com/tilezen/mapbox-vector-tile/issues/42) reasons).
* Handle edge cases where polygon buffer makes a multi-polygon, ensuring inner rings are dropped when subtracting them from the polygon would make it invalid, and not adding multipolygons as array elements for multipolygon constructor.
* Calculate area more properly by using PolyTree result from Clipper.
* Factor out polygon validity code into its own file.

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.