Skip to main content
  • EN

I created a workspace to pull aerial imagery stored in a number of different folders. As a result I have 3 FeatureReaders, and in order to get the imagery to write with .tfw I need the schema output port to be connected to the writer. The problem is I need to run the workspace and wait to see which FeatureReader is going to first output a file and then ensure this is the schema output port running to the writer. I want to start using this workspace with WorkSpaceRunner but unless it is completely automated I won't be able to? Am I going wrong somewhere, is it possible to fix this? I don't want to have to wait and manually connect the schema output port.

 

Also with the same workspace, I have noticed a change (bug?) since I upgraded to 2019.0. In 2018.1 when I uploaded a particular AOI shapefile the output came from the TIFF_READER (see image below), but now (2019.0) it comes from the Feature_Reader_2. There is no reason for the change, it should be sending the vast majority through the TIFF_READER and when there are two images for one area the Feature_Reader_2 then outputs the most up to date. This no longer works as everything is coming through the Feature_Reader_2 now. I've uploaded the workbench. I hope this makes sense, thanks for any help. B

 

Do you really need the 3 featurereaders? Is it not possible to manage what you need with one?

I'm not clear why you need to use Schema feature and Dynamic writer feature type. The TIFF writer creates world files (*.tfw) by default, regardless of whether it's configured as dynamic or not.

I'm not clear why you need to use Schema feature and Dynamic writer feature type. The TIFF writer creates world files (*.tfw) by default, regardless of whether it's configured as dynamic or not.

When I was writing using the Dynamic writer I was not getting .tfw unless I had the Schema port connected, I am now no longer using a Dynamic writer and it has solved the problem. Thanks for the help.

Do you really need the 3 featurereaders? Is it not possible to manage what you need with one?

I am reading the UNC path for each file, these are broken into 3 separate lists, therefore I want to read 3 different 'Datasets' (see below). I thought this was the only way to achieve this, I am not an expert, I could well be doing it the wrong way, is there a way to achieve this using one FeatureReader? Thanks B

I'm not clear why you need to use Schema feature and Dynamic writer feature type. The TIFF writer creates world files (*.tfw) by default, regardless of whether it's configured as dynamic or not.

I was wrong. As you said, dynamic writer didn't generate tfw files unless receiving schema feature. Strange...

Anyway, why do you need to configure the writer with dynamic mode?

I was wrong. As you said, dynamic writer didn't generate tfw files unless receiving schema feature. Strange...

Anyway, why do you need to configure the writer with dynamic mode?

'Why do you need to configure the writer with dynamic mode?'

I don't, that was my mistake. I only realised when you pointed the above out and went back and changed it.

Thanks for the help.

B

Do you really need the 3 featurereaders? Is it not possible to manage what you need with one?

You can use an attributecreator to create the filepath attribute depending on your tests

 

e.g. if 15cm_Year = 2017 filepath = 15cm_path

then you use this newly created filepath in a single feature reader

Reply


Community Stats

30,159
Posts
114,480
Replies
37,806
Members
Terms & ConditionsCookie settings
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.