Personally, I’d prefer the buttons at the bottom. As the number of items (banners, buttons, etc.) above an image multiply, that pushes the image(s) further down on the screen. I want to see the images up front without having to scroll down.
I love this, but I was noticing the couple of times I’ve used the ‘Score Image’ option that it doesn’t seem to have correct ‘expected nearby’ details (nothing was marked as expected nearby, even though various things on the list are). I’m in Australia, which shouldn’t make a difference but maybe does somehow?
(Okay, yes, it sounds kind of stupid to say ‘I love this’ and then complain’ - but starting in with a complaint when I do really appreciate it sounds wrong too. So, please take it in the spirit intended… 
)
Haha, no worries. The only good bug is a dead bug (in this context only 
). I’ll see if I’m ignoring that metadata when building my own suggestions list. Thanks!
This tool is really wonderful! I noticed the same thing as grampianshiker. Though the functionality seems to work similar to how “Compare” does where it doesn’t take location into account. So probably not a bug. Probably just more involved to use the location as well.
The autofill is working mostly for me. Sometimes I will click on a genus and it will fill in a species name. And one time I clicked on a genus and it filled+selected the subgenus of the same name. It’s still very useful, just need to make sure you’re selecting what you intended to.
Hey, it’s working for me now! Many thanks, much appreciated.
Edit: Or maybe not? It worked on one page (maybe that was an observation page?) but now it’s not working in Identify.
Further edit: Yes, it seems to definitely work on observation pages but not in Identify. Very odd.
I submitted a new build, 1.1.0, to the extensions store with these features/fixes:
- add rotation buttons to Crop modal (@scarletskylight)
- fix “Expected Nearby” on Identify page (@grampianshiker @ncb1221)
- disable Score Image and Crop buttons for sounds and image-less observations
- Make button color and placement configurable (@schoenitz @kanescompendium @DianaStuder)
- Respect user’s common/scientific name preference when presenting CV suggestions (@DianaStuder)
- Make “copy geocoordinates” button on Identify page consistent with native button on observation pages.
These are the available button settings:
I’ll reply when it’s live, but you’ll probably notice before me :)
Really appreciate being able to crop to - see, that little blue flower there - what is it ?
Today my buttons are elegantly understated. No garish green shouting at me. Thank you !
And my scientific names - which I took for granted as I used them - but that is also new !
Yep, 1.1.0 is live now. Glad you’re enjoying it!
Yes, it’s excellent now (it already was excellent). Thank you.
An integral part of iNaturalist for me, not sure how I’d do without it, all this just to say thank you 
.
hey @sessilefielder, is it intentional that the new buttons/functionality don’t work for images that people have set to all rights reserved?
The score image button gives this pop-up error:
and the crop for CV button gives this error:
Nope. Can you link me to an example?
https://www.inaturalist.org/observations/340560078
I’ve tested it for about 20 different users that have all rights reserved, got the error for all of them. Never encountered the error for any other license
Thanks for being my QA! Sounds pretty deterministic. I’ll look into it as soon as I get a chance.
I also think this tool is fantastic and should be more widely used. I have a relatively small and hopefully easy request, would it be possible to add rotation to the “crop” tool (similar to the mobile iNat crop tool)? Sometimes the picture is messy in terms of background, especially for small plants, and being able to rotate a crop would allow cropping out other flowers while not losing foliage or other key features.
I can include a screenshot if that helps.
I got the same error for score image the first try. But then I refreshed and it worked with no issues. I never got the error for the crop button. All using the same link you shared. Interesting
In this case the photo gets rotated around the selection box, but I’ve seen other systems where the selection box itself can be rotated.
This would be useful for observations that are not one’s own so that we could cut out particular parts of the image for the ML to work “undistracted”. In the screenshot above, the foliage is for a different plant, so the crop selection would allow cutting that out so the ML wouldn’t take the 2nd plant foliage into account when making suggestions.
If it’s more intensive or difficult I understand, I really have no sense of what’s practical vs not practical when creating functions in an extension/app!