Changelog History
Page 4
-
v0.13.0 Changes
2020-04-13
โ Removes the
Line
type. This was done in order to better align simplefeatures with the OGC Simple Feature Access specification, and allows ๐ many edge cases in the code to be removed. Users previously using theLine
type should use theLineString
type instead.โ Adds an explicit
GeometryType
type, which represents one of the 7 types of geometry (Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection). TheType
method now returns aGeometryType
rather than astring
.
-
v0.12.0 Changes
2020-04-11
โ Removes redundant PostGIS reference implementation tests, improving CI speed.
Overhauls WKB and WKT interfaces. These now return
[]byte
andstring
respectively, rather than writing to a suppliedio.Writer
.โ Removes the
IsValid
method. If users want to know if a geometry is valid or not, they should check for an error when geometries are constructed.Unexports the partially implemented
Intersection
method. It will be reexported once the feature is complete.๐ Fixes a memory related bug in the
github.com/peterstace/simplefeatures/geos
package.โ Adds a wrapper for the GEOS simplify function.
๐ฆ Simplifies the
github.com/peterstace/simplefeatures/geos
package by not exporting the 'handle' concept. The package now just exposes standalone functions.
-
v0.11.0 Changes
2020-04-05
- โ Adds a new package
github.com/peterstace/simplefeatures/geos
that wraps the GEOS library. The following functions are wrapped: Equals, Disjoint, Touches, Contains, Covers, Intersects, Within, CoveredBy, Crosses, Overlaps, Union, Intersection, and Buffer.
- โ Adds a new package
-
v0.10.1 Changes
2020-03-24
- โ Adds documentation comments to all exported symbols.
-
v0.10.0 Changes
2020-03-20
- โ Adds support to geometries for Z (3D) and M (Measure) values. This includes many breaking changes, primarily around geometry constructor functions.
-
v0.9.0 Changes
2020-03-03
๐ Special thanks to Frank Sun and Peter Jones for contributing to this release.
๐ Fixes a bug in the intersects predicate between
MultiLineString
andMultiPolygon
.โ Removes the
EmptySet
type. ThePoint
,LineString
, andPolygon
types can now represent empty geometries.โ Adds the
GeometryType
method, which returns a string representation of the geometry type (e.g. returns"LineString"
for theLineString
geometries).โ Adds support to store empty
Point
geometries withinMultiPoint
geometries.Simplifies geometry constructor options by removing the
DisableExpensiveValidations
option.โ Removes the
Equals
predicate (which was only implemented for a small proportion of geometry type pairs).Modifies the
TransformXY
methods to return their own concrete geometry type.
-
v0.8.0 Changes
2020-02-20
๐ Special thanks to Lachlan Patrick for contributing to this release.
โ Adds a
Length
implementation for theGeometry
type.Modifies the
Boundary
for concrete geometry types to return a concrete geometry type (rather than the genericGeometry
type).โ Modifies the Fuzz Tests to use batching.
๐ Fixes a bug in the
IsSimple
method forMultiLineString
.โ Adds
Centroid
implementations for all geometry types.โ Adds a new suite of reference implementation tests using
libgeos
.
-
v0.7.0 Changes
2020-01-24
๐ Fixes a deficiency where
LineString
would not retain coincident adjacent points.โ Adds two new methods to
LineString
.NumLines
gives the number ofLine
segments making up theLineString
, andLineN
allows access to thoseLine
segments.โฌ๏ธ Reduces the memory required to store a
LineString
.
-
v0.6.0 Changes
2020-01-21
๐ Special thanks to Lachlan Patrick for contributing to this release.
โ Adds
Reverse
methods, which reverses the order of each geometry's control points.โ Adds
SignedArea
methods, which calculate the signed area of geometries. The signed area takes into consideration winding order, and produces either a negative or positive result for non-empty areal geometries.
-
v0.5.0 Changes
2020-01-17
๐ Fixes a bug where polygons with nested rings would erroneously be reported as valid.
๐ Performance improvements have been made to
Polygon
andMultiPolygon
validation. The algorithms used now have sub-quadratic time complexity, and memory allocations have been significantly reduced.