Skip to main content
  • EN

Good evening,

 

I have two shapefiles, which I want to merge with each other and then continue working with the partial results. One shapefile contains the boundaries of the municipalities and the other shapefile contains the BoundaryBoxes of the LAS tiles. Since the amount of data is too large, I want to process the data community by community.

The tiles marked in blue contain the names and paths of the individual LAS tiles in an attribute ID].

In my Workbench I perform a spatial selection using the SpatialRelator. For this I connected the shapefile with the information of the LAS tiles to the supplier port and connected the community boundaries to the requester port. .

As a result, I get a list of all elements that contain the community (like the tiles marked blue in the first picture). To check if the selection is correct, I exploded the list with the Listexploder. The result is correct and so far everything is clear.

Next, I want to read the 22 selected tiles, which are stored in the ID] column with the path, from the directory of all tiles and process them for this municipality. I would do this with the FeatureReader, but I am not sure how to set up the settings so that only these 22 tiles are read in and are available for further processing. All my attempts with various settings either didn't bring any data for further processing or all data in the (total) data directory were read in. My question now is, how do I configure FeatureReader to read only the elements of my "_relationships" list, their path and name in the ID] attribute? Maybe there is a more efficient way?

 

Thanks a lot in advance from a FME newbie.

 

PS: Once I have solved this problem, I wonder how I can do this automatically on a community basis (community by community). At the moment I have defined the one community directly with a tester.

After exploding the list, you can use the ID in the FeatureReader like this:

Then use the Generic output port, which should get you the set of Lidar features.

Another option, instead of exploding the list, would be using the ListConcatenator to create a comma separated string of files from _relationships{0}.ID.

Then you can pass the whole set of files to the FeatureReader in one go, using the ID attribute.

Hope this helps.

Hi Jan Erik,

thanks a lot for your two suggestions. Both of them are working perfectly. It was so simple, but I always thought that I had to reference to the list. Thanks a lot. 8-)

On your second point, you could consider creating a parent workspace with a workspace runner to process community by community

Reply


Community Stats

30,177
Posts
114,555
Replies
37,843
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.