Platform: Website
App version number, if a mobile app issue: n/a
Browser, if a website issue: Chrome
URLs (aka web addresses) of any relevant observations or pages: https://www.inaturalist.org/stats/2026/texas_nature_family
Screenshots of what you are seeing:
Description of problem:
Step 1: Go to your year in review
Step 2: Generate if needed
Step 3: Scroll down to your map
the standalone torquemap page has the same issue. see: https://forum.inaturalist.org/t/map-animation-of-observations-over-time/1217/9. i don’t think it’s broken exactly. it’s just that Carto (the map tile provider in this case) is requiring an API key nowadays. (i think the Carto folks want to be able to track who’s using their tiles nowadays so that they can enforce a 5MM tile/month free tier developer limit.)
I’m getting the same issue as the opening poster, but only when using Safari. In Chrome it seems fine.
Happens to me in both Chrome and Firefox. I’ve filed an issue, but because year in review is mostly made for December and January, a potential fix would probably not be a priority now.
Gotcha! Thank you! I use year in review a lot because it seems to be the only way to see how many IDs I’ve given in a day. :D
you can get identifications for a given date range, like so: https://jumear.github.io/stirfry/iNatAPIv1_identifications?user_id=texas_nature_family&own_observation=false&per_page=200&d1=2025-09-01T00:00:00.000-05:00&d2=2025-09-01T23:59:59.999-05:00
this would do something similar via an iNaturalist web page, but doesn’t show a count: https://www.inaturalist.org/identifications?user_id=texas_nature_family&for=others¤t=true&d1=d1=2025-09-01T00:00:00.000-05:00&d2=2025-09-01T23:59:59.999-05:00
this shows only a count:
https://api.inaturalist.org/v1/identifications?user_id=texas_nature_family&own_observation=false&per_page=0&d1=2025-09-01T00:00:00.000-05:00&d2=2025-09-01T23:59:59.999-05:00
however, besides the year-in-review page, i’m not aware of anything that will automatically get identification counts for a series of days right now (because there’s not really an efficient way right now to retrieve this information for really prolific identifiers across more than, say, a month’s worth of days).
Fixed, looking good to me.
