google-images-download had an option to use a configuration file for downloading, e.g., googleimagesdownload -cf google_images_download/sample_config.json.
The content of the configuration is something like the following:
These records are executed sequentially, where for each search we can configure the parameters separately.
We can use this to set up a batch job -- though non-repeatable since google's image search engine is not deterministic. In addition, we should be able to specify
the designation folder for the search (as opposed to the default based on the search term)
the number of raw files, based on our distribution requirements
adding metadata (e.g., using the "online_chip" as a label, #1) to the log, hopefully directly in COCO JSON to start with ( #4) .
google-images-download
had an option to use a configuration file for downloading, e.g.,googleimagesdownload -cf google_images_download/sample_config.json
.The content of the configuration is something like the following:
These
records
are executed sequentially, where for each search we can configure the parameters separately.We can use this to set up a batch job -- though non-repeatable since google's image search engine is not deterministic. In addition, we should be able to specify