Creating Multi-Part Polygons that touch internally using ArcGIS Desktop?Converting adjacent singlepart...
Is it improper etiquette to ask your opponent what his/her rating is before the game?
How to indicate a cut out for a product window
What was the exact wording from Ivanhoe of this advice on how to free yourself from slavery?
Are paving bricks differently sized for sand bedding vs mortar bedding?
What should you do if you miss a job interview (deliberately)?
Has any country ever had 2 former presidents in jail simultaneously?
Removing files under particular conditions (number of files, file age)
Multiplicative persistence
Electoral considerations aside, what are potential benefits, for the US, of policy changes proposed by the tweet recognizing Golan annexation?
C++ debug/print custom type with GDB : the case of nlohmann json library
When were female captains banned from Starfleet?
Should I outline or discovery write my stories?
What does chmod -u do?
How to explain what's wrong with this application of the chain rule?
Biological Blimps: Propulsion
How do you respond to a colleague from another team when they're wrongly expecting that you'll help them?
Must Legal Documents Be Siged In Standard Pen Colors?
What if a revenant (monster) gains fire resistance?
Problem with TransformedDistribution
Which one is correct as adjective “protruding” or “protruded”?
Delivering sarcasm
Why is so much work done on numerical verification of the Riemann Hypothesis?
It grows, but water kills it
A social experiment. What is the worst that can happen?
Creating Multi-Part Polygons that touch internally using ArcGIS Desktop?
Converting adjacent singlepart polygons to multipart?Merging parcels but keeping Geometry separate in ArcGIS Desktop?Merge without dissolve in ArcGIS for Desktop?Finding parcel polygon features with frontage on multiple streets using ArcGIS Desktop?Merging parcels but keeping Geometry separate in ArcGIS Desktop?Splitting multi-part polygon into single polygons using ArcGIS Desktop?How to merge single polygons to multi part polygons by maximum distances?Unsplit/Dissolve multiple touching lines in Stream Network using ArcGIS Desktop?Merging lines (that might cross) at common endpoints without multi-part features in the resultDelineating boundary around many small polygons to reduce number of polygons but retain relative coverage using ArcGIS Desktop?Merging or dissolving points while maintaining attributes using ArcGIS Desktop?Dissolving feature/field by interval using ArcGIS Desktop?Is there a “Merge Parts” tool in QGIS?
I have a set of parcels as illustrated in the image below. There are currently no multi-part features in dataset. What I would like to do is to merge (not the right word) all of the parcels with same address, say 421 for example. I want to have these three polygons as one multi-part polygon, that still has the same geometry, as in it doesn't dissolve the lines.
When I have tried this thus far, the lines dissolve resulting in only the boundary being preserved.
I feel like there is a super easy was to do this, but I can't find it. I have full access to ArcGIS Advanced and use it to manage the topology of this dataset.
arcgis-desktop polygon multipart parcel adjacency
add a comment |
I have a set of parcels as illustrated in the image below. There are currently no multi-part features in dataset. What I would like to do is to merge (not the right word) all of the parcels with same address, say 421 for example. I want to have these three polygons as one multi-part polygon, that still has the same geometry, as in it doesn't dissolve the lines.
When I have tried this thus far, the lines dissolve resulting in only the boundary being preserved.
I feel like there is a super easy was to do this, but I can't find it. I have full access to ArcGIS Advanced and use it to manage the topology of this dataset.
arcgis-desktop polygon multipart parcel adjacency
1
I'm thinking that maybe managing a topology with lines and polygons can help fix this. Any thoughts?
– Cody Brown
Jun 8 '13 at 19:36
add a comment |
I have a set of parcels as illustrated in the image below. There are currently no multi-part features in dataset. What I would like to do is to merge (not the right word) all of the parcels with same address, say 421 for example. I want to have these three polygons as one multi-part polygon, that still has the same geometry, as in it doesn't dissolve the lines.
When I have tried this thus far, the lines dissolve resulting in only the boundary being preserved.
I feel like there is a super easy was to do this, but I can't find it. I have full access to ArcGIS Advanced and use it to manage the topology of this dataset.
arcgis-desktop polygon multipart parcel adjacency
I have a set of parcels as illustrated in the image below. There are currently no multi-part features in dataset. What I would like to do is to merge (not the right word) all of the parcels with same address, say 421 for example. I want to have these three polygons as one multi-part polygon, that still has the same geometry, as in it doesn't dissolve the lines.
When I have tried this thus far, the lines dissolve resulting in only the boundary being preserved.
I feel like there is a super easy was to do this, but I can't find it. I have full access to ArcGIS Advanced and use it to manage the topology of this dataset.
arcgis-desktop polygon multipart parcel adjacency
arcgis-desktop polygon multipart parcel adjacency
edited 4 mins ago
PolyGeo♦
53.7k1781244
53.7k1781244
asked Jun 7 '13 at 20:08
Cody BrownCody Brown
2,44033366
2,44033366
1
I'm thinking that maybe managing a topology with lines and polygons can help fix this. Any thoughts?
– Cody Brown
Jun 8 '13 at 19:36
add a comment |
1
I'm thinking that maybe managing a topology with lines and polygons can help fix this. Any thoughts?
– Cody Brown
Jun 8 '13 at 19:36
1
1
I'm thinking that maybe managing a topology with lines and polygons can help fix this. Any thoughts?
– Cody Brown
Jun 8 '13 at 19:36
I'm thinking that maybe managing a topology with lines and polygons can help fix this. Any thoughts?
– Cody Brown
Jun 8 '13 at 19:36
add a comment |
1 Answer
1
active
oldest
votes
I think this is an ideal candidate for an ArcGIS Idea (if there is not already one).
The Online Help for Multipart Polygons says (with my bolding):
Keep in mind that parts in a multipart polygon are spatially
separated. They can touch each other at vertices, but they cannot
share edges or overlap. When you are sketching a multipart polygon,
any parts that share an edge will be merged into a single part when
you finish the sketch. In addition, any overlap among parts will be
removed, leaving a hole in the polygon.
So it seems like you are hitting a limitation in the design of multipart polygon features within shapefiles and geodatabase feature classes.
Why that limitation is there I do not know because your use case seems like a valid one.
1
I agree. Dang ESRI and it's limitations. Although I can't find a QGIS solution either. I'll post the link on here when I make an ArcGIS Idea on this.
– Cody Brown
Jun 8 '13 at 19:35
3
It's not an ESRI limitation, it's per the OGC Simple Feature Access Standard. *"boundaries of any 2 Polygons that are elements of a MultiPolygon may not 'cross' and may touch at only a finite number of Points," i.e., parts of a multipart polygon can't share an edge. * quote from GeoNet topic
– user2856
Sep 20 '15 at 10:23
1
However, such geometries can be expressed as an OGC simple feature by using GeometryCollectionGEOMETRYCOLLECTION ( POLYGON (( 423 357, 423 358, 424 358, 424 357, 423 357 )), POLYGON (( 422 357, 422 358, 423 358, 423 357, 422 357 )), POLYGON (( 424 357, 424 358, 425 358, 425 357, 424 357 )))
They may not be supported in ArcGIS, though.
– user30184
Sep 20 '15 at 12:54
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "79"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f63042%2fcreating-multi-part-polygons-that-touch-internally-using-arcgis-desktop%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think this is an ideal candidate for an ArcGIS Idea (if there is not already one).
The Online Help for Multipart Polygons says (with my bolding):
Keep in mind that parts in a multipart polygon are spatially
separated. They can touch each other at vertices, but they cannot
share edges or overlap. When you are sketching a multipart polygon,
any parts that share an edge will be merged into a single part when
you finish the sketch. In addition, any overlap among parts will be
removed, leaving a hole in the polygon.
So it seems like you are hitting a limitation in the design of multipart polygon features within shapefiles and geodatabase feature classes.
Why that limitation is there I do not know because your use case seems like a valid one.
1
I agree. Dang ESRI and it's limitations. Although I can't find a QGIS solution either. I'll post the link on here when I make an ArcGIS Idea on this.
– Cody Brown
Jun 8 '13 at 19:35
3
It's not an ESRI limitation, it's per the OGC Simple Feature Access Standard. *"boundaries of any 2 Polygons that are elements of a MultiPolygon may not 'cross' and may touch at only a finite number of Points," i.e., parts of a multipart polygon can't share an edge. * quote from GeoNet topic
– user2856
Sep 20 '15 at 10:23
1
However, such geometries can be expressed as an OGC simple feature by using GeometryCollectionGEOMETRYCOLLECTION ( POLYGON (( 423 357, 423 358, 424 358, 424 357, 423 357 )), POLYGON (( 422 357, 422 358, 423 358, 423 357, 422 357 )), POLYGON (( 424 357, 424 358, 425 358, 425 357, 424 357 )))
They may not be supported in ArcGIS, though.
– user30184
Sep 20 '15 at 12:54
add a comment |
I think this is an ideal candidate for an ArcGIS Idea (if there is not already one).
The Online Help for Multipart Polygons says (with my bolding):
Keep in mind that parts in a multipart polygon are spatially
separated. They can touch each other at vertices, but they cannot
share edges or overlap. When you are sketching a multipart polygon,
any parts that share an edge will be merged into a single part when
you finish the sketch. In addition, any overlap among parts will be
removed, leaving a hole in the polygon.
So it seems like you are hitting a limitation in the design of multipart polygon features within shapefiles and geodatabase feature classes.
Why that limitation is there I do not know because your use case seems like a valid one.
1
I agree. Dang ESRI and it's limitations. Although I can't find a QGIS solution either. I'll post the link on here when I make an ArcGIS Idea on this.
– Cody Brown
Jun 8 '13 at 19:35
3
It's not an ESRI limitation, it's per the OGC Simple Feature Access Standard. *"boundaries of any 2 Polygons that are elements of a MultiPolygon may not 'cross' and may touch at only a finite number of Points," i.e., parts of a multipart polygon can't share an edge. * quote from GeoNet topic
– user2856
Sep 20 '15 at 10:23
1
However, such geometries can be expressed as an OGC simple feature by using GeometryCollectionGEOMETRYCOLLECTION ( POLYGON (( 423 357, 423 358, 424 358, 424 357, 423 357 )), POLYGON (( 422 357, 422 358, 423 358, 423 357, 422 357 )), POLYGON (( 424 357, 424 358, 425 358, 425 357, 424 357 )))
They may not be supported in ArcGIS, though.
– user30184
Sep 20 '15 at 12:54
add a comment |
I think this is an ideal candidate for an ArcGIS Idea (if there is not already one).
The Online Help for Multipart Polygons says (with my bolding):
Keep in mind that parts in a multipart polygon are spatially
separated. They can touch each other at vertices, but they cannot
share edges or overlap. When you are sketching a multipart polygon,
any parts that share an edge will be merged into a single part when
you finish the sketch. In addition, any overlap among parts will be
removed, leaving a hole in the polygon.
So it seems like you are hitting a limitation in the design of multipart polygon features within shapefiles and geodatabase feature classes.
Why that limitation is there I do not know because your use case seems like a valid one.
I think this is an ideal candidate for an ArcGIS Idea (if there is not already one).
The Online Help for Multipart Polygons says (with my bolding):
Keep in mind that parts in a multipart polygon are spatially
separated. They can touch each other at vertices, but they cannot
share edges or overlap. When you are sketching a multipart polygon,
any parts that share an edge will be merged into a single part when
you finish the sketch. In addition, any overlap among parts will be
removed, leaving a hole in the polygon.
So it seems like you are hitting a limitation in the design of multipart polygon features within shapefiles and geodatabase feature classes.
Why that limitation is there I do not know because your use case seems like a valid one.
edited Sep 19 '15 at 23:05
answered Jun 8 '13 at 8:25
PolyGeo♦PolyGeo
53.7k1781244
53.7k1781244
1
I agree. Dang ESRI and it's limitations. Although I can't find a QGIS solution either. I'll post the link on here when I make an ArcGIS Idea on this.
– Cody Brown
Jun 8 '13 at 19:35
3
It's not an ESRI limitation, it's per the OGC Simple Feature Access Standard. *"boundaries of any 2 Polygons that are elements of a MultiPolygon may not 'cross' and may touch at only a finite number of Points," i.e., parts of a multipart polygon can't share an edge. * quote from GeoNet topic
– user2856
Sep 20 '15 at 10:23
1
However, such geometries can be expressed as an OGC simple feature by using GeometryCollectionGEOMETRYCOLLECTION ( POLYGON (( 423 357, 423 358, 424 358, 424 357, 423 357 )), POLYGON (( 422 357, 422 358, 423 358, 423 357, 422 357 )), POLYGON (( 424 357, 424 358, 425 358, 425 357, 424 357 )))
They may not be supported in ArcGIS, though.
– user30184
Sep 20 '15 at 12:54
add a comment |
1
I agree. Dang ESRI and it's limitations. Although I can't find a QGIS solution either. I'll post the link on here when I make an ArcGIS Idea on this.
– Cody Brown
Jun 8 '13 at 19:35
3
It's not an ESRI limitation, it's per the OGC Simple Feature Access Standard. *"boundaries of any 2 Polygons that are elements of a MultiPolygon may not 'cross' and may touch at only a finite number of Points," i.e., parts of a multipart polygon can't share an edge. * quote from GeoNet topic
– user2856
Sep 20 '15 at 10:23
1
However, such geometries can be expressed as an OGC simple feature by using GeometryCollectionGEOMETRYCOLLECTION ( POLYGON (( 423 357, 423 358, 424 358, 424 357, 423 357 )), POLYGON (( 422 357, 422 358, 423 358, 423 357, 422 357 )), POLYGON (( 424 357, 424 358, 425 358, 425 357, 424 357 )))
They may not be supported in ArcGIS, though.
– user30184
Sep 20 '15 at 12:54
1
1
I agree. Dang ESRI and it's limitations. Although I can't find a QGIS solution either. I'll post the link on here when I make an ArcGIS Idea on this.
– Cody Brown
Jun 8 '13 at 19:35
I agree. Dang ESRI and it's limitations. Although I can't find a QGIS solution either. I'll post the link on here when I make an ArcGIS Idea on this.
– Cody Brown
Jun 8 '13 at 19:35
3
3
It's not an ESRI limitation, it's per the OGC Simple Feature Access Standard. *"boundaries of any 2 Polygons that are elements of a MultiPolygon may not 'cross' and may touch at only a finite number of Points," i.e., parts of a multipart polygon can't share an edge. * quote from GeoNet topic
– user2856
Sep 20 '15 at 10:23
It's not an ESRI limitation, it's per the OGC Simple Feature Access Standard. *"boundaries of any 2 Polygons that are elements of a MultiPolygon may not 'cross' and may touch at only a finite number of Points," i.e., parts of a multipart polygon can't share an edge. * quote from GeoNet topic
– user2856
Sep 20 '15 at 10:23
1
1
However, such geometries can be expressed as an OGC simple feature by using GeometryCollection
GEOMETRYCOLLECTION ( POLYGON (( 423 357, 423 358, 424 358, 424 357, 423 357 )), POLYGON (( 422 357, 422 358, 423 358, 423 357, 422 357 )), POLYGON (( 424 357, 424 358, 425 358, 425 357, 424 357 )))
They may not be supported in ArcGIS, though.– user30184
Sep 20 '15 at 12:54
However, such geometries can be expressed as an OGC simple feature by using GeometryCollection
GEOMETRYCOLLECTION ( POLYGON (( 423 357, 423 358, 424 358, 424 357, 423 357 )), POLYGON (( 422 357, 422 358, 423 358, 423 357, 422 357 )), POLYGON (( 424 357, 424 358, 425 358, 425 357, 424 357 )))
They may not be supported in ArcGIS, though.– user30184
Sep 20 '15 at 12:54
add a comment |
Thanks for contributing an answer to Geographic Information Systems Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f63042%2fcreating-multi-part-polygons-that-touch-internally-using-arcgis-desktop%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I'm thinking that maybe managing a topology with lines and polygons can help fix this. Any thoughts?
– Cody Brown
Jun 8 '13 at 19:36