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
1. I have a 7000 results list forgeoreferences of collecting events that I would like to seein the graph of the spatial summary to detect bad georeferences ones. (This is the url of the search I am working with in OSF)
2. When I selectthe spatial summary from the linker on the left for the 7053 results it takes more than 3 minutes and the wheel keeps on turning around.
3. So then I tried with less results. So I selectjust 50 records and use the linker on the right. It works properly. (By the way, there are two linkers on the right... I think because a duplication?
4. As I have to check on 7000 and more in other groups, I tried to see 2500 results altogether. It took 2 minutes and a half to show me a text that said: "414 Request - URI too large. nginx/1.18.0 (Ubuntu)"```### Screenshot![image](https://github.com/SpeciesFileGroup/taxonworks/assets/63611746/2ee2dd37-7798-4b65-ae2e-ab122cdc1aeb)There are the two linkers.![image](https://github.com/SpeciesFileGroup/taxonworks/assets/63611746/790f548c-6b34-41e0-a043-c713cd61a073)### Expected behavior```I would need to use this summary for many results... Is there any way this can be possible?
Or maybe it is not possible and it does not work for curating large batch of specimens...
Additional Screenshots
No response
Environment
Production
Sandbox Used
No response
Version
v0.41.0
Browser Used
Chrome
The text was updated successfully, but these errors were encountered:
mabecabrera
changed the title
Spatial Summary of the results in Filter Collecting Event do not work with large sets
Spatial Summary of the results in Filter Collecting Event "URI too large error"
May 7, 2024
Steps to reproduce the bug
Additional Screenshots
No response
Environment
Production
Sandbox Used
No response
Version
v0.41.0
Browser Used
Chrome
The text was updated successfully, but these errors were encountered: