-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tool naming #84
Comments
Ah, that's unfortunate. I didn't know the name had dashes. I can see how that would cause problems. I am pretty sure changing those to underscores would be ok. Have you tried that with your own copy? |
I would suggest just removing the dash, which got me past one hurdle... Since underscores are used to differentiate between the toolbox alias and tool name, when calling it, I think using them would be especially problematic. |
This is still causing me headaches - you can't import the toolbox for use in other scripts if there are dashes in the tool names |
Whoops, sorry Ryan. Just posted a new release with all dashes removed. |
Thanks - that fixed it! |
@gbvnturn, @tfelger
A while ago I wrote a series of tools (https://github.com/rcrow/MapExtractor_SchemaConverter) that use the GeMS toolbox - they use the importtoolbox method. Currently we are getting issues (somewhat inconsistently...) like the one explained here: https://support.esri.com/en/technical-article/000014511. Previously, I had issues with this because the GeMS toolbox alias was undefined or there were special characters in the names of the tools. Although our issues are complex..., part of our issues seems related to the use of dashes in the names of the new FGDC metadata tools. Would it create issues to remove those dashes?
This webpage is not completely related but perhaps helpful: https://desktop.arcgis.com/en/arcmap/latest/analyze/managing-tools-and-toolboxes/renaming-a-toolbox.htm
I am curious if anyone else imports the GeMS toolbox for use in other scripts and if that works for them.
The text was updated successfully, but these errors were encountered: