Open kitenetter opened 3 months ago
Linked to #101 ?
The immediate solution to the current issue seems to be to change things so that the app stores a lat/long for the centre of a manually entered grid square, rather than a lat/long for the south-west corner of the grid square (as discussed yesterday).
I'm not quite sure if that will also resolve #101 - maybe it will?
A user has provided multiple examples of records that were entered into the app and given a geolocation by typing the grid reference into the app. When the records are displayed in iRecord they are given an output_gridref that is for the grid square immediately below the grid square originally entered.
My assumption is that the app is translating the typed grid ref into a lat/long, and then Indicia translates the lat/long back into a different grid ref.
Can we find a way of ensuring that if a user types in a grid ref, or selects a grid ref by clicking on the map, then the user-supplied grid ref will be retained for use as the output grid ref?
Example record IDs: 37941853 37934217 37986435 35584390