Skip to main content
Question

How can I fan out to individual features in a GDB based on the "LAYER" attribute found in my data?

  • October 19, 2022
  • 5 replies
  • 195 views

Forum|alt.badge.img+1

I realize the fanout option is probably the best option. I have not used FME in quite a while and am looking for someone to spoon feed this to me.

I need to read in a single GDB and export to another GDB based on the "LAYER" field.

 

image

5 replies

dustin
Influencer
Forum|alt.badge.img+31
  • Influencer
  • 627 replies
  • October 19, 2022

The fanout option would be used to create multiple gdbs named per the LAYER field. To create feature classes based on the LAYER field: In your writer parameters, set the Feature Class or Table Name parameter to 'LAYER'.image


Forum|alt.badge.img+1
  • Author
  • 20 replies
  • October 19, 2022

So I do this and I get the error: Geodatabase Writer: Feature Type Definition 'Traffic Separation Scheme Boundary' was requested, but not defined


Forum|alt.badge.img+1
  • Author
  • 20 replies
  • October 19, 2022

To me, it is reading in the "feature_type" which in this case is "Traffic Separation Scheme Boundary" and trying to Write based on "LAYER" which has a different value then "Traffic Separation Scheme Boundary". Can I force my reader to read in features based on "LAYER"?


Forum|alt.badge.img+1
  • Author
  • 20 replies
  • October 19, 2022

I want to read in everything from the GDB, dynamically I believe, I dont want 600 separate feature class readers coming in, then I want to fanout my current feature classes based on the "LAYER" field. When I attempt this I get that error. This seems extremely easy and I am probably missing one or 2 clicks/settings.

 


Forum|alt.badge.img+2
  • 1891 replies
  • October 20, 2022

@sjolster31​ FME is trying to create a layer called "Traffic Separation Scheme Boundary" but there is no schema to tell it what to create. You need to link the "Traffic Separation Scheme Boundary" to the source feature - probably using fme_feature_type. The Dynamic Workflows tutorial describes some of this. Probably in the section Destination Schema Contains Different Feature Type