shrug-l: Two Polygon Topology

Karen Blaney karen.blaney at gmail.com
Thu Mar 5 19:17:34 EST 2009


Must not overlap
Must not have gaps

bring them into one feature class and use the two above topology rules to
identify the overlaps and gaps, but edit each of the feature classes
separately when getting rid of the gaps and overlaps using snapping options.

Good luck.


On 3/5/09, Halverstadt, Heather <heather.halverstadt at brevardcounty.us>
wrote:
>
>  Hey SHRUGgies, hope your day has gone well!
>
>
>
> I have a problem that I could use your help on. I have two polygons, (let’s
> call them A  and B) that eventually will be going into an intersect. A and B
> don’t always share a boundary, but where they do, that boundary needs to be
> identical to avoid creating slivers when they intersect. For example, say
> one of the features in A is a square with four sides (let’s call them N, S,
> E and W). Only the W and N  sides have to be identical to the corresponding
> feature B, and the S and E sides don’t share that boundary. Essentially, I
> am trying to identify gaps and overlaps between the two shapefiles. I ran
> topology on them individually, but when I went to run topology on them
> together, I had a very hard time finding a good rule that worked well.  Your
> advice would be very much appreciated!
>
>
>
> Thanks,
>
>
>
> Heather Halverstadt
>
> GIS Analyst III
>
> 911 Administration
>
> Government Center C-201
>
> 2725 Judge Fran Jamison Way
>
> Viera, FL 32940-6602
>
> (321) 690-6846
>
>
>
> _______________________________________________
> SHRUG-L mailing list
> SHRUG-L at lists.dep.state.fl.us
> http://lists.dep.state.fl.us/mailman/listinfo/shrug-l
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.dep.state.fl.us/pipermail/shrug-l/attachments/20090305/ccba9f93/attachment.html


More information about the SHRUG-L mailing list