Upgrade from `wicket` to `wellknown` for wkt-geojson conversions
Type of change
-
Bug Fix -
Feature
Please provide link to gitlab issue or ADR(Architecture Decision Record)
#251 (closed)
Does this introduce a change in the core logic?
- [YES/NO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [YES/NO]
What is the current behavior?
- WKT <-> GeoJSON Conversions carried out by
wicket
dependency.
What is the new/expected behavior?
- WKT <-> GeoJSON Conversions carried out by
wellknown
dependency. End result is identical.
Have you added/updated Unit Tests and Integration Tests?
NA.
Any other useful information
wellknown
has open source ISC license, which is functionally identical to the MIT License and compatible with Apache 2.0. This is opposed to wicket
which carries GPLv3 license which is not compatible with Apache 2.0 license. No modifications were made to the wellknown
source code for the use applied here.
Closes #251 (closed)