Split By Attributes tool not recognizing Feature Dataset as Target Workspace?
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
edited Dec 18 '18 at 23:14
PolyGeo♦
53.2k1779238
asked Dec 18 '18 at 23:03
Stu Smith
1,9011330
add a comment |
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
edited Dec 18 '18 at 23:14
PolyGeo♦
53.2k1779238
asked Dec 18 '18 at 23:03
Stu Smith
1,9011330
add a comment |
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
edited Dec 18 '18 at 23:14
PolyGeo♦
53.2k1779238
asked Dec 18 '18 at 23:03
Stu Smith
1,9011330
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 Dec 18 '18 at 23:14
PolyGeo♦
53.2k1779238
asked Dec 18 '18 at 23:03
Stu Smith
1,9011330
edited Dec 18 '18 at 23:14
PolyGeo♦
53.2k1779238
asked Dec 18 '18 at 23:03
Stu Smith
1,9011330
edited Dec 18 '18 at 23:14
PolyGeo♦
53.2k1779238
edited Dec 18 '18 at 23:14
PolyGeo♦
53.2k1779238
edited Dec 18 '18 at 23:14
PolyGeo♦
53.2k1779238
53.2k1779238
asked Dec 18 '18 at 23:03
Stu Smith
1,9011330
asked Dec 18 '18 at 23:03
Stu Smith
1,9011330
asked Dec 18 '18 at 23:03
Stu Smith
1,9011330
1,9011330
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The provided/accepted answer explains the behavior. This answer provides a possible workaround.
As Split by Attributes is a Script tool, you can hack it a little bit. (I don't have 10.5 to test if this change will 'just work', but I know the hack will get you the behavior you want: to set the output in the tool to a feature dataset).
- With ArcToolbox or the Catalog Window toolbox, find Split by Attributes, right click and Copy
- Create a new toolbox in your working directory, right click and Paste the tool in.
- Right click the copied tool and select Properties
- Select the Target Workspace. The Data Type will be set to Workspace. In the drop down change this to Workspace or Feature Dataset
- Click ok to save changes and run the tool
If the tool doesn't "work", that means the code inside doesn't allow the writing of output to the feature dataset. Thus you could ping Esri to enhance the tool. If it does work you could still ping Esri and call the problem a bug (oversight that the wrong data type was selected in the tool design).
answered Dec 19 '18 at 19:30
KHibma
9,94411738
Hot Damn, it worked! The output now goes to a feature dataset. You, Sir, have mad skills! ESRI desperately needs to hire you...
– Stu Smith
Dec 19 '18 at 21:23
@StuSmith Open his profile for a pleasant surprise! Note received and will be looked into, cheers
– scw
Dec 20 '18 at 2:19
@scw I may have already pinged a certain maple syrup loving member of the GP team about it. ;)
– KHibma
Dec 20 '18 at 2:53
@scw Indeed, that is a pleasant surprise. Do I see a Far North Employee of the Day Award in the offing? Now, what about those orphan file locks?
– Stu Smith
Dec 20 '18 at 6:51
add a comment |
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.
answered Dec 18 '18 at 23:13
PolyGeo♦
53.2k1779238
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
Dec 18 '18 at 23:18
2
@MichaelStimson it came in version 10.5.
– Hornbydd
Dec 18 '18 at 23:38
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
Dec 18 '18 at 23:41
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
Dec 18 '18 at 23:58
1
@StuSmith see the answer I provided which expands on MichaelStimson's idea as a way to get the tool to a state you want.
– KHibma
Dec 19 '18 at 19:31
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
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The provided/accepted answer explains the behavior. This answer provides a possible workaround.
As Split by Attributes is a Script tool, you can hack it a little bit. (I don't have 10.5 to test if this change will 'just work', but I know the hack will get you the behavior you want: to set the output in the tool to a feature dataset).
- With ArcToolbox or the Catalog Window toolbox, find Split by Attributes, right click and Copy
- Create a new toolbox in your working directory, right click and Paste the tool in.
- Right click the copied tool and select Properties
- Select the Target Workspace. The Data Type will be set to Workspace. In the drop down change this to Workspace or Feature Dataset
- Click ok to save changes and run the tool
If the tool doesn't "work", that means the code inside doesn't allow the writing of output to the feature dataset. Thus you could ping Esri to enhance the tool. If it does work you could still ping Esri and call the problem a bug (oversight that the wrong data type was selected in the tool design).
answered Dec 19 '18 at 19:30
KHibma
9,94411738
Hot Damn, it worked! The output now goes to a feature dataset. You, Sir, have mad skills! ESRI desperately needs to hire you...
– Stu Smith
Dec 19 '18 at 21:23
@StuSmith Open his profile for a pleasant surprise! Note received and will be looked into, cheers
– scw
Dec 20 '18 at 2:19
@scw I may have already pinged a certain maple syrup loving member of the GP team about it. ;)
– KHibma
Dec 20 '18 at 2:53
@scw Indeed, that is a pleasant surprise. Do I see a Far North Employee of the Day Award in the offing? Now, what about those orphan file locks?
– Stu Smith
Dec 20 '18 at 6:51
add a comment |
The provided/accepted answer explains the behavior. This answer provides a possible workaround.
As Split by Attributes is a Script tool, you can hack it a little bit. (I don't have 10.5 to test if this change will 'just work', but I know the hack will get you the behavior you want: to set the output in the tool to a feature dataset).
- With ArcToolbox or the Catalog Window toolbox, find Split by Attributes, right click and Copy
- Create a new toolbox in your working directory, right click and Paste the tool in.
- Right click the copied tool and select Properties
- Select the Target Workspace. The Data Type will be set to Workspace. In the drop down change this to Workspace or Feature Dataset
- Click ok to save changes and run the tool
If the tool doesn't "work", that means the code inside doesn't allow the writing of output to the feature dataset. Thus you could ping Esri to enhance the tool. If it does work you could still ping Esri and call the problem a bug (oversight that the wrong data type was selected in the tool design).
answered Dec 19 '18 at 19:30
KHibma
9,94411738
Hot Damn, it worked! The output now goes to a feature dataset. You, Sir, have mad skills! ESRI desperately needs to hire you...
– Stu Smith
Dec 19 '18 at 21:23
@StuSmith Open his profile for a pleasant surprise! Note received and will be looked into, cheers
– scw
Dec 20 '18 at 2:19
@scw I may have already pinged a certain maple syrup loving member of the GP team about it. ;)
– KHibma
Dec 20 '18 at 2:53
@scw Indeed, that is a pleasant surprise. Do I see a Far North Employee of the Day Award in the offing? Now, what about those orphan file locks?
– Stu Smith
Dec 20 '18 at 6:51
add a comment |
The provided/accepted answer explains the behavior. This answer provides a possible workaround.
As Split by Attributes is a Script tool, you can hack it a little bit. (I don't have 10.5 to test if this change will 'just work', but I know the hack will get you the behavior you want: to set the output in the tool to a feature dataset).
- With ArcToolbox or the Catalog Window toolbox, find Split by Attributes, right click and Copy
- Create a new toolbox in your working directory, right click and Paste the tool in.
- Right click the copied tool and select Properties
- Select the Target Workspace. The Data Type will be set to Workspace. In the drop down change this to Workspace or Feature Dataset
- Click ok to save changes and run the tool
If the tool doesn't "work", that means the code inside doesn't allow the writing of output to the feature dataset. Thus you could ping Esri to enhance the tool. If it does work you could still ping Esri and call the problem a bug (oversight that the wrong data type was selected in the tool design).
answered Dec 19 '18 at 19:30
KHibma
9,94411738
The provided/accepted answer explains the behavior. This answer provides a possible workaround.
As Split by Attributes is a Script tool, you can hack it a little bit. (I don't have 10.5 to test if this change will 'just work', but I know the hack will get you the behavior you want: to set the output in the tool to a feature dataset).
- With ArcToolbox or the Catalog Window toolbox, find Split by Attributes, right click and Copy
- Create a new toolbox in your working directory, right click and Paste the tool in.
- Right click the copied tool and select Properties
- Select the Target Workspace. The Data Type will be set to Workspace. In the drop down change this to Workspace or Feature Dataset
- Click ok to save changes and run the tool
If the tool doesn't "work", that means the code inside doesn't allow the writing of output to the feature dataset. Thus you could ping Esri to enhance the tool. If it does work you could still ping Esri and call the problem a bug (oversight that the wrong data type was selected in the tool design).
answered Dec 19 '18 at 19:30
KHibma
9,94411738
answered Dec 19 '18 at 19:30
KHibma
9,94411738
answered Dec 19 '18 at 19:30
KHibma
9,94411738
answered Dec 19 '18 at 19:30
KHibma
9,94411738
9,94411738
Hot Damn, it worked! The output now goes to a feature dataset. You, Sir, have mad skills! ESRI desperately needs to hire you...
– Stu Smith
Dec 19 '18 at 21:23
@StuSmith Open his profile for a pleasant surprise! Note received and will be looked into, cheers
– scw
Dec 20 '18 at 2:19
@scw I may have already pinged a certain maple syrup loving member of the GP team about it. ;)
– KHibma
Dec 20 '18 at 2:53
@scw Indeed, that is a pleasant surprise. Do I see a Far North Employee of the Day Award in the offing? Now, what about those orphan file locks?
– Stu Smith
Dec 20 '18 at 6:51
add a comment |
Hot Damn, it worked! The output now goes to a feature dataset. You, Sir, have mad skills! ESRI desperately needs to hire you...
– Stu Smith
Dec 19 '18 at 21:23
@StuSmith Open his profile for a pleasant surprise! Note received and will be looked into, cheers
– scw
Dec 20 '18 at 2:19
@scw I may have already pinged a certain maple syrup loving member of the GP team about it. ;)
– KHibma
Dec 20 '18 at 2:53
@scw Indeed, that is a pleasant surprise. Do I see a Far North Employee of the Day Award in the offing? Now, what about those orphan file locks?
– Stu Smith
Dec 20 '18 at 6:51
Hot Damn, it worked! The output now goes to a feature dataset. You, Sir, have mad skills! ESRI desperately needs to hire you...
– Stu Smith
Dec 19 '18 at 21:23
Hot Damn, it worked! The output now goes to a feature dataset. You, Sir, have mad skills! ESRI desperately needs to hire you...
– Stu Smith
Dec 19 '18 at 21:23
@StuSmith Open his profile for a pleasant surprise! Note received and will be looked into, cheers
– scw
Dec 20 '18 at 2:19
@StuSmith Open his profile for a pleasant surprise! Note received and will be looked into, cheers
– scw
Dec 20 '18 at 2:19
@scw I may have already pinged a certain maple syrup loving member of the GP team about it. ;)
– KHibma
Dec 20 '18 at 2:53
@scw I may have already pinged a certain maple syrup loving member of the GP team about it. ;)
– KHibma
Dec 20 '18 at 2:53
@scw Indeed, that is a pleasant surprise. Do I see a Far North Employee of the Day Award in the offing? Now, what about those orphan file locks?
– Stu Smith
Dec 20 '18 at 6:51
@scw Indeed, that is a pleasant surprise. Do I see a Far North Employee of the Day Award in the offing? Now, what about those orphan file locks?
– Stu Smith
Dec 20 '18 at 6:51
add a comment |
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.
answered Dec 18 '18 at 23:13
PolyGeo♦
53.2k1779238
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
Dec 18 '18 at 23:18
2
@MichaelStimson it came in version 10.5.
– Hornbydd
Dec 18 '18 at 23:38
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
Dec 18 '18 at 23:41
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
Dec 18 '18 at 23:58
1
@StuSmith see the answer I provided which expands on MichaelStimson's idea as a way to get the tool to a state you want.
– KHibma
Dec 19 '18 at 19:31
add a comment |
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.
answered Dec 18 '18 at 23:13
PolyGeo♦
53.2k1779238
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
Dec 18 '18 at 23:18
2
@MichaelStimson it came in version 10.5.
– Hornbydd
Dec 18 '18 at 23:38
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
Dec 18 '18 at 23:41
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
Dec 18 '18 at 23:58
1
@StuSmith see the answer I provided which expands on MichaelStimson's idea as a way to get the tool to a state you want.
– KHibma
Dec 19 '18 at 19:31
add a comment |
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.
answered Dec 18 '18 at 23:13
PolyGeo♦
53.2k1779238
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.
answered Dec 18 '18 at 23:13
PolyGeo♦
53.2k1779238
edited Dec 19 '18 at 0:45
answered Dec 18 '18 at 23:13
PolyGeo♦
53.2k1779238
answered Dec 18 '18 at 23:13
PolyGeo♦
53.2k1779238
answered Dec 18 '18 at 23:13
PolyGeo♦
53.2k1779238
53.2k1779238
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
Dec 18 '18 at 23:18
2
@MichaelStimson it came in version 10.5.
– Hornbydd
Dec 18 '18 at 23:38
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
Dec 18 '18 at 23:41
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
Dec 18 '18 at 23:58
1
@StuSmith see the answer I provided which expands on MichaelStimson's idea as a way to get the tool to a state you want.
– KHibma
Dec 19 '18 at 19:31
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
Dec 18 '18 at 23:18
2
@MichaelStimson it came in version 10.5.
– Hornbydd
Dec 18 '18 at 23:38
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
Dec 18 '18 at 23:41
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
Dec 18 '18 at 23:58
1
@StuSmith see the answer I provided which expands on MichaelStimson's idea as a way to get the tool to a state you want.
– KHibma
Dec 19 '18 at 19:31
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
Dec 18 '18 at 23:18
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
Dec 18 '18 at 23:18
2
2
@MichaelStimson it came in version 10.5.
– Hornbydd
Dec 18 '18 at 23:38
@MichaelStimson it came in version 10.5.
– Hornbydd
Dec 18 '18 at 23:38
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
Dec 18 '18 at 23:41
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
Dec 18 '18 at 23:41
1
1
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
Dec 18 '18 at 23:58
@MichaelStimson Your command line suggestion works, so as you suggest, it appears to be a tool dialog oversight. Hello, ESRI???
– Stu Smith
Dec 18 '18 at 23:58
1
1
@StuSmith see the answer I provided which expands on MichaelStimson's idea as a way to get the tool to a state you want.
– KHibma
Dec 19 '18 at 19:31
@StuSmith see the answer I provided which expands on MichaelStimson's idea as a way to get the tool to a state you want.
– KHibma
Dec 19 '18 at 19:31
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
