Hi Chris,
Thanks for the quick response. What I’m hoping is to not have to specify the name “trail” etc. Instead, have the map load all the content from a taxonomy based on what is populating the archive below. Say, someone hits a specific trail in the archive, it would show all 34 locations along the trail on the map, but display only the first 12 locations on the page, until the user went to page 2, where it would display all the same locations on the map, but only the next 12 locations below. Does that make sense?
The issue is this: people visit the page and look at the map only. They don’t bother to scroll down or to go to page 2. And that leaves multiple locations unvisited. Thanks,
Joe