In a FGDB, I have:
I want to export a copy of the FC that brings in the information from the related records. So the challenge is: how to handle the 1:M relationship?
Options:
For option #3, how can I propagate duplicate features for each related record?
If I were working in pure SQL, I'd simply use a LEFT JOIN from the FC to the table. But I don't think I can write full-blown SQL queries with JOIN clauses on FGDB data (i.e. Query Layers).
Thanks.
Solved! Go to Solution.
It looks like the Add Join (Data Management) geoprocessing tool might do what I want:
Related:
Test:
Before:
After:
A different option:
Alternatively, I could add XY fields to the point FC. Then join (in-map join in attribute table) from the table to the FC. Then make an XY event layer from the result. I think that would give me the duplicated points.
It looks like the Add Join (Data Management) geoprocessing tool might do what I want:
Related:
Test:
Before:
After:
A different option:
Alternatively, I could add XY fields to the point FC. Then join (in-map join in attribute table) from the table to the FC. Then make an XY event layer from the result. I think that would give me the duplicated points.