Notes to self, besides the polygons:

#118

#115

#113

#112

#106

#96

#68

@jimsafley Can we change the map interface language? We are introducing "Features" into the vocabulary in the documentation (to mean markers and shapes). But the two interface buttons say "Edit layers" and "Delete layers", and it's not clear what layer refers to. Perhaps "Edit features" and "Delete features" instead?

I've changed the language to use "feature" instead of "layer".

Okay, I've:

• removed all mention of Stamen maps
• added shapes
• added a section on site-wide settings including cluster disabling and site-wide base maps
• changed a bunch of language
• updated many screenshots, renamed files
• added the map block for item sets
• updated advanced search and batch edit info
• updated the very outdated map-by-query instructions.

I did NOT test timelines or look at the docs at all; I did not test CSV or edit the doc section at all, since that will be next.

The linked PR is ready for review @jimsafley @sleon, though I want it to stay in draft until I get a chance to double-check some things on Sharon's installation.

Sharon updated her install and no data was lost, so I'm happy with this.

#122 is the only thing outstanding before a new release, I believe, and I'm happy with that too.

There is one additional change that we should possibly add before a new release. The paginate-map-browse branch introduces pagination to the map browse page, where before there was a hard limit of 5000 items. It's a relatively small change, but it would need testing and styling. What do you think?

There is one additional change that we should possibly add before a new release. The paginate-map-browse branch introduces pagination to the map browse page, where before there was a hard limit of 5000 items. It's a relatively small change, but it would need testing and styling. What do you think?

I like it, but it's not working for me. I've got a map browse setting of 23. The map is showing 23 items, but also indicating that only 23 items in the whole site have map data. (It should be 346.)

The buttons could be centered under the map? Or appear under the page title, more in the vein of other browse pages?

I forgot to mention that this feature requires you to check out the set-correct-total-scalar-results branch on core.

As for the pagination's position: @kimisgold Do you have thoughts on where pagination should go on the map browse page?