For example, the device is at the field and all the values are captured, but then when our field person is at home, they notice something they missed and enter the missing value at home. The last location (home) would be stored. Depending on if they synced before editing at home, you will be able to see the field position in the history though. This means that in case you [...]
If you want to record correct site locations, explicitly create a location field for an observation group linked only to the site. This means that for each site, staff will have to collect the value once explicitly and can also correct eventual errors by checking on a google map. If you want to make sure your staff is actually recording data at the correct location, you can use the automatic [...]
No, not at all. It's by single observation group record.
It is updated on each edit on the mobile, but only stored as a single history entry on every sync. This means that if you edit the data without syncing, it will just update the same record on your device. Once it's synced, a history entry will be created on the server. If you then change it again on the device and sync, it will create a new history record [...]
Would all the observations for the same site and observation group always have all the same lat/long/timestamp values?
No, an observation group record is created for each combination of dimensions/visit, eg for each plot if its site/rep/variety, for each site if its a site observation or for each plot/sample if its a sampled plot observation.
This data is updated every time an observation group record is updated. Values are stored together in one record per observation group and selected dimensions. Eg, if you would have an observation group for 4 values and you record them for a certain visit / plot, this will generate a single record with all 4 values and a time / GPS.