Raster 2 Polyon
Extracting vector polygons from raster images
Installation
pip install raster2polygon
Example :
from raster2polygon import polygonize
polygonize("data/masks_v2/4", "labels.geojson")
Args :
input_path: Path of the directory where the image files are stored.
output_path: Path of the output file.
remove_inputs: Clears the input image after geojson is produced
simplify_tolerance : the simplification accuracy as max. percentage of the arc length, in [0, 1] , Percentage Tolerance= ( Tolerance in Meters / Arc Length in Meters)×100
merging_distance_threshold : Minimum distance to define adjacent polygons, in meters , default 0.5 m
area_threshold (float, optional): Threshold for filtering polygon areas. Defaults to 1 sqm.
Metadata
Release files for raster2polygon 0.0.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 | Provenance | Actions |
|---|---|---|---|---|
| raster2polygon-0.0.1.tar.gz | 8.6 kB | Without provenance | Details for raster2polygon-0.0.1.tar.gz |
Release files / raster2polygon-0.0.1.tar.gz
| Download URL | raster2polygon-0.0.1.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63f1541c9cd7eb5a86f78f37fd72118ed775397217e8ff672b695c41f6133252
|
|
BLAKE2b-256 checksum How to use checksums |
1102649d3ff1794e65194fb9f7a92411d43d2bb448dee8b3dbff22540eaf580f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Security for raster2polygon 0.0.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.