June 2020

Recording in the field, syncing and editing at a different location

By |2020-06-09T06:42:17+02:00June 8th, 2020|

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 [...]

May 2020

What are best practices around using GPS locations?

By |2020-06-08T07:56:26+02:00May 27th, 2020|

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 [...]

How does this get updated?

By |2020-06-08T07:56:26+02:00May 27th, 2020|

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 [...]

How is automatic lat/long/timestamp data captured?

By |2020-06-08T07:56:26+02:00May 27th, 2020|

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.

Go to Top