Skip to content

Releases: jillesvangurp/geogeometry

3.4.2

24 Jul 16:48
Compare
Choose a tag to compare
  • add id field to Feature so a strict parser configuration won't break when that field is present (#40)

Full Changelog: 3.4.1...3.4.2

DEFAULT_JSON externalized

04 Jun 04:31
Compare
Choose a tag to compare
  • DEFAULT_JSON and DEFAULT_PRETTY_JSON now live in an external library. This will break your imports if you were using that but should be a simple update. Reason for this is that I have multiple projects where I was copy pasting this thing. So, I created a separate library for it.
  • Update to kotlin 2.0 and clean up the build file. 1.9 api is still supported.

Wasm support

15 May 05:53
Compare
Choose a tag to compare

Adds a wasm build target.

3.3.9

15 Jan 15:28
Compare
Choose a tag to compare
  • now sets jvmTarget 11 to fix #39
  • misc improvements related to translate and rotate functionality
  • improved geojson handling and some nice integration with geojsonio for debugging

Full Changelog: 3.3.7...3.3.9

MGRS coordinates

17 Nov 14:04
Compare
Choose a tag to compare
  • adds a robust implementation for mgrs / usng coordinates

Add support for UPS coordinates

13 Nov 10:53
Compare
Choose a tag to compare

Add support for UPS coordinates and automatic switching between UTM and UPS depending on the latitude.

utm & centroid improvements

10 Nov 16:52
Compare
Choose a tag to compare
  • swapped out the implementation for UTM coordinates for a better one after finding some bugs
  • improved centroid calculation on geometries and also fixed polygonCenter to behave the same
  • slightly improve concave hull
  • misc build improvements

scaleX, scaleY, rotate, & more multiplatform targets

02 Nov 20:53
Compare
Choose a tag to compare
  • update to kotlin 1.9.20
  • add more multiplatform targets (linux, mac, windows, IOS). Android is to be done as it requires an additional plugin.
  • implement scaleX, scaleY, and rotate functions for geojson that works for Geometry instances, Features, Feature collections, and the various coordinate arrays.
  • fix bug with centroid implementation to use the min/max divided by two instead of the mean of the coordinates.

NATO UTM Coordinate support

15 Sep 12:36
Compare
Choose a tag to compare

Lat lon confusion on calculate suitable hash length

15 Dec 11:43
Compare
Choose a tag to compare
  • #36 calculate suitable hashlength was broken (swapped lat/lon) Thanks @IdoPrem !