Just because it always bears re-iteration for anyone still reading,
when I ask for a URL, I don't mean a URL for the phenomenon as a
whole, I just mean a URL for *any* page showing the phenomenon you're
describing. If that seems too obvious to include, please understand
that it isn't. The best bug reports for a website include a URL that
shows an example of what you're talking about, a screenshot showing
what *you're* seeing, since that will vary from setup to setup, and
any details that aren't obvious from those forms of evidence, like the
actions it takes to reproduce the conditions you're experiencing,
details about browser, operating system, etc.
The reason URLs are so important is that saying "the species page"
could mean a lot of different things to different people. There are
species depicted on almost every page of the site, including
http://www.inaturalist.org/observations/2384510,
http://www.inaturalist.org/taxa/79240-Stipa-miliacea,
http://www.inaturalist.org/listed_taxa/6493387,
http://www.inaturalist.org/check_lists/3087-Carbon-Canyon-Regional-Park-Check-List,
and
http://www.inaturalist.org/places/carbon-canyon-regional-park, to
point out a few examples.
In this case, it would have helped if you provided URLs like
http://www.inaturalist.org/observations/2384510 and
http://www.inaturalist.org/taxa/79240-Stipa-miliacea with screenshots
of each showing the absence of the GBIF option in the map legend, so I
could see *exactly* what parts of the site you were talking about,
since inevitably what happens is that someone says something is wrong,
I try to guess what the heck they're talking about, and go somewhere
completely different on the site and see no problems, and the problem
doesn't get fixed.
I'm mostly just venting here, since this problem is basically as old
as software engineering, if not engineering itself.
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html summarizes the
problem well, and it was written back in the bronze age of 1999.
On Sun, Nov 15, 2015 at 4:32 PM, Charlie Hohn