You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whats the issue
Strings composed of only numbers are converted to numeric types
Use case
I have a set of GPS points stored as character that are required to have a certain level of precision. In some instances, lat/long values will end with 1 or more zeros. When data were entered, the trailing zeros were sometimes omitted and need to be updated. (e.g. data entered as 1 instead of 1.0000). I use a corrections log to update the data (changing 1 to 1.0000) and then use the comparedf function to make sure all changes have been made. However, when evaluating the difference between the original and the updated data, "1" and "1.0000" are treated as the same. So when I check if the expected number of changes were made the output from comparedf provides an undercount.
The text was updated successfully, but these errors were encountered:
collinschwantes
changed the title
Strings composed of only numbers are converted to numeric types
Strings composed of only numbers are not compared as expected
Jul 17, 2024
Whats the issue
Strings composed of only numbers are converted to numeric types
Use case
I have a set of GPS points stored as character that are required to have a certain level of precision. In some instances, lat/long values will end with 1 or more zeros. When data were entered, the trailing zeros were sometimes omitted and need to be updated. (e.g. data entered as 1 instead of 1.0000). I use a corrections log to update the data (changing 1 to 1.0000) and then use the
comparedf
function to make sure all changes have been made. However, when evaluating the difference between the original and the updated data,"1"
and"1.0000"
are treated as the same. So when I check if the expected number of changes were made the output fromcomparedf
provides an undercount.Reproducible example
The text was updated successfully, but these errors were encountered: