**jany_ wrote:**
I found that using AddFeature with a new feature is never a good idea. I think creating a feature without a featureSet seems to be a bad idea too. That seems to cause more problems than it helps.We have (legacy) code creating features like this in a few other places, and i don't want to break anything that currently works, i suppose to put a feature within the context of it's parent featureset i can set the featureSet.ParentFeature property, or do you see more reasons why creating a new Feature() like this is a bad idea ?
I think labeling MultiPolygons works so we should be able to label MultiLineStrings too. I'll check again why I thought it worked for me. Maybe it just didn't work because you create a MultiLineString in a way I didn't know or think about.So i am not the only one wondering why we need the separate BasicGeometries layer, i hope the NTS integration project is a success, that would be a big improvement for version 2.0 !
I'm currently working on integrating the newest NetTopologySuite. That means that FromBasicGeometry should become obsolete as soon as I'm done. I couldn't figure out why we have those BasicGeometries (which the original NTS-code doesn't) just to convert them to full geometries again and again.