Hei Ravi,
3. Please consider making UNION of two layers by adding both layer's attribute tables in the resulting file. A + B = C (C contains a table with attributes of both A and Bwhere there is no intersection, attributes are not populated)Been trying to make an exercise on Mineral prognostication, but is held up at this point as there is no UNION.
this function should not be called union, but rather merging as the term union in the manner we use it is derived from the OGC simple features standard. Further what you want is not that easy.. For instance: what do you do if several feartures (i.e. points) are contained within one polygon? which point do you chose? The feature works only if there is a one-to-one relation. Basically I have programmed a similar function right now for the thiessen polygons.. but I am not sure if people are aware of the problems when using it...
what do others think.. Should I implement it despite my reservations? Should I extend the "Transfer Attributes" function for "intersection"? Should we also rename Overlay.. to intersection? PS: please move on with this discussion [EMAIL PROTECTED] Stefan
ThanX in anticipation. Ravi Kumar
_______________________________________________ jump-users mailing list [email protected] http://lists.refractions.net/mailman/listinfo/jump-users
