NetTopologySuite v2.1.0 Release NotesRelease Date: 2020-08-04 // 7 months ago
- ⚡️ Updated JTS compatibility to 1.17.0.
- See JTS' own release notes for details of what's included in this; those will not be reproduced here.
- Note that the API breaking change included in JTS 1.17.0 was not ported to this release. You may safely cast
Polygon.ExteriorRing, any element of
Polygon.InteriorRings, and the return value of
- 👌 Improve xmldoc.
- 🛠 Fix some packaging issues.
- ➕ Add
GeometryFactoryEx, which allows callers to force polygon rings to be a certain orientation.
NtsGeometryServicesin order to allow subclasses to alter the behavior of
- Mark a few useful members on
QuadEdgeas public instead of internal (they are public in JTS).
- GML readers read Z values now.
Coordinatemethods that accept
Ordinateenum values now treat values greater than
Measure16the same way they treat all other "
Ordinatevalue is not present in this instance" situations. In the most literal sense, this is technically a behavior breaking change, but only for people who are both casting integer values >32 to
Ordinateenum values and actually using them with
CoordinateSequenceinstances with at least 19 dimensions, at least 17 of which are measures.
STRtree<T>.Removenow has a possibility of working as expected when T is a value type, instead of never removing anything. It now uses the default equality comparer for the type. Reference types still use object reference equality, for backwards compatibility and performance reasons (it's OK to do this for value types, because Remove was essentially a really slow no-op for them anyway).
- The internal
Coordinatesubclass that we use for everything other than XY / XYZ / XYM / XYZM now handles "missing" ordinate values consistently with how other Coordinate types handle them.
- Copying a Geometry no longer clobbers its
GeometryFactorywith a brand new one based on the SRID (JTS uses a separate field for this, so this is more faithful).
- More methods on
GeometryFactoryhave been marked virtual, for consistency with JTS.
- 🛠 Fix an incorrect port:
GeometryTransformer.Transformwas inappropriately transforming a
LinearRinginto a plain
LineString, which is never better.
- The center of a
BintreeInterval is now computed correctly (JTS does not have a method for this; previously, it was the same as the width).
- ➕ Add
Envelope.Diameterto get the largest possible distance between any two points that both intersect the bounding box.
- 🛠 Fix an issue with
- Start using
Microsoft.DotNet.ApiCompatto help us avoid accidentally making API breaking changes.
- 👀 In the same spirit of the improvements to WKT number formatting that came with JTS 1.17.0, also work around a very old bug in .NET Framework / earlier versions of .NET Core before 3.0. For details of the bug and its fix in .NET Core 3.0, see: https://devblogs.microsoft.com/dotnet/floating-point-parsing-and-formatting-improvements-in-net-core-3-0/
- ➕ Add
IEntireCoordinateSequenceFilter. Very similar to
ICoordinateSequenceFilter, but it is only called once per
CoordinateSequence, to enable some significant performance optimizations. We do not currently take advantage of this in NTS, but we're already looking at opportunities, and we're excited to see what you do with it!
- ⚡️ Updated JTS compatibility to 1.17.0.
Previous changes from v2.0.0
🚀 This major release represents several efforts to improve usability and consistency throughout NTS, brought on by some changes in JTS 1.16.0 that we felt would not be best to port as-is.
🚀 As such, this release contains many breaking changes, some of which are very significant. Because the NuGet ecosystem heavily favors using SemVer for versioning, we felt that it's time to start deviating from using the JTS compatibility version numbering scheme that we have used in the past, and call this first release 2.0.0.
Some of the breaking changes:
📦 1. NetTopologySuite is, again, the primary NTS package.
- GeoAPI has been gutted. The relevant useful parts are now inside of NTS.
- Many interfaces have been removed, in favor of just using their corresponding classes.
Coordinate.Zis no longer stored in a field on the base class. Full
Zsupport is added by subclasses.
Ordinatesnow define 16 spatial dimensions and 16 measure dimensions.
CoordinateSequence) now uses integer ordinate indexes. 0️⃣ 7. By default, reading WKT without "Z", "M", or "ZM" tags using
WKTWriterwill now give a geometry that appears to support holding Z values, even if no Z values are actually present.
falseto prevent this, but keep in mind that this will break things like
"POINT (1 2 3)"that older versions of NTS supported.
GeoAPI issues addressed in 2.0.0, in the order they were closed:
🚚 1. NetTopologySuite/GeoAPI#54: Remove obsolete interfaces, classes and members
- NetTopologySuite/GeoAPI#55: Future of Coordinate class 🚚 3. NetTopologySuite/GeoAPI#59: Remove ICloneable implementations across the board
- NetTopologySuite/GeoAPI#64: Target just .NET Standard 2.0 🚚 5. NetTopologySuite/GeoAPI#65: Remove reflection-based GeometryServiceProvider.Instance bootstrap
- NetTopologySuite/GeoAPI#68: Replace notable interfaces with abstract classes, for multiple reasons 🚚 7. NetTopologySuite/GeoAPI#70: Remove (standalone) GeoAPI
NTS issues addressed in 2.0.0, in the order they were closed:
⚡️ 1. #265: Update to JTS 1.16.0
- #292: Target just .NET Standard 2.0 ⚡️ 3. #294: Update to JTS 1.16.1 👻 4. #282: Exception while fetching Interior Point - NetTopologySuite.Geometries.TopologyException 🚚 5. #291: Remove obsolete types and members
- #316: Mark a few more things obsolete 💻 7. #289: DistanceComputer.PointToSegmentString skips the last vertex of an ICoordinateSequence 🚚 8. #308: Remove IGeometry warts 📦 9. #315: Tweak NuGet packages again
- #244: Consider replacing AssemblyInfo.cs and *.nuspec with additional things in *.csproj
- #309: Make IsWithinDistance an extension method
- #311: Fix the design of Ordinate values to be consistent and behave predictably
- #246: Aggregate operations 👍 14. #324: Support MSSQL-compatible WKT writing
- #156: WKTWriter doesn't create the expected result