If I use this
https://www.inaturalist.org/observations?place_id=175&subview=map&view=observers
I only get the first 500 users. Is there a way to get more than 500 or, better yet, unique user IDs by county?
why would you want to do this? as far as i can tell, even the API doesn’t allow you to see beyond the top 500 observers for any given set of observations. that’s not to say you wouldn’t be able to get the information you’re wanting. it would probably just require some extra effort to accomplish the task.
1 Like
(whispering) some of us live in places that do not have counties.
4 Likes
The country the OP linked to has counties.
1 Like
Ye-es… I think my point (sorry, it was extraordinarily subtle, I admit) was that perhaps the formula might be specified by place (be it county, country, city, what have you), as this one was.
(We seem to be getting a number of these similar "how do I generate results for ______" topics recently where the ______ is a place, the type of which really is not the important part, the how to part is.)
That said, I think pisum’s question of what the benefit would be of more than the top 500 results is a good one for smaller localities.
2 Likes
Is there a way to do it 500 at a time or something similar?
i don’t understand what you’re asking. as noted before, you can get the top 500 observers, but then you can’t get the rest of the observers for the same set of observations.
as noted before, if you can describe why you want this information, maybe there is another workflow that might help in your case.
In other instances of limits on records, I think I was able to get the first X number of records, then the second set, etc… The original question came up in relation to messaging/tagging people about a bioblitz but now it’s mainly curiosity.
most other API endpoints limit results to the top 10000 records, but as far as i can tell, none of the /.../observers and /.../identifiers endpoints give you anything beyond the top 500. i can’t imagine a specific technical reason for this smaller limit, and i assume it’s primarily there to prevent folks from easily using the API to generate large user litsts (for purposes like messaging / tagging tons of users).
that’s not to say generating such lists couldn’t be done, but if it’s just for curiosity’s sake, it’s not worth explaining how to do, nor actually doing it.
1 Like
OK, thanks. Seems odd that I could get them by downloading all of the observations, assuming less than 200K, and getting unique usernames from the download but can’t just get just the usernames.
the standard csv export is not always very quick and easy to use. so going with that sort of workflow is not without pain. and i’m guessing the point is that all your options now are not without some pain and that you really need to work to get it, if you want it.
2 Likes
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.