Hi, I use a FeatureReader for two purposes: to clip features with a polygon, and to select some desired geodatabase layers (of several geometry types: point, line and polygon).
After the “succesful translation” the new geodatabase has been created. However, this database seems to be empty.
What could be possible causes? Wrong Schema/Data Features of the FeatureReader? In the Reader I have:
In the Writer I have:
Connectiefile is the file where the polygon for the clipping purpose can be found. Other schema sources are not available. Any ideas?
Page 1 / 1
What does the log say? Any warnings or errors?
No errors, there are a lot of warnings, sometimes saying “FileGDB Writer: A feature with feature type ‘[name]’ could not be written”. Below is a part of the very long translation log:
However, the summary in the log showed that features have been written.
I think you use a dynamic workflow using schema features to write the result? The log says something like the schema feature is missing.
Cannot find a matching schema named ‘scheiding_v’ in the knowd set of schemas: ‘REF.BGT/Contour_BGT’.
Without seeing more of the workspace it is hard to tell what is causing this.
Yes, dynamic workflow seems to be needed because of several geometry types in the featurereader.
Contour_BGT contains no physical data, it is a polygon only, purely for clipping purpose.
Below is the FME script (partly in Dutch, I’m sorry).
If I use a SpatialFilter instead of FeatureReader and add Esri fgdb reader
then it runs well and fgdb can be viewed in ArcGIS.
Maybe it has to do something with FeatureReader which is a transformer and not a reader? In the Writer of the second workspace the schema “BGT [GEODATABASE_FILE]” can be selected.
This is not the case in the first workspace with the FeatureReader.
However, I would like to use the FeatureReader because it has the big advantage that only the features which fall within the polygon “Contour_BGT” will be read. How?
Can’t you just connect the FeatureReaders Schema output to the Writer? This is the way it works using a FeatureWriter. Not sure how this works with classic writers, I stopped using these when the FeatureReader and FeatureWriter were introduced.
Can’t you just connect the FeatureReaders Schema output to the Writer? This is the way it works using a FeatureWriter. Not sure how this works with classic writers, I stopped using these when the FeatureReader and FeatureWriter were introduced.
What Niel said is spot on. For Feature reader to write the database correctly with dynamic settings, you will need to connect the schema output from reader to the writer.
I usually connect them to the Sorter where it merge all the stream together before the feature writer, and sorted in such ways that the Schema goes to the writer first. This ensure that schemas exist, and the data can write to the database base on schema its matching.
In schema sources the “SourceDataset_GEODATABASE_FILE” cannot be selected.
Pfff, I'll rest it for a while. Tomorrow a new day!
Can’t you just connect the FeatureReaders Schema output to the Writer? This is the way it works using a FeatureWriter. Not sure how this works with classic writers, I stopped using these when the FeatureReader and FeatureWriter were introduced.
What Niel said is spot on. For Feature reader to write the database correctly with dynamic settings, you will need to connect the schema output from reader to the writer.
I usually connect them to the Sorter where it merge all the stream together before the feature writer, and sorted in such ways that the Schema goes to the writer first. This ensure that schemas exist, and the data can write to the database base on schema its matching.
Interesting! I'll try it tomorrow. Thanks for now!
In schema sources the “SourceDataset_GEODATABASE_FILE” cannot be selected.
Pfff, I'll rest it for a while. Tomorrow a new day!
Try connect this port to the Feature Writer as well.
That was the crucial step to the solution! Thank you!
