All,
I am looking for some direction...I have a hosted feature layer for catch basins, which are point features. I am using url parameters (...center={Lat},{Long}) to give inspection records the same coordinates as the basin being inspected. My issue is occasionally a basin is found to be incorrectly located and is moved, or is completely missing from the map and a new feature is created. If they perform an inspection on the moved, or new feature, the coordinates for the survey are either incorrect or blank coordinates are passed. I figure I could run a script daily that recalculates the fields in the feature layer but this wouldn't fully solve the problem unless they wait until the following day to inspect modified/new features (not practical). Since designing this system I have learned a lot more about AGOL and intend to redesign our CB cleaning and inspection program in the next year to utilize related tables, but for now we are continuing with this system...
Is it possible for a new or modified feature to somehow automatically populate the lat/long columns? We are using the map in field maps, which I know recently added calculated expressions, though I am unsure how/if I could calculate lat and long. Is there a better way to pass location to a survey?
Any ideas as to how I could best approach this problem are appreciated.
Best,
Brandon