review action items from Open Maps Meeting

[kmcdono2]

The below is from the notes with action items list.

---

• Speed up the automatic building on GitHub
• Chat about how to gear away from Machines Reading Maps (if we want that) as it’s catching on in projects like Artemis — and instead towards text detection in MapReader?
• The importance of linked data = should be a through-line in Data/Culture projects more broadly (maybe we can leverage some of these conversations to kickstart Seshat)
• Explore whether pyvips would be a good option for us to load images – if it speeds things up [dependent on Python 3.13]
  Is it possible for us to move back and forth in the workflow? Is it easy? Can we illustrate how it works / should work?

From Slack

• do we have ability to mask on xyz tiles somehow..? just thinking about how this whole cropping rectangles/“hiding” part of the map could fit into our workflow.
• We should really create videos as well, that can be used in these settings - and they should probably include quick(ish) demos of the workflow to make sure we can easily communicate this to a fairly low-tech audience.
• Explore QGIS plugin for MapReader: https://docs.qgis.org/3.34/en/docs/pyqgis_developer_cookbook/plugins/plugins.html#getting-started
• we really need to revisit our slides, and come up with some nice-looking ones with the current workflow etc…

From WhatsApp

• Kalle Westerling: I think what we should do is to model (with drawings + pseudocode) what IIIF integration into MapReader would look like
• Kalle Westerling: might be nice to develop a pretend-workflow from IIIF -> allmaps -> mapreader for the documentation... (using the command line tool that Bert showed!)
• Kalle Westerling: Where can we implement open standards and open data/science practices beyond what we do today?
• Kalle Westerling: We need to simplify URLs on our slides to make it easier for folks to get to the page. I see lots of phones out taking pictures of the URLs…