Hi, this is a definite bug. As you know, the grey nurse shark species has separate populations that never meet (and have not done so for thousands of years). In the below match, it tried to match a shark from the East Coast of Australia to a shark in the US.
Please can you ensure that East Coast of Australia sharks ONLY match to other sharks from the East Coast of Australia. And that West Coast of Australia sharks ONLY match to other sharks from West Coast of Australia. Same for South Africa and the US - they should only match to sharks from their geographical area.
Please see attached the error spot map. See modified groth results number 11:
Weirdly, despite the match candidate locations appearing above the match table, there doesn’t appear to be a way on the user side to edit which locations are matched against. This doesn’t appear to be a bug, just bad design.
Locations from the Modified Groth match page you linked:
Location from result 11’s encounter:
I’m going to change this to a feature request. I’ll follow up with a ticket soon.
Hi Anastasia,
I’m running into the opposite problem – just trying to cross-check new Seychelles whale shark IDs against the full database, and there seems to be no way to select location – as far as I can tell, both PIE and MIEW are only matching against other Seychelles encounters, with no way for me to manually expand out the search area.
Thanks!
Simon.
Interesting! And this is happening for spot mapped results? Can you post a link to the match results page so I can include it as an example in the ticket for the devs?
Hi Anastasia,
Example here: Sharkbook: Wildbook for Sharks
This is with the PIE/MIEW results – I haven’t tried manual spot mapping. It was the same with each shark I tried; I can’t see where to manually expand the geographical search area out from Seychelles.
Thanks!
Simon.
Ah! I see – If I ‘Start Another Match’ from the Encounter Page, I can choose my search area.
Ah, I see. This feature request is specifically about setting match locations within spot mapping, which currently isn’t an option.
For our AI matching workflow that your’e referencing, the default behavior is to check for matches in the location ID on the encounter unless the encounter is part of a bulk import. If you bulk import encounters, you can select multiple locations to match against during the first ID attempt. Otherwise for individually reported encounters you’ll need to use the Start another match option and choose additional locations to find match candidates in.
