Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

I cannot get the Parse Path tool to pass each file name to the next tool. In the example shown, the Raster to Ascii tool will take the first entry in the 'filename' variable list as part of the output name. But when it runs the next iteration, the Raster to Ascii tool uses some generic file naming convention. 'filename' is set as a precondition for the R2A tool.

Example: raster1.tif raster2.tif Run the Model in Batch mode, using tifs as parameters. 1st output = raster1_asc.txt 2nd output = RastTo_rast.txt <--- this is wrong.

Model Builder running as Batch

Summary: Raster to Ascii tool sucessfully uses the filename variable as inline variable as part of the output file name. However, the the Raster to Ascii tool uses a generic naming convention for the following files (running Model as Batch).

Does anyone have an insight as to why this is happening?

share|improve this question
    
Try calling %filename% in the raster to ascii output without making filename a precondition. –  Aaron Dec 12 '12 at 0:36
    
Perhaps review Does Calculate Value (Model Only Tool) work correctly in tools run in Batch? - apparently custom tools from ModelBuilder that run fine standalone don't always work from the Batch Grid - this is currently treated by Esri as a Known Limit but its one that I think they should try to address - your Question reminds me of this one. –  PolyGeo Dec 12 '12 at 0:38
    
@Aaron - Tried that, no difference. –  Ryan Mendieta Dec 12 '12 at 0:58
    
@PolyGeo - if I'm reading the post right, it seems like that's what's happening here. The same filename variable is used the second time, and the tool avoids overwriting the previous file by using a generic name. Maybe? –  Ryan Mendieta Dec 12 '12 at 0:59
add comment

1 Answer

Perhaps review Does Calculate Value (Model Only Tool) work correctly in tools run in Batch?

Apparently custom tools from ModelBuilder that run fine standalone don't always work from the Batch Grid.

This is NIM053898 and is currently treated by Esri as a Known Limit. However, I think it should be addressed with priority because being able to use ModelBuilder to create a tool that can simply be run in Batch is very appealing.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.