How to avoid stacking of new features in field maps

[KennethJohnston]

I have built several maps and forms for their use in Field Maps for various projects. Most have been creating new features and filling out the form for the new location where we sampled. However, we now have a project that has static sampling locations (USGS gage stations) and will be sampling at these exact sites repetitively. There is also past data for each static location (although slightly off my GPS location) to append which I will need to have at least 1 header named the same to append (site name etc.).

In Field Maps, I would like to select the sampling site and fill out a new form each time I sample. I also want to view a list of past data at the location. I do not want to create a new feature every time I sample at the site and create a cluster or a stack of points in this one location. This makes it challenging and messy to view past data and enter new data for a static location. I have resolved the data visualization on MapViewer by creating a cluster through augmentation.  My problem is avoiding a stack of new features as I sample throughout the seasons in one static location. 

How would I go about resolving this stacking issue? 

[David_Tipping]

Hi - there are several ways to do this. I have recently been using the related table option. There is a great set of 6 YouTube videos on how to set this up using hydrant inspection as an example workflow: https://www.youtube.com/watch?v=v0W6X6ovi_Q 

David

[KennethJohnston]

Thanks this helps!

[TravisSizemore]

What David said. Related tables are exactly meant for this purpose. One feature to many records. Once you create the layer, tables, and relationship classes in Pro and publish them to ArcGIS Online, Field Maps will set this up automatically when you create the web map. 

[KennethJohnston]

Thanks!