Thanks for sending your spreadsheet!
I do have a quick update:
You know what? You’re absolutely right. I had forgotten that we haven’t yet standardized the location ID codes in ARW according to this ticket: Cleanup for mismatched name and id fields in locationID.json · Issue #711 · WildMeOrg/Wildbook · GitHub
I got pulled into another project for Wildbook upgrades and this location ID standardization task was left unfinished. For context, in the location ID code for the site, the id and name lines are supposed to match. The name is what appears in the drop-down menu of the site, but what the image analysis workflow actually uses to determine the location is what’s in the id part. Here’s what that bit of the code looks like for this location ID:
So in short; carry on! HKW is the correct way to enter this location in an import. I’m sorry I didn’t recall this sooner. When ARW does get this update made to the location ID file, we’ll be sure to post a notice on the site/Community.
I was able to get your spreadsheet committed and appearing correctly on my end. This has come up before as a result of Excel’s automatic formatting and is usually resolved by saving the file as a .csv and then saving that .csv file as .xlsx. That should make the error message disappear.
The devs confirmed your missing project matches are a bug. Because yellow-bellied toads are only identified by their bellies, ARW didn’t bother configuring the viewpoint on automatic detections since it can only work from one viewpoint. When the upgrade happened, it was looking for a viewpoint configuration (since most Wildbooks need one to work) and when it found that one wasn’t set, it couldn’t complete identification. We’re working on this and will let you know when it’s been fixed.