Personally, I usually draw or drag the edges to overlap, then erase the unwanted area using the other object. Steve Wallace Florida Farm Bureau -----Original Message----- From: Jacques Paris <[EMAIL PROTECTED]> To: Jeff Rogers <[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Thursday, February 11, 1999 8:29 AM Subject: MI RE: Snap Tolerance >> -----Original Message----- >> I've been trying to join the borders of one polygon with another using the >> node editor tool. When I specify a tolerance of 5 pixels the nodes appear >> to snap to the corresponding nodes in the bordering polygon however, when >I >> zoon in the nodes are not snapped. I have to progressively zoom in and >> re-edit before the nodes coorectly snap. Is this a bug in MapInfos >editing >> capabilities? Is there a way arround this? > >Jeff, > >I think you have there a typical situation where the "native" MI resources >are very limited, i.e. editing maps for eliminating internal "errors". There >are several third party utilities at a noticeable cost to do that. > >As a way around?... Snapping is operative only while "moving" (or creating) >nodes. Just setting a tolerance level does not snap existing nodes to each >other within that limit. Zoom level will only show more distinctly the >non-coincidental nodes and there is no way to identify visually "snapped" >nodes from "not-snapped" ones. You have to move each node away from its >original position and back to its "neighbor" position to be sure that it is >snapped to it. > >The trick is to find a way to locate the nodes that have to be re-snapped so >that you do not have to go through each one. I often use the "combine" of >two adjacent polygons to check visually if there is any "trace" along their >common border, or to find out the number of polygons in the combined region. >That may help me to locate the nodes that would be "apart" form each other >leaving a gap between the original regions. Then, ther is the problem of the >overlapping nodes; sometimes, the "intersect" can help in the same manner as >the combine. > >All that to say that there is no simple way around if you cannot afford >those editing tools. Even a free utility like MapCheck will not do the job >for you; it may identify some problem areas (and may be not all), but you >will have to do the "repairs" youself. > >I expect you will have many answers because your question is a deep concern >to many of us. > >Jacques Paris >============================================================ >e-mail [EMAIL PROTECTED] > >gis activity (MapInfo mainly) > http://www.total.net/~rparis/gisproducts.htm >============================================================ > >---------------------------------------------------------------------- >To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put >"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED] ---------------------------------------------------------------------- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
