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 far as I understand, the record table doesn't contain information about the number of individuals. Do you think it's possible to add such information as an extra column? This will allow the users to use such information in their modelling and analyses.
Colleagues @jimcasaer and @MartijnUH at INBO (Wild life management and Invasive Species Team) asked me to add a similar column to the record tables I generate in camtraptor, see vignette and this screenshot:
Still, I would like to keep in touch with you as the main goal of camtraptor's get_record_table() function is to generate a record table as similar as possible to the one camtrapR generates so that it can be used as input in camtrapR's detectionHistory().
In case you agree, I am also very open to discuss with you about the name and the position of this column. I could also work on this in a PR if you wish. Thanks 👋
The text was updated successfully, but these errors were encountered:
As far as I understand, the record table doesn't contain information about the number of individuals. Do you think it's possible to add such information as an extra column? This will allow the users to use such information in their modelling and analyses.
Colleagues @jimcasaer and @MartijnUH at INBO (Wild life management and Invasive Species Team) asked me to add a similar column to the record tables I generate in camtraptor, see vignette and this screenshot:
![image](https://private-user-images.githubusercontent.com/33662631/282447018-e7f599b0-55d1-4185-9a6e-0bb659b9d430.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjAyOTkwNDEsIm5iZiI6MTcyMDI5ODc0MSwicGF0aCI6Ii8zMzY2MjYzMS8yODI0NDcwMTgtZTdmNTk5YjAtNTVkMS00MTg1LTlhNmUtMGJiNjU5YjlkNDMwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzA2VDIwNDU0MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTY0MGQ3NWUwZjI0YzhiNzVkM2JkYzA0ZmM1YzliNzk3YjgzNWE3MjRhY2VmNWVkYTZiODVmY2RiNDAwZTllZjUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.iyMiJkYm6NTgvDp_JZRPFnizPz8yTXXRWu63eie8ba4)
Still, I would like to keep in touch with you as the main goal of camtraptor's
get_record_table()
function is to generate a record table as similar as possible to the one camtrapR generates so that it can be used as input in camtrapR'sdetectionHistory()
.In case you agree, I am also very open to discuss with you about the name and the position of this column. I could also work on this in a PR if you wish. Thanks 👋
The text was updated successfully, but these errors were encountered: