It’s good to know there’s a reason for it. Has it been discussed before whether something can or should be done about hidden/unconfirmed observations skewing the bounds returned by /v1/observations?
I suppose if I started building out the map query grammar, I could have it support:
/map taxon1,taxon2,... from location1,location2,...
Where the keyword “from” indicates that one or more locations separated by keywords follow. Then if the user notices the map is off-center, they could redo the query with the “from” filter to recenter the map.
Or … back to the usual use case, a user would simply recenter the map (which is what the above would accomplish, though additionally it would filter the observations).