'Still waiting for detection', Annotations are not made

What Wildbook are you working in?
Giraffe Spotter
What is the entire URL out of the browser, exactly where the error occurred?

https://giraffespotter.org/encounters/encounter.jsp?number=80011094-1747-4cfc-bbf6-3b795b3a9016
https://giraffespotter.org/encounters/encounter.jsp?number=01af3083-7ecc-42c2-a205-ab3b955939dd
https://giraffespotter.org/encounters/encounter.jsp?number=fa31782a-2133-4ee6-af48-c4a7995974fc
https://giraffespotter.org/encounters/encounter.jsp?number=3c6cd183-26b2-44f3-b576-96a759377f6a
https://giraffespotter.org/encounters/encounter.jsp?number=f1bc529e-53eb-487d-8038-b3ebe297b15d
https://giraffespotter.org/encounters/encounter.jsp?number=b60843af-23db-424c-86cc-38364b9ea349
https://giraffespotter.org/encounters/encounter.jsp?number=6b894413-8e6c-427a-a5f2-131f0707e437
https://giraffespotter.org/encounters/encounter.jsp?number=13ca4123-6ce5-4385-9f43-5c738b2c637f
https://giraffespotter.org/encounters/encounter.jsp?number=0c7c13fd-fae5-4fe3-b1cb-7871363c02d4
https://giraffespotter.org/encounters/encounter.jsp?number=d4c06bdd-0de9-4041-b3ab-4efa55358960
https://giraffespotter.org/encounters/encounter.jsp?number=151389a9-e442-4848-a116-0b85daf82e4f
https://giraffespotter.org/encounters/encounter.jsp?number=98eb4c8b-d7fb-49c4-a9c2-e8b87cd11674
https://giraffespotter.org/encounters/encounter.jsp?number=b2b3a377-6235-4a5d-aa50-b3d822ac2f55
https://giraffespotter.org/encounters/encounter.jsp?number=0390578f-b1a4-4591-81d2-4726355d2298
https://giraffespotter.org/encounters/encounter.jsp?number=681c18e6-0a24-419e-abfc-3cf5e5d413b2

Can you describe what the issue is you’re experiencing?
Hi,
in a nutshell, I dont get automatic annotations when I upload new encounters. It says ‘Still waiting for detection’ for several months now. I’ve been having this issue every now and then since I started using GiraffeSpotter. However, since this year (2021), it never worked for me. I’ve been trying to make manual annotations using the ‘Add Annotation’ function. However, after selecting the side that is shown of the animal, it doesn’t give me the option to draw an annotation (Or I just don’t know what the trick is behind the function).

Anyways, I’ve been trying to identify my last encounters using the visual matcher but it is much more time consuming and it would be nice if the automatic identification worked again.

I am aware that there are some more topics on that in this forum, though I thought I’d start a new as the answer is normally some specific change in the code.

Can you provide steps on how to reproduce what you’re experiencing?
I always upload single encounters and not bulk imports. I often add several pictures of the same encounter to have more perspectives and sides shown of the respective animals (maybe that is an issue?). I normally input my coordinates using the provided interactive map, as the coordinates I have don’t match the coordinate reference system that GiraffeSpotter uses and the animals end up somewhere in Sudan.
I have created a ‘project’ since this year under which I safe some of my encounters. Maybe that also poses a problem for the AI?.
Other than that I submit the encounter forms normally. After having submitted them, the ‘Still waiting for detection’ text in the burger menu under ‘My Encounters’ is stuck.

I hope I have explained this well enough.
Looking forward to hearing from you.

Regards
Tom :slight_smile:

If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report

Hi @letom

We see the issue, which is caused by a misspelling of Giraffa tippelskirchi thornicrofti in our configuration files. Filed as bug WB-1864 and working on immediately.

More soon,
Jason

1 Like

Hi Jason,
thanks a lot!

Hi Jason,
the scientific name has now been updated and annotations were made. Excellent, thank you!

Just one more thing. Even though annotations are now present in my encounters, I miss the button for automatic identification in the burger menu. Was that moved to somewhere else or is that a bug?

Regards
Tom

Hi @letom

This should now be resolved. We found one more misspelling of “tippelskirchi” that was also blocking matching.

Can you please confirm you can run ID now?

Thanks,
Jason and @jon

Hi Jason,
everything working nicely now.
Thanks a lot for your help

Tom

1 Like