arnaldmarcer
commented
1 year ago Certainly,John. We’ll change this. Thank you, Arnald
On 18 Jul 2023, at 18:41, John Wieczorek @.***> wrote:
In a previous issue the values of the latitudes and longitudes in the copied output were incorrectly assigned (swapped). It looks like the fix was to re-label the fields in the output, but to keep their order. This puts decimalLongitude before decimalLatitude, which is contrary to the order they take in every other context, including the Georeferencing Calculator copied output. This will be problematic when using the two tools together. Can the copied output have the order decimalLatitude then decimalLongitude?
— Reply to this email directly, view it on GitHubhttps://github.com/aescobarr/GeoPick/issues/83, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADYZFUYVQ45WFNNWKQZDHS3XQ24DFANCNFSM6AAAAAA2OVJFPQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>
In a previous issue the values of the latitudes and longitudes in the copied output were incorrectly assigned (swapped). It looks like the fix was to re-label the fields in the output, but to keep their order. This puts decimalLongitude before decimalLatitude, which is contrary to the order they take in every other context, including the Georeferencing Calculator copied output. This will be problematic when using the two tools together. Can the copied output have the order decimalLatitude then decimalLongitude?