Combine 2016-2017 and 2012-2014 datasets

[gsganden]

Using only the 2016-2017 data is very limiting because it is only from mid-summer. I wouldn't expect models trained on just this data to generalize to other times of year, and indeed we have seen substantial performance drops on images from other times of year. We have data from all seasons from 2012-2014. It is formatted differently but contains roughly the same information. Putting these datasets together and training on the result is the lowest-hanging fruit for providing more value with this project.

[DigitalPhilosopher]

Would it be possible to train models for each different part of the year? So a model for summer, a model for fall, etc.
With these models it would be possible to conclude a probability by either (1) taking the sum of the probabilities of each model or (2) detecting the season in which the photo was taken.

[gsganden]

It would be possible, but I doubt that it would be better. Do you think that it would be?

[DigitalPhilosopher]

I think it would be possible to get better results. Detecting objects (or in this case animals) is easier/more efficient in similar environments. I think, that this would factor in for this algorithm as well.

[gsganden]

Try it!

[datmar]

Hi all! Came across this project and it looks both interesting and in my wheelhouse. Interested in contributing if you are open to it and it is still an active project.

@DigitalPhilosopher are you working on this issue or is it up for grabs?

[gsganden]

Great! It is absolutely an active project in theory :-). Addressing this issue in particular would be a great help in moving it forward.

[datmar]

@gsganden Good to know ! I've made progress cleaning the 2012-14 labels in the CSV to align with 16-17, but I may need some extra information to restructure the image filenames to run through the build_dataset process. Particularly to recreate a process_raw.py for the 2012-14 images.

Is there any additional documentation regarding filename structure?

[gsganden]

I am not aware of any. @mfidino can you provide additional information?

[mfidino]

The filename structure should be something like:

./images_2016/DPT/D03-AMP1/ _CHIL - D03-AMP1-JU16_00037.JPG

This represents:

./{year sampled}/{transect sampled}/{site sampled}/{file name}

Transect is section of the city we are sampling (DPT is north west, RST is west, SCT is southwest, JNT is the heart of Chicago. What I think is likely the most important this is the site sampled part of the file name, which likely lines up with the 2012 - 2014 data?

You could also just parse the {file name} part to get the site info if you wanted.

[gsganden]

I'm seeing two issues with the 2012-2014 data:

1. The CSV says that the file paths start like this, with the season/year repeated in the third component: SP12/DPT/D02-HUP1-SP12/. However, the paths in the actual "FA" directories don't repeat the season in the third component, e.g. FA12/DPT/D02-HUP1/. @datmar is that what you are seeing?
2. labels.csv only covers 2012. @mfidino could we get labels for the 2013 and 2014 images?

[mfidino]

It's going to take me a bit to look into the labels for the 2013 and 2014 images for a couple reasons.

1. I'm taking a few weeks off of work as I just became a father.
2. Those data are on the zoo network, and when I am back to work I'll be working remotely due to covid-19.

Way back when we tagged those images we used to write the species tag into the photo metadata. I wrote a ruby script a long time ago to pull those tags (If I recall all the keywords are in the under subject in the exif data.

Ruby script here. Which may at least point out to where you can look to get the species tags.
https://github.com/mfidino/photo_pull/blob/master/parse_photo_exif.rb

[gsganden]

Thank you, and congrats on the new baby!

[datmar]

mfidino thank you, that's good to know!

@gsganden
Sorry haven't had much time to work on this, schedule's been a little upended due to covid-19 (I'm in Manhattan).
Will squeeze some time into getting this done in the next few days.

I'm seeing two issues with the 2012-2014 data:

1. The CSV says that the file paths start like this, with the season/year repeated in the third component: SP12/DPT/D02-HUP1-SP12/. However, the paths in the actual "FA" directories don't repeat the season in the third component, e.g. FA12/DPT/D02-HUP1/. @datmar is that what you are seeing?
2. labels.csv only covers 2012. @mfidino could we get labels for the 2013 and 2014 images?

1. I am seeing that as well, should be an easy fix?
2. Answered by mfidino. Will look into it.