If you go to Explore → Filters and set your filters you can use the Atom link in the bottom right to get the RSS feed. Works great, including if you add a project filter
However if you are editing a project and click the ‘Preview Observations with these Observation Requirements’ button to take you to Explore → filters and you add a project slug, it will break the atom link and take you to a 404 not found page. I cannot see any difference in the filters I set manually vs using this button from project page, but it does break the atom link for some reason.
i can’t reproduce this.
it would help to provide for each of your cases:
- the Explore page URLs prior to clicking the Atom button.
- the URLs after pressing the Atom button
Here is my step by step:
- edit project (mushrooms of pei)
- on edit page I press the ‘Preview Observations with these Observation Requirements’ button
- this takes to explore page, has URL of: https://inaturalist.ca/observations?quality_grade=research,needs_id,casual&photos=true&without_taxon_id=48712,48327,54755,504101,117423,791361,117897,372828,152525,152550,117956,125752,117869,69968,55174,125772&taxon_ids=47169,48250,47685&place_id=9116&verifiable=any
- press the Filters button, if I press the atom link now it will work fine
- in the filters window I use drop down to get more filters
- add project
- click Atom link, get 404 not found error, here is the link: https://inaturalist.ca/observations.atom?verifiable=any&page=1&spam=false&quality_grade=research%2Cneeds_id%2Ccasual&photos=true&without_taxon_id=48712%2C48327%2C54755%2C504101%2C117423%2C791361%2C117897%2C372828%2C152525%2C152550%2C117956%2C125752%2C117869%2C69968%2C55174%2C125772&taxon_ids=47169%2C48250%2C47685&place_id=9116&user_id=&swlng=&swlat=&nelng=&nelat=&lat=&lng=&projects=mushrooms-of-pei
If I just build my filter manually, without starting with the ‘Preview Observations with these Observation Requirements’ it works fine,
Hope that helps.
can you provide your URLs just before and just after clicking the Atom button in this case?
ok. so the trigger seems to be the combination of filtering for multiple taxa (
&taxon_ids=47169%2C48250%2C47685) and filtering for a project that has multiple taxa defined in its rules (
&projects=mushrooms-of-pei). i didn’t dig into the code to see exactly what’s happening here, but i guess if we step back a little bit, why do you need to apply a project filter on top of all the project criteria filters? (they’re redundant, since they should be filtering for the same thing, right? you really only need either the project filter or the project criteria filters, not both.)
Yea, that is probably true. Seems like it would save some effort it if just added the project and not all the other stuff. Given the point I assume of the button is to test your settings, using the project has the same effect. Either way, it shouldnt 404.