Help with Geofile Reader and Relative File Paths

[rryontz]

I have all of my data stored in a data folder under my current workflow. With typical file readers, I can choose the file using the “Relative to Current workflow data area.” I read in the Geofile Reader documentation that it says to use standard local file paths such as C:\KNIME\workspace.… or /KNIME/workspace/… depending on filesystem. However, I plan to package the workflow with the data files to send to a coworker whose local path workspace will be different than mine. Is there a way to work around this issue? I am sure there is a good reason to force local file paths for this component, but it is making it very difficult in this circumstance.

I have tried searching for a way to convert the “Relative to Current workflow data area” to a local file path so I can use string manipulations, but I have been unsuccessful with that as well.

[rfeigel]

See if this post helps.

Get a local file path and relative path of the same folder

Hello KNIMErs As part of a workflow that will be deployed to a KNIME server I need to: a) create a temp folder within the workflow directory - done! b) get the path relative to the local workflow data area - done! c) get the local file path for that new folder e.g. C:\KNIME\WorkFlows\CoolFlow\data\Process\6cfc7cf6-011d-4819-aee9-663019823951 - NOT done I know I can hardcode strings to append and create a local file path, but, this part of the flow, is / will be a component which will be use…

[rryontz]

That did it! I knew there had to be something simple I was missing and it was that Extract Context Properties node. Thanks!