NuGet · #2456 most downloaded on NuGet

NetTopologySuite.IO.GeoJSON4STJ

4.0.013M downloads/moNetTopologySuite/NetTopologySuite.IO.GeoJSON ↗New releases in your daily digest, changelog included.

This package contains the System.Text.Json version of the GeoJSON IO library.

Last release 3 years ago
no release in 18 months
Ships unpredictably
gaps range from 4 weeks to 120.5 years
Nearly every release is documented
notes for 6 of 6 stable releases
3 versions withdrawn
withdrawn after publishing
127 years old
9 releases · first in 1900

Release timeline

9 releases since 1900

Releases

4.0.015 Sept 2023
Support a variant of JsonElementAttributesTable that can be modified in-place, at a cost to reading performance. by @airbreather in #118
What's Changed

Support a variant of JsonElementAttributesTable that can be modified in-place, at a cost to reading performance. by @airbreather in #118

Fix feature serialization when attributes or geometry are null (#128) by @jjanuszkiewicz in #129

fix code style violation errors by @jjanuszkiewicz in #124

add GeoJsonConverterFactory constructors that don't require a GeometryFactory by @jjanuszkiewicz in #125

Fix serialization bug by @alex2512 in #130

Homogenize exceptions in GeoJSON by @FObermaier in #132

Slightly better exception types in 4STJ by @airbreather in #134

New Contributors

@jjanuszkiewicz made their first contribution in #129

@alex2512 made their first contribution in #130

Full Changelog: v3.0.0...v4.0.0

From the same repository

NetTopologySuite/NetTopologySuite.IO.GeoJSON

NetTopologySuite.IO.GeoJSONNuGetThis package contains the GeoJSON IO library. Portions of this library were inspired from an early version of GeoJSON.Net by Jörg Battermann.

3.0.025 Nov 2022

geojsonwriter support for dimension 3 by @xfischer in #76

What's Changed

geojsonwriter support for dimension 3 by @xfischer in #76
Custom coordinates formatting by @bstordrup in #81
Add link to geojson.org in the README by @verdie-g in #84
handled additional properties in geometry by @DGuidi in #95
Fix Issue #89 by @mymatthew in #90
fixed GeometryConverter for empty geometries deserialization by @DGuidi in #97
fixed "newtonsoft" empty geometries deserialization by @DGuidi in #99
Switch to GitHub Actions and update target versions. by @airbreather in #103
Fix proper polygon ring orientation by @FObermaier in #112

New Contributors

@xfischer made their first contribution in #76
@bstordrup made their first contribution in #81
@verdie-g made their first contribution in #84
@mymatthew made their first contribution in #90

Full Changelog: v2.0.4...v3.0.0

Open source →

Additional notes

What's Changed

Feature/skip unknown feature members by @Jobbakker in #70
Add link to geojson.org in the README by @verdie-g in #84
handled additional properties in geometry by @DGuidi in #95
Fix Issue #89 by @mymatthew in #90
handled 'writebbox' parameters for features and featurecollections by @DGuidi in #101
Switch to GitHub Actions and update target versions. by @airbreather in #103
Fix proper polygon ring orientation by @FObermaier in #112
Support JsonElement <--> IAttributeTable by @airbreather in #113

New Contributors

@Jobbakker made their first contribution in #70
@verdie-g made their first contribution in #84
@mymatthew made their first contribution in #90

Full Changelog: stj-v2.1.0...stj-v3.0.0

2.1.116 Oct 2020

Empty geometries are now written with "coordinates": [] instead of "coordinates": null , for better interoperability with other implementations that f

Changes:

Empty geometries are now written with "coordinates": [] instead of "coordinates": null, for better interoperability with other implementations that follow RFC 7946's suggestion to do it this way (#67).

Open source →

2.0.416 Jul 2020

Everything related to our use of the serializer context, most visibly its instability in a multithreaded environment, has been fixed by coming up with

Bug fixes:

Everything related to our use of the serializer context, most visibly its instability in a multithreaded environment, has been fixed by coming up with an alternative way to achieve the same goals (#59). Thanks @russcam!
Geometries specified with "coordinates": null (or "geometries": null for GeometryCollection) are now treated as empty, instead of causing us to read arbitrarily far into the stream (#65). This is done primarily to work around uninspired behavior in our converters for the System.Text.Json library.

Open source →

Additional notes

One bug fix: