Latest Contributions by NathanBush1

Has there been any progress on this? Similar situation where I have point layer with a PairID field that I want passed to the related table. This is a 1:M, Unfortunately, the relationship was built on different field, so PairID is not carried over from the point to the related table.  ... View more

I have field staff using Field Maps to navigate to an existing set of points, each point has a unique "Feature_ID". Once they arrive within the vicinity, they click on the point to open the popup window where a link takes them a more detailed Survey 123 form. I'd like to use the pulldata() function to auto-populate a question within the form with the "Feature_ID" pulled from the point. I see the point-within-poly, but will this work for just a point? Maybe I'm overseeing a more simpler approach?  Thanks!  ... View more

Excellent!  I'll give it shot!  ... View more

Xander Bakker‌ you're absolutely right about the user experience - not so friendly right now.  Unfortunately, grouping species won't be very helpful since these data will be used to guide management decisions at the species-level (different actions for different species).  Your second suggestion about the predominant species within each grid might be a cool way to quickly see where higher densities exist without having to create copies for each species. Do you have a code snippet I could fiddle with?  btw...thanks for all the help!  ... View more

Xander Bakker‌, The ordering now makes sense, thank you.  Below is a screenshot of user experience. This is "live" data being collected via Collector. Field teams are collecting species percent cover within each grid (attribute table in previous response). When finished, the team marks the grid as 'YES" for complete and the grid turns from clear to green - calling this "survey effort". The layer list displays one example of a species' labeling and color ramping I wish to code out in ARCADE since there may be over a 100. As of now, the user must open the layer list and check on the species they are interested in viewing. It's a bit clunky and I'd love to have a custom widget...something like an ordered list, or scroll.. There is other data in this app (bottom 3 panels) that can be disregarded in this conversation. ... View more

Hi Xander Bakker‌,  So each species is an individual field with a domain (0-5, 99, 100) referring to the different categories (had to set up the attribute table wide version for field data collection purposes). For display purposes in a webapp, I'm simply copying the feature service, and symbolizing by each species and by the category. Hopefully this is making sense, below is a screenshot of part of the attribute table:   Again, the legend is NOT in the order I want, and the colors need specific ramping to show densities (zero to >60%) ... View more

Hi Xander,  I'm trying to get away from having to make manual changes to the order...I have over a hundred similar layers that need to be in the same order and same color for each category.  You're right about the missing categories, the data is just not present yet. ... View more

This is good stuff!  I have this bit of code to assign intuitive labels to my categories, but Id also like to assign certain colors to each category, and order as in the code:  var dif=$feature["Alligator_Weed"]; if (dif <1){ return 'Zero'; } else if (dif==1){ return '<1%'; } else if (dif==2){ return '1-10%'; } else if (dif==3){ return '10-25%'; } else if (dif==4){ return '25-60%'; } else if (dif==5){ return '>60%'; } else if (dif==99){ return 'NOT TARGETED' } else { return 'UNKNOWN' } This is my results so far...  ... View more