Calculating boundaries of different adjacent polygons

2134
10
08-26-2012 02:33 PM
AndreasDaim
Occasional Contributor
Attached you can see a meadow (selected polygon) and i want to calculate the length of the shared boundary with the blue, green, red, black polygons and store this length information in the meadow attribute table. (e.g: red: 150m, blue: 200m etc..)

Is this possible?

[ATTACH=CONFIG]17243[/ATTACH]

best regards
andreas
0 Kudos
10 Replies
AndreasDaim
Occasional Contributor
...and i've in my whole map not always perfect hand drawn polygons (meadows, woods, fields...) touching each other or overlapping.
is there an easy way to get rid of this problem?
0 Kudos
MarkFawkes
Occasional Contributor
How have you stored the polygon data? i.e. individual shapefiles for each colour/class, single shapefile with attribute symbology, geodatabase feature classes or shapefiles?
0 Kudos
MarkBoucher
Regular Contributor II
...and i've in my whole map not always perfect hand drawn polygons (meadows, woods, fields...) touching each other or overlapping.
is there an easy way to get rid of this problem?


You could set up topology rules and use the topology editing tools to correct the hand drawn polygons so they don't overlap or have gaps.
0 Kudos
AndreasDaim
Occasional Contributor
How have you stored the polygon data? i.e. individual shapefiles for each colour/class, single shapefile with attribute symbology, geodatabase feature classes or shapefiles?


Calculation should be done between polygons from:

Feature Class "Grasslands" with different subtypes
Feature Class "Fields" with different subtypes
Feature Class "Woods" with different subtypes
And single Feature classes for infrastructure: residential areas...

and i need the output stored into the attribute table of the grasslands subtypes.
0 Kudos
AndreasDaim
Occasional Contributor
You could set up topology rules and use the topology editing tools to correct the hand drawn polygons so they don't overlap or have gaps.


sounds good, have to check this first out for myself. could work. thanks!
0 Kudos
ChristopherThompson
Regular Contributor
I think you may have to convert your polygons to polylines, make sure they are attributed by the classes you are interested in, and then perform an intersection or a spatial join between the datasets to do this.  I'm not sure that you can achieve what you want with polygons.
0 Kudos
AndreasDaim
Occasional Contributor
hm, polylines sounds like a workaround.
Calculating the boundary length of each other touching polygons not easier possible?

best regards
andreas
0 Kudos
AndreasDaim
Occasional Contributor
You could set up topology rules and use the topology editing tools to correct the hand drawn polygons so they don't overlap or have gaps.


checked out the topology and a question therefore: isn't it possible to make a topology between different feature class datasets?
Do I have to put all feature classes together in ONE Featuer class dataset, between which I want to use topology rules?

attachment:
so I want to build a topology between feature class "Gruenlandflaechen" (grasslands) and feature class "Wald" (wood) which is in another feature dataset "Feldinfrastruktur"
[ATTACH=CONFIG]18668[/ATTACH]

an if it's just possible to get topology working by using one feature dataset: what's the best and fastest way to put all feature classes into one dataset?

best regards
andreas
0 Kudos
MarkBoucher
Regular Contributor II
A topology only works on the feature classes in the feature dataset it is in. It is basically a database function that works in the database it is in.

Yes, you can set up the topology to work on just one feature class in the feature dataset. For example, you can say you want there to be no gaps and no overlaps between the features in the feature class.

My understanding is that if you want to include more than one feature class in the topology, they MUST to be in the same dataset as the topology.

A fast way to get all the feature classes in one dataset is to use ArcCatalog. Right click on the feature dataset, choose import, choose Feature Class (multiple). See image:

[ATTACH=CONFIG]18670[/ATTACH]
0 Kudos