In order to do something similar without python (code used in video description) especially if you did not need the query data you could: - Do an attribute join of the id field to the larger feature class Result: a feature class where only the values with an Id in the subset have a value in the joined table ID field. - Select by attributes - Select where join table ID field is “not null” Result: This will select only the features that matched the joined excel table - Export the selected features- right click on the feature class - go to data - export features
@@dadb97 Yes that is possible good point, but in this case we do not have two feature classes. Only 1 and a table with none spatial data, just a matching ID field. So we need to leverage that matching ID field since we don't have a feature class to perform a spatial intersect on. Let me know if i'm not understanding your question correctly?
In order to do something similar without python (code used in video description) especially if you did not need the query data you could:
- Do an attribute join of the id field to the larger feature class
Result: a feature class where only the values with an Id in the subset have a value in the joined table ID field.
- Select by attributes - Select where join table ID field is “not null”
Result: This will select only the features that matched the joined excel table
- Export the selected features- right click on the feature class - go to data - export features
is not possible to make an intersect between the two ft class? That way you generate a new one with just the smaller ft class
@@dadb97 Yes that is possible good point, but in this case we do not have two feature classes. Only 1 and a table with none spatial data, just a matching ID field. So we need to leverage that matching ID field since we don't have a feature class to perform a spatial intersect on. Let me know if i'm not understanding your question correctly?
Excellent 👌
Thanks so Much!