Split By Attributes tool not recognizing Feature Dataset as Target Workspace?
up vote
2
down vote
favorite
Using ArcGIS Desktop 10.5.1, I have a FGDB that contains a feature dataset. I would like the output from the "Split By Attributes" tool to go inside this feature dataset. However, the tool does not show the existing feature dataset as an available target workspace, as shown here:
How do I send the output feature classes to a feature dataset?
arcgis-desktop workspace feature-dataset split-by-attribute
add a comment |
up vote
2
down vote
favorite
Using ArcGIS Desktop 10.5.1, I have a FGDB that contains a feature dataset. I would like the output from the "Split By Attributes" tool to go inside this feature dataset. However, the tool does not show the existing feature dataset as an available target workspace, as shown here:
How do I send the output feature classes to a feature dataset?
arcgis-desktop workspace feature-dataset split-by-attribute
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Using ArcGIS Desktop 10.5.1, I have a FGDB that contains a feature dataset. I would like the output from the "Split By Attributes" tool to go inside this feature dataset. However, the tool does not show the existing feature dataset as an available target workspace, as shown here:
How do I send the output feature classes to a feature dataset?
arcgis-desktop workspace feature-dataset split-by-attribute
Using ArcGIS Desktop 10.5.1, I have a FGDB that contains a feature dataset. I would like the output from the "Split By Attributes" tool to go inside this feature dataset. However, the tool does not show the existing feature dataset as an available target workspace, as shown here:
How do I send the output feature classes to a feature dataset?
arcgis-desktop workspace feature-dataset split-by-attribute
arcgis-desktop workspace feature-dataset split-by-attribute
edited 3 hours ago
PolyGeo♦
53.1k1779238
53.1k1779238
asked 3 hours ago
Stu Smith
1,8891330
1,8891330
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
It appears that the Split By Attributes tool does not currently support creating its output feature classes in a Feature Dataset.
One way to workaround that software limit would be to use an ArcPy answer to Exporting feature class into multiple feature classes based on field values using ArcGIS Desktop? as starting code to develop one.
Another is the suggestion in a comment by @MichaelStimson:
try running the tool from the python console and just see if it has an
issue with using a feature dataset as a parameter for Target_Workspace
when being run without the dialog (which would prove it's the dialog
that's bad and not the tool)
Alternatively, you could post an ArcGIS Idea to have the tool support a Feature Dataset as the Target Workspace.
2
It appears to be an oversight in the tool dialog; I can't find it in 10.2 so it must be fairly new.. two options: Export to a gdb without a feature dataset then import into your feature dataset or try running the tool from the python console and just see if it has an issue with using a feature dataset as a parameter for Target_Workspace when being run without the dialog (which would prove it's the dialog that's bad and not the tool). I'd try the command line first and if that still has a problem then the two-step process.
– Michael Stimson
3 hours ago
2
@MichaelStimson it came in version 10.5.
– Hornbydd
2 hours ago
Ah @Hornbydd that would explain why I have written a script that does essentially the same thing, I prefer not to re-invent the wheel (unless the wheel is indeed broken). I'm still stuck on 10.2 because of ArcGIS (ArcMap) handling of versioning during an edit session.
– Michael Stimson
2 hours ago
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
2 hours ago
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%2f306472%2fsplit-by-attributes-tool-not-recognizing-feature-dataset-as-target-workspace%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
up vote
3
down vote
accepted
It appears that the Split By Attributes tool does not currently support creating its output feature classes in a Feature Dataset.
One way to workaround that software limit would be to use an ArcPy answer to Exporting feature class into multiple feature classes based on field values using ArcGIS Desktop? as starting code to develop one.
Another is the suggestion in a comment by @MichaelStimson:
try running the tool from the python console and just see if it has an
issue with using a feature dataset as a parameter for Target_Workspace
when being run without the dialog (which would prove it's the dialog
that's bad and not the tool)
Alternatively, you could post an ArcGIS Idea to have the tool support a Feature Dataset as the Target Workspace.
2
It appears to be an oversight in the tool dialog; I can't find it in 10.2 so it must be fairly new.. two options: Export to a gdb without a feature dataset then import into your feature dataset or try running the tool from the python console and just see if it has an issue with using a feature dataset as a parameter for Target_Workspace when being run without the dialog (which would prove it's the dialog that's bad and not the tool). I'd try the command line first and if that still has a problem then the two-step process.
– Michael Stimson
3 hours ago
2
@MichaelStimson it came in version 10.5.
– Hornbydd
2 hours ago
Ah @Hornbydd that would explain why I have written a script that does essentially the same thing, I prefer not to re-invent the wheel (unless the wheel is indeed broken). I'm still stuck on 10.2 because of ArcGIS (ArcMap) handling of versioning during an edit session.
– Michael Stimson
2 hours ago
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
2 hours ago
add a comment |
up vote
3
down vote
accepted
It appears that the Split By Attributes tool does not currently support creating its output feature classes in a Feature Dataset.
One way to workaround that software limit would be to use an ArcPy answer to Exporting feature class into multiple feature classes based on field values using ArcGIS Desktop? as starting code to develop one.
Another is the suggestion in a comment by @MichaelStimson:
try running the tool from the python console and just see if it has an
issue with using a feature dataset as a parameter for Target_Workspace
when being run without the dialog (which would prove it's the dialog
that's bad and not the tool)
Alternatively, you could post an ArcGIS Idea to have the tool support a Feature Dataset as the Target Workspace.
2
It appears to be an oversight in the tool dialog; I can't find it in 10.2 so it must be fairly new.. two options: Export to a gdb without a feature dataset then import into your feature dataset or try running the tool from the python console and just see if it has an issue with using a feature dataset as a parameter for Target_Workspace when being run without the dialog (which would prove it's the dialog that's bad and not the tool). I'd try the command line first and if that still has a problem then the two-step process.
– Michael Stimson
3 hours ago
2
@MichaelStimson it came in version 10.5.
– Hornbydd
2 hours ago
Ah @Hornbydd that would explain why I have written a script that does essentially the same thing, I prefer not to re-invent the wheel (unless the wheel is indeed broken). I'm still stuck on 10.2 because of ArcGIS (ArcMap) handling of versioning during an edit session.
– Michael Stimson
2 hours ago
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
2 hours ago
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
It appears that the Split By Attributes tool does not currently support creating its output feature classes in a Feature Dataset.
One way to workaround that software limit would be to use an ArcPy answer to Exporting feature class into multiple feature classes based on field values using ArcGIS Desktop? as starting code to develop one.
Another is the suggestion in a comment by @MichaelStimson:
try running the tool from the python console and just see if it has an
issue with using a feature dataset as a parameter for Target_Workspace
when being run without the dialog (which would prove it's the dialog
that's bad and not the tool)
Alternatively, you could post an ArcGIS Idea to have the tool support a Feature Dataset as the Target Workspace.
It appears that the Split By Attributes tool does not currently support creating its output feature classes in a Feature Dataset.
One way to workaround that software limit would be to use an ArcPy answer to Exporting feature class into multiple feature classes based on field values using ArcGIS Desktop? as starting code to develop one.
Another is the suggestion in a comment by @MichaelStimson:
try running the tool from the python console and just see if it has an
issue with using a feature dataset as a parameter for Target_Workspace
when being run without the dialog (which would prove it's the dialog
that's bad and not the tool)
Alternatively, you could post an ArcGIS Idea to have the tool support a Feature Dataset as the Target Workspace.
edited 1 hour ago
answered 3 hours ago
PolyGeo♦
53.1k1779238
53.1k1779238
2
It appears to be an oversight in the tool dialog; I can't find it in 10.2 so it must be fairly new.. two options: Export to a gdb without a feature dataset then import into your feature dataset or try running the tool from the python console and just see if it has an issue with using a feature dataset as a parameter for Target_Workspace when being run without the dialog (which would prove it's the dialog that's bad and not the tool). I'd try the command line first and if that still has a problem then the two-step process.
– Michael Stimson
3 hours ago
2
@MichaelStimson it came in version 10.5.
– Hornbydd
2 hours ago
Ah @Hornbydd that would explain why I have written a script that does essentially the same thing, I prefer not to re-invent the wheel (unless the wheel is indeed broken). I'm still stuck on 10.2 because of ArcGIS (ArcMap) handling of versioning during an edit session.
– Michael Stimson
2 hours ago
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
2 hours ago
add a comment |
2
It appears to be an oversight in the tool dialog; I can't find it in 10.2 so it must be fairly new.. two options: Export to a gdb without a feature dataset then import into your feature dataset or try running the tool from the python console and just see if it has an issue with using a feature dataset as a parameter for Target_Workspace when being run without the dialog (which would prove it's the dialog that's bad and not the tool). I'd try the command line first and if that still has a problem then the two-step process.
– Michael Stimson
3 hours ago
2
@MichaelStimson it came in version 10.5.
– Hornbydd
2 hours ago
Ah @Hornbydd that would explain why I have written a script that does essentially the same thing, I prefer not to re-invent the wheel (unless the wheel is indeed broken). I'm still stuck on 10.2 because of ArcGIS (ArcMap) handling of versioning during an edit session.
– Michael Stimson
2 hours ago
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
2 hours ago
2
2
It appears to be an oversight in the tool dialog; I can't find it in 10.2 so it must be fairly new.. two options: Export to a gdb without a feature dataset then import into your feature dataset or try running the tool from the python console and just see if it has an issue with using a feature dataset as a parameter for Target_Workspace when being run without the dialog (which would prove it's the dialog that's bad and not the tool). I'd try the command line first and if that still has a problem then the two-step process.
– Michael Stimson
3 hours ago
It appears to be an oversight in the tool dialog; I can't find it in 10.2 so it must be fairly new.. two options: Export to a gdb without a feature dataset then import into your feature dataset or try running the tool from the python console and just see if it has an issue with using a feature dataset as a parameter for Target_Workspace when being run without the dialog (which would prove it's the dialog that's bad and not the tool). I'd try the command line first and if that still has a problem then the two-step process.
– Michael Stimson
3 hours ago
2
2
@MichaelStimson it came in version 10.5.
– Hornbydd
2 hours ago
@MichaelStimson it came in version 10.5.
– Hornbydd
2 hours ago
Ah @Hornbydd that would explain why I have written a script that does essentially the same thing, I prefer not to re-invent the wheel (unless the wheel is indeed broken). I'm still stuck on 10.2 because of ArcGIS (ArcMap) handling of versioning during an edit session.
– Michael Stimson
2 hours ago
Ah @Hornbydd that would explain why I have written a script that does essentially the same thing, I prefer not to re-invent the wheel (unless the wheel is indeed broken). I'm still stuck on 10.2 because of ArcGIS (ArcMap) handling of versioning during an edit session.
– Michael Stimson
2 hours ago
1
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
2 hours ago
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
2 hours ago
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%2f306472%2fsplit-by-attributes-tool-not-recognizing-feature-dataset-as-target-workspace%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