Latest Contributions by GayleNeufeld

Everything is a feature service from query layers in both dashboards.   ... View more

@Anonymous User Thanks for the response.  This is good news.  Unfortunately the fields we need filtered first are numeric fields.  When do you think phase 1 will make it into an update? ... View more

@Anonymous User  You mentioned in mid March that you were planning your Q2 work "within the next few weeks".  Since the filter by attribute functionality hasn't been moved to In Product Plan by now, should I assume this functionality hasn't been approved?  It would be helpful to know as my management team is going to be meeting about the mapping problems we have faced and decide on which alternative to use.   Thanks, Gayle Neufeld   ... View more

@Anonymous User I know this is under consideration for the June/July update, but I was hoping I could get a confirmation that this was really going to happen.  We are in the middle of a very busy field season, and it's been a nightmare trying to use the app without this functionality.  Next year will be busier for us, and using FM without being able to filter by attributes is not an option.  It's so bad this year that we will have to resort to going back to paper maps, or just skip mapping altogether, if I can't find an affordable alternative.    ... View more

Hi @KlaraSchmitt Thank you!  I'll give it a try.   ... View more

@MatthewFogarty I'm right there with you.  The workaround I have to do to keep our data confidential (which is required by state law) was way too much work this year.  It is looking like next year will have more projects, and my workaround will not be useful at that point.  I'm going to start looking into different options next month.  I've been asking for this functionality for 2 years now. ... View more

Hi @AaronPulver, My main fields for filtering (community ID and household ID) are long and short integers, no coded value domains.  The resource field, which is a plus if you can get it so I can filter but not necessary, is a text field with a coded value domain. My operator will always be "equals".   Thank you!   ... View more

Hi @AaronPulver, this is great!  Thanks for starting the process. 1. Should the mobile worker have the ability to create a filter using any field? Some products allow the map author to configure pre-defined filters/selectors where the user either enables/disables the filter or the user only selects the value (not the field). Yes, being able to create a filter using any field would be very helpful for us.  We conduct interviews with rural Alaskans on their subsistence harvests.  We would need to be able to filter by our assigned Community and Household identifiers. We work in areas without wifi and would therefore need it to be something that can be done in the field offline.  Dropdown menus would be ideal.  I don't think predefined filters would work for us. 2. We are looking for specific examples of the layer you would use, and the filter you would like to use. For example "I would like to filter a trees layer by the age of tree and specie of the tree." We're trying to understand the complexity of the filters that are needed. How many conditions are expected? We conduct interviews in which we gather information about rural Alaskans subsistence activities and harvests.  We aim to interview an adult from each household within the community, and each household has a number assigned to it as an identifier.  We would need to filter by the community number first, and then household number so that only the data from that household is showing up on the map.  We would need to filter it as we are collecting the data so that no other household's data shows up.   For the most part, filtering by two fields (Community ID, Household ID) is absolutely required.  If there was an ability to filter by more than that, such as resource (the plant or animal harvested), it would be helpful.  If we needed to search for the moose harvest for household 5 in community 56, being able to do that would make the field worker's job much easier. 3. Why do you need to filter a layer? Is it reduce the visual complexity of the map to find nearby features? Is it to reduce search results for searching for specific features? There are several reasons we require a filter.  First and foremost is that by state statute, the data we collect is confidential.  By not being able to filter the data, we as a state agency are in violation of state law.  Obviously, this is not acceptable.  What I've done for a work around is to make a separate map for each household in each community so that only one household's data shows on the map during an interview.  This gets very clunky and overwhelming for my field workers, and it is a lot of extra work for me.  But it is the only way we can collect our data without violating state law.   Second reason is that seeing the responses from other households is likely to introduce bias into an interviewee's responses.  While there is always some bias when collecting data from interviews, we have developed questions to try to limit it.  But we can't limit bias when we show them where other people hunt, fish and gather resources.   Third reason is that our field workers go into remote communities without access to wifi, and sometimes they go from one community to another without coming into the office in between.  Each community can result in hundreds of overlapping polygons (see attached photo).  It ends up being a mess, and impossible to collect new data or edit existing data.  Often the data is cleaned up after an interview is completed, so being able to find the correct polygon is essential, and this is where being able to filter by more than one attribute would be helpful.   This is an example of a subset of overlapping polygons from one community (with location and identifying attributes not shown) Example of overlapping polygons from one community 4. Should filters be persisted/saved so they can easily be turned on/off for a layer? I don't think this is necessary for us but could be useful.   A dropdown for the filter field and then another either dropdown or box for the specific household ID being interviewed/edited is really all we require.   This is our main attribute table.   Attribute table   Let me know if you need any further explanation, or more information. Thanks, Gayle Neufeld Alaska Department of Fish and Game   ... View more

@Anonymous User Glad to see this is under consideration!  I'm also willing to provide further clarification, and help out with testing.  My team will be thrilled to adopt this! ... View more

I've been asking for this for 2 years (with Collector).  I'm very disappointed that this very basic functionality hasn't been included in Field Maps.  We end up having hundreds of overlapping polygons on each iPad, and we work offline for days or weeks at a time without any access to WIFI.  Without the ability to filter by attribute we find that the Esri field data collection apps are unusable for us. ... View more