EXIF tags with an "=" "count=5"
The current Batch Edit tool, while clunky, will do this. Edit a batch,
click "Batch operations," choose the "count" field, and apply the
value.
If you use http://www.inaturalist.org/observations/upload, iNat will
also add observation fields from EXIF tags with an "=" in them, so if
you add tags to your photos like "count=5" that will also work
(incidentally it should also work for taxa, e.g. eating=Homo sapiens
for a photo of an organism eating a human).
o one could possibly use the "User Comment" Exif Tag and add something like
count=5, Insect Nectar Plant=Eriogonum fasciculatum, Elevation=3000 uld like to be able to upload a csv file where the Count field could be included in a record. I use a program for data collection which includes a count field, so it is currently a lot of work to upload a large number of records and then manually wade through them all adding a count to those with > 1 in that count fiel
Further to my first request, I notice that the GPS Accuracy, while it is a standard data entry value for iNaturalist via the App or geotagged photo upload, is not supported in CSV upload. Similarly, Annotations are not supported and are a manual entry only. These seem like significant oversights to me and I would request that all of the standard observation fields be included in the base import csv format. In addition, I have found, through an anonymous tipster, that the csv upload format can be "customized" via a "hidden" process by first creating a Project and specifying custom Fields in the Project, which will then generate a custom template which will include the specified Fields. However, it would seem to be much more flexible and universal if the CSV header row was simply used as the template by default and this feature was documented. While field data entry using the App is fun and useful for occasional observations where a data connection is readily available, it is far too cumbersome and battery and data intensive for serious field data collection where a dat connection is available and extremely tedious and punishing when no data connection is available.
An intelligent alternative which would satisfy all such issues in a flexible, conventional and well defined way would be to support JSON format which would support better serious data entry options than the current App can provide.
iNaturalist is evolving nicely and has now become a very useful system to share all of my most significant natural history observations with photos. I am looking forward to the time when it will be feasible to upload all of my significant observations without photos and my more casual, but still valuable observations with or without photo