Question

Merge borering shape files with diferent names

  • 12 March 2019
  • 3 replies
  • 0 views
aron
Rank
Badge +14
  • aron Contributor
  • Contributor
  • 120 replies

I have a dataset with a large number of areas (tiles) that border each other. Each area contains a large number of shape files. Each area folder holds the same types of data. All files have unique names.

They have the following syntax: area_datatype.shp.

I would like to merge all the files of a similar datatype into one. So instead of having X areas with Y shape files in each I would like to have Y shapefiles covering all areas X.

The standard procedure is to build a dynamic work space and use fme_feature_type for the output, but I can't get it working this time. My guess is that I somehow need to pull the name of the data table, if that is possible? Or is there some nifty setting that I might have missed?

Any advice on how I can get this to work?

3 replies

takashi
Rank
Userlevel 2
Badge +17

I think you could still use fme_feature_type as the schema definition name, if you defined the destination Shepefile name with other attribute e.g. "_filename".

In the dynamic writer feature type, set fme_feature_type to Schema Definition Name explicitly and set the destination file name to Shapefile Name, as in:

aron
Rank
Badge +14

I think you could still use fme_feature_type as the schema definition name, if you defined the destination Shepefile name with other attribute e.g. "_filename".

In the dynamic writer feature type, set fme_feature_type to Schema Definition Name explicitly and set the destination file name to Shapefile Name, as in:

Thanks @takashi!

A follow up question: How do I expose _filename? I can not find anywhere to expose this attribute.

 

Edit: I figured it out on my own. FilenamePartExtractor to the rescue.

takashi
Rank
Userlevel 2
Badge +17

I think you could still use fme_feature_type as the schema definition name, if you defined the destination Shepefile name with other attribute e.g. "_filename".

In the dynamic writer feature type, set fme_feature_type to Schema Definition Name explicitly and set the destination file name to Shapefile Name, as in:

"_filename" is just an example. You can specify any attribute which stores your required destination Shapefile name.

Reply


Community Stats

28,670
Posts
109,366
Replies
36,531
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.