v3.0.0

This library is now Kotlin Multiplatform, that is, JVM, JS, native.

I was unable to preserve the old CountryBoundaries.load(inputStream) API on JVM. Not sure if there would have been a way, but I didn't find any, hence a new major version. An instance is now initialized via CountryBoundariesUtils.deserializeFrom(inputStream) on Java.

There are no other changes, so users on Java may want to decide to stay on 2.x for now, as this migration of course also added new dependencies (on Kotlin standard library and on Kotlin IO library).

v2.1

Fix raster sizes other than 360x180 didn't work correctly.

v2.0

The data serialization format changed. It is now more compact and not specific to Java anymore, about half the size as before.

Hence, when upgrading to this version, you need to get the newly generated default data from the data/ directory or generate it yourself using the Java program in the generator/ directory if you are using a custom geojson/osm data source.

v1.6

Fix #12:

• at latitudes / longitudes that are exactly at raster cell edges, the library would not find any country under certain circumstances (e.g. longitude 6.0 for all three data sets)
• for longitude +180.0°, the library would never find any country