Skip to main content

Hi, I'm trying to run the attached workspace on a series of files to check the coordinate system then output the filename and whether it's georeferenced or not.

 

I want to extend this functionality later, but am struggling to just run it on files instead of the features within.

 

Can someone please explain the best way to achieve this - my current way is to run a separate workspace runner and direct it to this, I don't think I'm quite getting it though still.

 

I'm also running a different workspace for internal feature checks, and assume this would be the way to go - to break to an internal feature check, and file check workbench (can't think of clean way to organise the data otherwise.)

 

Thanks!

 

 

Hi @jp12212​ ,

 

The workspace you have configured looks correct as you will need to read features in, in order to extract the coordinate system used and test against the newly created attribute (_coordsys). If you want to batch run this against an entire directory or more, you can use a second workspace that contains a Directory and File Pathnames Reader (you can either use a Path filter for *.dwg files or specify the directory of interest), then connect it to a WorkspaceRunner and feed in the "path_windows" attribute into the Source AutoDesk AutoCAD RealDWG File(s) parameter. This will process the files one by one but the Maximum Concurrent FME Processes allow up to 7 processes to run at a time. You may want to add a writer at the end of the coord_sys.fmw to write the results out to something like a text file so you can review the results after all of the files have been processed. You can also use something like the SlackConnector or Emailer to notify yourself once all of the files have been processed by the WorkspaceRunner instead of checking back periodically on the workspace. 2023-09-13_10-35-08Note, this is only on FME Form so you'll need to manually start the task. If you want to have this be automated or triggered by an event like a schedule, when the directory is modified, or any of the other available triggers, you can publish the same workspace to FME Flow for use in an Automation. Depending on the trigger used, you can feed in the path using output keys from the Trigger to populate the published parameter containing the file path to the dwg file.


Reply