geo changelog

Changelog History

Page 1

• v3.3.5

  August 26, 2020

  • 🛠 Fixed
    • Typespec on Point

• v3.3.4

  August 07, 2020

  • 🛠 Fixed
    • Update typespec to make Point easier to use

• v3.3.3

  • 🛠 Fixed
    • Add missing MultiPointZ in list of geometry types
    • Improve docs around Geo.endian type

• v3.3.2

  • 🛠 Fixed
    • Some optimizations based on benchmarking

• v3.3.1

  • 🛠 Fixed
    • Bugs found while property testing

• v3.3.0

  • ➕ Added
    • Updated Type Specs
    • Allow to disable String.Chars implementation for Geo objects

• v3.2.0

  • ➕ Added
    • 3D versions of the various datatypes

• v3.1.1

  • 🛠 Fixed
    • Optimise reverse_byte_order/1

• v3.1.0

  February 08, 2019

  • ➕ Added
    • Support WKB empty multipolygons
    • Add PointZ support to Geo.Json

• v3.0.0

  April 14, 2018

  • ➕ Add

    • Geo.WKT.encode!
    • Geo.WKT.decode!
    • Geo.WKB.encode!
    • Geo.WKB.decode!
    • Geo.JSON.encode!
    • Geo.JSON.decode!

  • ✨ Enhancement

    • Geometry struct now have a properties field. This is used to convert GeoJSON properties

  • 💥 Breaking

    • Geo.WKT.encode now returns either {:ok, binary} or {:error, exception}
    • Geo.WKT.decode now returns either {:ok, geometry} or {:error, exception}
    • Geo.WKB.encode now returns either {:ok, binary} or {:error, exception}
    • Geo.WKB.decode now returns either {:ok, geometry} or {:error, exception}
    • Geo.JSON.encode now returns either {:ok, map} or {:error, exception}
    • Geo.JSON.decode now returns either {:ok, geom} or {:error, exception}
    • All Ecto.Type behaviour implementations were removed. This may not effect too many people, but it was moved to the geo_postgis package

• 1
• 2
• 3
• 4
• 5
• Next ›
• Last »