I would need your advice. I have a lot of Collada files (more than 40000 files) and I want to import them to FME in order to add them some attributes and export them again to Collada. What is the easiest way to do that? I tried with add directories, but it didn't work. Or what is the easiest way to conect mulitple readers with transformer. Thank you for your advice in advance!
Question
Importing a big dataset of Collada files to Workspace
Hi all,
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+21- Safer
Hi,
The easiest way to connect multiple workspace features (transformers and feature types) is to use the Feature Types Connections window. You can open it via the View menu > Windows > Feature Types Connections.
Hej Italy, thank you for your answer. This is a feature that I was looking for. :) Do you advise me that I can import all 20000 collada files into one project, or what would be your approach?
+21- Safer
Hi Slon,
Have you tried the advanced brouwser options?
http://docs.safe.com/fme/html/FME_Workbench/Default.htm#Merging_Similar_Datasets.htm
Hej Italy, I think I my case that is not an option since I cannot open Edit Paramter (or maybe I cannot see that)
+21- Safer
It should be possible, you can select it from within the ws (source collada files parameter) or with a new reader as shown above.
Thank you so much, that was really great help. One more question out of the topic - when i do the following workflow (pictures below) - it is quite strange that I have so many more outputs than Collada inputs after using PointOnAreaOverlay - it there some trick that it will overlay better? Because also when I check on the ispector the attribute table is really unorganized. and not clear. 
+21- Safer
Glad I could help.
According to the documentation "Aggregates are not supported by this transformer."
I am no expert on Collada files, but I think they are most probably aggregates, have you tried de-aggregating before the overlayer?
Hmm, it seems that doesn't effect anything - I get the same amount of the outputs if I use Deaggregator or not. And the inspector table is also the same. 
Hi,
It seems that you have specified "YES" to "Areas First" parameter of the PointOnAreaOverlayer. The help documentation says "If Areas First is set to Yes, then the PointOnAreaOverlayer assumes that all AREA features will enter the transformer before any POINT features. ... Any further AREA features that arrive after the first POINT feature will be logged with a warning and discarded."
Did you get the warning?
I wasn't able to find something other than it from your screenshots.
How about checking via the Inspector whether Areas and Points were created correctly?
Takashi
Hi Takashi, thank you for your answer. I didn't get the warrning, I think here is not the issue. I checked the area with teh inspectore and it looks like this:
Maybe is really problem with the geometry...