Jaisen Mathai

Looks like there are free tiers depending on the API being used. `elodie` should qualify for _free and public_. https://developers.google.com/maps/pricing-and-plans/#details

@bdillahu dumping the EXIF is an interesting idea. If we version the photos themselves it also backs up the EXIF (inside the backed up photo). It's a bit heavy handed...

Do either of you know which file this error occurred? If you could send me the file that may help me reproduce the bug.

@dixonge looks like that's the last photo which succeeded. It would be helpful to know which one caused an error. Could you add `print(_file)` to [this line](https://github.com/jmathai/elodie/blob/master/elodie/filesystem.py#L324) and run the...

@dixonge sort order is based on the default of `os.walk` which is not guaranteed to be of any order. However, there's a pull request to [sort them alphabetically](https://github.com/jmathai/elodie/pull/240) which has...

Sure, here you go. ``` def process_file(self, _file, destination, media, **kwargs): print(_file) move = False if('move' in kwargs): move = kwargs['move'] ```

There's a local database at `~/.elodie/hash.json`. You can delete that file whenever you want to reimport photos. There's also a `--allow-duplicates` flag you can pass in where it skips the...

Is it the same corpus of photos that caused an error before and with the same config file?

@dixonge for the sake of this bug do you mind rerunning the import with the original config file which caused the error and letting me know what file causes it?...

Yes, I would include the `--debug`. Also, the `print(_file)` should output the file that is being imported before failing.