Latest Contributions by RPGIS

Then how about this suggestion. Since Layer A and Layer B both have a common attribute, have you tried creating a relationship between the two. Creating a relationship would allow for one layer to potentially filter the other simply by what it relates to. This could potentially give you what you need. If that method has either been tested or proves to not give you the results that you are looking for, then I am afraid that there isn't a current solution aside from the solutions that were provided (or a combination of). As suggested before, you can either create or promote the idea to the ideas page so that the community votes it enough so that Esri would be to willing to implement it. I have seen ideas get taken into consideration and even end up as part of the next set of updates.  ... View more

It shouldn't, especially if you are doing this in a local geodatabase. Both ArcMap and ArcPro local gdbs can create relationships. The relationship does need a relationship class, which can easily by created in any local gdb. That would allow for specific records in the main layer to be filtered, which in turn, will auto-filter the other layer specifically by the records in which they are related to. Here is some documentation to help with this. Create Relationships  ... View more

Then you can either use an attribute query (cumbersome) or if you are looking to create basic points, you can dissolve them by attribute. Using the dissolve tool and setting the tool to dissolve the points by attribute will give a unique set of points based on each unique attribute value. However, the dissolve tool will make it to where the all the points that share that unique attribute value will dissolve into one unique record pertaining to that attribute value. The only other alternative, since you are using depth, is to use the Aggregate Points tool(GeoAnalytics). This may help identify points based on created polygons with common attribute values. ... View more

Hi @AbdAhmad, So I gave it more thought and I do believe that there may be another option. Have you tried using the Query Widget instead of the filter widget. The query widget, which I completely forgot about, is very similar to the filter widget but it may have the capabilities that you are looking for. ... View more

Hi @E_A_Bloomquist, Have you tried setting the data as a related table. In regards to related tables, it is possible to create filters so that when one layer is filtered it will filter the layer in the related table as well.  ... View more

OK, I understand your situation a little better now. If that is the case, then the suggestion that I provided would provide a possible solution. If needed, I can try to provide a set of detailed instructions on how that would look using two different map frames. ... View more

You can do this in one of several ways. Add the table to the map Right click on the table and select data Select display XY data Export the features to a database Run the XY Table to Point tool Run Make XY Event Layer tool ... View more

And that is really the purpose of sharing/posting the idea. A lot of times developers will look on here and see if there are any ideas that are worthwhile. If they find one that is and the community greatly likes the idea, then they will take a further look into it. ... View more

Your welcome AbdAhmed, I don't think that there is a way to create a filter subset in one layer from an existing layer with similar attributes, aside from the possible suggestions previously noted, despite having common attributes to filter by. This might be a current limitation of the filter widget. I can try to see if there is any other possible solutions, but there may not be one currently. Have you tried posting the idea of creating a filter widget to utilize two layers to filter one another?   Also, I made a mistake of saying "contains" when I meant to say "is any of" in my previous suggestion. I tried to see if there were any other possible ways to set the filter but I could not create any. ... View more

That I did. I forgot to mention the other option but you stated that already. ... View more

So you can accomplish this using the intersect tool (or similar) in conjunction with other tools, or methods, to determine the highest "1-12" for each polygon assuming that each polygon has that many points inside. Also, what do you mean by highest attribute "1-12". If you mean ObjectID, then that will take a few more steps. ... View more

After some testing, I came across a possible solution. For the filter widget, here is a possible solution though not quite in the manner that you are looking for. For the filter widget: "Display features that match all of the filters" Create filter set for Layer B Choose "All of the following expressions in this set to be true" Set expression "Distcode" - "contains" - select all unique values  "Ask for values" unchecked Set expression "SubdistName" - "is" - select unique values "Ask for values" checked Create filter set for Layer A Choose "All of the following expressions in this set to be true" Set expression "Distcode" - "contains" - select all unique values  "Ask for values" unchecked Set expression "DistName" - "is" - select unique values "Ask for values" checked The only other option for the filter widget (similar to above but simpler) is to add the "DistName" field to Layer B feature class and field calculate the corresponding name by joining the table for layer A to layer B. You can re-publish the layer and set the filter (similar to what was mentioned above) with the only difference for the expression is swapping out the "Distcode" for "DistName" by unique value and asking users to select a value. You can then set the "SubdistName" filter below to only allow for predefined values based on the previous filter. As for Layer A, simply set it to filter all values that contain the district name and it should simply filter by default. ... View more