Unfortunately, there isn’t a quick fix for this issue. With ThinkGeo v12, we moved over to support using .NET Core 3.x and above. Due to this, we no longer have support for Microsoft’s
SqlTypes geometry functions that were integral to the speed of IsoLines. It will take some time in order for us to develop an enhancement comparable speed for v12.
In the meantime, if you just want to just get the polygons in an
IsoLineLayer, you can extract them with the following code:
Collection<Feature> features = isoLineLayer.GetIsoLineFeatures();
foreach (var feature in features)
LineShape line = feature.GetShape() as LineShape;
PolygonShape polygon = line.ToPolygonShape();
Feature polyFeature = new Feature(polygon, feature.ColumnValues);
// Do work on polygons, or save them to a layer
This will check to see if any of the lines generated by
LinesOnly can be converted into polygons and creates a new Feature with the same column value as the line. Of course, this won’t be 100% like
ClosedLinesAsPolygons and might not show properly on the map with opaque fill styles, but it will have a similar outcome.
I will update this thread and tag you once we have a proper fix released.