Change makes behaviour of the app consistent with how irecord normally commits records,
using 'entered_sref' for both lat/long pairs or for OS gridref strings
the interpretation of the field is determined by 'entered_sref_system' which default to a lat/lng interpretation.
The app currently always provides lat/lng and doesn't set 'entered_sref_system'.
The change provides a gridref for 'entered_sref' and OSGB as the system. This is correct for NYPH (becuase Irish refs aren't yet being handled anyway) and although in an ideal world GPS refs might be better treated as lat/lng, for current purposes users will expect to see grid-refs. Almost on-one uses lat/lng for botanical recording in the UK.
Change makes behaviour of the app consistent with how irecord normally commits records, using 'entered_sref' for both lat/long pairs or for OS gridref strings the interpretation of the field is determined by 'entered_sref_system' which default to a lat/lng interpretation.
The app currently always provides lat/lng and doesn't set 'entered_sref_system'.
The change provides a gridref for 'entered_sref' and OSGB as the system. This is correct for NYPH (becuase Irish refs aren't yet being handled anyway) and although in an ideal world GPS refs might be better treated as lat/lng, for current purposes users will expect to see grid-refs. Almost on-one uses lat/lng for botanical recording in the UK.