Hello, Yes, your type of buffer is exactly what I'm trying to do.
While I would love, eventually, to talk about the details/robustness of the design, for now I simply want to get *any* result. I grab a point layer, extract the features, use their geometries to buffer and union (JTS operations) then build a feature. Now I need to make this feature into a "layer". I gather once I have a "layer" I can create an AddLayerCommand and use IMap.sendCommand(A)Sync() to add the layer to the map. How do we go from having a Geotools Feature to having a uDig Layer? thanks, adrian On Mon, 2006-02-27 at 18:59 +0200, Vitali Diatchkov wrote: > Hello, Adrian! > What do you mean "buffer operation" ? > > I implemented the functionality (for my customers) of buffering the whole > layer with linear type of geometry (let's say - roads, represented > as features with linear type of geometry and the width as a feature > attribute). In this case the attribute value is used as a width for the > buffering (linear geometry goes to the polygonal geometry). Buffering > operation is performed using JTS stuff that is stable and good enough. > > Do you mean "buffering" in this sense? > > Or is the architectural problem with converting features from one layer > while the new features should go to another layer? > > Could you describe the problem with more details... Probably I will give > some hints... > > Vitali. > _______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
