| Name | brdr JSON |
| Version |
0.5.0
JSON |
| download |
| home_page | None |
| Summary | BRDR - a Python library to assist in realigning (multi-)polygons (OGC Simple Features) to reference borders |
| upload_time | 2024-11-14 12:49:19 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.9 |
| license | MIT License
Copyright (c) 2024 Onroerend Erfgoed
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE. |
| keywords |
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# `brdr`
a Python library to assist in realigning (multi-)polygons (OGC Simple Features) to reference borders
<!-- badges: start -->
[](https://doi.org/10.5281/zenodo.11385644)
<!-- badges: end -->
Quick links:
- [Installation](#installation)
- [Development](#development)
- [Issues, questions, comments and contributions](#comments-and-contributions)
## Description
### Intro
`brdr` is a Python package that assists in aligning geometric boundaries to reference boundaries. This is an important
task in geographic data management to enhance data quality.
* In the context of geographic data management, it is important to have accurate and consistent boundaries for a variety
of applications such as calculating areas, analyzing spatial relationships, and visualizing and querying geographic
information.
* When creating geographic data, it is often more efficient to derive boundaries from existing reference data rather
than collecting new data in the field.
* `brdr` can be used to align boundaries from new data to reference data, ensuring that the boundaries are accurate and
consistent.
### Example
The figure below shows:
* the original thematic geometry (blue),
* A reference layer (yellow-black).
* The resulting geometry after alignment with `brdr` (green)
### Functionalities
`brdr` provides a variety of functionalities in the Aligner-class to assist in aligning boundaries, including:
* Loaders:
* aligner.load_thematic_data():Loading thematic data ((Multi-)Polygons) as a dictionary (DictLoader) or geojson (
GeoJsonFileLoader,GeoJsonUrlLoader)
* aligner.load_reference_data():Loading reference data ((Multi-)Polygons) as a dictionary (DictLoader) or geojson (
GeoJsonFileLoader,GeoJsonUrlLoader)
* Processors:
* aligner.process(): Align thematic boundaries to reference boundaries with a specific relevant
distance or a range of relevant distances
* aligner.predictor(): Searches all 'stable' (=predicted) processresults in a range of relevant distances
* aligner.get_brdr_formula(): Calculating a descriptive formula of a thematic boundary based on a reference layer
* evaluate(): Compares & evaluates input geometries with another version and adds a EVALUATION_FIELD_NAME
* Exporters:
* aligner.get_results_as_geojson(): Returns a collection of geojson-dictionaries with the processresults (resulting
geometry, differences,...): This can be used for all processresults or only the 'predicted' results
* aligner.get_input_as_geojson(): Returns a geojson-featurecollection from input-dictionaries (thematic or
reference)
* aligner.save_results(): Exports the resuling geojson-files to a specified path:This can be used for all
processresults or only the 'predicted' results
Besides the generic functionalities, a range of Flanders-specific functionalities are provided:
* Loaders:
* GRBActualLoader: Loading actual GRB (parcels, buildings)
* GRBFiscalParcelLoader: Loading fiscal GRB-parcels of a specific year
* Processors:
* grb.get_geoms_affected_by_grb_change(): get thematic geometries that are possibly affected by GRB-changes during a
specific timespan
* grb.update_to_actual_grb(): aligns the boundaries of thematic features to the actual GRB-boundaries
### Possible application fields
* Geodata-management:
* Implementation of `brdr` in business-processes and tooling
* Bulk geodata-alignment
* Alignment after reprojection of data
* Cleaning data: In a postprocessing-phase, the algorithm executes sliver-cleanup and validity-cleaning on the
resulting geometries
* ...
* Data-Analysis: Investigate the pattern in deviation and change between thematic and reference boundaries
* Update-detection: Investigate the descriptive formula before and after alignment to check for (automatic)
alignment of geodata
* ...
### QGIS-script
An implementation of `brdr` for QGIS can be found at [GitHub-brdrQ](https://github.com/OnroerendErfgoed/brdrQ/).
This QGIS- script provides a User Interface to align thematic data to a reference layer, showing the results in the QGIS
Table of Contents.
## Installation
You can install the latest release of `brdr` from
[GitHub](https://github.com/OnroerendErfgoed/brdr/) or
[PyPi](https://pypi.org/project/brdr/):
``` python
pip install brdr
```
## Basic example
``` python
from brdr.aligner import Aligner
from brdr.enums import OpenbaarDomeinStrategy
from brdr.geometry_utils import geom_from_wkt
from brdr.loader import DictLoader
# CREATE AN ALIGNER
aligner = Aligner(
crs="EPSG:31370",
)
# ADD A THEMATIC POLYGON TO THEMATIC DICTIONARY and LOAD into Aligner
thematic_dict = {"theme_id_1": geom_from_wkt("POLYGON ((0 0, 0 9, 5 10, 10 0, 0 0))")}
loader = DictLoader(thematic_dict)
aligner.load_thematic_data(loader)
# ADD A REFERENCE POLYGON TO REFERENCE DICTIONARY and LOAD into Aligner
reference_dict = {"ref_id_1": geom_from_wkt("POLYGON ((0 1, 0 10,8 10,10 1,0 1))")}
loader = DictLoader(reference_dict)
aligner.load_reference_data(loader)
# EXECUTE THE ALIGNMENT
relevant_distance = 1
process_result = aligner.process(
relevant_distance=relevant_distance,
od_strategy=OpenbaarDomeinStrategy.SNAP_SINGLE_SIDE,
threshold_overlap_percentage=50,
)
# PRINT RESULTS IN WKT
print("result: " + process_result["theme_id_1"][relevant_distance]["result"].wkt)
print(
"added area: "
+ process_result["theme_id_1"][relevant_distance]["result_diff_plus"].wkt
)
print(
"removed area: "
+ process_result["theme_id_1"][relevant_distance]["result_diff_min"].wkt
)
```
The resulting figure shows:
* the reference polygon (yellow-black)
* the original geometry (blue)
* the resulting geometry (green line)
* the added zone (green squares)
* the removed zone (red squares)
<img src="docs/figures/basic_example.png" width="100%" />
More examples can be found in [Examples](https://github.com/OnroerendErfgoed/brdr/tree/main/examples)
## Workflow
(see also Basic example)
To use `brdr`, follow these steps:
* Create a Aligner-class with specific parameters:
* relevant_distance (m) (default: 1): Distance-parameter used to decide which parts will be aligned, and which parts
remain unchanged.
* od_strategy (enum) (default: SNAP_SINGLE_SIDE): Strategy to align geodata that is not covered by reference-data
* threshold_overlap_percentage (%)(0-100) (default 50)
* crs: The Coordinate Reference System (CRS) (default: EPSG:31370 - Belgian Lambert72)
* Load thematic data
* Load reference data
* Process (align) the thematic data
* Results are returned:
* Resulting geometry
* Differences: parts that are 'different' from the original geometry (positive or negative)
* Positive differences: parts that are added to the original geometry
* Negative differences: parts that are removed form the original geometry
* Relevant intersections: relevant intersecting parts of the reference geometries
* Relevant differences: relevant differences of the reference geometries
## The `brdr`-algorithm
The algorithm for alignment is based on 2 main principles:
* Principle of intentionality: Thematic boundaries can consciously or unconsciously deviate from the reference borders.
The algorithm should keep notice of that.
* Selective spatial conservation of shape: The resulting geometry should re-use the shape of the reference borders where
aligned is of relevance.
The figure below shows a schematic overview of the algorithm:
The algorithm can be split into 3 main phases:
* Initialisation:
* Deciding which reference polygons are candidate-polygons to re-use its shape.
The reference candidate polygons are selected based on spatial intersection with the thematic geometry.
* Processing:
* Process all candidate-reference polygons one-by-one
* Calculate relevant zones for each candidate-reference-polygon
* relevant intersections: zones that must be present in the final result
* relevant differences: zones that must be excluded from the final result
* Evaluate each candidate based on their relative zones: which parts must be kept and which parts must be excluded
* Union all kept parts to recompose a resulting geometry
* Post-processing:
* Validation/correction of differences between the original input geometry and the composed intermediate resulting
geometry after processing the algorithm
* Technical validation of inner holes and multipolygons that are created by processing the algorithm
* Clean-up slivers
* Make the resulting geometry valid
RESULT:
A new resulting output geometry, aligned to the reference-polygons
## Development
### pip-compile
```sh
PIP_COMPILE_ARGS="-v --strip-extras --no-header --resolver=backtracking --no-emit-options --no-emit-find-links"
pip-compile $PIP_COMPILE_ARGS
pip-compile $PIP_COMPILE_ARGS -o requirements-dev.txt --all-extras
```
### tests
```python
python - m
pytest - -cov = brdr
tests / --cov - report
term - missing
```
## Motivation & citation
A more in-depth description of the algorithm can be found in the following article (in dutch):
- Dieussaert, K., Vanvinckenroye, M., Vermeyen, M., & Van Daele, K. (2024). Grenzen verleggen.
Automatische correcties van geografische afbakeningen op verschuivende
onderlagen *Onderzoeksrapporten Agentschap Onroerend Erfgoed*,
332. <https://doi.org/10.55465/SXCW6218>.
## Comments and contributions
We would love to hear from you and your experiences with
`brdr` or its sister project [`brdrQ`](https://github.com/OnroerendErfgoed/brdrQ).
The [discussions forum](https://github.com/OnroerendErfgoed/brdr/discussions/) is the place to be when:
- You have any questions on using `brdr` or `brdrQ` or their
applicability to your use cases
- Want to share your experiences with the library
- Have any suggestions for improvements or feature requests
If you have discovered a bug in the `brdr` library you can report it here:
<https://github.com/OnroerendErfgoed/brdr/issues>
We try to keep the list of issues as clean as possible. If
you're unsure whether something is a bug, or whether the bug is in `brdr`
or `brdrQ`, we encourage you to go through the [discussions forum](https://github.com/OnroerendErfgoed/brdr/discussions)
first.
## Acknowledgement
This software was created by [Athumi](https://athumi.be/en/), the Flemish data utility company,
and [Flanders Heritage Agency](https://www.onroerenderfgoed.be/flanders-heritage-agency).
Raw data
{
"_id": null,
"home_page": null,
"name": "brdr",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.9",
"maintainer_email": "Emrys Roef <emrys.roef@vlaanderen.be>, Koen Van Daele <koen.vandaele@vlaanderen.be>, Vermeyen Maerten <maarten.vermeyen@vlaanderen.be>",
"keywords": null,
"author": null,
"author_email": "Karel Dieussaert <karel.dieussaert@vlaanderen.be>, Emrys Roef <emrys.roef@vlaanderen.be>",
"download_url": "https://files.pythonhosted.org/packages/89/65/33dd8795544534170632372e46427f129dbdac34fad9959a3e671faa858c/brdr-0.5.0.tar.gz",
"platform": null,
"description": "# `brdr`\n\na Python library to assist in realigning (multi-)polygons (OGC Simple Features) to reference borders\n\n<!-- badges: start -->\n\n\n\n[](https://doi.org/10.5281/zenodo.11385644)\n\n<!-- badges: end -->\n\nQuick links:\n\n- [Installation](#installation)\n- [Development](#development)\n- [Issues, questions, comments and contributions](#comments-and-contributions)\n\n## Description\n\n### Intro\n\n`brdr` is a Python package that assists in aligning geometric boundaries to reference boundaries. This is an important\ntask in geographic data management to enhance data quality.\n\n* In the context of geographic data management, it is important to have accurate and consistent boundaries for a variety\n of applications such as calculating areas, analyzing spatial relationships, and visualizing and querying geographic\n information.\n* When creating geographic data, it is often more efficient to derive boundaries from existing reference data rather\n than collecting new data in the field.\n* `brdr` can be used to align boundaries from new data to reference data, ensuring that the boundaries are accurate and\n consistent.\n\n### Example\n\nThe figure below shows:\n\n* the original thematic geometry (blue),\n* A reference layer (yellow-black).\n* The resulting geometry after alignment with `brdr` (green)\n\n\n\n### Functionalities\n\n`brdr` provides a variety of functionalities in the Aligner-class to assist in aligning boundaries, including:\n\n* Loaders:\n * aligner.load_thematic_data():Loading thematic data ((Multi-)Polygons) as a dictionary (DictLoader) or geojson (\n GeoJsonFileLoader,GeoJsonUrlLoader)\n * aligner.load_reference_data():Loading reference data ((Multi-)Polygons) as a dictionary (DictLoader) or geojson (\n GeoJsonFileLoader,GeoJsonUrlLoader)\n\n* Processors:\n * aligner.process(): Align thematic boundaries to reference boundaries with a specific relevant\n distance or a range of relevant distances\n * aligner.predictor(): Searches all 'stable' (=predicted) processresults in a range of relevant distances\n * aligner.get_brdr_formula(): Calculating a descriptive formula of a thematic boundary based on a reference layer\n * evaluate(): Compares & evaluates input geometries with another version and adds a EVALUATION_FIELD_NAME\n* Exporters:\n * aligner.get_results_as_geojson(): Returns a collection of geojson-dictionaries with the processresults (resulting\n geometry, differences,...): This can be used for all processresults or only the 'predicted' results\n * aligner.get_input_as_geojson(): Returns a geojson-featurecollection from input-dictionaries (thematic or\n reference)\n * aligner.save_results(): Exports the resuling geojson-files to a specified path:This can be used for all\n processresults or only the 'predicted' results\n\nBesides the generic functionalities, a range of Flanders-specific functionalities are provided:\n\n* Loaders:\n * GRBActualLoader: Loading actual GRB (parcels, buildings)\n * GRBFiscalParcelLoader: Loading fiscal GRB-parcels of a specific year\n* Processors:\n * grb.get_geoms_affected_by_grb_change(): get thematic geometries that are possibly affected by GRB-changes during a\n specific timespan\n * grb.update_to_actual_grb(): aligns the boundaries of thematic features to the actual GRB-boundaries\n\n### Possible application fields\n\n* Geodata-management:\n * Implementation of `brdr` in business-processes and tooling\n * Bulk geodata-alignment\n * Alignment after reprojection of data\n * Cleaning data: In a postprocessing-phase, the algorithm executes sliver-cleanup and validity-cleaning on the\n resulting geometries\n * ...\n* Data-Analysis: Investigate the pattern in deviation and change between thematic and reference boundaries\n* Update-detection: Investigate the descriptive formula before and after alignment to check for (automatic)\n alignment of geodata\n* ...\n\n### QGIS-script\n\nAn implementation of `brdr` for QGIS can be found at [GitHub-brdrQ](https://github.com/OnroerendErfgoed/brdrQ/).\nThis QGIS- script provides a User Interface to align thematic data to a reference layer, showing the results in the QGIS\nTable of Contents.\n\n## Installation\n\nYou can install the latest release of `brdr` from\n[GitHub](https://github.com/OnroerendErfgoed/brdr/) or\n[PyPi](https://pypi.org/project/brdr/):\n\n``` python\npip install brdr\n```\n\n## Basic example\n\n``` python\nfrom brdr.aligner import Aligner\nfrom brdr.enums import OpenbaarDomeinStrategy\nfrom brdr.geometry_utils import geom_from_wkt\nfrom brdr.loader import DictLoader\n\n# CREATE AN ALIGNER\naligner = Aligner(\n crs=\"EPSG:31370\",\n)\n# ADD A THEMATIC POLYGON TO THEMATIC DICTIONARY and LOAD into Aligner\nthematic_dict = {\"theme_id_1\": geom_from_wkt(\"POLYGON ((0 0, 0 9, 5 10, 10 0, 0 0))\")}\nloader = DictLoader(thematic_dict)\naligner.load_thematic_data(loader)\n# ADD A REFERENCE POLYGON TO REFERENCE DICTIONARY and LOAD into Aligner\nreference_dict = {\"ref_id_1\": geom_from_wkt(\"POLYGON ((0 1, 0 10,8 10,10 1,0 1))\")}\nloader = DictLoader(reference_dict)\naligner.load_reference_data(loader)\n# EXECUTE THE ALIGNMENT\nrelevant_distance = 1\nprocess_result = aligner.process(\n relevant_distance=relevant_distance,\n od_strategy=OpenbaarDomeinStrategy.SNAP_SINGLE_SIDE,\n threshold_overlap_percentage=50,\n)\n# PRINT RESULTS IN WKT\nprint(\"result: \" + process_result[\"theme_id_1\"][relevant_distance][\"result\"].wkt)\nprint(\n \"added area: \"\n + process_result[\"theme_id_1\"][relevant_distance][\"result_diff_plus\"].wkt\n)\nprint(\n \"removed area: \"\n + process_result[\"theme_id_1\"][relevant_distance][\"result_diff_min\"].wkt\n)\n```\n\nThe resulting figure shows:\n\n* the reference polygon (yellow-black)\n* the original geometry (blue)\n* the resulting geometry (green line)\n* the added zone (green squares)\n* the removed zone (red squares)\n <img src=\"docs/figures/basic_example.png\" width=\"100%\" />\n\nMore examples can be found in [Examples](https://github.com/OnroerendErfgoed/brdr/tree/main/examples)\n\n## Workflow\n\n(see also Basic example)\n\nTo use `brdr`, follow these steps:\n\n* Create a Aligner-class with specific parameters:\n * relevant_distance (m) (default: 1): Distance-parameter used to decide which parts will be aligned, and which parts\n remain unchanged.\n * od_strategy (enum) (default: SNAP_SINGLE_SIDE): Strategy to align geodata that is not covered by reference-data\n * threshold_overlap_percentage (%)(0-100) (default 50)\n * crs: The Coordinate Reference System (CRS) (default: EPSG:31370 - Belgian Lambert72)\n* Load thematic data\n* Load reference data\n* Process (align) the thematic data\n* Results are returned:\n * Resulting geometry\n * Differences: parts that are 'different' from the original geometry (positive or negative)\n * Positive differences: parts that are added to the original geometry\n * Negative differences: parts that are removed form the original geometry\n * Relevant intersections: relevant intersecting parts of the reference geometries\n * Relevant differences: relevant differences of the reference geometries\n\n## The `brdr`-algorithm\n\nThe algorithm for alignment is based on 2 main principles:\n\n* Principle of intentionality: Thematic boundaries can consciously or unconsciously deviate from the reference borders.\n The algorithm should keep notice of that.\n* Selective spatial conservation of shape: The resulting geometry should re-use the shape of the reference borders where\n aligned is of relevance.\n\nThe figure below shows a schematic overview of the algorithm:\n\n\nThe algorithm can be split into 3 main phases:\n\n* Initialisation:\n * Deciding which reference polygons are candidate-polygons to re-use its shape.\n The reference candidate polygons are selected based on spatial intersection with the thematic geometry.\n* Processing:\n * Process all candidate-reference polygons one-by-one\n * Calculate relevant zones for each candidate-reference-polygon\n * relevant intersections: zones that must be present in the final result\n * relevant differences: zones that must be excluded from the final result\n \n * Evaluate each candidate based on their relative zones: which parts must be kept and which parts must be excluded\n \n * Union all kept parts to recompose a resulting geometry\n* Post-processing:\n * Validation/correction of differences between the original input geometry and the composed intermediate resulting\n geometry after processing the algorithm\n * Technical validation of inner holes and multipolygons that are created by processing the algorithm\n * Clean-up slivers\n * Make the resulting geometry valid\n\nRESULT:\n\nA new resulting output geometry, aligned to the reference-polygons\n\n## Development\n\n### pip-compile\n\n```sh\nPIP_COMPILE_ARGS=\"-v --strip-extras --no-header --resolver=backtracking --no-emit-options --no-emit-find-links\"\npip-compile $PIP_COMPILE_ARGS\npip-compile $PIP_COMPILE_ARGS -o requirements-dev.txt --all-extras\n```\n\n### tests\n\n```python\npython - m\npytest - -cov = brdr\ntests / --cov - report\nterm - missing\n```\n\n## Motivation & citation\n\nA more in-depth description of the algorithm can be found in the following article (in dutch):\n\n- Dieussaert, K., Vanvinckenroye, M., Vermeyen, M., & Van Daele, K. (2024). Grenzen verleggen.\n Automatische correcties van geografische afbakeningen op verschuivende\n onderlagen *Onderzoeksrapporten Agentschap Onroerend Erfgoed*,\n 332. <https://doi.org/10.55465/SXCW6218>.\n\n## Comments and contributions\n\nWe would love to hear from you and your experiences with\n`brdr` or its sister project [`brdrQ`](https://github.com/OnroerendErfgoed/brdrQ).\nThe [discussions forum](https://github.com/OnroerendErfgoed/brdr/discussions/) is the place to be when:\n\n- You have any questions on using `brdr` or `brdrQ` or their\n applicability to your use cases\n- Want to share your experiences with the library\n- Have any suggestions for improvements or feature requests\n\nIf you have discovered a bug in the `brdr` library you can report it here:\n\n<https://github.com/OnroerendErfgoed/brdr/issues>\n\nWe try to keep the list of issues as clean as possible. If\nyou're unsure whether something is a bug, or whether the bug is in `brdr`\nor `brdrQ`, we encourage you to go through the [discussions forum](https://github.com/OnroerendErfgoed/brdr/discussions)\nfirst.\n\n## Acknowledgement\n\nThis software was created by [Athumi](https://athumi.be/en/), the Flemish data utility company,\nand [Flanders Heritage Agency](https://www.onroerenderfgoed.be/flanders-heritage-agency).\n\n\n\n",
"bugtrack_url": null,
"license": "MIT License\n \n Copyright (c) 2024 Onroerend Erfgoed\n \n Permission is hereby granted, free of charge, to any person obtaining a copy\n of this software and associated documentation files (the \"Software\"), to deal\n in the Software without restriction, including without limitation the rights\n to use, copy, modify, merge, publish, distribute, sublicense, and/or sell\n copies of the Software, and to permit persons to whom the Software is\n furnished to do so, subject to the following conditions:\n \n The above copyright notice and this permission notice shall be included in all\n copies or substantial portions of the Software.\n \n THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\n IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\n FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\n AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\n LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\n OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\n SOFTWARE.",
"summary": "BRDR - a Python library to assist in realigning (multi-)polygons (OGC Simple Features) to reference borders ",
"version": "0.5.0",
"project_urls": {
"Documentation": "https://github.com/OnroerendErfgoed/brdr/blob/main/README.md",
"Issues": "https://github.com/OnroerendErfgoed/brdr/issues",
"Repository": "https://github.com/OnroerendErfgoed/brdr"
},
"split_keywords": [],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "205e80768e67791e56d861ceb95d9546c0c757155abc59db0a6577577cd4da18",
"md5": "64ba1ea1789b461aaa3520c86c0242fc",
"sha256": "d9a0af88f2b22f54fd3e6b7dba1771be72f39823abf651be61d6a84e379bf63c"
},
"downloads": -1,
"filename": "brdr-0.5.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "64ba1ea1789b461aaa3520c86c0242fc",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9",
"size": 43351,
"upload_time": "2024-11-14T12:49:02",
"upload_time_iso_8601": "2024-11-14T12:49:02.855144Z",
"url": "https://files.pythonhosted.org/packages/20/5e/80768e67791e56d861ceb95d9546c0c757155abc59db0a6577577cd4da18/brdr-0.5.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "896533dd8795544534170632372e46427f129dbdac34fad9959a3e671faa858c",
"md5": "77cb97c8f2180ce304969abd370b5d7a",
"sha256": "92145dddf7663ca8d71c736291be3753504e97041e2ddf9e66856ff3c8260ee3"
},
"downloads": -1,
"filename": "brdr-0.5.0.tar.gz",
"has_sig": false,
"md5_digest": "77cb97c8f2180ce304969abd370b5d7a",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9",
"size": 19842849,
"upload_time": "2024-11-14T12:49:19",
"upload_time_iso_8601": "2024-11-14T12:49:19.178505Z",
"url": "https://files.pythonhosted.org/packages/89/65/33dd8795544534170632372e46427f129dbdac34fad9959a3e671faa858c/brdr-0.5.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-11-14 12:49:19",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "OnroerendErfgoed",
"github_project": "brdr",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"lcname": "brdr"
}
