You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have received a record of Six Spot Burnet via the iRecord Butterflies app. I can't accept it as it may well be a Narrow-bordered Five-spot Burnet. The recorder didn't consider this possibility and just looked at the images in the app which doesn't appear to include this species? I can maybe understand wanting to avoid confusion with Five-spot Burnet in England, but even so I think having all three in the app is better than one. Having a little warning popping up for the selected species where there are confusion species in the area would also be a worthwhile enhancement to consider for the app?
I also note that Six Spot is down as not recorded in my area when the map in the info page for the moth shows that it is.
The text was updated successfully, but these errors were encountered:
Understood @DavidRoy and I had suggested the main iRecord app to the user. The user was surprised that the image recognition did not recognise Box Tree Moth, is that because the butterflies app only recognises the species that it allows to be recorded?
Message from Mark Cubitt
I have received a record of Six Spot Burnet via the iRecord Butterflies app. I can't accept it as it may well be a Narrow-bordered Five-spot Burnet. The recorder didn't consider this possibility and just looked at the images in the app which doesn't appear to include this species? I can maybe understand wanting to avoid confusion with Five-spot Burnet in England, but even so I think having all three in the app is better than one. Having a little warning popping up for the selected species where there are confusion species in the area would also be a worthwhile enhancement to consider for the app?
I also note that Six Spot is down as not recorded in my area when the map in the info page for the moth shows that it is.
The text was updated successfully, but these errors were encountered: