Performing Split By Attributes on OBJECTID?
up vote
2
down vote
favorite
Using ArcGIS Desktop, 10.5.1, I need to "explode" a singlepart polygon FGDB Feature Class into separate FCs.
For example, if the input FC contains 3 polygons, the output will be 3 separate FCs, each containing a single polygon.
I am using the Split By Attributes tool.
How do I split by the input FC's Objectid field?
When I open the tool, it does not include the Objectid as an allowed Split Field:
arcgis-desktop split-by-attribute
edited 4 hours ago
PolyGeo♦
53.1k1779238
asked 7 hours ago
Stu Smith
1,8891330
add a comment |
up vote
2
down vote
favorite
Using ArcGIS Desktop, 10.5.1, I need to "explode" a singlepart polygon FGDB Feature Class into separate FCs.
For example, if the input FC contains 3 polygons, the output will be 3 separate FCs, each containing a single polygon.
I am using the Split By Attributes tool.
How do I split by the input FC's Objectid field?
When I open the tool, it does not include the Objectid as an allowed Split Field:
arcgis-desktop split-by-attribute
edited 4 hours ago
PolyGeo♦
53.1k1779238
asked 7 hours ago
Stu Smith
1,8891330
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Using ArcGIS Desktop, 10.5.1, I need to "explode" a singlepart polygon FGDB Feature Class into separate FCs.
For example, if the input FC contains 3 polygons, the output will be 3 separate FCs, each containing a single polygon.
I am using the Split By Attributes tool.
How do I split by the input FC's Objectid field?
When I open the tool, it does not include the Objectid as an allowed Split Field:
arcgis-desktop split-by-attribute
edited 4 hours ago
PolyGeo♦
53.1k1779238
asked 7 hours ago
Stu Smith
1,8891330
Using ArcGIS Desktop, 10.5.1, I need to "explode" a singlepart polygon FGDB Feature Class into separate FCs.
For example, if the input FC contains 3 polygons, the output will be 3 separate FCs, each containing a single polygon.
I am using the Split By Attributes tool.
How do I split by the input FC's Objectid field?
When I open the tool, it does not include the Objectid as an allowed Split Field:
arcgis-desktop split-by-attribute
arcgis-desktop split-by-attribute
edited 4 hours ago
PolyGeo♦
53.1k1779238
asked 7 hours ago
Stu Smith
1,8891330
edited 4 hours ago
PolyGeo♦
53.1k1779238
asked 7 hours ago
Stu Smith
1,8891330
edited 4 hours ago
PolyGeo♦
53.1k1779238
edited 4 hours ago
PolyGeo♦
53.1k1779238
edited 4 hours ago
PolyGeo♦
53.1k1779238
53.1k1779238
asked 7 hours ago
Stu Smith
1,8891330
asked 7 hours ago
Stu Smith
1,8891330
asked 7 hours ago
Stu Smith
1,8891330
1,8891330
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
2
down vote
accepted
One solution would be to create a new field named ID or something similar. Then Calculate Field and set it equal to OBJECTID, which does show up in the field calculator. Then you can use the new ID field as the Split Field in the Split By Attributes tool.
answered 7 hours ago
lambertj
1,8501523
This works! FWIW, I find it odd that OBJECTID isn't available "out of the box"...
– Stu Smith
3 hours ago
Yeah, me too. I've run into this same problem for a few other tools too. Creating a second ID column always seems to do the trick.
– lambertj
3 hours ago
add a comment |
up vote
1
down vote
Create a new field and populate with your OBJECTID values, then split by that field
answered 7 hours ago
Maksim
6,24621340
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
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%2f306444%2fperforming-split-by-attributes-on-objectid%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
One solution would be to create a new field named ID or something similar. Then Calculate Field and set it equal to OBJECTID, which does show up in the field calculator. Then you can use the new ID field as the Split Field in the Split By Attributes tool.
answered 7 hours ago
lambertj
1,8501523
This works! FWIW, I find it odd that OBJECTID isn't available "out of the box"...
– Stu Smith
3 hours ago
Yeah, me too. I've run into this same problem for a few other tools too. Creating a second ID column always seems to do the trick.
– lambertj
3 hours ago
add a comment |
up vote
2
down vote
accepted
One solution would be to create a new field named ID or something similar. Then Calculate Field and set it equal to OBJECTID, which does show up in the field calculator. Then you can use the new ID field as the Split Field in the Split By Attributes tool.
answered 7 hours ago
lambertj
1,8501523
This works! FWIW, I find it odd that OBJECTID isn't available "out of the box"...
– Stu Smith
3 hours ago
Yeah, me too. I've run into this same problem for a few other tools too. Creating a second ID column always seems to do the trick.
– lambertj
3 hours ago
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
One solution would be to create a new field named ID or something similar. Then Calculate Field and set it equal to OBJECTID, which does show up in the field calculator. Then you can use the new ID field as the Split Field in the Split By Attributes tool.
answered 7 hours ago
lambertj
1,8501523
One solution would be to create a new field named ID or something similar. Then Calculate Field and set it equal to OBJECTID, which does show up in the field calculator. Then you can use the new ID field as the Split Field in the Split By Attributes tool.
answered 7 hours ago
lambertj
1,8501523
answered 7 hours ago
lambertj
1,8501523
answered 7 hours ago
lambertj
1,8501523
answered 7 hours ago
lambertj
1,8501523
1,8501523
This works! FWIW, I find it odd that OBJECTID isn't available "out of the box"...
– Stu Smith
3 hours ago
Yeah, me too. I've run into this same problem for a few other tools too. Creating a second ID column always seems to do the trick.
– lambertj
3 hours ago
add a comment |
This works! FWIW, I find it odd that OBJECTID isn't available "out of the box"...
– Stu Smith
3 hours ago
Yeah, me too. I've run into this same problem for a few other tools too. Creating a second ID column always seems to do the trick.
– lambertj
3 hours ago
This works! FWIW, I find it odd that OBJECTID isn't available "out of the box"...
– Stu Smith
3 hours ago
This works! FWIW, I find it odd that OBJECTID isn't available "out of the box"...
– Stu Smith
3 hours ago
Yeah, me too. I've run into this same problem for a few other tools too. Creating a second ID column always seems to do the trick.
– lambertj
3 hours ago
Yeah, me too. I've run into this same problem for a few other tools too. Creating a second ID column always seems to do the trick.
– lambertj
3 hours ago
add a comment |
up vote
1
down vote
Create a new field and populate with your OBJECTID values, then split by that field
answered 7 hours ago
Maksim
6,24621340
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
add a comment |
up vote
1
down vote
Create a new field and populate with your OBJECTID values, then split by that field
answered 7 hours ago
Maksim
6,24621340
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
add a comment |
up vote
1
down vote
up vote
1
down vote
Create a new field and populate with your OBJECTID values, then split by that field
answered 7 hours ago
Maksim
6,24621340
Create a new field and populate with your OBJECTID values, then split by that field
answered 7 hours ago
Maksim
6,24621340
answered 7 hours ago
Maksim
6,24621340
answered 7 hours ago
Maksim
6,24621340
answered 7 hours ago
Maksim
6,24621340
6,24621340
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f306444%2fperforming-split-by-attributes-on-objectid%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
