Geoprocessing Services - Directory Parameter

Question

Hello,

I have a script tool that processes multiple files in a directory specified by the user. The user also defines the output directory. When shared as a Geoprocessing Service, it seems as if the user is unable to browse for and/or enter these folder locations, perhaps because they fall into the "container" group of input data types. One way around this might be to change the parameter type to "string"; however, this makes it less intuitive for the user, as they have to enter the exact path as text. Is there any way to allow them to navigate to a folder on the file system using a geoprocessing service?

Thanks!

Amy

AmySmith3 · Answer

Desktop has the ability to send the file to the Server, and the service with a few lines of Python code could unzip the contents of the file to a local directory, perform some operations, then zip up the output.

A very belated thank you for your response!

I was wondering if you could point me in the direction of some help documentation on returning an output file to the user.

Thanks,

Amy

KyttMacManus · Answer

I have a similar question, please let me know if it should be restated in a separate thread.

I am running a GP Service and want to save my outputs to a local File GDB.  I have tried hard coding the output file paths as a parameter, but it seems they are automatically replaced by the Scratch.GDB in an individual job directory.

Is it possible to save the outputs from a GP Service to a local folder?  I have already registered the folder with the data store and that seems to be working alright.

Thanks for your help.

Kytt MacManus
Geographic Information Specialist
Columbia University CIESIN

KevinHibma · Answer

Amy,

This is a sort of "classic" GP Server problem: how can GP Server work with "user supplied data". GP Server can only execute against data that it has access to.
Typically thats either "project" data: data which is essential to the service that the server has access to and doesn't change.
Or user supplied input, generally are simple strings, numbers, or digitized features for example.

In your situation you want to get more complex data / project data / multiple datasets over to the Server for it to crunch.
This is where you have to really define your workflow to achieve desired results.

As I said, Server needs the data to act on, so the problem is how to get the data to the Server. There is no mechanism to pass a "folder" to the Server and say "upload everything in here".
Since you're using Desktop as the client, you can pass a fileto Server. The best way I can think to do this would be to have your user zip up the files on their harddrive, then have the GP Service accept a file input (instead of a folder). Desktop has the ability to send the file to the Server, and the service with a few lines of Python code could unzip the contents of the file to a local directory, perform some operations, then zip up the output.

An alternative approach if your users share a common folder that the Server has access to would be to move their data to this folder manually. Then in the Service they submit the path to the data (as a string), and because the Server has access to that path, it finds the data and crunches it.

I personally like approach #1, but your users, internal network and deployment criteria will determine which method works best for you.

I hope this helps.