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
As you can see in the spec change it looks like I'm referring to two different columns,
in working through the fix for this I had to trace through the workflow to figure out what happens to the column name:
get_subjectgroup_observations returns with extra__subject__name process_relocations turns extra__subject__name into name relocations_to_trajectory re-adds extra so from name to extra__name
To me this highlights the need for a rethink of our column naming in ecoscope core and something to look at with a refactor of the base Relocs and Traj objects, if not sooner...
As you can see in the spec change it looks like I'm referring to two different columns,
in working through the fix for this I had to trace through the workflow to figure out what happens to the column name:
get_subjectgroup_observations
returns withextra__subject__name
process_relocations
turnsextra__subject__name
intoname
relocations_to_trajectory
re-adds extra so fromname
toextra__name
To me this highlights the need for a rethink of our column naming in ecoscope core and something to look at with a refactor of the base Relocs and Traj objects, if not sooner...
Originally posted by @atmorling in https://github.com/wildlife-dynamics/ecoscope-workflows/issues/425#issuecomment-2474464825
The text was updated successfully, but these errors were encountered: