Hi,
U can use the Joiner for that.
Reader 1 to Joiner and in joiner use Ownership Parcels .
The joining etc. is selfexplanatory i think.
..after Joiner u can test for the _matched_records attribute to select only the matches..of course..
Hi,
If the format of Ownership Parcels is a database, I think the SQLExecutor is worth to be considered.
Takashi
I think the Longhonrfan said they are excell files.
In a db you would do a join using sql.
And if u still want or prefer to use sql joining, you can insert both excell in a workspace and use a InlineQuerier.
If the Ownership dataset is not a database, the InlineQuerier would be one of candidates of course. But I'm afraid that the InlineQuerior might consume long time to create a temporary database storing millions of records...
Yes, i assume millions of records would reside in a db.
Then a joiner is still viable.
Comparison Joiner/Merger/SqlExecutor:
http://blog.safe.com/2011/05/fmeevangelist79/
Agree that the Joiner is still viable.
Regarding the blog article about performance comparison, I think the SQLExecutor use case is a "bad role model". The SQL was executed more than a million times to combine every geometry and attributes. Naturally it takes long time. The SQLExcutor is not suitable to such a usage.
In this case, if the Ownership is a database, you can fetch all the required records from the database, executing just one query. The SQL statement for the SQLExecutor would be something like this:
select * from Ownership where County in (@Value(CountyList))
Here, "CountyList" is an attribute which is held by the input feature, it stores comma-separated target county names. The input feature can be created based on the Excel table.
I think this query is very efficient. Of course the source dataset has to be a database
The source is indeed a database. I'm going to spend some time messing with these based on the input you've both given me. Thanks for the help and I'll get back to you.
It turns out the ExpressionEvaluator works perfectly for doing this. I must have been entering the query wrong. User error right?
