Create Shapefile From WKT failed about nettopologysuite.io.esri HOT 6 CLOSED

About wkt, I tried both use EPSG:3826 and EPSG:4326, but no one work.

I tried this below and not work too:

...
var geometry = wktReader.Read(wkt) as Polygon;
...

from nettopologysuite.io.esri.

I finally fixed this issue by separating polygon writer from original polygon writer, who use MultiPolygon at begin and cause this error I guessed.
Now, I have MultiPolygonWriter ( original PolygonWriter ) and PolygonWriter ( new ), the newer one will only create the type Polygon in Geometry, and other polygon types will be processed by the original writer.

If anyone need the change I made, here is the repo: https://github.com/anthea-wu/NetTopologySuite.IO.Esri

Hopes it can be helpful 😃

from nettopologysuite.io.esri.

from nettopologysuite.io.esri.

please consider that NetTopologySuite.IO.Esri is in heavily development mode, so maybe you can give a try to the more stable NetTopologySuite.IO.Shapefile

from nettopologysuite.io.esri.

I would like to leave open the issue, so we can track the problem when the IO.ESRI API will be stable enough to check what happens

from nettopologysuite.io.esri.

I checked a bit the code you posted and - no bad feelings - the code that checks if the geometry is a polygon or a myltipolygon is flawed.
There is no need for an additional writer because the API expects (at this stage, at least) ALWAYS multigeometries to be written.

So here how you can handle your use case:

var geometry = wktReader.Read(...
var poly = (Polygon)geometry;
var mpoly = poly.Factory.CreateMultiPolygon(new[] {poly});
geometry = mpoly;

A similar handling is done in a test for a single-linestring write

Actually it is not clear to me how the API works this way, but I suppose that maybe can be improved once the API will be considered stable enough.

@KubaSzostak FYI, I closed the issue but of course feel free to add your own thoughts

from nettopologysuite.io.esri.