Suggestion: make two sets of interfaces - data and methods about geoapi HOT 3 CLOSED

Perhaps specific interfaces could be created for the parts that only hold data. The existing interfaces should then be split into a data part and a method part which is derived from the data part.

from geoapi.

Why not use NetTopologySuite.IO.GeoJSON package.
It was derived from @jbatterman s GeoJSON-Net code a while back. It might not be fully in line with the current package, but you get NTS/GeoAPI geometries for free :)

The original GeoAPI package was derived from the GeoAPI java (some ancient 0.x version) package that has undergone some sort of standardization. That was a long time before I joined the project so I cannot really say anything about it.

The only implementation of the GeoAPI interface set (.NET) that I know of is NetTopologySuite.
For your project I would suggest you go with a set of extension methods to cast GeoJSON-Net geometries to GeoAPI geometries.

from geoapi.

The original GeoAPI package was derived from the GeoAPI java

Actually, we (I) started with this goal, but then I switched to a simple(r) "abstraction" over NTS/JTS Geometry model.
Anyway, as @FObermaier said, it's straightforward to create some extension methids to converto from/to GeoJSON-Net objects.

from geoapi.