if you’re talking about:
i can’t reproduce this problem, and it’s not just me:
if you want someone to troubleshoot this, it will be helpful to add some screenshots, i think.
ok. there are cases where if you just refresh the Explore page, say, 10 times, 1 or 2 out the 10 times, the map will fail to zoom into the extent of the observations, and the markers will fail to display.
it sort of looks like a timing thing to me. if the page is loaded before it makes the API request to GET /observations, it won’t have the boundaries for the extent of the observations – so it won’t know how far to zoom in, and i assume that if it doesn’t perform the zoom step, then it also fails to look for the markers. (note in the screenshot below, the highlighted request begins after the red line.)
that said, if it is a timing thing, then probably it also requires general systemwide slowness to consistently trigger the issue. right now, if you can usually resolve the issue by refreshing the page once or twice.
i sort of think you should log this as a separate bug report if you really want someone to try to fix the problem.
a note for developers: it may be worth noting that when the page does zoom in and get markers successfully, it actually seems to be issuing 2 /places/nearby requests, which seems unnecessary and probably should be fixed. (actually, the places nearby request probably doesn’t need to occur until you click the places nearby button, i would think.)