Select to view content in your preferred language

Repeated data entry for same site?

542
2
04-12-2023 03:59 AM
Status: Already Offered
Labels (1)
Carl_Sack
New Contributor II

Is there a way in Survey123 or Field Maps to allow a user to select from existing sites, then add periodic data that would go into a related table? For a use case, say I'm doing water quality monitoring at a variety of sites in a watershed. I collect data at each site on a periodic basis, say every month. I want to be able to select the already existing site closest to my GPS location on a map or from a list, then add a record of the water quality attributes that would go into its own timestamped row in a related table. I would also like to be able to occasionally add a feature to establish a new site, then periodically add records for that site as well using the app.

The closest functionality I have seen reference to is Repeats, which use a related table. But I don't think what I'm thinking of is handled by the repeat functionality, since repeats are geared toward adding copies of the same inputs on a single form entry. What I want is to repeat the form entry for a single site an unlimited number of times without altering the attributes in the feature table for that site. This would be extremely useful for many scientific data collection purposes.

2 Comments
ThomasM

You're describing Repeat Tables exactly. The parent table stores information about your location that doesn't change with each visit (name, description, coordinates), then the entries in the repeat table contain your sampling data (time of sampling, name of sample taker, temp/pH/etc.) with each sample being linked to a location. This setup prevents you from having to re-enter the location information every time you sample, but all of that information is tide to each sample.

If that's really not how you want it setup, you could list out all of your locations as choices (a domain) in the sampling survey, then the sampler could just choose from a dropdown list for a "sample location" question. My thought here is, you would then have a separate dataset of sampling locations and (assuming you have these datasets in a database and not hosted in AGOL) you would create a relationship class between the sampling locations feature class and the sampling feature class using your domain field.

IsmaelChivite
Status changed to: Already Offered

Hi. Check this 60' recording. It covers your workflow in detail: https://mediaspace.esri.com/media/t/1_rge1ajj8