Is there a way to query features based on its related data (using relationship class, NOT join or relate)?
It is difficult to elaborate more than the precursor to the table...
I am not sure of your purpose, but you will have to read the rest of the help tree
to see if what you want to do is feasible. It may or may not be permissible so you will have to decide what is the most important functionality.
see the pros and cons table here Deciding between relationship classes, relates, and joins—Help | ArcGIS for Desktop apparently a big no for sql queries and symbology
Thanks for the reference Dan,
Due to the 1-many cardinality that I have, seems that I should choose between the relate and the relationship class, and referring to the pros and cons table, seems that relate needs a join to enable the query and symbology (In the screenshot below). Actually, I could not understand this point. may you please elaborate it more?
Thanks for the helpful link Dan,
According to the help-page mentioned above, there is a benefit from using relationship class which is:
I don't know if this means that I can query my features based on its related? What do you think Dan?
Are you adverse to trying it yourself if you already have an example set up?
Thanks for the valuable contribution,
My example is: I have parcels feature class, these parcels are related to valuation table (each parcel has a certain valuation each year), and the estimation table is related to another table which is the the owners table that includes the owners for each parcel in each year, and I want to apply a query on the owners table that finds the related parcels. E.g. I want to search for "Dan" in the owners table, and after I find it, I want to view your parcels.
I tried this in ArcMap and it worked! I just got confused because in the reference you mentioned, it is stated that this is possible (and actually it is possible). However, you mentioned in your first reply that this is NOT possible.
I'm with Dan on his last post; sometimes you just gotta give it a go.
I will however provide you an example of a query I perform via a 1-many relationship class: I maintain a point feature class of business names and it has a relationship with an alternate names table. When I have business names with the same 'root' name (think 7-11) the points are named 7-11<CityCode> where <CityCode> is a three letter City abbreviation. There are dozens of 7-11s in my area of operation and the points are named like this:
Each one has a related record in the Alternate Names table where the name is simply 7-11. If I query the Altername Names table for "Name ='7-11' and then select the related tables tab, I'll get all of them. Make sense? This is actually a 1-1 example, but it works for all my alternate names. For example I have three points:
Joes Bar And Grill
Joes Tool and Die
Since all of them have a related entry of Joes I can query for that. Or if I'm looking for a beer and a burger I can query for Joes Bar and get the desired result of Joes Bar and Grill....
Retrieving data ...