An issue arises when setting the "latitude" and "longitude" columns if there is more than one lat/lon column in the Echoview exports, which can happen when export parameters are not correctly set. This arose in the 2015 data (both lat_s/lon_s and lat_e/lon_e columns in Canadian Echoview export data). There was already a fix in EchoPro for defaulting to lat_m and lon_m when more than one lat/lon column was found. However, since lat_s and lon_s are the preferred variables, I updated the code in read_echoview_export (in nasc.py) to use those columns instead. It is possible that lat_m was set instead of lat_s because of issues in some other years, so this issue might arise again in a different form when validating importing Echoview exports in a different year.
I will try and push the updated code up. :-) Apologies in advance for my mistakes in that process.
An issue arises when setting the "latitude" and "longitude" columns if there is more than one lat/lon column in the Echoview exports, which can happen when export parameters are not correctly set. This arose in the 2015 data (both lat_s/lon_s and lat_e/lon_e columns in Canadian Echoview export data). There was already a fix in EchoPro for defaulting to lat_m and lon_m when more than one lat/lon column was found. However, since lat_s and lon_s are the preferred variables, I updated the code in read_echoview_export (in nasc.py) to use those columns instead. It is possible that lat_m was set instead of lat_s because of issues in some other years, so this issue might arise again in a different form when validating importing Echoview exports in a different year.
I will try and push the updated code up. :-) Apologies in advance for my mistakes in that process.