• est_id & egt_uid: reflect what is observed and contain species codes, as reflected in the attached species.csv.
• loc_use_class_options & loc_use: apply to migratory animals and reflect the habitat use. This is used to ensure that each stage of life is reflected and considered for the conservation of the species.
• conc_feat_ & LOC_UNCERT: are used in our spatial methodology. If these are too confusing/distracting, then change them to hidden fields and they'll just be populated with the default values.
• The section in grey just gets to the location. You may or may not be using points, lines, and/or polygons to record location in your surveys. For our purposes, all 3 are needed, as represented by the grey section, so you could incorporate any of this that you want. I presume you are already recording the spatial location. In dark grey are fields that are integral to our work. These reflect the locational uncertainty distance or precision of the given location, as auto-calculated or manually entered, as necessary.
• The green section reflects the date of the observation. Because this can be a date range or exact date, the actual field that we need is that in dark green which is the date in text format. If you are just recording the date as a date field, if you could just add the calculate field with the name = v_date, that would meet our needs.
• detected_ind: if all of the observations collected within your surveys are detected, then this could be added as a hidden field as it already defaults to Y.

Should you have any questions, send an email to [email protected].