There's a few useful attributes coming out of the Path reader: path_unix (or path_windows, depending on your OS) and path_rootname. I've used those to set up the workspacerunner like this:
path_rootname contains the name of the GDB (without the .gdb) and is used to specify the name of the output file.
There's a few useful attributes coming out of the Path reader: path_unix (or path_windows, depending on your OS) and path_rootname. I've used those to set up the workspacerunner like this:
path_rootname contains the name of the GDB (without the .gdb) and is used to specify the name of the output file.
Hi
redgeographics,
thank for your help . i tried using your solution and it works fine but it just takes the first GDB and create the output for that and then it stops. dosen't go for the rest of the GDB's
Hi
redgeographics,
thank for your help . i tried using your solution and it works fine but it just takes the first GDB and create the output for that and then it stops. dosen't go for the rest of the GDB's
That's odd. How many features are coming out of the Path reader?
That's odd. How many features are coming out of the Path reader?
for test i had just taken 2 GDB's .. so it shows 3 feature from path reader but out is created for 1st GDB only.
for test i had just taken 2 GDB's .. so it shows 3 feature from path reader but out is created for 1st GDB only.
It might be due to how the child workspace is set up. I've created mine to be a simple dynamic A-to-B translation. Could you share the logs of both workspaces?
That's odd. How many features are coming out of the Path reader?
Hi
redgeographics.. thnks a lot . i have recreated everything and it worked .
