Where to draw the line between helpful and hurtful places regarding burden on servers

the more often the place is actually used, the more justification for its existence. if you’re not going to use it, and nobody else is likely to use it either, or if you’re only going to use it once or twice, it probably doesn’t need to exist in the system.

to the extent that you can use the Explore page instead of a checklist, creating a place without a checklist should reduce the burden on the system.

you can get this information without needing a place.

you could approximate the boundaries of a place using a box or a circle, and then you could look for the species in that area that you haven’t seen. for example: https://www.inaturalist.org/observations?lat=34.43156871694205&lng=-81.6890998058282&place_id=any&radius=6.753734887265693&subview=map&unobserved_by_user_id=jfox16

here’s a somewhat taxonomic view of the information above (which is effectively the same information that you would get from the unobserved species view in your Dynamic Life List, specifying circle or box instead of a place): https://jumear.github.io/stirfry/iNat_observations_taxonomy?verifiable=true&lat=34.43156871694205&lng=-81.6890998058282&radius=6.753734887265693&unobserved_by_user_id=jfox16

this describes another way to visualize this kind of information without having to define any boundaries: https://forum.inaturalist.org/t/identifriday-is-the-happiest-day-of-the-week/26908/1631.

here’s another way to get similar information in a different way: https://forum.inaturalist.org/t/a-tool-to-help-you-fill-local-data-gaps-easily-missed/37575.

1 Like