@GIStack a little bit. If you can expand on what you're attempting I might be able to help some. One method to get a push start with geoprocessing scripts is to do a few things interactively, the "normal" way, then open the Results pane, select one of the processes and "Copy as python snippet" from the r-click context menu.
The command line window is only so-so useful as a tool for script writing, because it uses a different syntax from what's needed for the standalone/toolbox scripts.
The online help docs are pretty useful for looking up what's expected from what you see in the snippets and model saves, and for translating commandline syntax to script syntax and vice versa.
Using the results window - help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//…
reference page for one command (clip) - help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Clip/…
3 hours later…
This is a wicked problem, not substantially different from just "how can we protect our [music, movies, articles, ...]". There is continual tension between the opposing forces of making things useful or making things secure. The more secure it is, the harder to use, the easier to use, the less secure.
I venture the only thing one can really do is a) ensure your content is identifiable as yours (watermarks, traps, unique sign-out id, etc. A suitably motivated (or bored) person will strip out or mask whatever is put in though.), b) have clear license terms of what is and isn't acceptable use, and c) aggressively pursue those who transgress the license terms. All very time consuming and expensive, and the best you can hope to achieve is to stem the tide, never win.
I think any organization that centres it's value in the data they provide, as opposed to services built on using and interpreting the data, is facing a long and never ending battle against dissolution. And it's only going to get harder as computers continually get faster, software more more capable and sophisticated, and more people get more skilled in using them. Look at we can do with these things now, and the vast majority of computer users have not ventured farther than point, click.
« first day (130 days earlier) ← previous day next day → last day (1637 days later) »