GNSS and Field Maps setting into metadata

[CPHSDnelson]

I am not sure if this is the correct community to post this question but I thought I would start here. 

Is there anyway to have the settings from the GNSS and Field Maps populate into the metadata.  The other day I noticed settings were changed when a new field member was using the GNSS.  We are currently using an Arrow 100+ GNSS.  Within the GNSS settings you set up a profile that includes antenna height, GNSS coordinate system and map coordinate system.  Having those settings along with the field maps location profile populated into attribute fields would be a huge help to verify how the data was collected. 

[ColinLawrence]

Hi @CPHSDnelson ,

The "Source Type" and "Receiver Name" fields exist in the metadata schema and can indicate what device is being used to generate that location. The Provider and Location Profile are also displayed in the GPS details in the app but the current Location Profile is not an existing Metadata Field. The team is exploring methods to define Web Map settings via Field Maps Designer that could potentially restrict usage to certain Profiles or Providers on a per map basis, for example. Currently in Designer you can set required accuracy and require a Fix Type which could catch if a Field Worker was not connected to their Arrow receiver, for example. Not exactly what you are looking for at this time but hopefully this helps. 

[ahargreaves_FW]

@CPHSDnelson how do i access the "Source Type" and "Receiver Name" fields within Field Maps? As these are system managed I can't display them in smart forms for the end user to see...

[ColinLawrence]

The metadata fields can be added/removed from the read-only popup when configuring the map. After a feature is collected using the GPS the end user should be able to see the values for these fields in the popup. If you meant displaying in the Editable form you could use Arcade to add a read-only field and pull in the value(s) for these fields for the end user to see. For example:

var domName = DomainName($feature, "esrignss_positionsourcetype")

return domName

You want to make sure you are using the DomainName property or the resulting would be meaningless to the end user. 

It is obviously not recommended to add these fields as editable in your forms. I hope this info helps!

[CPHSDnelson]

Sorry I did not reply much sooner.  Thank you for taking the time to reply my inquiry!