Skip to main content
Question

How to set up Workspace Runner to convert two thousand ESRI ArcGIS binary grids to ESRI Ascii Grids?

  • May 30, 2019
  • 8 replies
  • 33 views
nicholas
Contributor
Forum|alt.badge.img+14

Hello all,

 

I have 2,450 ESRI ArcGIS Binary grids, and I want to convert all of them to ESRI Ascii Grids. That is; one binary grid becomes one ascii grid.

I am trying and failing to use Workspace Runner to do this process.

I have successfully made a workbench to convert one binary grid to an ascii grid.

But I have failed to configure the Workspace Runner to run the first workbench

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

8 replies

M
Forum|alt.badge.img

In your place, I use model builder in Arcmap (add dataset iterator and select recursive, then add raster to other format, and for output name use %Name%.

That will export every Binary grids to Ascii Grids with the same name.

debbiatsafe
Safer
Forum|alt.badge.img+21

Hi @nicholas

What errors are you getting for the 'failed' runs?

In addition, how are you setting up the workspace with the WorkspaceRunner? Are you using the Path and Directory reader as shown in this Batch Processing Using the WorkspaceRunner article?

nicholas
Contributor
Forum|alt.badge.img+14
  • nicholasContributor
  • Author
  • Contributor
  • June 3, 2019

Hi @nicholas

What errors are you getting for the 'failed' runs?

In addition, how are you setting up the workspace with the WorkspaceRunner? Are you using the Path and Directory reader as shown in this Batch Processing Using the WorkspaceRunner article?

That was the exact article I followed to set up my workspace.

The error from the log is;

WorkspaceRunner: Failed to run workspace `E:/2019/05/adf2asc_1.fmw' -- Trace was:

FME 2018.1.0.0 Beta (20180516 - Build 18479 - WIN64)

FME Desktop Oracle Edition (floating)

Permanent License.

Machine host name is: TM10328902

Operating System: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)

Copyright (c) 1994 - 2018, Safe Software Inc.

Safe Software Inc.

Expected an even number of command line arguments, instead got 5 for command line: >> `--SourceDataset_ARCVIEWGRID' `\\\\podcisilon\\Groups\\Geospatial_GIS\\ALS\\2018\\LGA_SunshineCoast\\Products\\DEM1m\\ESRI_GRID\\Tiles_1mX1m\\' `--FEATURE_TYPES' `--DestDataset_ESRIASCIIGRID' `E:\\2019\\05/asc' <<

An error occurred during the batch file execution, 1 translation failed. The following error message was raised:

#2 : Expected an even number of command line arguments, instead got 5 for command line: >> `--SourceDataset_ARCVIEWGRID' `\\\\podcisilon\\Groups\\Geospatial_GIS\\ALS\\2018\\LGA_SunshineCoast\\Products\\DEM1m\\ESRI_GRID\\Tiles_1mX1m\\' `--FEATURE_TYPES' `--DestDataset_ESRIASCIIGRID' `E:\\2019\\05/asc' <<

Program Terminating

Translation FAILED.

 

virtualcitymatt
Celebrity
Forum|alt.badge.img+47

That was the exact article I followed to set up my workspace.

The error from the log is;

WorkspaceRunner: Failed to run workspace `E:/2019/05/adf2asc_1.fmw' -- Trace was:

FME 2018.1.0.0 Beta (20180516 - Build 18479 - WIN64)

FME Desktop Oracle Edition (floating)

Permanent License.

Machine host name is: TM10328902

Operating System: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)

Copyright (c) 1994 - 2018, Safe Software Inc.

Safe Software Inc.

Expected an even number of command line arguments, instead got 5 for command line: >> `--SourceDataset_ARCVIEWGRID' `\\\\podcisilon\\Groups\\Geospatial_GIS\\ALS\\2018\\LGA_SunshineCoast\\Products\\DEM1m\\ESRI_GRID\\Tiles_1mX1m\\' `--FEATURE_TYPES' `--DestDataset_ESRIASCIIGRID' `E:\\2019\\05/asc' <<

An error occurred during the batch file execution, 1 translation failed. The following error message was raised:

#2 : Expected an even number of command line arguments, instead got 5 for command line: >> `--SourceDataset_ARCVIEWGRID' `\\\\podcisilon\\Groups\\Geospatial_GIS\\ALS\\2018\\LGA_SunshineCoast\\Products\\DEM1m\\ESRI_GRID\\Tiles_1mX1m\\' `--FEATURE_TYPES' `--DestDataset_ESRIASCIIGRID' `E:\\2019\\05/asc' <<

Program Terminating

Translation FAILED.

 

That sounds like there is an issue with one of the published parameters. I suspect that there is a <space> Character somewhere which isn't properly being escaped although from the log I can't see where this would be. You could try and delete the "FEATURE_TYPES" published parameter to see if it has any effect.

debbiatsafe
Safer
Forum|alt.badge.img+21

That was the exact article I followed to set up my workspace.

The error from the log is;

WorkspaceRunner: Failed to run workspace `E:/2019/05/adf2asc_1.fmw' -- Trace was:

FME 2018.1.0.0 Beta (20180516 - Build 18479 - WIN64)

FME Desktop Oracle Edition (floating)

Permanent License.

Machine host name is: TM10328902

Operating System: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)

Copyright (c) 1994 - 2018, Safe Software Inc.

Safe Software Inc.

Expected an even number of command line arguments, instead got 5 for command line: >> `--SourceDataset_ARCVIEWGRID' `\\\\podcisilon\\Groups\\Geospatial_GIS\\ALS\\2018\\LGA_SunshineCoast\\Products\\DEM1m\\ESRI_GRID\\Tiles_1mX1m\\' `--FEATURE_TYPES' `--DestDataset_ESRIASCIIGRID' `E:\\2019\\05/asc' <<

An error occurred during the batch file execution, 1 translation failed. The following error message was raised:

#2 : Expected an even number of command line arguments, instead got 5 for command line: >> `--SourceDataset_ARCVIEWGRID' `\\\\podcisilon\\Groups\\Geospatial_GIS\\ALS\\2018\\LGA_SunshineCoast\\Products\\DEM1m\\ESRI_GRID\\Tiles_1mX1m\\' `--FEATURE_TYPES' `--DestDataset_ESRIASCIIGRID' `E:\\2019\\05/asc' <<

Program Terminating

Translation FAILED.

 

Hi @nicholas

Thank you for the information.

Based on the log snippet, I believe you're using an older beta build of 2018.1. The build you're using is affected by a WorkspaceRunner bug where empty parameters will cause the transformer to fail (same issue mentioned in this Q&A post).

Would you be able to try using to a newer version of 2018.1 (build 18510 and higher) or 2019.0 to run your workspaces? Alternatively, you can try @virtualcitymatt's suggestion of deleting the 'FEATURE_TYPES' parameter from your child workspace.
nicholas
Contributor
Forum|alt.badge.img+14
  • nicholasContributor
  • Author
  • Contributor
  • June 3, 2019

Hi @nicholas

Thank you for the information.

Based on the log snippet, I believe you're using an older beta build of 2018.1. The build you're using is affected by a WorkspaceRunner bug where empty parameters will cause the transformer to fail (same issue mentioned in this Q&A post).

Would you be able to try using to a newer version of 2018.1 (build 18510 and higher) or 2019.0 to run your workspaces? Alternatively, you can try @virtualcitymatt's suggestion of deleting the 'FEATURE_TYPES' parameter from your child workspace.

My version of FME is;

FME Desktop Oracle Edition (floating)

FME(R) 2018.1.0.0 (20180516 - Build 18479 - WIN64)

nicholas
Contributor
Forum|alt.badge.img+14
  • nicholasContributor
  • Author
  • Contributor
  • June 3, 2019

My version of FME is;

FME Desktop Oracle Edition (floating)

FME(R) 2018.1.0.0 (20180516 - Build 18479 - WIN64)

I deleted the FEATURE_TYPES parameter from the child workspace as you suggested, but this did not fix it

debbiatsafe
Safer
Forum|alt.badge.img+21

I deleted the FEATURE_TYPES parameter from the child workspace as you suggested, but this did not fix it

Is the error still the same?

Community Stats

32,120
Posts
121,954
Replies
39,772
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.