Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.
Platform (Android, iOS, Website): website
App version number, if a mobile app issue (shown under Settings or About):
Browser, if a website issue (Firefox, Chrome, etc) : chrome
URLs (aka web addresses) of any relevant observations or pages:
Screenshots of what you are seeing (instructions for taking a screenshot on computers and mobile devices: https://www.take-a-screenshot.org/):
Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.):
Going over 500 compared taxa breaks the tool, unfortunately. There are 559 being compared here. You seem to have added more observations from this place ID yesterday, which brought you over the tool’s limit.
It should display that on the right in red, “Some queries missing taxa.” It displays that when I open your link. It should be a bit more obvious and straightforward, though.
if you were to set up a project for the place, you could probably use @kildor’s “missed species” page to generate a comparison list. maybe kildor might even be interested in updating the page so that it could work with a place_id in place of a project_id?
I tried the missed species page and it works great. The main gap, and a significant one for me, is that the parameters are not a part of the URL, so I’ll have to type them in each time I use the site. Is there any way they can be added, so I can bookmark a link for a specific place? I have the compare tool bookmarked for certain sites and use it often.
Is there any way the 500 taxon limit for the compare tool could be increased? I find the tool to be very useful and would definitely like to use it for cases beyond this limit. I have currently broken plants into dicots and non-dicots to get around it, but if I have a much bigger region, I’ll have to break up dicots and that might become very tedious.
probably not. i doubt that iNat staff would make any further changes to an experimental tool that could be deprecated at any time. short of that, you would have to update the page (or a copy of it) yourself or convince someone else to update the page. (the code should be over at the iNat GitHub repo.)
