- Enhancements
- Updated dependencies to allow for using ecto 2.0 beta versions
- Enhancements
- Updated Postgrex and Poison optional dependencies
- Enhancements
- Made Postgrex, Ecto, and Poison optional dependencies
- Breaking
- Geo.JSON.encode and Geo.JSON.decode now do not do any JSON parsing at all and instead work on a map representation of GeoJSON. All JSON encoding and decoding must be done before or after calling those functions.
- Enhancements
- Made Postgrex a required dependency
- Enhancements
- Updated to Ecto 1.0
- Enhancements
- Added an
opts
parameter toGeo.JSON.encode
to allow for skipping JSON encoding
- Added an
- Enhancements
- Fixed st_dwithin macro
- Enhancements
- Updated cast function on structs to handle maps and strings
- Now reading the srid from geo json
- Enhancements
- Basic Support for Geography datatype
-
Enhancements
- Added PostGIS function macros for use in Ecto Queries. Currently only the OpenGIS ones
-
Breaking
Geo.PostGIS
is nowGeo.PostGIS.Extension
- Changed from Jazz to Poison for JSON encoding and decoding
- Enhancements
- Geo.PostGIS is now a Postgrex Extension
- Updated to work with latest version of Ecto
- Bug fixes
- Correctly decoding WKB strings that caused invalid geometries to be produced when there is one element in a multi geometry
- Bug fixes
- Fixed bug when decoding multi geometry wkb with one geometry inside would cause a crash
-
Enhancements
- Created structs for the supported geospatial types (Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, GeometryCollection)
- GeoJson module will encode the srid as a crs property if an srid exists
-
Backwards incompatible changes
- Removed the Geometry struct. Use one of the geometry type structs instead
- The base coordinate pairs are now tuples ({0,0} instead of [0,0])