The general problem, which is "solved" by systems like TIGER is that you
should really never draw a boundary between two regions twice. Once should
be enough, and if you draw the boundary only once, you can never have
slivers or gaps.
The MapInfo solution is a little indirect. This is what you do. You draw
one polygon as precisely as you can. Then draw, (or edit) the other
polygon to overlap the first one substantially. I deliberately make it
crude so that the second polygons version of the boundary can never be
mistaken for the correct one. The next step is to make the crude polygon a
target (Objects > Set target). I assume that it is editable, because we
were just editing. Next, select the bordering polygon which has the
carefully drawn border, and click on Objects > Erase. That is all. The
parts of the crude polygon inside the carefully drawn polygon are erased,
and the boundaries match.
At 08:05 PM 2/10/99 -0800, Jeff Rogers wrote:
>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 Rogers
>[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]
>
>
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
