<rss xmlns:source="http://source.scripting.com/" version="2.0">
  <channel>
    <title>OldInsuranceMaps News</title>
    <link>https://blog.oldinsurancemaps.net/</link>
    <description></description>
    
    <language>en</language>
    
    <lastBuildDate>Fri, 01 May 2026 12:06:00 -0500</lastBuildDate>
    <item>
      <title>Georeference-a-thons! HistoryForge (New Orleans), UMD, and UIUC</title>
      <link>https://blog.oldinsurancemaps.net/2026/04/30/georeferenceathons-historyforge-new-orleans-umd/</link>
      <pubDate>Thu, 30 Apr 2026 17:14:57 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2026/04/30/georeferenceathons-historyforge-new-orleans-umd/</guid>
      <description>&lt;h2 id=&#34;upcoming-georeferencing-events-in-new-orleans&#34;&gt;Upcoming Georeferencing Events in New Orleans&lt;/h2&gt;
&lt;p&gt;Here in New Orleans we are looking forward to two georeferencing events coming right up! For the next two Tuesdays (May 5th &amp;amp; 12th) we&amp;rsquo;ll be partnering with HistoryForge to host georeference-a-thons at Second Line Brewing, just like we&amp;rsquo;ve done in the past; these will be our 7th and 8th events here!&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2026/georeferenceathon2026-thisone-wlink.png&#34; width=&#34;600&#34; height=&#34;436&#34; alt=&#34;&#34;&gt;
&lt;p&gt;These are fairly informal gatherings, with an intro and demo at 6:30, and then socializing and georeferencing to follow. We also hope to have a short presentation about areas we&amp;rsquo;ll be working on (8th Ward and 12th Ward), though are still ironing out those details.&lt;/p&gt;
&lt;p&gt;If you are in the area and would like to attend, please RSVP here: &lt;a href=&#34;https://tiny.cc/georef&#34;&gt;tiny.cc/georef&lt;/a&gt; looking forward to seeing some of you next week!&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;d also like to highlight a couple events that other groups have held recently.&lt;/p&gt;
&lt;h2 id=&#34;mapping-historical-duluth-a-crazy-long-term-project-you-can-contribute-to&#34;&gt;Mapping Historical Duluth: A Crazy Long-Term Project You Can Contribute To&lt;/h2&gt;
&lt;p&gt;At University of Minnesota Duluth, Laure Charleux put together a public history workshop as part of the Twin Ports Festival of History. The event featured not only map georeferencing with OldInsuranceMaps.net, but also a historical photo tagging activity, which proved to be especially popular with attendees! Laure and her students are working on multiple digital history projects here: &lt;a href=&#34;https://historical-gis-duluth-umn.hub.arcgis.com/&#34;&gt;Duluth Historical GIS&lt;/a&gt;.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2026/c5b32e12c7.jpg&#34; width=&#34;600&#34; height=&#34;337&#34; alt=&#34;&#34;&gt;
&lt;h2 id=&#34;engineering-open-house-at-uiuc&#34;&gt;Engineering Open House at UIUC&lt;/h2&gt;
&lt;p&gt;Members of the Healthy Regions and Policies lab at University of Illinois, Urbana-Champaign put together a Friday evening map-a-thon as part of the &lt;a href=&#34;https://www.eohillinois.org&#34;&gt;Engineering Open House, 2026&lt;/a&gt;. Continuing to work on maps in their area, the group completed the &lt;a href=&#34;https://oldinsurancemaps.net/map/sanborn02194_005&#34;&gt;Urbana 1909&lt;/a&gt; atlas (almost 30 layers) as well as maps of some other small towns in the area. Thanks to Gabi, Anya, Marc, and especially Cat for putting this event together!&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;If you or your organization would like to use OldInsuranceMaps.net to facilitate an event, don&amp;rsquo;t hesitate to &lt;a href=&#34;https://docs.oldinsurancemaps.net/#contact&#34;&gt;get in touch&lt;/a&gt;! I&amp;rsquo;ve also &lt;a href=&#34;https://oldinsurancemaps.net/community-georeferencing/&#34;&gt;drafted a page&lt;/a&gt; describing these events in general. A comprehensive list of all past events is still in the works though&amp;hellip;&lt;/p&gt;
</description>
      <source:markdown>## Upcoming Georeferencing Events in New Orleans

Here in New Orleans we are looking forward to two georeferencing events coming right up! For the next two Tuesdays (May 5th &amp; 12th) we&#39;ll be partnering with HistoryForge to host georeference-a-thons at Second Line Brewing, just like we&#39;ve done in the past; these will be our 7th and 8th events here!

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2026/georeferenceathon2026-thisone-wlink.png&#34; width=&#34;600&#34; height=&#34;436&#34; alt=&#34;&#34;&gt;

These are fairly informal gatherings, with an intro and demo at 6:30, and then socializing and georeferencing to follow. We also hope to have a short presentation about areas we&#39;ll be working on (8th Ward and 12th Ward), though are still ironing out those details.

If you are in the area and would like to attend, please RSVP here: [tiny.cc/georef](https://tiny.cc/georef) looking forward to seeing some of you next week!

I&#39;d also like to highlight a couple events that other groups have held recently.

## Mapping Historical Duluth: A Crazy Long-Term Project You Can Contribute To

At University of Minnesota Duluth, Laure Charleux put together a public history workshop as part of the Twin Ports Festival of History. The event featured not only map georeferencing with OldInsuranceMaps.net, but also a historical photo tagging activity, which proved to be especially popular with attendees! Laure and her students are working on multiple digital history projects here: [Duluth Historical GIS](https://historical-gis-duluth-umn.hub.arcgis.com/).

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2026/c5b32e12c7.jpg&#34; width=&#34;600&#34; height=&#34;337&#34; alt=&#34;&#34;&gt;

## Engineering Open House at UIUC

Members of the Healthy Regions and Policies lab at University of Illinois, Urbana-Champaign put together a Friday evening map-a-thon as part of the [Engineering Open House, 2026](https://www.eohillinois.org). Continuing to work on maps in their area, the group completed the [Urbana 1909](https://oldinsurancemaps.net/map/sanborn02194_005) atlas (almost 30 layers) as well as maps of some other small towns in the area. Thanks to Gabi, Anya, Marc, and especially Cat for putting this event together!

---
If you or your organization would like to use OldInsuranceMaps.net to facilitate an event, don&#39;t hesitate to [get in touch](https://docs.oldinsurancemaps.net/#contact)! I&#39;ve also [drafted a page](https://oldinsurancemaps.net/community-georeferencing/) describing these events in general. A comprehensive list of all past events is still in the works though...
</source:markdown>
    </item>
    
    <item>
      <title>Code4Lib 2026 - Video links and other notes</title>
      <link>https://blog.oldinsurancemaps.net/2026/04/25/codelib-video-links-and-other/</link>
      <pubDate>Sat, 25 Apr 2026 17:39:07 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2026/04/25/codelib-video-links-and-other/</guid>
      <description>&lt;h2 id=&#34;code4lib-2026&#34;&gt;Code4Lib 2026&lt;/h2&gt;
&lt;p&gt;Early last month I attended Code4Lib 2026 in Philadelphia, and gave a presentation called &lt;a href=&#34;https://www.youtube.com/live/6nBJ9ihhKkA?t=2382s&#34;&gt;Old Maps for New Apps: Making and Using Georeferenced Sanborn Maps at Scale&lt;/a&gt;. It was a short one, 10 minutes, and while at first I thought I would be too pressed for time to give a full overview of OldInsuranceMaps.net to a new audience, I changed things around from how I usually do them and I&amp;rsquo;m really happy with how it turned out. Per Code4Lib norms I&amp;rsquo;ve made my slides &lt;a href=&#34;https://zenodo.org/records/18925497&#34;&gt;available on Zenodo&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I also facilitated an after-conference workshop, &lt;a href=&#34;https://2026.code4lib.org/workshops/running-a-community-georeferencing-event&#34;&gt;Running a Community Georeferencing Event&lt;/a&gt;, and five people came to learn about how OIM can be used for collaborative work at community events. We worked on &lt;a href=&#34;https://oldinsurancemaps.net/map/sanborn05436_001&#34;&gt;Camden, N.J., 1885&lt;/a&gt;, and also a bit on &lt;a href=&#34;https://oldinsurancemaps.net/map/sanborn05017_002&#34;&gt;Helena, MT, 1888&lt;/a&gt; where one of the attendees was from. Shoutout to kcamanch1 for completing Camden even after we finished the workshop!&lt;/p&gt;
&lt;p&gt;It was my first time at Code4Lib and I really enjoyed it! As I don&amp;rsquo;t work in a library many of the talks were not especially relevant to my day-to-day endeavors, but I did like seeing topics discussed that I had learned about in grad school, like BibFrame and EAD, and of course the ever-present dilemma of how to handle all of these bot scrapers&amp;hellip; I especially enjoyed &lt;a href=&#34;https://www.youtube.com/live/2vPK483jqn0?si=Murrh3_v3iwjkjKu&amp;amp;t=1092&#34;&gt;Brandon Nightingale&amp;rsquo;s keynote&lt;/a&gt; about digitizing historical newspapers at the &lt;a href=&#34;https://msrc.howard.edu/black-press-archive&#34;&gt;Black Press Archive&lt;/a&gt; (Howard University). &amp;ldquo;Digitizing is not passive work, it is architecture&amp;rdquo;, i.e. the structure of a digital archive determines how useful it can be in the future. This is an approach to the work that certainly resonates with me.&lt;/p&gt;
</description>
      <source:markdown>## Code4Lib 2026

Early last month I attended Code4Lib 2026 in Philadelphia, and gave a presentation called [Old Maps for New Apps: Making and Using Georeferenced Sanborn Maps at Scale](https://www.youtube.com/live/6nBJ9ihhKkA?t=2382s). It was a short one, 10 minutes, and while at first I thought I would be too pressed for time to give a full overview of OldInsuranceMaps.net to a new audience, I changed things around from how I usually do them and I&#39;m really happy with how it turned out. Per Code4Lib norms I&#39;ve made my slides [available on Zenodo](https://zenodo.org/records/18925497). 

I also facilitated an after-conference workshop, [Running a Community Georeferencing Event](https://2026.code4lib.org/workshops/running-a-community-georeferencing-event), and five people came to learn about how OIM can be used for collaborative work at community events. We worked on [Camden, N.J., 1885](https://oldinsurancemaps.net/map/sanborn05436_001), and also a bit on [Helena, MT, 1888](https://oldinsurancemaps.net/map/sanborn05017_002) where one of the attendees was from. Shoutout to kcamanch1 for completing Camden even after we finished the workshop!

It was my first time at Code4Lib and I really enjoyed it! As I don&#39;t work in a library many of the talks were not especially relevant to my day-to-day endeavors, but I did like seeing topics discussed that I had learned about in grad school, like BibFrame and EAD, and of course the ever-present dilemma of how to handle all of these bot scrapers... I especially enjoyed [Brandon Nightingale&#39;s keynote](https://www.youtube.com/live/2vPK483jqn0?si=Murrh3_v3iwjkjKu&amp;t=1092) about digitizing historical newspapers at the [Black Press Archive](https://msrc.howard.edu/black-press-archive) (Howard University). &#34;Digitizing is not passive work, it is architecture&#34;, i.e. the structure of a digital archive determines how useful it can be in the future. This is an approach to the work that certainly resonates with me.
</source:markdown>
    </item>
    
    <item>
      <title></title>
      <link>https://blog.oldinsurancemaps.net/2026/04/03/last-month-i-presented-at/</link>
      <pubDate>Fri, 03 Apr 2026 09:20:46 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2026/04/03/last-month-i-presented-at/</guid>
      <description>&lt;p&gt;Last month I presented at #Code4Lib: &lt;a href=&#34;https://www.youtube.com/live/6nBJ9ihhKkA?t=2382s.&#34;&gt;www.youtube.com/live/6nBJ&amp;hellip;&lt;/a&gt; While preparing the slides, 10 minutes was feeling really short (especially for a new audience) but I reworked some things and I think it&amp;rsquo;s actually the best introductory talk about the project I&amp;rsquo;ve given!&lt;/p&gt;
</description>
      <source:markdown>Last month I presented at #Code4Lib: [www.youtube.com/live/6nBJ...](https://www.youtube.com/live/6nBJ9ihhKkA?t=2382s.) While preparing the slides, 10 minutes was feeling really short (especially for a new audience) but I reworked some things and I think it&#39;s actually the best introductory talk about the project I&#39;ve given!
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: Winter (pt 2)</title>
      <link>https://blog.oldinsurancemaps.net/2026/03/02/newsletter-winter-pt/</link>
      <pubDate>Mon, 02 Mar 2026 08:49:38 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2026/03/02/newsletter-winter-pt/</guid>
      <description>&lt;h2 id=&#34;new-newsletter-platform&#34;&gt;New newsletter platform&lt;/h2&gt;
&lt;p&gt;This email is (hopefully) finding you via my new setup on &lt;a href=&#34;https://blog.oldinsurancemaps.net/&#34;&gt;Micro.blog&lt;/a&gt;. So, so you&amp;rsquo;ll see a different &amp;ldquo;from&amp;rdquo; address. Most importantly, unlike before, &lt;em&gt;you cannot reply directly to this newsletter to get in touch&lt;/em&gt;. Please write separately to &lt;code&gt;hello@oldinsurancemaps.net&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&#34;getting-out-and-about&#34;&gt;Getting out and about&lt;/h2&gt;
&lt;h3 id=&#34;mapping-usa-video-now-on-youtube&#34;&gt;Mapping USA: Video now on YouTube&lt;/h3&gt;
&lt;p&gt;At the very end of January I co-led a workshop during OpenStreetMap US&amp;rsquo;s virtual Mapping USA conference,  &lt;a href=&#34;https://www.youtube.com/watch?v=jTEge4z5_14&#34;&gt;Historical Mapping with OpenHistoricalMap, OldInsuranceMaps.net, and Yesterdays&lt;/a&gt;. These are three community-focused history projects that all swirl around the OpenStreetMap ecosystem, and&lt;/p&gt;
&lt;h3 id=&#34;this-week-tomorrow-code4lib&#34;&gt;This week (tomorrow!): Code4Lib&lt;/h3&gt;
&lt;p&gt;I&amp;rsquo;m in Philadelphia this week presenting at &lt;a href=&#34;https://2026.code4lib.org&#34;&gt;Code4Lib 2026&lt;/a&gt;. If you happen to be attending, make sure to say hello! If not, all the presentations will be streamed on YouTube (&lt;a href=&#34;https://2026.code4lib.org/general-info/attend&#34;&gt;more info here&lt;/a&gt;), so you can tune in around 9:30 am Eastern Time on Tuesday (tomorrow) to see me. Really looking forward to this!&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ll also be doing a workshop on Thursday about hosting georeference-a-thons, and this will ultimately yield more information on the main website about that topic, so stay tuned for that.&lt;/p&gt;
&lt;h3 id=&#34;hacker-news-post&#34;&gt;Hacker News post&lt;/h3&gt;
&lt;p&gt;Earlier this month someone &lt;a href=&#34;https://news.ycombinator.com/item?id=46788588&#34;&gt;posted OldInsuranceMaps.net on HackerNews&lt;/a&gt;, which was exciting and just a bit stressful, 4,000 visitors in one day, about 100x the normal numbers! Overall it seems like the site held up pretty well, and it was fun to answer some questions in the ensuing discussion.&lt;/p&gt;
&lt;h2 id=&#34;rss-anyone&#34;&gt;RSS, anyone??&lt;/h2&gt;
&lt;p&gt;We have a new code contributor, the first in many years! Josiah &lt;a href=&#34;https://github.com/ohmg-dev/OldInsuranceMaps/pull/344&#34;&gt;added some RSS feeds&lt;/a&gt; to the platform, so you can track activity on any maps within a given place. If you haven&amp;rsquo;t heard anyone mention RSS in the last 10 years, you aren&amp;rsquo;t alone. It is a protocol for publishing news feeds, but now we just get email notifications for everything. If you are interested in keeping track of what&amp;rsquo;s going on in OldInsuranceMaps.net without going to the website every morning, then find your place of interest &lt;a href=&#34;https://oldinsurancemaps.net&#34;&gt;here&lt;/a&gt; and click the RSS icon in the top right to get the feed URL. I expect we&amp;rsquo;ll be making updates to this over the next few months, so please reach out if you have any ideas or feedback.&lt;/p&gt;
</description>
      <source:markdown>## New newsletter platform

This email is (hopefully) finding you via my new setup on [Micro.blog](https://blog.oldinsurancemaps.net/). So, so you&#39;ll see a different &#34;from&#34; address. Most importantly, unlike before, *you cannot reply directly to this newsletter to get in touch*. Please write separately to `hello@oldinsurancemaps.net`.

## Getting out and about

### Mapping USA: Video now on YouTube

At the very end of January I co-led a workshop during OpenStreetMap US&#39;s virtual Mapping USA conference,  [Historical Mapping with OpenHistoricalMap, OldInsuranceMaps.net, and Yesterdays](https://www.youtube.com/watch?v=jTEge4z5_14). These are three community-focused history projects that all swirl around the OpenStreetMap ecosystem, and 

### This week (tomorrow!): Code4Lib

I&#39;m in Philadelphia this week presenting at [Code4Lib 2026](https://2026.code4lib.org). If you happen to be attending, make sure to say hello! If not, all the presentations will be streamed on YouTube ([more info here](https://2026.code4lib.org/general-info/attend)), so you can tune in around 9:30 am Eastern Time on Tuesday (tomorrow) to see me. Really looking forward to this!

I&#39;ll also be doing a workshop on Thursday about hosting georeference-a-thons, and this will ultimately yield more information on the main website about that topic, so stay tuned for that.

### Hacker News post

Earlier this month someone [posted OldInsuranceMaps.net on HackerNews](https://news.ycombinator.com/item?id=46788588), which was exciting and just a bit stressful, 4,000 visitors in one day, about 100x the normal numbers! Overall it seems like the site held up pretty well, and it was fun to answer some questions in the ensuing discussion.

## RSS, anyone??

We have a new code contributor, the first in many years! Josiah [added some RSS feeds](https://github.com/ohmg-dev/OldInsuranceMaps/pull/344) to the platform, so you can track activity on any maps within a given place. If you haven&#39;t heard anyone mention RSS in the last 10 years, you aren&#39;t alone. It is a protocol for publishing news feeds, but now we just get email notifications for everything. If you are interested in keeping track of what&#39;s going on in OldInsuranceMaps.net without going to the website every morning, then find your place of interest [here](https://oldinsurancemaps.net) and click the RSS icon in the top right to get the feed URL. I expect we&#39;ll be making updates to this over the next few months, so please reach out if you have any ideas or feedback.
</source:markdown>
    </item>
    
    <item>
      <title>Upcoming: Mapping USA and Code4Lib</title>
      <link>https://blog.oldinsurancemaps.net/2026/01/27/upcoming-mapping-usa-and-codelib/</link>
      <pubDate>Tue, 27 Jan 2026 13:16:21 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2026/01/27/upcoming-mapping-usa-and-codelib/</guid>
      <description>&lt;h2 id=&#34;mapping-usa-january-31&#34;&gt;Mapping USA (January 31)&lt;/h2&gt;
&lt;p&gt;This coming Saturday at 1pm CST I&amp;rsquo;ll be co-presenting in a workshop at &lt;a href=&#34;https://openstreetmap.us/events/mapping-usa/2026/&#34;&gt;Mapping USA&lt;/a&gt;, a free virtual conference organized by OpenStreetMap US. The workshop, &lt;a href=&#34;https://openstreetmap.us/events/mapping-usa/2026/historical-mapping-workshop/&#34;&gt;Historical Mapping with OpenHistoricalMap, OldInsuranceMaps.net, and Yesterdays&lt;/a&gt; will feature demos from me, Jeff of &lt;a href=&#34;https://openhistoricalmap.org&#34;&gt;OpenHistoricalMap&lt;/a&gt;, and (particularly excitingly) Jacob and Mike from the new project &lt;a href=&#34;https://yesterdays.maprva.org&#34;&gt;Yesterdays&lt;/a&gt;. We&amp;rsquo;ll be showing how all of these crowdsourced applications are interrelated, for example, how georeferenced maps OldInsuranceMaps.net have been integrated directly into Yesterdays.&lt;/p&gt;
&lt;p&gt;Registration is free, so come join us online this Saturday afternoon!&lt;/p&gt;
&lt;h2 id=&#34;code4lib-march-2-5&#34;&gt;Code4Lib (March 2-5)&lt;/h2&gt;
&lt;p&gt;I also have a presentation &lt;em&gt;and&lt;/em&gt; workshop coming up at &lt;a href=&#34;https://2026.code4lib.org/&#34;&gt;Code4Lib 2026&lt;/a&gt; in Philadelphia. This will be my first time at this conference, so I&amp;rsquo;m especially looking forward to meeting new people in the library world.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://2026.code4lib.org/talks/old-maps-for-new-apps-making-and-using-georeferenced-sanborn-maps-at-scale&#34;&gt;Old Maps for New Apps: Making and Using Georeferenced Sanborn Maps at Scale&lt;/a&gt; - Main conference presentation (in-person and accessible via online registration)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://2026.code4lib.org/workshops/running-a-community-georeferencing-event&#34;&gt;Running a Community Georeferencing Event&lt;/a&gt; - Post-conference workshop (in-person only)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This workshop will be the first time I have designed and presented materials specifically about the &amp;ldquo;georeference-a-thons&amp;rdquo; that we here in New Orleans and folks at a number of other organizations have held over the last few years. Preparing for this workshop will yield more documentation and materials around that part of the website, so stay tuned for more updates.&lt;/p&gt;
</description>
      <source:markdown>## Mapping USA (January 31)

This coming Saturday at 1pm CST I&#39;ll be co-presenting in a workshop at [Mapping USA](https://openstreetmap.us/events/mapping-usa/2026/), a free virtual conference organized by OpenStreetMap US. The workshop, [Historical Mapping with OpenHistoricalMap, OldInsuranceMaps.net, and Yesterdays](https://openstreetmap.us/events/mapping-usa/2026/historical-mapping-workshop/) will feature demos from me, Jeff of [OpenHistoricalMap](https://openhistoricalmap.org), and (particularly excitingly) Jacob and Mike from the new project [Yesterdays](https://yesterdays.maprva.org). We&#39;ll be showing how all of these crowdsourced applications are interrelated, for example, how georeferenced maps OldInsuranceMaps.net have been integrated directly into Yesterdays.

Registration is free, so come join us online this Saturday afternoon!

## Code4Lib (March 2-5)

I also have a presentation _and_ workshop coming up at [Code4Lib 2026](https://2026.code4lib.org/) in Philadelphia. This will be my first time at this conference, so I&#39;m especially looking forward to meeting new people in the library world.

* [Old Maps for New Apps: Making and Using Georeferenced Sanborn Maps at Scale](https://2026.code4lib.org/talks/old-maps-for-new-apps-making-and-using-georeferenced-sanborn-maps-at-scale) - Main conference presentation (in-person and accessible via online registration)
* [Running a Community Georeferencing Event](https://2026.code4lib.org/workshops/running-a-community-georeferencing-event) - Post-conference workshop (in-person only)

This workshop will be the first time I have designed and presented materials specifically about the &#34;georeference-a-thons&#34; that we here in New Orleans and folks at a number of other organizations have held over the last few years. Preparing for this workshop will yield more documentation and materials around that part of the website, so stay tuned for more updates.
</source:markdown>
    </item>
    
    <item>
      <title></title>
      <link>https://blog.oldinsurancemaps.net/2025/12/27/blog-migration-completed-ive-consolidated/</link>
      <pubDate>Sat, 27 Dec 2025 22:52:41 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2025/12/27/blog-migration-completed-ive-consolidated/</guid>
      <description>&lt;p&gt;Blog migration completed! I&amp;rsquo;ve consolidated all past blog posts and newsletters into this single feed on &lt;a href=&#34;http://micro.blog&#34;&gt;@micro.blog&lt;/a&gt; , and replaced the existing blog site at &lt;a href=&#34;https://blog.oldinsurancemaps.net.&#34;&gt;blog.oldinsurancemaps.net.&lt;/a&gt; Looks like some strangeness remains with dates on migrated past posts, but overall, success.&lt;/p&gt;
</description>
      <source:markdown>Blog migration completed! I&#39;ve consolidated all past blog posts and newsletters into this single feed on [@micro.blog](http://micro.blog) , and replaced the existing blog site at [blog.oldinsurancemaps.net.](https://blog.oldinsurancemaps.net.) Looks like some strangeness remains with dates on migrated past posts, but overall, success.
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: Winter 2025</title>
      <link>https://blog.oldinsurancemaps.net/2025/12/12/winter-newsletter/</link>
      <pubDate>Fri, 12 Dec 2025 13:55:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2025/12/12/winter-newsletter/</guid>
      <description>&lt;p&gt;Herein: Updates on the future of OIM, some good ol&#39; tech improvements, new blog post, and community notes. For new readers, welcome! And here are &lt;a href=&#34;https://oldinsurancemaps.net/news/&#34;&gt;all past newsletters&lt;/a&gt; in case one isn&amp;rsquo;t enough.&lt;/p&gt;
&lt;h2 id=&#34;2026-and-what-it-will-look-like&#34;&gt;2026 and what it will look like&lt;/h2&gt;
&lt;p&gt;In mid-January, I will be leaving my position at the &lt;a href=&#34;https://healthyregions.org/team&#34;&gt;Healthy Regions &amp;amp; Policies Lab&lt;/a&gt; where I have been for the past 2½ years, leading or contributing to elements of meaningful efforts like the &lt;a href=&#34;https://sdohplace.org&#34;&gt;SDOH &amp;amp; Place Project&lt;/a&gt;, &lt;a href=&#34;https://oeps.healthyregions.org&#34;&gt;OEPS&lt;/a&gt;, and &lt;a href=&#34;https://chichives.com&#34;&gt;Chives&lt;/a&gt;). I&amp;rsquo;ve worked with wonderful people and learned a LOT, but plan now to return to freelance consulting for a bit through my own company &lt;a href=&#34;https://legiongis.com&#34;&gt;Legion GIS&lt;/a&gt;, and figure out what comes next.&lt;/p&gt;
&lt;p&gt;With that in mind, I&amp;rsquo;m beginning to lay the groundwork for upgrades and enhancements to OldInsuranceMaps.net, and in the new year will be looking to 1) solicit one-off funding for specific efforts, and 2) create a new sponsorship model to provide more sustained support. As always, I am also open to larger institutional funding and collaborative opportunities.&lt;/p&gt;
&lt;p&gt;Roadmap, a.k.a. wishlist:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ability to load maps from other collections, an oft-requested enhancement!&lt;/li&gt;
&lt;li&gt;A new map &amp;ldquo;request hub&amp;rdquo;, to better track community requests and interest in particular volumes&lt;/li&gt;
&lt;li&gt;A new and improved web viewer for all maps in a given city&lt;/li&gt;
&lt;li&gt;More ways to visualize and explore statistics around the work that has been performed on the site (a small example of this below)&lt;/li&gt;
&lt;li&gt;Text extraction and search framework&lt;/li&gt;
&lt;li&gt;Comments, favorites, tagging, reporting issues, and other social things&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;If you or your organization would like to help make one of these happen (or have other ideas), please get in touch!&lt;/strong&gt; You can reply directly to this email.&lt;/p&gt;
&lt;h2 id=&#34;who-uses-oldinsurancemapsnet&#34;&gt;Who uses OldInsuranceMaps.net?&lt;/h2&gt;
&lt;p&gt;The home page now includes a new section, &lt;a href=&#34;https://oldinsurancemaps.net/#who&#34;&gt;who uses this platform?&lt;/a&gt;. I encourage you to check it out, as the list was longer than I even thought (over a dozen orgs and many individuals) and it was gratifying to put together. There are a few other in-progress collaborations that I hope to add soon.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://s3.us-central-1.wasabisys.com/oldinsurancemaps/uploaded/markdownx/43e36b6a-c349-4aba-9119-1ea04fde9931.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;h2 id=&#34;improvements-to-the-multimask-interface&#34;&gt;Improvements to the &amp;ldquo;multimask&amp;rdquo; interface&lt;/h2&gt;
&lt;p&gt;I made a few small improvements to the interface that you can use to trim margins of adjacent georeferenced layers, which I call a &amp;ldquo;multimask&amp;rdquo; within the platform. Checkout this recent blog post &lt;a href=&#34;https://blog.oldinsurancemaps.net/post/2025-12-01-reintroducing-the-multimask-interface/&#34;&gt;(Re)Introducing the Multimask Interface&lt;/a&gt; to learn more about how this works (it has a bunch more animated gifs too!).&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-add-mask.drvyhwq7-1sai7v.webp&#34; width=&#34;600&#34; height=&#34;352&#34; alt=&#34;&#34;&gt;
&lt;h2 id=&#34;is-that-a-leaderboard&#34;&gt;Is that&amp;hellip; a leaderboard??&lt;/h2&gt;
&lt;p&gt;Every time we have a georeference-a-thon, some rogue georeferencer or especially competitive couple asks if there is a leaderboard. There &lt;em&gt;kind of&lt;/em&gt; was, just a list of all users with numbers on the platform, but it was an old page and took forever to load. Moreover, it always ended up with Ibrahim or Nate or WallyKitty at the top which (while impressive!!) wasn&amp;rsquo;t very useful for events where new folks were working on one map all together.&lt;/p&gt;
&lt;p&gt;So now there is a Stats table scoped to each Map, which you can find within the &lt;a href=&#34;https://oldinsurancemaps.net/map/sanborn03376_011#summary&#34;&gt;Summary section&lt;/a&gt;. I&amp;rsquo;m sure this will evolve over time, but for now it is a fun, quick (and sortable) way to see who has been working on content. Also, that original profiles page is now &lt;a href=&#34;https://oldinsurancemaps.net/profiles&#34;&gt;a lot faster&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://s3.us-central-1.wasabisys.com/oldinsurancemaps/uploaded/markdownx/aeefa228-7307-4816-8df0-029a6279df14.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;p&gt;Since the beginning, I&amp;rsquo;ve deliberately not gamified this platform. I figured why not see how far we can get without all of that. That said, there is a side of seeing this information that tells the story of who has done the work, which &lt;em&gt;is&lt;/em&gt; a core tenant here, so I do hope to add more elements like this in the future. Who knows, maybe we&amp;rsquo;ll have georeferencing capitáns at some point too.&lt;/p&gt;
&lt;h2 id=&#34;faster-tile-loading&#34;&gt;Faster tile loading&lt;/h2&gt;
&lt;p&gt;I implemented TiTiler on AWS as a Lambda service, rather then running it in a Docker container on the main server. If any of that makes sense to you, you are probably just surprised it wasn&amp;rsquo;t already setup that way. Well, now it is!&lt;/p&gt;
&lt;p&gt;There are still more tweaks to make (thanks for the tips, Eliot!), but already you should notice that the mosaic previews with 100 layers will load those layers all at once, instead of incrementally which was one of the limitations that came with the previous setup, and kind of a drag.&lt;/p&gt;
&lt;h2 id=&#34;community-notes&#34;&gt;Community notes&lt;/h2&gt;
&lt;h3 id=&#34;georeference-a-thons-in-new-orleans&#34;&gt;Georeference-a-thons in New Orleans&lt;/h3&gt;
&lt;p&gt;In mid-September, in collaboration with the Midlo Center for New Orleans Studies we held two back-to-back georeference-a-thons here in New Orleans, and our usual location of Second Line Brewing. Over the course of two evenings, about 30 people came, with only one person coming both nights (shoutout &lt;a href=&#34;https://oldinsurancemaps.net/profile/scanlan&#34;&gt;scanlan&lt;/a&gt;!). We worked on New Orleans, 1896, &lt;a href=&#34;https://oldinsurancemaps.net/map/sanborn03376_006&#34;&gt;vol. 2&lt;/a&gt;, and &lt;a href=&#34;https://oldinsurancemaps.net/map/sanborn03376_008&#34;&gt;vol. 4&lt;/a&gt;. The latter was especially fun because we split the tables into Carrollton, Gretna, Algiers, and 9th Ward.&lt;/p&gt;
&lt;p&gt;A huge thanks to everyone for coming out! We focused on these volumes in particular because the UNO archaeology crew had just done work in Duncan Plaza, so Elizabeth shared some slides about the research and what they had found.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://s3.us-central-1.wasabisys.com/oldinsurancemaps/uploaded/markdownx/a390427e-898f-4bda-a6a2-3aa4a32c722c.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;h3 id=&#34;maprva-presents-yesterdays&#34;&gt;MapRVA presents: Yesterdays&lt;/h3&gt;
&lt;p&gt;A small and mighty team, &lt;a href=&#34;https://maprva.org&#34;&gt;MapRVA&lt;/a&gt; is an OpenStreetMap group in Richmond, VA, and a few months ago they began developing a new community project called &lt;a href=&#34;https://yesterdays.maprva.org&#34;&gt;Yesterdays&lt;/a&gt;. It is a &lt;em&gt;fantastic&lt;/em&gt; crowdsourcing application for geolocating historical photographs of Richmond. They have already placed 5,000 photos!&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://s3.us-central-1.wasabisys.com/oldinsurancemaps/uploaded/markdownx/473ebfdb-12d8-4ed9-b494-35da8c011130.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;p&gt;I learned about Yesterdays when they incorporated mosaics of Sanborn maps made in OldInsuranceMaps.net directly into their interface, which has proved an essential point of reference for placing historical photos. They&amp;rsquo;ve done more georeferncing since to add more layers&amp;ndash;John just georeferenced all of &lt;a href=&#34;https://oldinsurancemaps.net/map/sanborn09064_007&#34;&gt;1925, vol. 2&lt;/a&gt; in a couple of days by himself!&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;That&amp;rsquo;s all for now, thanks for reading!&lt;/p&gt;
&lt;p&gt;You can follow this project on Bluesky &lt;a href=&#34;https://bsky.app/profile/oldinsurancemaps.net&#34;&gt;@oldinsurancemaps&lt;/a&gt;, or for folks on the &lt;a href=&#34;https://openstreetmap.us/get-involved/slack/&#34;&gt;OpenStreetMap US Slack&lt;/a&gt;, find the new #oldinsurancemaps channel.&lt;/p&gt;
</description>
      <source:markdown>Herein: Updates on the future of OIM, some good ol&#39; tech improvements, new blog post, and community notes. For new readers, welcome! And here are [all past newsletters](https://oldinsurancemaps.net/news/) in case one isn&#39;t enough.

## 2026 and what it will look like

In mid-January, I will be leaving my position at the [Healthy Regions &amp; Policies Lab](https://healthyregions.org/team) where I have been for the past 2½ years, leading or contributing to elements of meaningful efforts like the [SDOH &amp; Place Project](https://sdohplace.org), [OEPS](https://oeps.healthyregions.org), and [Chives](https://chichives.com)). I&#39;ve worked with wonderful people and learned a LOT, but plan now to return to freelance consulting for a bit through my own company [Legion GIS](https://legiongis.com), and figure out what comes next.

With that in mind, I&#39;m beginning to lay the groundwork for upgrades and enhancements to OldInsuranceMaps.net, and in the new year will be looking to 1) solicit one-off funding for specific efforts, and 2) create a new sponsorship model to provide more sustained support. As always, I am also open to larger institutional funding and collaborative opportunities.

Roadmap, a.k.a. wishlist:

- Ability to load maps from other collections, an oft-requested enhancement!
- A new map &#34;request hub&#34;, to better track community requests and interest in particular volumes
- A new and improved web viewer for all maps in a given city
- More ways to visualize and explore statistics around the work that has been performed on the site (a small example of this below)
- Text extraction and search framework
- Comments, favorites, tagging, reporting issues, and other social things

**If you or your organization would like to help make one of these happen (or have other ideas), please get in touch!** You can reply directly to this email.

## Who uses OldInsuranceMaps.net?

The home page now includes a new section, [who uses this platform?](https://oldinsurancemaps.net/#who). I encourage you to check it out, as the list was longer than I even thought (over a dozen orgs and many individuals) and it was gratifying to put together. There are a few other in-progress collaborations that I hope to add soon.

![](https://s3.us-central-1.wasabisys.com/oldinsurancemaps/uploaded/markdownx/43e36b6a-c349-4aba-9119-1ea04fde9931.png)


## Improvements to the &#34;multimask&#34; interface

I made a few small improvements to the interface that you can use to trim margins of adjacent georeferenced layers, which I call a &#34;multimask&#34; within the platform. Checkout this recent blog post [(Re)Introducing the Multimask Interface](https://blog.oldinsurancemaps.net/post/2025-12-01-reintroducing-the-multimask-interface/) to learn more about how this works (it has a bunch more animated gifs too!).

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-add-mask.drvyhwq7-1sai7v.webp&#34; width=&#34;600&#34; height=&#34;352&#34; alt=&#34;&#34;&gt;

## Is that... a leaderboard??

Every time we have a georeference-a-thon, some rogue georeferencer or especially competitive couple asks if there is a leaderboard. There _kind of_ was, just a list of all users with numbers on the platform, but it was an old page and took forever to load. Moreover, it always ended up with Ibrahim or Nate or WallyKitty at the top which (while impressive!!) wasn&#39;t very useful for events where new folks were working on one map all together.

So now there is a Stats table scoped to each Map, which you can find within the [Summary section](https://oldinsurancemaps.net/map/sanborn03376_011#summary). I&#39;m sure this will evolve over time, but for now it is a fun, quick (and sortable) way to see who has been working on content. Also, that original profiles page is now [a lot faster](https://oldinsurancemaps.net/profiles).

![](https://s3.us-central-1.wasabisys.com/oldinsurancemaps/uploaded/markdownx/aeefa228-7307-4816-8df0-029a6279df14.png)

Since the beginning, I&#39;ve deliberately not gamified this platform. I figured why not see how far we can get without all of that. That said, there is a side of seeing this information that tells the story of who has done the work, which _is_ a core tenant here, so I do hope to add more elements like this in the future. Who knows, maybe we&#39;ll have georeferencing capitáns at some point too.

## Faster tile loading

I implemented TiTiler on AWS as a Lambda service, rather then running it in a Docker container on the main server. If any of that makes sense to you, you are probably just surprised it wasn&#39;t already setup that way. Well, now it is!

There are still more tweaks to make (thanks for the tips, Eliot!), but already you should notice that the mosaic previews with 100 layers will load those layers all at once, instead of incrementally which was one of the limitations that came with the previous setup, and kind of a drag.

## Community notes

### Georeference-a-thons in New Orleans

In mid-September, in collaboration with the Midlo Center for New Orleans Studies we held two back-to-back georeference-a-thons here in New Orleans, and our usual location of Second Line Brewing. Over the course of two evenings, about 30 people came, with only one person coming both nights (shoutout [scanlan](https://oldinsurancemaps.net/profile/scanlan)!). We worked on New Orleans, 1896, [vol. 2](https://oldinsurancemaps.net/map/sanborn03376_006), and [vol. 4](https://oldinsurancemaps.net/map/sanborn03376_008). The latter was especially fun because we split the tables into Carrollton, Gretna, Algiers, and 9th Ward.

A huge thanks to everyone for coming out! We focused on these volumes in particular because the UNO archaeology crew had just done work in Duncan Plaza, so Elizabeth shared some slides about the research and what they had found.

![](https://s3.us-central-1.wasabisys.com/oldinsurancemaps/uploaded/markdownx/a390427e-898f-4bda-a6a2-3aa4a32c722c.png)

### MapRVA presents: Yesterdays

A small and mighty team, [MapRVA](https://maprva.org) is an OpenStreetMap group in Richmond, VA, and a few months ago they began developing a new community project called [Yesterdays](https://yesterdays.maprva.org). It is a _fantastic_ crowdsourcing application for geolocating historical photographs of Richmond. They have already placed 5,000 photos!

![](https://s3.us-central-1.wasabisys.com/oldinsurancemaps/uploaded/markdownx/473ebfdb-12d8-4ed9-b494-35da8c011130.png)

I learned about Yesterdays when they incorporated mosaics of Sanborn maps made in OldInsuranceMaps.net directly into their interface, which has proved an essential point of reference for placing historical photos. They&#39;ve done more georeferncing since to add more layers--John just georeferenced all of [1925, vol. 2](https://oldinsurancemaps.net/map/sanborn09064_007) in a couple of days by himself!

---

That&#39;s all for now, thanks for reading!

You can follow this project on Bluesky [@oldinsurancemaps](https://bsky.app/profile/oldinsurancemaps.net), or for folks on the [OpenStreetMap US Slack](https://openstreetmap.us/get-involved/slack/), find the new #oldinsurancemaps channel.
</source:markdown>
    </item>
    
    <item>
      <title>(Re)Introducing the MultiMask Interface</title>
      <link>https://blog.oldinsurancemaps.net/2025/11/30/reintroducing-the-multimask-interface/</link>
      <pubDate>Sun, 30 Nov 2025 19:00:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2025/12/01/reintroducing-the-multimask-interface/</guid>
      <description>&lt;p&gt;The &amp;ldquo;multimask&amp;rdquo; is a concept in &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt; that greatly eases the creation of seamless mosaics from many different georeferenced layers. I recently made some updates to the user interface for this tool, and decided to take the time to provide a better introduction to feature as a whole.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/pittsburgh-multimask.bz4jm5z7-356wq.webp&#34; width=&#34;600&#34; height=&#34;206&#34; alt=&#34;&#34;&gt;
&lt;h2 id=&#34;make-me-a-clean-mosaic&#34;&gt;Make me a clean mosaic&lt;/h2&gt;
&lt;p&gt;To understand how the multimask idea came about, consider that if you georeference all pages in a historical atlas, you&amp;rsquo;ll get something like this:&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/no-1908-vol2-nomasks.evyq7fmv-1ggjcu.webp&#34; width=&#34;600&#34; height=&#34;381&#34; alt=&#34;&#34;&gt;
&lt;p&gt;This is the historic French Quarter in New Orleans, as shown on 24 georeferenced pages from the &lt;a href=&#34;https://oldinsurancemaps.net/map/sanborn03376_010&#34;&gt;Sanborn map, Vol. 2, 1908&lt;/a&gt;. As you can see, while each individual layer would look fine on its own, when they are all displayed together in a single web map the margins from each sheet overlap each other. This obscures information on adjacent sheets, and, generally speaking, looks very messy.&lt;/p&gt;
&lt;p&gt;Instead, we want to see a seamless mosaic like this, so that we don&amp;rsquo;t lose information due overlapping pages, and as a single, clean layer, the mosaic becomes much easier to deal with.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/no-1908-vol2-masks2.b9byt-7f-z1hmj9g.webp&#34; width=&#34;600&#34; height=&#34;381&#34; alt=&#34;&#34;&gt;
&lt;p&gt;Removing the edges is achieved by cropping or masking each layer, but creating these masks is typically very time-consuming and tedious work. &lt;em&gt;OldInsuranceMaps.net&lt;/em&gt; uses a multimask to handle the task in a new way, and to understand why we&amp;rsquo;ll back up a couple of steps to how the overall workflow is put together (or you can just skip to the end of this post to see some nice animated GIFs I made last night).&lt;/p&gt;
&lt;h2 id=&#34;cropping-vs-splitting--trimming&#34;&gt;Cropping vs. splitting &amp;amp; trimming&lt;/h2&gt;
&lt;p&gt;It&amp;rsquo;s common in georeferencing workflows to use a two-step process:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Crop the image to remove unnecessary margins&lt;/li&gt;
&lt;li&gt;Georeference the cropped image&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If you are working with a single standalone map, as opposed to a map that is a single page of a multi-page atlas, then this is a sufficient approach. Set the mask in the beginning, and you&amp;rsquo;ll very likely have no reason to modify it later.&lt;/p&gt;
&lt;p&gt;However, with multi-page atlases, careful and fine adjustments to a mask may be needed &lt;em&gt;after&lt;/em&gt; the page has been georeferenced, once you see how it lines up with an adjacent layer. Depending on the details of how the mask is implemented, this crop ➞ georeference workflow may not lend itself well to making iterative adjustments.&lt;/p&gt;
&lt;p&gt;Another thing to consider is that it is fairly common to have multiple maps drawn on a single page, especially in these city-wide multi-page atlases. For example, &lt;a href=&#34;https://oldinsurancemaps.net/map/sanborn03267_002&#34;&gt;Alexandria, La., 1892&lt;/a&gt; is a Sanborn map with three sheets (shown below), each with a different number of distinct mapped areas: sheet one has four different regions, sheet two has two regions, and sheet three is one full-page map.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/preparation-examples3.cjrglbnq-1p5rlo.webp&#34; width=&#34;600&#34; height=&#34;241&#34; alt=&#34;&#34;&gt;
&lt;p&gt;It would be nice to deal with these using a pair of digital scissors, cutting or splitting each page until each map region stands on its own. Then each one of these seven pieces can be georeferenced individually.&lt;/p&gt;
&lt;p&gt;To recap then, we have 1) a need to handle multiple map regions within a given page, and 2) a need to carefully mask layers after they have been georeferenced, to properly accommodate the edges and masks of adjacent layers. These considerations led to the creation of a three-step workflow:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Split a page: define the individual geographic regions&lt;/li&gt;
&lt;li&gt;Georeference each region: create and apply ground control points&lt;/li&gt;
&lt;li&gt;Trim the layer: remove margins of each georeferenced region as desired&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Instead of crop ➞ georeference, where the first step both defines the region to georeference &lt;em&gt;and&lt;/em&gt; determines the final mask, split ➞ georeference ➞ trim fully separates these concerns, as they are now handled on either side of the actual georeferencing operation. While technically adding a step, this granularity actually creates a simpler and more efficient workflow.&lt;/p&gt;
&lt;h2 id=&#34;trimming-each-layer-by-itself-is-slow&#34;&gt;Trimming each layer by itself is slow&lt;/h2&gt;
&lt;p&gt;To facilitate this final trim step, &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt; originally implemented a &amp;ldquo;create a mask&amp;rdquo; interface that operated on a per-layer basis. Once an item had been georeferenced, you could add a mask (stored as GeoJSON), which allowed you to trim the margins from layers in a manner that was easy to modify and didn&amp;rsquo;t affect the existing georeferencing work.&lt;/p&gt;
&lt;figure&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/2022-02-01-22-25.cqetjqxb-z4is46.webp&#34; width=&#34;600&#34; height=&#34;380&#34; alt=&#34;&#34;&gt;
&lt;figcaption&gt;Screenshot of trimming interface from Feb 1st, 2022, when the pilot project went live.&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;However, it didn&amp;rsquo;t take long to realize that on a layer-by-layer basis this approach was cumbersome and practically unworkable. Even though it was easy to alter masks at any point because they were simply laid on top of the layers (and didn&amp;rsquo;t alter any files), doing so in an isolated environment provided no useful context for how to position one layer&amp;rsquo;s mask with regard to that of its neighbor.&lt;/p&gt;
&lt;h2 id=&#34;putting-it-all-together-multimask&#34;&gt;Putting it all together: Multimask&lt;/h2&gt;
&lt;p&gt;Eventually it became clear that there must be a better way to handle this whole trimming thing, and the key came down to changing the conceptual level at which the task was approached (which, as I think about it, is a theme throughout a lot of the platform&amp;rsquo;s tooling). &lt;em&gt;Instead of trimming each layer one at a time, let&amp;rsquo;s do them all at once!&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In practice, this looks like putting all layers on the map at once (see the messy image at the top of this post) and then selecting a layer, drawing a mask, then selecting the next layer, drawing a mask, and so on. This is more efficient simply because there is no moving between web pages to move on to the next layer, but with the design features shown below, things &lt;em&gt;really&lt;/em&gt; start to look different.&lt;/p&gt;
&lt;h3 id=&#34;snapping-as-a-core-value&#34;&gt;Snapping as a core value&lt;/h3&gt;
&lt;p&gt;One of the main challenges with creating adjacent masks is making sure that they line up exactly with each other. &lt;a href=&#34;https://openlayers.org&#34;&gt;OpenLayers&lt;/a&gt;, the web mapping library that &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt; uses throughout, has a very nice snapping capability, which is a key feature of the multimask interface.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-add-mask.drvyhwq7-1sai7v.webp&#34; width=&#34;600&#34; height=&#34;352&#34; alt=&#34;&#34;&gt;
&lt;p&gt;In the animation above, one sheet still needs to be masked, while all of its neighbors have already been handled. To create the mask for this final layer, you can just click, click, click, snapping to all adjacent vertices. Upon completion (double-click on the last point) a mask is created and applied to the layer immediately. This new mask shares exact vertices with all of its neighbors, guaranteeing seamless coverage and shared boundaries between layers.&lt;/p&gt;
&lt;h3 id=&#34;masks-make-a-fabric&#34;&gt;Masks make a fabric&lt;/h3&gt;
&lt;p&gt;Many great things happen when you can use snapping. Not only is it easy to create masks quickly, but once multiple masks share the same vertex, any alterations to that vertex affect each mask.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-move-vertex.prpdqwt-z14cyxe.webp&#34; width=&#34;600&#34; height=&#34;347&#34; alt=&#34;&#34;&gt;
&lt;p&gt;For example, if four masks share a corner, moving that corner vertex will change all of them at once.&lt;/p&gt;
&lt;h3 id=&#34;what-is-that-street-name&#34;&gt;What is that street name?&lt;/h3&gt;
&lt;p&gt;Fine-tuning the boundaries between different sheets is necessary when there are certain details at the edge of one layer that should be masked around to ensure that important information isn&amp;rsquo;t lost. Making small adjustments like this is very easy because adding a vertex to a shared boundary automatically applies it to both masks.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-fine-tune.b9ikbwfm-zxhn6e.webp&#34; width=&#34;600&#34; height=&#34;347&#34; alt=&#34;&#34;&gt;
&lt;p&gt;In some cases, two neighboring sheets may have the name of the same street in very close proximity to each after they have been georeferenced, so you&amp;rsquo;ll want to reveal that street name from on layer and hide it from the other.&lt;/p&gt;
&lt;h3 id=&#34;using-colors-for-quality-control&#34;&gt;Using colors for quality control&lt;/h3&gt;
&lt;p&gt;Until recently, all vertices were white within the multimask interface, but a couple months ago I &lt;a href=&#34;https://github.com/ohmg-dev/OldInsuranceMaps/pull/306&#34;&gt;added something&lt;/a&gt; I had had in mind for a while: color-coding. If a vertex stands on its own, it is white, but if it has been snapped to another vertex it is green. This is especially helpful for cleaning up internal vertices that should be snapped together but for some reason haven&amp;rsquo;t been.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-fix-inner.rzibcl2h-z15ybkk.webp&#34; width=&#34;600&#34; height=&#34;347&#34; alt=&#34;&#34;&gt;
&lt;p&gt;There are plenty of cases in which a vertex will legitimately stand on its own, like an exterior corner, or even internally where edges of sheets don&amp;rsquo;t actually overlap. But having this new visual cue makes comprehensive cleanup efforts much easier to do.&lt;/p&gt;
&lt;h2 id=&#34;some-final-thoughts&#34;&gt;Some final thoughts&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;There is still some clunkiness with how the whole interface works, and capabilities I hope to add in the coming year. So stay tuned!&lt;/li&gt;
&lt;li&gt;A foundational characteristic of the &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt; data model is &lt;em&gt;layersets&lt;/em&gt;, not covered here at all, which are thematic categories of cartographic content within a given atlas and the context within which a multimask is created and applied. A topic for a future post&amp;hellip;&lt;/li&gt;
&lt;li&gt;Creating masks is not only about trimming margins&amp;ndash;masks are also precise vector features that define the coverage area of every single layer. These boundaries can by used in many different ways, for example &lt;a href=&#34;https://observablehq.com/@mradamcox/interactive-map-mosaic&#34;&gt;this interactive mosaic demo I made many years ago&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Many thanks as always to the developers behind OpenLayers and &lt;a href=&#34;https://viglino.github.io/ol-ext/&#34;&gt;this set of extensions&lt;/a&gt;, the Crop filter from which makes this whole idea possible.&lt;/li&gt;
&lt;/ul&gt;
</description>
      <source:markdown>The &#34;multimask&#34; is a concept in [OldInsuranceMaps.net](http://OldInsuranceMaps.net) that greatly eases the creation of seamless mosaics from many different georeferenced layers. I recently made some updates to the user interface for this tool, and decided to take the time to provide a better introduction to feature as a whole.

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/pittsburgh-multimask.bz4jm5z7-356wq.webp&#34; width=&#34;600&#34; height=&#34;206&#34; alt=&#34;&#34;&gt;

## Make me a clean mosaic

To understand how the multimask idea came about, consider that if you georeference all pages in a historical atlas, you&#39;ll get something like this:

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/no-1908-vol2-nomasks.evyq7fmv-1ggjcu.webp&#34; width=&#34;600&#34; height=&#34;381&#34; alt=&#34;&#34;&gt;

This is the historic French Quarter in New Orleans, as shown on 24 georeferenced pages from the [Sanborn map, Vol. 2, 1908](https://oldinsurancemaps.net/map/sanborn03376_010). As you can see, while each individual layer would look fine on its own, when they are all displayed together in a single web map the margins from each sheet overlap each other. This obscures information on adjacent sheets, and, generally speaking, looks very messy.

Instead, we want to see a seamless mosaic like this, so that we don&#39;t lose information due overlapping pages, and as a single, clean layer, the mosaic becomes much easier to deal with.

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/no-1908-vol2-masks2.b9byt-7f-z1hmj9g.webp&#34; width=&#34;600&#34; height=&#34;381&#34; alt=&#34;&#34;&gt;

Removing the edges is achieved by cropping or masking each layer, but creating these masks is typically very time-consuming and tedious work. _OldInsuranceMaps.net_ uses a multimask to handle the task in a new way, and to understand why we&#39;ll back up a couple of steps to how the overall workflow is put together (or you can just skip to the end of this post to see some nice animated GIFs I made last night).

## Cropping vs. splitting &amp; trimming

It&#39;s common in georeferencing workflows to use a two-step process:

1. Crop the image to remove unnecessary margins    
2. Georeference the cropped image

If you are working with a single standalone map, as opposed to a map that is a single page of a multi-page atlas, then this is a sufficient approach. Set the mask in the beginning, and you&#39;ll very likely have no reason to modify it later.

However, with multi-page atlases, careful and fine adjustments to a mask may be needed _after_ the page has been georeferenced, once you see how it lines up with an adjacent layer. Depending on the details of how the mask is implemented, this crop ➞ georeference workflow may not lend itself well to making iterative adjustments.

Another thing to consider is that it is fairly common to have multiple maps drawn on a single page, especially in these city-wide multi-page atlases. For example, [Alexandria, La., 1892](https://oldinsurancemaps.net/map/sanborn03267_002) is a Sanborn map with three sheets (shown below), each with a different number of distinct mapped areas: sheet one has four different regions, sheet two has two regions, and sheet three is one full-page map.

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/preparation-examples3.cjrglbnq-1p5rlo.webp&#34; width=&#34;600&#34; height=&#34;241&#34; alt=&#34;&#34;&gt;

It would be nice to deal with these using a pair of digital scissors, cutting or splitting each page until each map region stands on its own. Then each one of these seven pieces can be georeferenced individually.

To recap then, we have 1) a need to handle multiple map regions within a given page, and 2) a need to carefully mask layers after they have been georeferenced, to properly accommodate the edges and masks of adjacent layers. These considerations led to the creation of a three-step workflow:

1.  Split a page: define the individual geographic regions
2.  Georeference each region: create and apply ground control points
3.  Trim the layer: remove margins of each georeferenced region as desired 

Instead of crop ➞ georeference, where the first step both defines the region to georeference _and_ determines the final mask, split ➞ georeference ➞ trim fully separates these concerns, as they are now handled on either side of the actual georeferencing operation. While technically adding a step, this granularity actually creates a simpler and more efficient workflow.

## Trimming each layer by itself is slow

To facilitate this final trim step, [OldInsuranceMaps.net](http://OldInsuranceMaps.net) originally implemented a &#34;create a mask&#34; interface that operated on a per-layer basis. Once an item had been georeferenced, you could add a mask (stored as GeoJSON), which allowed you to trim the margins from layers in a manner that was easy to modify and didn&#39;t affect the existing georeferencing work.

&lt;figure&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/2022-02-01-22-25.cqetjqxb-z4is46.webp&#34; width=&#34;600&#34; height=&#34;380&#34; alt=&#34;&#34;&gt;
&lt;figcaption&gt;Screenshot of trimming interface from Feb 1st, 2022, when the pilot project went live.&lt;/figcaption&gt;
&lt;/figure&gt;

However, it didn&#39;t take long to realize that on a layer-by-layer basis this approach was cumbersome and practically unworkable. Even though it was easy to alter masks at any point because they were simply laid on top of the layers (and didn&#39;t alter any files), doing so in an isolated environment provided no useful context for how to position one layer&#39;s mask with regard to that of its neighbor.

## Putting it all together: Multimask

Eventually it became clear that there must be a better way to handle this whole trimming thing, and the key came down to changing the conceptual level at which the task was approached (which, as I think about it, is a theme throughout a lot of the platform&#39;s tooling). _Instead of trimming each layer one at a time, let&#39;s do them all at once!_

In practice, this looks like putting all layers on the map at once (see the messy image at the top of this post) and then selecting a layer, drawing a mask, then selecting the next layer, drawing a mask, and so on. This is more efficient simply because there is no moving between web pages to move on to the next layer, but with the design features shown below, things _really_ start to look different.

### Snapping as a core value

One of the main challenges with creating adjacent masks is making sure that they line up exactly with each other. [OpenLayers](https://openlayers.org), the web mapping library that [OldInsuranceMaps.net](http://OldInsuranceMaps.net) uses throughout, has a very nice snapping capability, which is a key feature of the multimask interface.

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-add-mask.drvyhwq7-1sai7v.webp&#34; width=&#34;600&#34; height=&#34;352&#34; alt=&#34;&#34;&gt;

In the animation above, one sheet still needs to be masked, while all of its neighbors have already been handled. To create the mask for this final layer, you can just click, click, click, snapping to all adjacent vertices. Upon completion (double-click on the last point) a mask is created and applied to the layer immediately. This new mask shares exact vertices with all of its neighbors, guaranteeing seamless coverage and shared boundaries between layers.

### Masks make a fabric

Many great things happen when you can use snapping. Not only is it easy to create masks quickly, but once multiple masks share the same vertex, any alterations to that vertex affect each mask.

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-move-vertex.prpdqwt-z14cyxe.webp&#34; width=&#34;600&#34; height=&#34;347&#34; alt=&#34;&#34;&gt;

For example, if four masks share a corner, moving that corner vertex will change all of them at once.

### What is that street name?

Fine-tuning the boundaries between different sheets is necessary when there are certain details at the edge of one layer that should be masked around to ensure that important information isn&#39;t lost. Making small adjustments like this is very easy because adding a vertex to a shared boundary automatically applies it to both masks.

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-fine-tune.b9ikbwfm-zxhn6e.webp&#34; width=&#34;600&#34; height=&#34;347&#34; alt=&#34;&#34;&gt;

In some cases, two neighboring sheets may have the name of the same street in very close proximity to each after they have been georeferenced, so you&#39;ll want to reveal that street name from on layer and hide it from the other.

### Using colors for quality control

Until recently, all vertices were white within the multimask interface, but a couple months ago I [added something](https://github.com/ohmg-dev/OldInsuranceMaps/pull/306) I had had in mind for a while: color-coding. If a vertex stands on its own, it is white, but if it has been snapped to another vertex it is green. This is especially helpful for cleaning up internal vertices that should be snapped together but for some reason haven&#39;t been.

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-fix-inner.rzibcl2h-z15ybkk.webp&#34; width=&#34;600&#34; height=&#34;347&#34; alt=&#34;&#34;&gt;

There are plenty of cases in which a vertex will legitimately stand on its own, like an exterior corner, or even internally where edges of sheets don&#39;t actually overlap. But having this new visual cue makes comprehensive cleanup efforts much easier to do.

## Some final thoughts

- There is still some clunkiness with how the whole interface works, and capabilities I hope to add in the coming year. So stay tuned!
- A foundational characteristic of the [OldInsuranceMaps.net](http://OldInsuranceMaps.net) data model is _layersets_, not covered here at all, which are thematic categories of cartographic content within a given atlas and the context within which a multimask is created and applied. A topic for a future post...
- Creating masks is not only about trimming margins--masks are also precise vector features that define the coverage area of every single layer. These boundaries can by used in many different ways, for example [this interactive mosaic demo I made many years ago](https://observablehq.com/@mradamcox/interactive-map-mosaic).
- Many thanks as always to the developers behind OpenLayers and [this set of extensions](https://viglino.github.io/ol-ext/), the Crop filter from which makes this whole idea possible.
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: Fall 2025 - Upcoming Events</title>
      <link>https://blog.oldinsurancemaps.net/2025/09/12/newsletter-fall-upcoming-events/</link>
      <pubDate>Fri, 12 Sep 2025 13:09:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2025/09/12/newsletter-fall-upcoming-events/</guid>
      <description>&lt;h2 id=&#34;georeference-a-thons-in-new-orleans&#34;&gt;Georeference-a-thons in New Orleans&lt;/h2&gt;
&lt;p&gt;Over the next couple of weeks we&amp;rsquo;ll be holding two community georeferencing events at Second Line Brewing in New Orleans. If you are in the area, we hope you can make it!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Dates: Tuesday Sept 16th &amp;amp; Tuesday Sept 23rd&lt;/li&gt;
&lt;li&gt;Time: 6:30-8:30pm&lt;/li&gt;
&lt;li&gt;Location: Second Line Brewing, 433 N Bernadotte St&lt;/li&gt;
&lt;li&gt;RSVP Form: &lt;a href=&#34;https://tiny.cc/georef-2025&#34;&gt;https://tiny.cc/georef-2025&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;As we have in the past, we&amp;rsquo;re doing these events in collaboration with the Midlo Center and HistoryForge. We&amp;rsquo;ll be starting work on the 1895 Vol. 2 Sanborn Map (which covers the CBD and more), and, excitingly, Elizabeth from the Midlo Center will also talk about the archaeological work they have been doing this summer in Duncan Plaza. We hope you can join!&lt;/p&gt;
&lt;h3 id=&#34;front-end-party&#34;&gt;Front-end Party!&lt;/h3&gt;
&lt;p&gt;In early October I&amp;rsquo;ll be doing a talk and activity for the wonderful Front-end Party software developer meetup here in New Orleans. Exact details TBD (they&amp;rsquo;ll be &lt;a href=&#34;https://www.noladevs.org/&#34;&gt;here&lt;/a&gt; eventually), but I&amp;rsquo;m really looking forward to getting some hack-a-thon action only weeks after all of these georeference-a-thons. Hopefully we&amp;rsquo;ll have some fun web maps to share by the end!&lt;/p&gt;
&lt;h3 id=&#34;thats-all-for-now&#34;&gt;That&amp;rsquo;s all for now!&lt;/h3&gt;
&lt;p&gt;But, one fun little detail, a couple weeks ago I added &amp;ldquo;duration&amp;rdquo; as a column to the &lt;a href=&#34;https://oldinsurancemaps.net/activity&#34;&gt;Activity page&lt;/a&gt;. This is how long someone has the &amp;ldquo;split&amp;rdquo; or &amp;ldquo;georeferencing&amp;rdquo; interface open when they are performing one of those tasks. Fun to see, eventually I&amp;rsquo;ll aggregate these durations for average time per sheet, etc. Also, there are sorting and filtering options on that table and many others within the site. Progress, slowly&amp;hellip;&lt;/p&gt;
&lt;p&gt;Until next time!&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;
</description>
      <source:markdown>## Georeference-a-thons in New Orleans

Over the next couple of weeks we&#39;ll be holding two community georeferencing events at Second Line Brewing in New Orleans. If you are in the area, we hope you can make it!

- Dates: Tuesday Sept 16th &amp; Tuesday Sept 23rd
- Time: 6:30-8:30pm
- Location: Second Line Brewing, 433 N Bernadotte St
- RSVP Form: [https://tiny.cc/georef-2025](https://tiny.cc/georef-2025)

As we have in the past, we&#39;re doing these events in collaboration with the Midlo Center and HistoryForge. We&#39;ll be starting work on the 1895 Vol. 2 Sanborn Map (which covers the CBD and more), and, excitingly, Elizabeth from the Midlo Center will also talk about the archaeological work they have been doing this summer in Duncan Plaza. We hope you can join!

### Front-end Party!

In early October I&#39;ll be doing a talk and activity for the wonderful Front-end Party software developer meetup here in New Orleans. Exact details TBD (they&#39;ll be [here](https://www.noladevs.org/) eventually), but I&#39;m really looking forward to getting some hack-a-thon action only weeks after all of these georeference-a-thons. Hopefully we&#39;ll have some fun web maps to share by the end!

### That&#39;s all for now!

But, one fun little detail, a couple weeks ago I added &#34;duration&#34; as a column to the [Activity page](https://oldinsurancemaps.net/activity). This is how long someone has the &#34;split&#34; or &#34;georeferencing&#34; interface open when they are performing one of those tasks. Fun to see, eventually I&#39;ll aggregate these durations for average time per sheet, etc. Also, there are sorting and filtering options on that table and many others within the site. Progress, slowly...

Until next time!

Adam
</source:markdown>
    </item>
    
    <item>
      <title>Using GDAL&#39;s VRTs for Georeferencing, from &#34;A look inside OldInsuranceMaps.net&#34;</title>
      <link>https://blog.oldinsurancemaps.net/2025/08/08/using-gdals-vrts-for-georeferencing/</link>
      <pubDate>Fri, 08 Aug 2025 18:00:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2025/08/08/using-gdals-vrts-for-georeferencing/</guid>
      <description>&lt;p&gt;Recently I gave a presentation about &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt; for &lt;a href=&#34;https://i-guide.io/i-guide-vco/&#34;&gt;I-GUIDE&amp;rsquo;s Virtual Consulting Office&lt;/a&gt; speaker series and I was able to talk a bit more about the technical details of the platform than I have in the past, which was really fun and a great excuse to make some more diagrams. One element of the system I described is the way that the georeferencing process relies on &lt;a href=&#34;https://gdal.org/en/stable/drivers/raster/vrt.html&#34;&gt;GDAL&amp;rsquo;s &amp;ldquo;virtual raster&amp;rdquo;&lt;/a&gt; driver (i.e. file format), and how this is used for, among other things, the live preview feature of the georeferencing interface. Here&amp;rsquo;s a short summary of that part of the talk with a few relevant slides. For more, you can &lt;a href=&#34;https://i-guide.io/i-guide-vco/a-look-inside-oldinsurancemaps/&#34;&gt;view the full recording&lt;/a&gt;, or find the &lt;a href=&#34;https://docs.google.com/presentation/d/1zv23HALxZ_3VP8ox3Mr089qDxOn4mNrO2zOKWKsseiA/edit?usp=sharing&#34;&gt;slides here&lt;/a&gt; (note, I&amp;rsquo;ve updated some of them a bit since the recording).&lt;/p&gt;
&lt;p&gt;The basic georeferencing process, which turns a non-spatial image into a geospatial dataset, works by chaining two VRTs together and then writing out a GeoTIFF (specifically, a Cloud-Optimized GeoTIFF, or &amp;ldquo;COG&amp;rdquo;). The first VRT references the original image and embeds the user-submitted ground control points (GCPs). The second VRT references the first VRT, and embeds the warping information (which transformation to use). The final step is a GDAL translation process which turns the warped VRT into an actual COG.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/make-cog1.webp&#34; width=&#34;600&#34; height=&#34;336&#34; alt=&#34;&#34;&gt;
&lt;p&gt;Importantly, a VRT is just a small XML file, so creating one is nearly instantaneous and requires virtually no storage space. In OldInsuranceMaps, they are also disposable, as the actual database stores all of the information that gets embedded into them. They can be recreated on demand and then deleted after they are no longer needed.&lt;/p&gt;
&lt;p&gt;With this in mind, the live preview that is presented in the georeferencing interface is created by injecting user-generated information directly into the VRT linkage chain, and updating that information on GCP creation or modification using a feedback loop. Creating this preview is actually very simple, because TiTiler, and MapServer which I used in the original implementation of this feature, can read and tile data directly from a VRT&amp;ndash;no need to actually generate a GeoTIFF.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/cog-vrt-preview.webp&#34; width=&#34;600&#34; height=&#34;336&#34; alt=&#34;&#34;&gt;
&lt;p&gt;Finally, to create the mosaics that are the ultimate end goal of the entire system, even more VRTs are added. First, on top of the warped VRT a new one is created that incorporates the layer&amp;rsquo;s mask, drawn by users through a unified, &amp;ldquo;multimask&amp;rdquo; interface. Then, all of the cropped VRTs are wrapped up into a single mosaicked VRT (mosiacking is actually what VRTs are most commonly used for), and that final VRT is then translated into a single (sometimes quite large) COG.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-move-vertex.prpdqwt-z14cyxe.webp&#34; width=&#34;600&#34; height=&#34;347&#34; alt=&#34;&#34;&gt;
&lt;p&gt;There is even more you can do with this concept of chaining VRTs together, for example enabling the support of custom projections during the georeferencing process. Sanborn Maps are all very large-scale, so warping to a non-Web Mercator projection isn&amp;rsquo;t necessary or useful. But I have implemented and tested this idea out with much smaller-scale maps that were drawn in a non-Mercator projection, and it works flawlessly. I described the concept in more detail in &lt;a href=&#34;https://github.com/cogeotiff/rio-tiler/discussions/565#discussioncomment-5844734&#34;&gt;this old comment on GitHub&lt;/a&gt;, and hope to properly implement it on the platform someday.&lt;/p&gt;
</description>
      <source:markdown>Recently I gave a presentation about [OldInsuranceMaps.net](http://OldInsuranceMaps.net) for [I-GUIDE&#39;s Virtual Consulting Office](https://i-guide.io/i-guide-vco/) speaker series and I was able to talk a bit more about the technical details of the platform than I have in the past, which was really fun and a great excuse to make some more diagrams. One element of the system I described is the way that the georeferencing process relies on [GDAL&#39;s &#34;virtual raster&#34;](https://gdal.org/en/stable/drivers/raster/vrt.html) driver (i.e. file format), and how this is used for, among other things, the live preview feature of the georeferencing interface. Here&#39;s a short summary of that part of the talk with a few relevant slides. For more, you can [view the full recording](https://i-guide.io/i-guide-vco/a-look-inside-oldinsurancemaps/), or find the [slides here](https://docs.google.com/presentation/d/1zv23HALxZ_3VP8ox3Mr089qDxOn4mNrO2zOKWKsseiA/edit?usp=sharing) (note, I&#39;ve updated some of them a bit since the recording).

The basic georeferencing process, which turns a non-spatial image into a geospatial dataset, works by chaining two VRTs together and then writing out a GeoTIFF (specifically, a Cloud-Optimized GeoTIFF, or &#34;COG&#34;). The first VRT references the original image and embeds the user-submitted ground control points (GCPs). The second VRT references the first VRT, and embeds the warping information (which transformation to use). The final step is a GDAL translation process which turns the warped VRT into an actual COG.

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/make-cog1.webp&#34; width=&#34;600&#34; height=&#34;336&#34; alt=&#34;&#34;&gt;

Importantly, a VRT is just a small XML file, so creating one is nearly instantaneous and requires virtually no storage space. In OldInsuranceMaps, they are also disposable, as the actual database stores all of the information that gets embedded into them. They can be recreated on demand and then deleted after they are no longer needed.

With this in mind, the live preview that is presented in the georeferencing interface is created by injecting user-generated information directly into the VRT linkage chain, and updating that information on GCP creation or modification using a feedback loop. Creating this preview is actually very simple, because TiTiler, and MapServer which I used in the original implementation of this feature, can read and tile data directly from a VRT--no need to actually generate a GeoTIFF.

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/cog-vrt-preview.webp&#34; width=&#34;600&#34; height=&#34;336&#34; alt=&#34;&#34;&gt;

Finally, to create the mosaics that are the ultimate end goal of the entire system, even more VRTs are added. First, on top of the warped VRT a new one is created that incorporates the layer&#39;s mask, drawn by users through a unified, &#34;multimask&#34; interface. Then, all of the cropped VRTs are wrapped up into a single mosaicked VRT (mosiacking is actually what VRTs are most commonly used for), and that final VRT is then translated into a single (sometimes quite large) COG.

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/mm-move-vertex.prpdqwt-z14cyxe.webp&#34; width=&#34;600&#34; height=&#34;347&#34; alt=&#34;&#34;&gt;

There is even more you can do with this concept of chaining VRTs together, for example enabling the support of custom projections during the georeferencing process. Sanborn Maps are all very large-scale, so warping to a non-Web Mercator projection isn&#39;t necessary or useful. But I have implemented and tested this idea out with much smaller-scale maps that were drawn in a non-Mercator projection, and it works flawlessly. I described the concept in more detail in [this old comment on GitHub](https://github.com/cogeotiff/rio-tiler/discussions/565#discussioncomment-5844734), and hope to properly implement it on the platform someday.
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: Summer 2025</title>
      <link>https://blog.oldinsurancemaps.net/2025/07/15/newsletter-summer/</link>
      <pubDate>Tue, 15 Jul 2025 07:38:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2025/07/15/newsletter-summer/</guid>
      <description>&lt;p&gt;Hello all! Writing to tell you about a few things that have happened in the last few months, and some upcoming news.&lt;/p&gt;
&lt;p&gt;For new readers: Welcome! You can find all past newsletters &lt;a href=&#34;https://oldinsurancemaps.net/news/&#34;&gt;in the archive&lt;/a&gt;. You can also respond directly to this email to say hello, and you&amp;rsquo;ll find an unsubscribe link below.&lt;/p&gt;
&lt;h3 id=&#34;online-presentation-for-i-guide-vco-series-tomorrow&#34;&gt;Online presentation for I-GUIDE VCO series, tomorrow!&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Wednesday 7/16, 11am US Central Time &amp;ndash; &lt;a href=&#34;https://i-guide.io/i-guide-vco/a-look-inside-oldinsurancemaps&#34;&gt;registration link&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Apologies for the late notice. Tomorrow I&amp;rsquo;ll be giving an online presentation as part of &lt;a href=&#34;https://i-guide.io/i-guide-vco/&#34;&gt;I-GUIDE&amp;rsquo;s Virtual Consulting Office&lt;/a&gt; showcase series. I&amp;rsquo;m really looking forward to this, as I&amp;rsquo;ll be able to get into some of the more technical details of the platform, and there should be plenty of time for Q&amp;amp;A as well. Registration is free and open to everyone! Big thank you to Alex Michels for organizing these talks.&lt;/p&gt;
&lt;p&gt;Also, &lt;em&gt;next week&lt;/em&gt; I&amp;rsquo;ll be co-presenting in the same forum with my colleagues from the Healthy Regions &amp;amp; Policies Lab about our work on the &lt;a href=&#34;https://sdohplace.org/search&#34;&gt;SDOH &amp;amp; Place Data Discovery&lt;/a&gt; application. Come to that one too for something completely different!&lt;/p&gt;
&lt;h3 id=&#34;results-of-a-past-georeference-a-thon&#34;&gt;Results of a past georeference-a-thon&lt;/h3&gt;
&lt;p&gt;This past April, Rowan University&amp;rsquo;s &lt;a href=&#34;https://chss.rowan.edu/centers/cdhr/&#34;&gt;Center for Digital Humanities Research&lt;/a&gt; hosted the largest georeferencing event that the site has facilitated to date. Over the course of an afternoon, 50 new people made accounts and georeferenced over 250 layers, covering a number of towns around Glassboro, New Jersey. It really had the server churning, slowed things down a bit for sure, but nothing broke. Read more about it in &lt;a href=&#34;thewhitonline.com/80663/features/rowans-center-for-digital-humanities-research-hosts-first-ever-map-a-thon/&#34;&gt;the Whit&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;website-content-reshuffle-and-new-blog&#34;&gt;Website content reshuffle and new Blog&lt;/h3&gt;
&lt;p&gt;I&amp;rsquo;ve accumulated content about OldInsuranceMaps.net in a few different places, and web analytics show that no one really looks at it. So, a couple weeks ago I bribed my wife with pizza and we spent some time figuring out how to reorganize. I&amp;rsquo;ve done my best to see these changes through over the last couple of weekends, and they aren&amp;rsquo;t complete, but&amp;hellip;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;New Blog! &lt;a href=&#34;https://blog.oldinsurancemaps.net&#34;&gt;blog.oldinsurancemaps.net&lt;/a&gt;&lt;/strong&gt; I&amp;rsquo;ll be transferring all kinds of pieces from different places into this blog, and it&amp;rsquo;ll be the best place to stay up-to-date on the project and see how it&amp;rsquo;s developed over time. I put a lot of entries in already (back-posting as if I&amp;rsquo;d been writing in it for years), and will continue to do that until I can&amp;rsquo;t think of anything more to add. Let me know if you have suggestions! (This newsletter isn&amp;rsquo;t going away though.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;More content on the main website&lt;/strong&gt; A while ago I created &lt;a href=&#34;https://about.oldInsuranceMaps.net&#34;&gt;about.oldinsurancemaps.net&lt;/a&gt; with documentation, background, and guides on it, but that content has remained somewhat obscure and much of it would be better housed directly within the main website itself. So, with a bit of an update to the main site&amp;rsquo;s structure, I&amp;rsquo;m beginning to transfer it over and that site will eventually go away. Still a work in progress, but finally on the way.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;and-a-final-tech-note&#34;&gt;And a final tech note&amp;hellip;&lt;/h3&gt;
&lt;p&gt;OldInsuranceMaps.net now stores all of its geotiffs in S3 object storage! In other words, there is a lot more space for new maps. This is a backend change that really opens the door for future work&amp;hellip; Not a difference you would notice from looking at the website, but for more information you can checkout &lt;a href=&#34;https://blog.oldinsurancemaps.net/post/2025-06-29-implementing-s3-storage/&#34;&gt;this blog post&lt;/a&gt; (on the new blog!).&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s all for now, hope to see some of you tomorrow morning,&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;
</description>
      <source:markdown>Hello all! Writing to tell you about a few things that have happened in the last few months, and some upcoming news.

For new readers: Welcome! You can find all past newsletters [in the archive](https://oldinsurancemaps.net/news/). You can also respond directly to this email to say hello, and you&#39;ll find an unsubscribe link below.

### Online presentation for I-GUIDE VCO series, tomorrow!

**Wednesday 7/16, 11am US Central Time -- [registration link](https://i-guide.io/i-guide-vco/a-look-inside-oldinsurancemaps)**

Apologies for the late notice. Tomorrow I&#39;ll be giving an online presentation as part of [I-GUIDE&#39;s Virtual Consulting Office](https://i-guide.io/i-guide-vco/) showcase series. I&#39;m really looking forward to this, as I&#39;ll be able to get into some of the more technical details of the platform, and there should be plenty of time for Q&amp;A as well. Registration is free and open to everyone! Big thank you to Alex Michels for organizing these talks.

Also, _next week_ I&#39;ll be co-presenting in the same forum with my colleagues from the Healthy Regions &amp; Policies Lab about our work on the [SDOH &amp; Place Data Discovery](https://sdohplace.org/search) application. Come to that one too for something completely different!

### Results of a past georeference-a-thon

This past April, Rowan University&#39;s [Center for Digital Humanities Research](https://chss.rowan.edu/centers/cdhr/) hosted the largest georeferencing event that the site has facilitated to date. Over the course of an afternoon, 50 new people made accounts and georeferenced over 250 layers, covering a number of towns around Glassboro, New Jersey. It really had the server churning, slowed things down a bit for sure, but nothing broke. Read more about it in [the Whit](thewhitonline.com/80663/features/rowans-center-for-digital-humanities-research-hosts-first-ever-map-a-thon/).

### Website content reshuffle and new Blog

I&#39;ve accumulated content about OldInsuranceMaps.net in a few different places, and web analytics show that no one really looks at it. So, a couple weeks ago I bribed my wife with pizza and we spent some time figuring out how to reorganize. I&#39;ve done my best to see these changes through over the last couple of weekends, and they aren&#39;t complete, but...

- **New Blog! [blog.oldinsurancemaps.net](https://blog.oldinsurancemaps.net)** I&#39;ll be transferring all kinds of pieces from different places into this blog, and it&#39;ll be the best place to stay up-to-date on the project and see how it&#39;s developed over time. I put a lot of entries in already (back-posting as if I&#39;d been writing in it for years), and will continue to do that until I can&#39;t think of anything more to add. Let me know if you have suggestions! (This newsletter isn&#39;t going away though.)
- **More content on the main website** A while ago I created [about.oldinsurancemaps.net](https://about.oldInsuranceMaps.net) with documentation, background, and guides on it, but that content has remained somewhat obscure and much of it would be better housed directly within the main website itself. So, with a bit of an update to the main site&#39;s structure, I&#39;m beginning to transfer it over and that site will eventually go away. Still a work in progress, but finally on the way.

### And a final tech note...

OldInsuranceMaps.net now stores all of its geotiffs in S3 object storage! In other words, there is a lot more space for new maps. This is a backend change that really opens the door for future work... Not a difference you would notice from looking at the website, but for more information you can checkout [this blog post](https://blog.oldinsurancemaps.net/post/2025-06-29-implementing-s3-storage/) (on the new blog!).

That&#39;s all for now, hope to see some of you tomorrow morning,

Adam
</source:markdown>
    </item>
    
    <item>
      <title>Implementing S3 Object Storage</title>
      <link>https://blog.oldinsurancemaps.net/2025/06/28/implementing-s-object-storage/</link>
      <pubDate>Sat, 28 Jun 2025 19:00:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2025/06/29/implementing-s-object-storage/</guid>
      <description>&lt;h2 id=&#34;what-is-s3-object-storage&#34;&gt;What is S3 Object Storage?&lt;/h2&gt;
&lt;p&gt;S3 object storage is a protocol developed by Amazon Web Services for handling file storage outside of a normal server environment and &amp;ldquo;in the cloud&amp;rdquo; instead. In other words, it&amp;rsquo;s a simplified way of uploading, downloading, or directly accessing files that are stored in remote &amp;ldquo;buckets&amp;rdquo;. In these buckets, storage is (broadly speaking) very cheap and practically unlimited. Many other companies have since adopted the S3 API so their own cloud storage offerings are compatible with it.&lt;/p&gt;
&lt;h2 id=&#34;implementing-a-new-storage-backend&#34;&gt;Implementing a new storage backend&lt;/h2&gt;
&lt;p&gt;To this point, &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt; has functioned by downloading image files from the Library of Congress (or other sources, in certain contexts) and storing those files on the main server. Once the images are available locally, the splitting, georeferencing, and mosaicking operations are performed directly on those files, creating even more files (ultimately, &lt;a href=&#34;https://cogeo.org/&#34;&gt;Cloud Optimized GeoTIFFs&lt;/a&gt;) on the server. Really, the entire point the platform is to build tools and workflows around the creation and management of these files.&lt;/p&gt;
&lt;p&gt;One downside to this approach is that the server has limited storage space, let&amp;rsquo;s say about 500gb. This has been plenty for the last few years (especially as &lt;a href=&#34;https://github.com/ohmg-dev/OldInsuranceMaps/pull/145&#34;&gt;I&amp;rsquo;ve implemented better compression methods&lt;/a&gt; over time) but as available space inevitably diminishes, I decided it was finally time to progress to a new storage strategy.&lt;/p&gt;
&lt;p&gt;To implement S3 storage for all content in OIM, there were two general tasks:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Update the code base to work with remotely stored content instead of relying on files on disk&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Upload all existing content to an S3 bucket&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;How much existing content? Well, quite a lot. After a big server cleanup effort (this was the first time I had comprehensively dealt with all kinds of orphan files and remnants from past experiments) there were &lt;em&gt;roughly&lt;/em&gt; 130,000 files using about 430gb of disk space.&lt;/p&gt;
&lt;p&gt;There were also a couple of important constraints to work around:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;S3 storage needs to be optional, so that future installations of the code base can run just using local file storage&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Gotta keep the site running! There is a bit of operational inertia that must be respected on the platform, now that there is a lot of content on it and people using it everyday. Practically speaking, this means making slow, incremental steps.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&#34;code-compatibility&#34;&gt;Code compatibility&lt;/h3&gt;
&lt;p&gt;OIM is built with the Django web framework, and there is a solid, standardized way for implementing S3 storage using &lt;a href=&#34;https://django-storages.readthedocs.io/en/latest/backends/amazon-S3.html&#34;&gt;django-storages.&lt;/a&gt; In theory then, the storages plugin could be installed, a switch could be flipped, and violá, Django will read and write to an S3 bucket instead of the local file system.&lt;/p&gt;
&lt;p&gt;However, it wasn&amp;rsquo;t that simple. Due to the fact that a lot of splitting, georeferencing, and mosaicking operations had been built with the expectation of local file storage, some of them failed once S3 got involved. Luckily, GDAL (on which OIM has relied from the start) has a &lt;a href=&#34;https://gdal.org/en/stable/user/virtual_file_systems.html&#34;&gt;fantastic virtual file system&lt;/a&gt; that allows it to read directly from S3 urls, and combining that with another GDAL feature, &lt;a href=&#34;https://gdal.org/en/stable/drivers/raster/vrt.html&#34;&gt;virtual rasters or VRTs&lt;/a&gt;, offered plenty of flexibility to work with. Ultimately, the implementation required rewriting and improving some basic functions at the core of the app, but produced a better code base in the end. If you are interested, you can read all the gory details in &lt;a href=&#34;https://github.com/ohmg-dev/OldInsuranceMaps/pull/280&#34;&gt;this pull request&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;syncing-the-content&#34;&gt;Syncing the content&lt;/h3&gt;
&lt;p&gt;With the code updated, I had only to transfer all files to an S3 bucket and then point the application to it. I chose to use &lt;a href=&#34;http://wasabisys.com&#34;&gt;Wasabi&lt;/a&gt;, a very cheap S3 storage solution, but the beauty of this upgrade is that the code is provider agnostic&amp;ndash;in the future switching to Amazon or Linode S3 Object Storage should be fairly painless.&lt;/p&gt;
&lt;p&gt;In the week before the final deployment, I configured &lt;a href=&#34;https://aws.amazon.com/cli/&#34;&gt;aws cli&lt;/a&gt; to point to a new backup bucket in Wasabi, and used it to periodically sync the entire set of files from the production server to that bucket. About 100 new files get created everyday, so the &lt;code&gt;sync&lt;/code&gt; operation (which only updates new or altered files) was crucial for seamlessly keeping everything up-to-date.&lt;/p&gt;
&lt;h2 id=&#34;the-result&#34;&gt;The result&lt;/h2&gt;
&lt;p&gt;It went well! Since the switch on a Sunday afternoon, all new files have gone straight to S3, and all of the existing interfaces and viewers on the site now run from COGs in S3 instead of through &lt;code&gt;nginx&lt;/code&gt; on the server.&lt;/p&gt;
&lt;p&gt;One hiccup I encountered was that the setting &lt;code&gt;AWS_QUERYSTRING_AUTH&lt;/code&gt; in Django was automatically set to &lt;code&gt;True&lt;/code&gt; , causing the URLs that the backend returned to have embedded expiration dates in them. Everything would be fine when I re-generated the lookups (which include saved URLs for things like thumbnails) but then the next day these same URLs would be &amp;ldquo;unauthorized&amp;rdquo; and no longer work. Setting &lt;code&gt;AWS_QUERYSTRING_AUTH=False&lt;/code&gt; fixed this issue.&lt;/p&gt;
&lt;p&gt;Wasabi is &lt;em&gt;very&lt;/em&gt; cheap, just $7/month per terabyte, meaning that the 440gb I have in the bucket (doubled if you include the backup bucket) falls within the lowest tier of usage. A very quick back-of-the-envelope calculation shows that if the &lt;em&gt;entire&lt;/em&gt; LOC Sanborn Map collection (500,000 sheets resulting in at least 3x that many files) were georeferenced on OIM, storage would be under 7tb ($49/month) or double that with a backup. That seems like a pretty good deal.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve talked about making this upgrade for a while, so it feels good to finally do it. Technically, I could delete all old content from the server and then downgrade it to reduce the monthly bill, but storage was just one of the elements in play, because the splitting and warping processes do benefit from a powerful server, not to mention I still run TiTiler directly on the server as well. All in good time&amp;hellip;&lt;/p&gt;
</description>
      <source:markdown>## What is S3 Object Storage?

S3 object storage is a protocol developed by Amazon Web Services for handling file storage outside of a normal server environment and &#34;in the cloud&#34; instead. In other words, it&#39;s a simplified way of uploading, downloading, or directly accessing files that are stored in remote &#34;buckets&#34;. In these buckets, storage is (broadly speaking) very cheap and practically unlimited. Many other companies have since adopted the S3 API so their own cloud storage offerings are compatible with it.

## Implementing a new storage backend

To this point, [OldInsuranceMaps.net](http://OldInsuranceMaps.net) has functioned by downloading image files from the Library of Congress (or other sources, in certain contexts) and storing those files on the main server. Once the images are available locally, the splitting, georeferencing, and mosaicking operations are performed directly on those files, creating even more files (ultimately, [Cloud Optimized GeoTIFFs](https://cogeo.org/)) on the server. Really, the entire point the platform is to build tools and workflows around the creation and management of these files.

One downside to this approach is that the server has limited storage space, let&#39;s say about 500gb. This has been plenty for the last few years (especially as [I&#39;ve implemented better compression methods](https://github.com/ohmg-dev/OldInsuranceMaps/pull/145) over time) but as available space inevitably diminishes, I decided it was finally time to progress to a new storage strategy.

To implement S3 storage for all content in OIM, there were two general tasks:

1.  Update the code base to work with remotely stored content instead of relying on files on disk
    
2.  Upload all existing content to an S3 bucket
    

How much existing content? Well, quite a lot. After a big server cleanup effort (this was the first time I had comprehensively dealt with all kinds of orphan files and remnants from past experiments) there were _roughly_ 130,000 files using about 430gb of disk space.

There were also a couple of important constraints to work around:

1.  S3 storage needs to be optional, so that future installations of the code base can run just using local file storage
    
2.  Gotta keep the site running! There is a bit of operational inertia that must be respected on the platform, now that there is a lot of content on it and people using it everyday. Practically speaking, this means making slow, incremental steps.
    

### Code compatibility

OIM is built with the Django web framework, and there is a solid, standardized way for implementing S3 storage using [django-storages.](https://django-storages.readthedocs.io/en/latest/backends/amazon-S3.html) In theory then, the storages plugin could be installed, a switch could be flipped, and violá, Django will read and write to an S3 bucket instead of the local file system.

However, it wasn&#39;t that simple. Due to the fact that a lot of splitting, georeferencing, and mosaicking operations had been built with the expectation of local file storage, some of them failed once S3 got involved. Luckily, GDAL (on which OIM has relied from the start) has a [fantastic virtual file system](https://gdal.org/en/stable/user/virtual_file_systems.html) that allows it to read directly from S3 urls, and combining that with another GDAL feature, [virtual rasters or VRTs](https://gdal.org/en/stable/drivers/raster/vrt.html), offered plenty of flexibility to work with. Ultimately, the implementation required rewriting and improving some basic functions at the core of the app, but produced a better code base in the end. If you are interested, you can read all the gory details in [this pull request](https://github.com/ohmg-dev/OldInsuranceMaps/pull/280).

### Syncing the content

With the code updated, I had only to transfer all files to an S3 bucket and then point the application to it. I chose to use [Wasabi](http://wasabisys.com), a very cheap S3 storage solution, but the beauty of this upgrade is that the code is provider agnostic--in the future switching to Amazon or Linode S3 Object Storage should be fairly painless.

In the week before the final deployment, I configured [aws cli](https://aws.amazon.com/cli/) to point to a new backup bucket in Wasabi, and used it to periodically sync the entire set of files from the production server to that bucket. About 100 new files get created everyday, so the `sync` operation (which only updates new or altered files) was crucial for seamlessly keeping everything up-to-date.

## The result

It went well! Since the switch on a Sunday afternoon, all new files have gone straight to S3, and all of the existing interfaces and viewers on the site now run from COGs in S3 instead of through `nginx` on the server.

One hiccup I encountered was that the setting `AWS_QUERYSTRING_AUTH` in Django was automatically set to `True` , causing the URLs that the backend returned to have embedded expiration dates in them. Everything would be fine when I re-generated the lookups (which include saved URLs for things like thumbnails) but then the next day these same URLs would be &#34;unauthorized&#34; and no longer work. Setting `AWS_QUERYSTRING_AUTH=False` fixed this issue.

Wasabi is _very_ cheap, just $7/month per terabyte, meaning that the 440gb I have in the bucket (doubled if you include the backup bucket) falls within the lowest tier of usage. A very quick back-of-the-envelope calculation shows that if the _entire_ LOC Sanborn Map collection (500,000 sheets resulting in at least 3x that many files) were georeferenced on OIM, storage would be under 7tb ($49/month) or double that with a backup. That seems like a pretty good deal.

I&#39;ve talked about making this upgrade for a while, so it feels good to finally do it. Technically, I could delete all old content from the server and then downgrade it to reduce the monthly bill, but storage was just one of the elements in play, because the splitting and warping processes do benefit from a powerful server, not to mention I still run TiTiler directly on the server as well. All in good time...
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: 2024 in Review &#43; new features!</title>
      <link>https://blog.oldinsurancemaps.net/2025/02/21/in-review-new-features/</link>
      <pubDate>Fri, 21 Feb 2025 09:30:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2025/02/21/in-review-new-features/</guid>
      <description>&lt;p&gt;Hello and happy second month of the New Year! It is high Mardi Gras season here in New Orleans and I feel like everything is happening at the same time.&lt;/p&gt;
&lt;p&gt;For new readers: Welcome! You can find all past newsletters &lt;a href=&#34;https://blog.oldinsurancemaps.net/archive&#34;&gt;in the archive&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Also, OldInsuranceMaps.net is &lt;a href=&#34;https://bsky.app/profile/oldinsurancemaps.net&#34;&gt;now on Bluesky&lt;/a&gt;, come be our 2nd follower! I&amp;rsquo;ll post smaller more frequent updates there, and it will also be something people/orgs can tag when they use OIM for events or research. And, don&amp;rsquo;t forget the &lt;a href=&#34;https://forum.openhistoricalmap.org/c/oldinsurancemaps/13&#34;&gt;discussion forum&lt;/a&gt; a great way to connect with other people using OldInsuranceMaps.net.&lt;/p&gt;
&lt;h3 id=&#34;2024-stats-and-summary&#34;&gt;2024 Stats and Summary&lt;/h3&gt;
&lt;p&gt;On NYE of 2023 I sent a &lt;a href=&#34;https://oldinsurancemaps.net/news/2023-year-in-review/&#34;&gt;newsletter with a nice chart&lt;/a&gt; of work performed over that year. For 2024, I don&amp;rsquo;t have anything that nice to offer, but here are some numbers from last year:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;New users: 170 (366 total)&lt;/li&gt;
&lt;li&gt;Preparation sessions: 23,235 (31,360 total)&lt;/li&gt;
&lt;li&gt;Georeferencing sessions: 29,402 (41,514 total)&lt;/li&gt;
&lt;li&gt;New Layers: 28,361 (32,362 total)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;As you can tell, 2024 &lt;em&gt;far exceeds&lt;/em&gt; all work from past years, largely owed to the incredible work of students and staff at the University of Richmond Digital Scholarship Lab, who seem to be georeferencing 24/7. There have been substantial individual efforts as well though:&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://oldinsurancemaps.net/profile/hayleox/&#34;&gt;hayleox&lt;/a&gt; in Cincinnati, OH • &lt;a href=&#34;https://oldinsurancemaps.net/profile/mrileyowens/&#34;&gt;mrileyowens&lt;/a&gt; in Cincinnati, OH (you two should talk!) • &lt;a href=&#34;https://oldinsurancemaps.net/profile/ekoparker/&#34;&gt;ekoparker&lt;/a&gt; in Chicago, IL •\r\n&lt;a href=&#34;https://oldinsurancemaps.net/profile/sanborn_again1&#34;&gt;sanborn_again1&lt;/a&gt; in Springfield, IL • &lt;a href=&#34;https://oldinsurancemaps.net/profile/mhowell/&#34;&gt;mhowell&lt;/a&gt; in Noblesville, IN • &lt;a href=&#34;https://oldinsurancemaps.net/profile/tagifford/&#34;&gt;tagifford&lt;/a&gt; in Schenectady/Scotia, NY • &lt;a href=&#34;https://oldinsurancemaps.net/profile/Gullimapozo/&#34;&gt;Gullimapozo&lt;/a&gt; in Gary, IN • &lt;a href=&#34;https://oldinsurancemaps.net/profile/lablakely/&#34;&gt;lablakely&lt;/a&gt; in Waco, Austin, and Georgetown, TX • &lt;a href=&#34;https://oldinsurancemaps.net/profile/cliftonmr/&#34;&gt;cliftonmr&lt;/a&gt; in Cleburne, TX • &lt;a href=&#34;https://oldinsurancemaps.net/profile/Pete_Zivkov/&#34;&gt;Pete_Zivkov&lt;/a&gt; in Bellingham, WA • and others!&lt;/p&gt;
&lt;p&gt;Plus, of course, a handful of georeference-a-thons (more on those below).&lt;/p&gt;
&lt;p&gt;Overall, &lt;em&gt;very roughly&lt;/em&gt;, I would estimate we have georeferenced over 1/20th of the entire Library of Congress Sanborn map collection (500k documents in the collection, 38k on OldInsuranceMaps, definitely at least 25k of those processed). Wild!&lt;/p&gt;
&lt;h3 id=&#34;georeference-a-thons&#34;&gt;Georeference-a-thons&lt;/h3&gt;
&lt;p&gt;Many of these since last newsletter in mid-November!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Healthy Regions &amp;amp; Policies Lab @ UIUC&lt;/strong&gt;: For GIS Day last year (Nov. 20th) I took the Amtrak to Champaign to work with my colleagues at the University of Illinois to have a 2-hour event where we georeferenced Champain and Urbana maps from 1915. We even had two guest speakers over Zoom! See &lt;a href=&#34;https://healthyregions.org/2025/01/31/gis-day-2024-community-georeferencing-of-sanborn-fire-insurance-maps/&#34;&gt;this blog post&lt;/a&gt; for more details (and action shots!).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;UChicago&lt;/strong&gt;: Later that day I joined a (very) small group at UChicago, which was kind of perfect because I got to show Parker and Rob around the site in detail. Thanks to Rob for setting this up, on top of all the other GIS Day programming!&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;OSU&lt;/strong&gt; - Also on GIS Day, the team at the Ohio State University Libraries hosted their &lt;a href=&#34;https://library.osu.edu/events/gis-day-2024&#34;&gt;third georeference-a-thon to date&lt;/a&gt;, working on maps of Columbus, great to see such a long-term, continued effort there.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Morgan State University + UIUC&lt;/strong&gt;: The following day, &amp;ldquo;Post-GIS Day&amp;rdquo;, we held a collaborative online event between a group at Morgan State led by Dr. Lawrence Brown, and Dr. Marynia Kolak&amp;rsquo;s Population Geography class at UIUC. Instead of Sanborn maps, we used OldInsuranceMaps.net to georeference FHA Block Data maps from the late 1930&amp;rsquo;s and 1940&amp;rsquo;s. Stay tuned for more about this project in the future.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Community Mapping Lab @ University of Georgia&lt;/strong&gt;: Just a few weeks ago, Dr. Jerry Shannon and team at UGA held an event to georeference Athens, GA maps, and you can read more about their work &lt;a href=&#34;https://www.communitymappinglab.org/digitizing-athens-sanborn-maps.html&#34;&gt;here&lt;/a&gt;. Jerry&amp;rsquo;s &lt;a href=&#34;https://bsky.app/profile/jerry-shannon.bsky.social/post/3li3w4jnv7s2u&#34;&gt;post on Bluesky&lt;/a&gt; also has some action shots!&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;new-features&#34;&gt;New features&lt;/h3&gt;
&lt;p&gt;I&amp;rsquo;d like to highlight a few new/experimental features I&amp;rsquo;ve added in the last couple of months.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Activity filters&lt;/strong&gt;: The &lt;a href=&#34;https://oldinsurancemaps.net/activity/&#34;&gt;activity page&lt;/a&gt; is the easiest way to see all current and past work that has been carried out on the platform. I&amp;rsquo;ve added filters so you can only show work on specific maps, within a date range, or by a certain user.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Parcel layer snapping&lt;/strong&gt;: We found that in San Francisco maps, each individual &lt;em&gt;block&lt;/em&gt; must be georeferenced individually. This is not only extremely tedious, but also more difficult because you can&amp;rsquo;t use street intersections for control points. So, I set up a system where current parcel lines can be added as a reference layer that you can snap your control points to, which not only speeds things up, but also greatly increases the accuracy of contributed work. I wrote a bit about that &lt;a href=&#34;https://forum.openhistoricalmap.org/t/street-widths-not-to-scale-more-examples/389&#34;&gt;on the forum&lt;/a&gt;. Have added this feature to a couple other cities, but it is still in development.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Allmaps and IIIF support&lt;/strong&gt;: Just last week/weekend, I finally set up endpoints on the site that will return IIIF Georeference Annotations for any layer or mosaic within OldInsuranceMaps.net, which can be used directly in the Allmaps Viewer. You can read more about the work in this &lt;a href=&#34;https://github.com/ohmg-dev/OldInsuranceMaps/pull/258&#34;&gt;pull request (examples included)&lt;/a&gt;, and you&amp;rsquo;ll now see links to &amp;ldquo;Open in Allmaps Viewer&amp;rdquo; within OldInsuranceMaps map overview pages. If you aren&amp;rsquo;t familiar with Allmaps, I strongly encourage you to &lt;a href=&#34;https://allmaps.org&#34;&gt;check it out&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;looking-ahead&#34;&gt;Looking ahead&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Colocate2 at Stanford&lt;/strong&gt;: Next week I am attending a small &amp;ldquo;unconference&amp;rdquo; at the David Rumsey Map Center at Stanford. Really looking forward to this and the discussions that will follow, as it is largely focused on institutional georeferencing work, GeoBlacklight, and Allmaps.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Louisiana History Association Annual Meeting&lt;/strong&gt;: On Sat. March 15th I&amp;rsquo;ll be participating in a round-table discussion &amp;ldquo;Mapping the Past: GIS Technology Implementation for Historic Sites&amp;rdquo; at the annual meeting of the Louisiana History Association, with Elizabeth Williams (Midlo Center at UNO, HistoryForge) and Sarah Waits (archivist at Archdiocese of New Orleans). If you are attending this meeting, please say hello!&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Georeference-a-thon at Rowan University&lt;/strong&gt;: In April, a group at Rowan University will hold a few events to georeference maps in Gloucester County, NJ. Hopefully I&amp;rsquo;ll be able to pass on another update about this next month.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;thank-you&#34;&gt;Thank you!&lt;/h3&gt;
&lt;p&gt;A big thank you to everyone who continues make this project possible. Especially my colleagues and lab PI Marynia Kolak at UIUC, as well as the team at the URichmond DSL and their partnership with the University of Michigan. Jeff and Minh continue to make &lt;a href=&#34;https://www.openhistoricalmap.org&#34;&gt;OpenHistoricalMap&lt;/a&gt; an inviting place to map history (checkout &lt;a href=&#34;https://www.openhistoricalmap.org/#map=17/39.107819/-84.516191&amp;amp;layers=O&amp;amp;date=1919-01-04&amp;amp;daterange=1825-01-01,2025-12-31&#34;&gt;hayleox&amp;rsquo;s work in Cincinnati&lt;/a&gt;, or Pete&amp;rsquo;s &lt;a href=&#34;https://www.openhistoricalmap.org/#map=18/29.958151/-90.064550&amp;amp;layers=O&amp;amp;date=1885-09-24&amp;amp;daterange=1825-01-01,2025-12-31&#34;&gt;super detail of New Orleans&#39; French Quarter in 1885&lt;/a&gt;), which in turn drives people to OldInsuranceMaps.net where they can create Sanborn base layers to digitize from. Finally, thank &lt;em&gt;you&lt;/em&gt; for reading this whole thing!&lt;/p&gt;
&lt;p&gt;&amp;ndash; Adam&lt;/p&gt;
</description>
      <source:markdown>Hello and happy second month of the New Year! It is high Mardi Gras season here in New Orleans and I feel like everything is happening at the same time.

For new readers: Welcome! You can find all past newsletters [in the archive](https://blog.oldinsurancemaps.net/archive).

Also, OldInsuranceMaps.net is [now on Bluesky](https://bsky.app/profile/oldinsurancemaps.net), come be our 2nd follower! I&#39;ll post smaller more frequent updates there, and it will also be something people/orgs can tag when they use OIM for events or research. And, don&#39;t forget the [discussion forum](https://forum.openhistoricalmap.org/c/oldinsurancemaps/13) a great way to connect with other people using OldInsuranceMaps.net.

### 2024 Stats and Summary

On NYE of 2023 I sent a [newsletter with a nice chart](https://oldinsurancemaps.net/news/2023-year-in-review/) of work performed over that year. For 2024, I don&#39;t have anything that nice to offer, but here are some numbers from last year:

- New users: 170 (366 total)
- Preparation sessions: 23,235 (31,360 total)
- Georeferencing sessions: 29,402 (41,514 total)
- New Layers: 28,361 (32,362 total)

As you can tell, 2024 _far exceeds_ all work from past years, largely owed to the incredible work of students and staff at the University of Richmond Digital Scholarship Lab, who seem to be georeferencing 24/7. There have been substantial individual efforts as well though:

[hayleox](https://oldinsurancemaps.net/profile/hayleox/) in Cincinnati, OH • [mrileyowens](https://oldinsurancemaps.net/profile/mrileyowens/) in Cincinnati, OH (you two should talk!) • [ekoparker](https://oldinsurancemaps.net/profile/ekoparker/) in Chicago, IL •\\r\\n[sanborn\_again1](https://oldinsurancemaps.net/profile/sanborn_again1) in Springfield, IL • [mhowell](https://oldinsurancemaps.net/profile/mhowell/) in Noblesville, IN • [tagifford](https://oldinsurancemaps.net/profile/tagifford/) in Schenectady/Scotia, NY • [Gullimapozo](https://oldinsurancemaps.net/profile/Gullimapozo/) in Gary, IN • [lablakely](https://oldinsurancemaps.net/profile/lablakely/) in Waco, Austin, and Georgetown, TX • [cliftonmr](https://oldinsurancemaps.net/profile/cliftonmr/) in Cleburne, TX • [Pete_Zivkov](https://oldinsurancemaps.net/profile/Pete_Zivkov/) in Bellingham, WA • and others!

Plus, of course, a handful of georeference-a-thons (more on those below).

Overall, _very roughly_, I would estimate we have georeferenced over 1/20th of the entire Library of Congress Sanborn map collection (500k documents in the collection, 38k on OldInsuranceMaps, definitely at least 25k of those processed). Wild!

### Georeference-a-thons

Many of these since last newsletter in mid-November!

- **Healthy Regions &amp; Policies Lab @ UIUC**: For GIS Day last year (Nov. 20th) I took the Amtrak to Champaign to work with my colleagues at the University of Illinois to have a 2-hour event where we georeferenced Champain and Urbana maps from 1915. We even had two guest speakers over Zoom! See [this blog post](https://healthyregions.org/2025/01/31/gis-day-2024-community-georeferencing-of-sanborn-fire-insurance-maps/) for more details (and action shots!).
- **UChicago**: Later that day I joined a (very) small group at UChicago, which was kind of perfect because I got to show Parker and Rob around the site in detail. Thanks to Rob for setting this up, on top of all the other GIS Day programming!
- **OSU** - Also on GIS Day, the team at the Ohio State University Libraries hosted their [third georeference-a-thon to date](https://library.osu.edu/events/gis-day-2024), working on maps of Columbus, great to see such a long-term, continued effort there.
- **Morgan State University + UIUC**: The following day, &#34;Post-GIS Day&#34;, we held a collaborative online event between a group at Morgan State led by Dr. Lawrence Brown, and Dr. Marynia Kolak&#39;s Population Geography class at UIUC. Instead of Sanborn maps, we used OldInsuranceMaps.net to georeference FHA Block Data maps from the late 1930&#39;s and 1940&#39;s. Stay tuned for more about this project in the future.
- **Community Mapping Lab @ University of Georgia**: Just a few weeks ago, Dr. Jerry Shannon and team at UGA held an event to georeference Athens, GA maps, and you can read more about their work [here](https://www.communitymappinglab.org/digitizing-athens-sanborn-maps.html). Jerry&#39;s [post on Bluesky](https://bsky.app/profile/jerry-shannon.bsky.social/post/3li3w4jnv7s2u) also has some action shots!

### New features

I&#39;d like to highlight a few new/experimental features I&#39;ve added in the last couple of months.

- **Activity filters**: The [activity page](https://oldinsurancemaps.net/activity/) is the easiest way to see all current and past work that has been carried out on the platform. I&#39;ve added filters so you can only show work on specific maps, within a date range, or by a certain user.
- **Parcel layer snapping**: We found that in San Francisco maps, each individual _block_ must be georeferenced individually. This is not only extremely tedious, but also more difficult because you can&#39;t use street intersections for control points. So, I set up a system where current parcel lines can be added as a reference layer that you can snap your control points to, which not only speeds things up, but also greatly increases the accuracy of contributed work. I wrote a bit about that [on the forum](https://forum.openhistoricalmap.org/t/street-widths-not-to-scale-more-examples/389). Have added this feature to a couple other cities, but it is still in development.
- **Allmaps and IIIF support**: Just last week/weekend, I finally set up endpoints on the site that will return IIIF Georeference Annotations for any layer or mosaic within OldInsuranceMaps.net, which can be used directly in the Allmaps Viewer. You can read more about the work in this [pull request (examples included)](https://github.com/ohmg-dev/OldInsuranceMaps/pull/258), and you&#39;ll now see links to &#34;Open in Allmaps Viewer&#34; within OldInsuranceMaps map overview pages. If you aren&#39;t familiar with Allmaps, I strongly encourage you to [check it out](https://allmaps.org).

### Looking ahead

- **Colocate2 at Stanford**: Next week I am attending a small &#34;unconference&#34; at the David Rumsey Map Center at Stanford. Really looking forward to this and the discussions that will follow, as it is largely focused on institutional georeferencing work, GeoBlacklight, and Allmaps.
- **Louisiana History Association Annual Meeting**: On Sat. March 15th I&#39;ll be participating in a round-table discussion &#34;Mapping the Past: GIS Technology Implementation for Historic Sites&#34; at the annual meeting of the Louisiana History Association, with Elizabeth Williams (Midlo Center at UNO, HistoryForge) and Sarah Waits (archivist at Archdiocese of New Orleans). If you are attending this meeting, please say hello!
- **Georeference-a-thon at Rowan University**: In April, a group at Rowan University will hold a few events to georeference maps in Gloucester County, NJ. Hopefully I&#39;ll be able to pass on another update about this next month.

### Thank you!

A big thank you to everyone who continues make this project possible. Especially my colleagues and lab PI Marynia Kolak at UIUC, as well as the team at the URichmond DSL and their partnership with the University of Michigan. Jeff and Minh continue to make [OpenHistoricalMap](https://www.openhistoricalmap.org) an inviting place to map history (checkout [hayleox&#39;s work in Cincinnati](https://www.openhistoricalmap.org/#map=17/39.107819/-84.516191&amp;layers=O&amp;date=1919-01-04&amp;daterange=1825-01-01,2025-12-31), or Pete&#39;s [super detail of New Orleans&#39; French Quarter in 1885](https://www.openhistoricalmap.org/#map=18/29.958151/-90.064550&amp;layers=O&amp;date=1885-09-24&amp;daterange=1825-01-01,2025-12-31)), which in turn drives people to OldInsuranceMaps.net where they can create Sanborn base layers to digitize from. Finally, thank _you_ for reading this whole thing!

-- Adam
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: GIS Day Events | NACIS | Data Agreement</title>
      <link>https://blog.oldinsurancemaps.net/2024/11/15/gis-day-events-nacis-data/</link>
      <pubDate>Fri, 15 Nov 2024 16:30:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2024/11/15/gis-day-events-nacis-data/</guid>
      <description>&lt;p&gt;In case you didn&amp;rsquo;t know, &lt;em&gt;GIS Day&lt;/em&gt; this year is next Wednesday, Nov. 20th, in the middle of &lt;a href=&#34;https://www.aag.org/geography-awareness-week-2024/&#34;&gt;Geography Awareness Week&lt;/a&gt;. &lt;em&gt;GIS Day&lt;/em&gt; was started by the company ESRI (of ArcGIS reknown) many years ago, and I &lt;a href=&#34;https://www.esri.com/about/newsroom/arcnews/discovering-the-world-on-gis-day/&#34;&gt;just learned&lt;/a&gt; that Ralph Nader was the inspiration behind the day. Of course, there is a lot to GIS beyond Esri, but as someone who learned about the field at the end of my undergrad and never looked back, I love that &lt;em&gt;GIS Day&lt;/em&gt; exists and consider it a great &amp;ldquo;holiday&amp;rdquo; to promote. Also, what better time to hold historical map crowdsourcing events?&lt;/p&gt;
&lt;p&gt;Also, if you skip most of this newsletter, please at least read about the new Data Agreement at the bottom.&lt;/p&gt;
&lt;h2 id=&#34;georeference-a-thons-of-future&#34;&gt;Georeference-a-thons of Future&lt;/h2&gt;
&lt;h3 id=&#34;uiuc---healthy-regions--policies-lab&#34;&gt;UIUC - Healthy Regions &amp;amp; Policies Lab&lt;/h3&gt;
&lt;p&gt;Through my work at HeRoP, we will be putting on a georeference-a-thon in Champaign next Wednesday. You can learn much more about it through this &lt;a href=&#34;https://www.eventbrite.com/e/historical-map-georeference-a-thon-tickets-1069694477979?aff=oddtdtcreator&#34;&gt;Eventbrite link&lt;/a&gt;. The event will be in-person, but we have a Zoom option as well (find it at the bottom of the Eventbrite) and we plan to have a couple of short talks via Zoom by researchers who use historical maps. We will be working on Sanborn maps of Champaign and Urbana from 1915, and I&amp;rsquo;m looking forward to students getting to learn about what their university environs looked like in the past.&lt;/p&gt;
&lt;h3 id=&#34;university-of-chicago-libraries&#34;&gt;University of Chicago Libraries&lt;/h3&gt;
&lt;p&gt;After our event at UIUC, the University of Chicago Library will also have a georeferencing event starting at 2pm in the afternoon. For more details about this event, stay tuned to &lt;a href=&#34;https://forum.openhistoricalmap.org/c/oldinsurancemaps/13&#34;&gt;OldInsuranceMaps.net Forum&lt;/a&gt;, an oft-overlooked-but-full-of-potential discussion space that we have. I&amp;rsquo;ll be posting all of this information there in the coming days.&lt;/p&gt;
&lt;h3 id=&#34;morgan-state-university---the-black-butterfly-project&#34;&gt;Morgan State University - The Black Butterfly Project&lt;/h3&gt;
&lt;p&gt;In collaboration with Dr. Lawrence Brown and the team at Morgan State, we&amp;rsquo;ll be doing a &lt;em&gt;non-Sanborn map&lt;/em&gt; georeference-a-thon on Nov. 21st. We will instead be working with old FHA Loan maps from the 1930s, which Dr. Brown sought out and scanned at the National Archives in Maryland. We are extremely lucky to be able to support this work, and we&amp;rsquo;ll finally get to see the site with a different set of maps! You can learn more about this event, and join from afar, through this &lt;a href=&#34;https://www.eventbrite.com/e/gis-day-georeference-a-thon-tickets-1037041628427?aff=oddtdtcreator&#34;&gt;Eventbrite link&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;the-ohio-state-university-libraries&#34;&gt;The Ohio State University Libraries&lt;/h3&gt;
&lt;p&gt;At the Ohio State University, Josh Sadvari and the team at the library will be putting on another &lt;a href=&#34;https://library.osu.edu/events/gis-day-2024&#34;&gt;GIS Day Georef-a-thon&lt;/a&gt; just like &lt;a href=&#34;https://waml.org/waml-information-bulletin/volume-55-number-2/piloting-a-sanborn-map-georef-a-thon/&#34;&gt;they did last year&lt;/a&gt;. This is an in-person event, and part of a full day of GIS talks, all of which look fascinating. Do check it out if you are in the Columbus area!&lt;/p&gt;
&lt;h2 id=&#34;georeference-a-thons-of-present&#34;&gt;Georeference-a-thons of Present&lt;/h2&gt;
&lt;p&gt;Not exactly &lt;em&gt;present&lt;/em&gt;, but just a couple days ago the team at the URichmond &lt;a href=&#34;http://dsl.richmond.edu/&#34;&gt;Digital Scholarship Lab&lt;/a&gt; held a &lt;em&gt;competitive&lt;/em&gt; georeference-a-thon (the first of its kind with &lt;em&gt;OIM&lt;/em&gt;) and it sure looked like a good time! Riley set up a point system for georeferenced content, complete with the option to challenge the quality of another team&amp;rsquo;s work to reduce their score.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://mradamcox.github.io/theme/img/1-crop.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;p&gt;In addition to points for georeferencing, teams also had to do some scavenger-hunting across the 1905 Richmond map to answer questions like &lt;em&gt;&amp;ldquo;Across N. 11th St. from City Hall is where you can find the ________ HOTEL&amp;rdquo;&lt;/em&gt; , or &lt;em&gt;&amp;ldquo;Just&lt;/em&gt; _east of Shockoe Slip is where you can find _______ COFFEE CO.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://mradamcox.github.io/theme/img/3-crop.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;p&gt;Congrats to the big winners (and some familiar names from the platform!!): &lt;em&gt;ibrahimalkaser&lt;/em&gt;, &lt;em&gt;samyoga&lt;/em&gt;, &lt;em&gt;bakeunsu&lt;/em&gt;, and &lt;em&gt;willguy&lt;/em&gt;.&lt;/p&gt;
&lt;h2 id=&#34;georeference-a-thons-of-past&#34;&gt;Georeference-a-thons of Past&lt;/h2&gt;
&lt;p&gt;Finally, we owe a big and belated thank you to everyone that showed up to the events we did with HistoryForge at Second Line Brewing in New Orleans, this past August. It was unexpectedly great to do two weeks in a row because it felt like we built some momentum, even though there were very few people who came both days.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://mradamcox.github.io/theme/img/IMG_6231-crop.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;p&gt;All together, we had about 25 people attend, made it through the entirety of &lt;a href=&#34;https://oldinsurancemaps.net/map/sanborn03376_010&#34;&gt;New Orleans, 1908, Vol. 2&lt;/a&gt;, and &lt;em&gt;much&lt;/em&gt; of &lt;a href=&#34;https://oldinsurancemaps.net/map/sanborn03376_011&#34;&gt;Vol. 3&lt;/a&gt; as well. Once these mosaics are completed and trimmed, we&amp;rsquo;ll be able to add them to the local HistoryForge &lt;a href=&#34;https://sela.historyforge.net/forge&#34;&gt;project&lt;/a&gt;, to help with trascribing and mapping historical US Census documents.&lt;/p&gt;
&lt;p&gt;\r\n&lt;/p&gt;
&lt;h2 id=&#34;presentations-at-nacis-in-october&#34;&gt;Presentation(s) at NACIS in October&lt;/h2&gt;
&lt;p&gt;\r\n&lt;/p&gt;
&lt;p&gt;Last month I traveled to the annual North American Cartographic Information Society meeting, this year in Tacoma, WA, and presented about &lt;em&gt;OldInsuranceMaps.net.&lt;/em&gt; The video of the talk is now on YouTube: &lt;a href=&#34;https://www.youtube.com/watch?v=DhRrZgCedqk&#34;&gt;Handling Complex Content within Georeferenced Historical Atlases&lt;/a&gt;. You can also flip through the slides here: &lt;a href=&#34;https://tiny.cc/nacis2024-ac&#34;&gt;tiny.cc/nacis2024-ac&lt;/a&gt;. Even though it sounds pretty boring, this was extremely gratifying to put together and present, because it distills what I think is most unique about the platform.&lt;/p&gt;
&lt;p&gt;As a lucky bonus, Riley Champine from the URichmond DSL presented in the same session right after me, so I encourage you to watch his talk as well: &lt;a href=&#34;https://www.youtube.com/watch?v=SK_2n5QStBs&#34;&gt;Using Old Maps for New Insights on America’s Cities&lt;/a&gt;. He discusses updates to the lab&amp;rsquo;s &lt;em&gt;Mapping Inequality&lt;/em&gt; project, and near the end has a fantastic demo of their new project &lt;em&gt;Fires of Industry&lt;/em&gt;, that is based on the monumental georeferencing effort their students are carrying out using &lt;em&gt;OldInsuranceMaps.net&lt;/em&gt;. I heard a few &amp;ldquo;wows&amp;rdquo; in the audience when he showed this.&lt;/p&gt;
&lt;h2 id=&#34;finally-data-agreement&#34;&gt;Finally: Data Agreement&lt;/h2&gt;
&lt;p&gt;As I have written in this newsletter before, I have been working toward being more precise about what happens with user-contributed data on OldInsuranceMaps.net. I have now added a &lt;a href=&#34;https://oldinsurancemaps.net/data-agreement&#34;&gt;Data Agreement&lt;/a&gt;, that states the following (in summary—see linked page for more details):&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Two core goals of&lt;/em&gt; OldInsuranceMaps.net &lt;em&gt;are:&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;To facilitate historical map georeferencing and mosaicking in a streamlined and participatory environment&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;To create publicly accessible datasets that can be used by anyone for any purpose&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;To that end,&lt;/em&gt; OldInsuranceMaps.net &lt;em&gt;collects user-contributed georeferencing data, and &lt;strong&gt;insofar as any of this data is copyrightable, users agree that their copyright is waived and &lt;a href=&#34;https://creativecommons.org/publicdomain/zero/1.0/&#34;&gt;CC0&lt;/a&gt; license is applied&lt;/strong&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The platform also records the georeferencing-related actions that a user takes while interacting with it, and uses &lt;a href=&#34;https://plausible.io/privacy-focused-web-analytics&#34;&gt;Plausible Analytics&lt;/a&gt; to collect general statistics about visitors to the site. No private user information is collected.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I will reiterate as I have said before: &lt;strong&gt;If you have already created content on the site, but would &lt;em&gt;not&lt;/em&gt; like to have it available under these conditions: Please get back to me and I will help you download it and will then remove it.&lt;/strong&gt; No problem at all! The files should be very easy to self-host.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Thanks, as always for reading, and hope to see some of you next week!&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;
</description>
      <source:markdown>In case you didn&#39;t know, _GIS Day_ this year is next Wednesday, Nov. 20th, in the middle of [Geography Awareness Week](https://www.aag.org/geography-awareness-week-2024/). _GIS Day_ was started by the company ESRI (of ArcGIS reknown) many years ago, and I [just learned](https://www.esri.com/about/newsroom/arcnews/discovering-the-world-on-gis-day/) that Ralph Nader was the inspiration behind the day. Of course, there is a lot to GIS beyond Esri, but as someone who learned about the field at the end of my undergrad and never looked back, I love that _GIS Day_ exists and consider it a great &#34;holiday&#34; to promote. Also, what better time to hold historical map crowdsourcing events?

Also, if you skip most of this newsletter, please at least read about the new Data Agreement at the bottom.

## Georeference-a-thons of Future

### UIUC - Healthy Regions &amp; Policies Lab


Through my work at HeRoP, we will be putting on a georeference-a-thon in Champaign next Wednesday. You can learn much more about it through this [Eventbrite link](https://www.eventbrite.com/e/historical-map-georeference-a-thon-tickets-1069694477979?aff=oddtdtcreator). The event will be in-person, but we have a Zoom option as well (find it at the bottom of the Eventbrite) and we plan to have a couple of short talks via Zoom by researchers who use historical maps. We will be working on Sanborn maps of Champaign and Urbana from 1915, and I&#39;m looking forward to students getting to learn about what their university environs looked like in the past.

### University of Chicago Libraries

After our event at UIUC, the University of Chicago Library will also have a georeferencing event starting at 2pm in the afternoon. For more details about this event, stay tuned to [OldInsuranceMaps.net Forum](https://forum.openhistoricalmap.org/c/oldinsurancemaps/13), an oft-overlooked-but-full-of-potential discussion space that we have. I&#39;ll be posting all of this information there in the coming days.

### Morgan State University - The Black Butterfly Project

In collaboration with Dr. Lawrence Brown and the team at Morgan State, we&#39;ll be doing a _non-Sanborn map_ georeference-a-thon on Nov. 21st. We will instead be working with old FHA Loan maps from the 1930s, which Dr. Brown sought out and scanned at the National Archives in Maryland. We are extremely lucky to be able to support this work, and we&#39;ll finally get to see the site with a different set of maps! You can learn more about this event, and join from afar, through this [Eventbrite link](https://www.eventbrite.com/e/gis-day-georeference-a-thon-tickets-1037041628427?aff=oddtdtcreator).

### The Ohio State University Libraries

At the Ohio State University, Josh Sadvari and the team at the library will be putting on another [GIS Day Georef-a-thon](https://library.osu.edu/events/gis-day-2024) just like [they did last year](https://waml.org/waml-information-bulletin/volume-55-number-2/piloting-a-sanborn-map-georef-a-thon/). This is an in-person event, and part of a full day of GIS talks, all of which look fascinating. Do check it out if you are in the Columbus area!

## Georeference-a-thons of Present

Not exactly _present_, but just a couple days ago the team at the URichmond [Digital Scholarship Lab](http://dsl.richmond.edu/) held a _competitive_ georeference-a-thon (the first of its kind with _OIM_) and it sure looked like a good time! Riley set up a point system for georeferenced content, complete with the option to challenge the quality of another team&#39;s work to reduce their score.

![](https://mradamcox.github.io/theme/img/1-crop.jpg)

In addition to points for georeferencing, teams also had to do some scavenger-hunting across the 1905 Richmond map to answer questions like _&#34;Across N. 11th St. from City Hall is where you can find the ________ HOTEL&#34;_ , or _&#34;Just_ _east of Shockoe Slip is where you can find _______ COFFEE CO.&#34;

![](https://mradamcox.github.io/theme/img/3-crop.jpg)

Congrats to the big winners (and some familiar names from the platform!!): _ibrahimalkaser_, _samyoga_, _bakeunsu_, and _willguy_.

## Georeference-a-thons of Past

Finally, we owe a big and belated thank you to everyone that showed up to the events we did with HistoryForge at Second Line Brewing in New Orleans, this past August. It was unexpectedly great to do two weeks in a row because it felt like we built some momentum, even though there were very few people who came both days.

![](https://mradamcox.github.io/theme/img/IMG_6231-crop.jpg)

All together, we had about 25 people attend, made it through the entirety of [New Orleans, 1908, Vol. 2](https://oldinsurancemaps.net/map/sanborn03376_010), and _much_ of [Vol. 3](https://oldinsurancemaps.net/map/sanborn03376_011) as well. Once these mosaics are completed and trimmed, we&#39;ll be able to add them to the local HistoryForge [project](https://sela.historyforge.net/forge), to help with trascribing and mapping historical US Census documents.

\\r\\n

## Presentation(s) at NACIS in October

\\r\\n

Last month I traveled to the annual North American Cartographic Information Society meeting, this year in Tacoma, WA, and presented about _OldInsuranceMaps.net._ The video of the talk is now on YouTube: [Handling Complex Content within Georeferenced Historical Atlases](https://www.youtube.com/watch?v=DhRrZgCedqk). You can also flip through the slides here: [tiny.cc/nacis2024-ac](https://tiny.cc/nacis2024-ac). Even though it sounds pretty boring, this was extremely gratifying to put together and present, because it distills what I think is most unique about the platform.

As a lucky bonus, Riley Champine from the URichmond DSL presented in the same session right after me, so I encourage you to watch his talk as well: [Using Old Maps for New Insights on America’s Cities](https://www.youtube.com/watch?v=SK_2n5QStBs). He discusses updates to the lab&#39;s _Mapping Inequality_ project, and near the end has a fantastic demo of their new project _Fires of Industry_, that is based on the monumental georeferencing effort their students are carrying out using _OldInsuranceMaps.net_. I heard a few &#34;wows&#34; in the audience when he showed this.

## Finally: Data Agreement

As I have written in this newsletter before, I have been working toward being more precise about what happens with user-contributed data on OldInsuranceMaps.net. I have now added a [Data Agreement](https://oldinsurancemaps.net/data-agreement), that states the following (in summary—see linked page for more details):

_Two core goals of_ OldInsuranceMaps.net _are:_

-  _To facilitate historical map georeferencing and mosaicking in a streamlined and participatory environment_
-  _To create publicly accessible datasets that can be used by anyone for any purpose_

_To that end,_ OldInsuranceMaps.net _collects user-contributed georeferencing data, and **insofar as any of this data is copyrightable, users agree that their copyright is waived and [CC0](https://creativecommons.org/publicdomain/zero/1.0/) license is applied**._

_The platform also records the georeferencing-related actions that a user takes while interacting with it, and uses [Plausible Analytics](https://plausible.io/privacy-focused-web-analytics) to collect general statistics about visitors to the site. No private user information is collected._

I will reiterate as I have said before: **If you have already created content on the site, but would _not_ like to have it available under these conditions: Please get back to me and I will help you download it and will then remove it.** No problem at all! The files should be very easy to self-host.

---

Thanks, as always for reading, and hope to see some of you next week!

Adam
</source:markdown>
    </item>
    
    <item>
      <title>&#34;Handling Complex Content within Georeferenced Historical Atlases&#34; </title>
      <link>https://blog.oldinsurancemaps.net/2024/11/14/handling-complex-content-within-georeferenced/</link>
      <pubDate>Thu, 14 Nov 2024 19:00:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2024/11/15/handling-complex-content-within-georeferenced/</guid>
      <description>&lt;p&gt;Last month I traveled to the annual North American Cartographic Information Society meeting, this year in Tacoma, WA, and presented about &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;&lt;em&gt;OldInsuranceMaps.net&lt;/em&gt;&lt;/a&gt;&lt;em&gt;.&lt;/em&gt; The video of the talk is now on YouTube: &lt;a href=&#34;https://www.youtube.com/watch?v=DhRrZgCedqk&#34;&gt;Handling Complex Content within Georeferenced Historical Atlases&lt;/a&gt;. You can also flip through the slides here: &lt;a href=&#34;http://tiny.cc/nacis2024-ac&#34;&gt;tiny.cc/nacis2024-ac&lt;/a&gt;. Even though it sounds pretty boring, this was extremely gratifying to put together and present, because it distills what I think is most unique about the platform.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Abstract:&lt;/strong&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;While georeferencing a single map is an easy one-off process, applying the work across a whole atlas (or multi-volume set) is a challenging task&amp;ndash;especially when pages have multiple insets and the atlas contains more than one category of maps. How do you structure this work, and create cohesive output? This presentation will describe the novel hierarchical approach within &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt;, a crowdsourced web georeferencing platform designed around the complexities of Sanborn fire insurance maps. Facilitating the creation of seamless mosaics from this collection has resulted in a robust, abstract workflow that could be applied to any other maps or collections as well.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I made a bunch of diagrams for the presentation using &lt;a href=&#34;https://d2lang.com&#34;&gt;d2&lt;/a&gt;, and here is my favorite one:&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/new-iberia-1885-full-workflow.skwkkw2n-2vyhnd.webp&#34; width=&#34;600&#34; height=&#34;623&#34; alt=&#34;&#34;&gt;
&lt;p&gt;As a lucky bonus, Riley Champine from the URichmond DSL presented in the same session right after me, so I encourage you to watch his talk as well: &lt;a href=&#34;https://www.youtube.com/watch?v=SK_2n5QStBs&#34;&gt;Using Old Maps for New Insights on America’s Cities&lt;/a&gt;. He discusses updates to the lab&amp;rsquo;s &lt;em&gt;Mapping Inequality&lt;/em&gt; project, and near the end has a fantastic demo of their new project &lt;em&gt;Fires of Industry&lt;/em&gt;, that is based on the monumental georeferencing effort their students are carrying out using &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;&lt;em&gt;OldInsuranceMaps.net&lt;/em&gt;&lt;/a&gt;. I heard a few &amp;ldquo;wows&amp;rdquo; in the audience when he showed this.&lt;/p&gt;
</description>
      <source:markdown>Last month I traveled to the annual North American Cartographic Information Society meeting, this year in Tacoma, WA, and presented about [_OldInsuranceMaps.net_](http://OldInsuranceMaps.net)_._ The video of the talk is now on YouTube: [Handling Complex Content within Georeferenced Historical Atlases](https://www.youtube.com/watch?v=DhRrZgCedqk). You can also flip through the slides here: [tiny.cc/nacis2024-ac](http://tiny.cc/nacis2024-ac). Even though it sounds pretty boring, this was extremely gratifying to put together and present, because it distills what I think is most unique about the platform.

**Abstract:**

&gt; While georeferencing a single map is an easy one-off process, applying the work across a whole atlas (or multi-volume set) is a challenging task--especially when pages have multiple insets and the atlas contains more than one category of maps. How do you structure this work, and create cohesive output? This presentation will describe the novel hierarchical approach within [OldInsuranceMaps.net](http://OldInsuranceMaps.net), a crowdsourced web georeferencing platform designed around the complexities of Sanborn fire insurance maps. Facilitating the creation of seamless mosaics from this collection has resulted in a robust, abstract workflow that could be applied to any other maps or collections as well.

I made a bunch of diagrams for the presentation using [d2](https://d2lang.com), and here is my favorite one:

&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/new-iberia-1885-full-workflow.skwkkw2n-2vyhnd.webp&#34; width=&#34;600&#34; height=&#34;623&#34; alt=&#34;&#34;&gt;

As a lucky bonus, Riley Champine from the URichmond DSL presented in the same session right after me, so I encourage you to watch his talk as well: [Using Old Maps for New Insights on America’s Cities](https://www.youtube.com/watch?v=SK_2n5QStBs). He discusses updates to the lab&#39;s _Mapping Inequality_ project, and near the end has a fantastic demo of their new project _Fires of Industry_, that is based on the monumental georeferencing effort their students are carrying out using [_OldInsuranceMaps.net_](http://OldInsuranceMaps.net). I heard a few &#34;wows&#34; in the audience when he showed this.
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: Fall 2024</title>
      <link>https://blog.oldinsurancemaps.net/2024/09/13/newsletter-fall/</link>
      <pubDate>Fri, 13 Sep 2024 14:00:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2024/09/13/newsletter-fall/</guid>
      <description>&lt;h2 id=&#34;upcoming-georeference-a-thons&#34;&gt;Upcoming Georeference-a-thons!&lt;/h2&gt;
&lt;p&gt;Here in New Orleans we have two public Georeference-a-thons &lt;strong&gt;&lt;em&gt;right around the corner!&lt;/em&gt;&lt;/strong&gt; On the next two Tuesdays we will be gathering at &lt;a href=&#34;https://www.secondlinebrewing.com/&#34;&gt;Second Line Brewing&lt;/a&gt; (as before) from 6:30 to 8:30pm to georeference more New Orleans Sanborn maps for &lt;a href=&#34;https://sela.historyforge.net/forge&#34;&gt;&lt;em&gt;HistoryForge.&lt;/em&gt;&lt;/a&gt; We did this last summer, and the resulting work has been integrated directly into the &lt;em&gt;HistoryForge&lt;/em&gt; platform (as you can see in the link, click the map icon). Having the Sanborn map layers is very helpful for tracking down old US Census records, and makes exploring the city&amp;rsquo;s history even more engaging. Hope to see you there!&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://mradamcox.github.io/theme/img/flyer.jpg&#34; alt=&#34;Flyer&#34;&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://docs.google.com/forms/d/e/1FAIpQLScGrN_XTk9u0CrmXXTPjvA4Qgfxjuxhpq227oF1hBe9MP9xew/viewform&#34;&gt;RSVP Form&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A big thank you to Elizabeth from &lt;em&gt;HistoryForge&lt;/em&gt; for making the flyer!&lt;/p&gt;
&lt;h2 id=&#34;cc-licensing-update&#34;&gt;CC licensing update&lt;/h2&gt;
&lt;p&gt;Last winter, I &lt;a href=&#34;https://oldinsurancemaps.net/news/2023-year-in-review/&#34;&gt;wrote&lt;/a&gt; about my interest in applying a &lt;a href=&#34;https://creativecommons.org/licenses/by/4.0/&#34;&gt;CC BY&lt;/a&gt; license to the work that people have completed on &lt;em&gt;OldInsuranceMaps.net&lt;/em&gt;. Since then, I have done much more research on the topic by reaching out to people with experience in other crowdsourcing applications, as well as copyright experts within university libraries. Overall, I&amp;rsquo;ve found that &lt;a href=&#34;https://creativecommons.org/public-domain/cc0/&#34;&gt;&lt;strong&gt;CC0&lt;/strong&gt;&lt;/a&gt; &lt;strong&gt;will be a better fit for contributed content on the site,&lt;/strong&gt; which would place individual contributions &amp;ldquo;as completely as possible in the public domain,&amp;rdquo; to borrow Creative Commons language. &lt;em&gt;CC0&lt;/em&gt; is the most permissive Creative Commons license, and will allow the use of map content for research, personal, or commercial use. &lt;em&gt;CC BY&lt;/em&gt; would require that attribution be given whenever content is used elsewhere, which sounds good in theory but would bring a level of enforcement and legal burden that I am not able to meet in practice.&lt;/p&gt;
&lt;p&gt;\r\n&lt;/p&gt;
&lt;p&gt;More importantly, however, I&amp;rsquo;ve learned that the data created through the georeferencing process is unlikely to be considered copyrightable in the first place, because the cut-lines, ground control points, and masks are effectively recordation of facts (&amp;ldquo;this is the boundary of an inset&amp;rdquo;, &amp;ldquo;this pixel coordinate corresponds to that lat/long&amp;rdquo;), and facts cannot be copyrighted. So the language I will be adopting soon will be along the lines of:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&amp;ldquo;To the extent that contributed content on OldInsuranceMaps.net can be considered copyrightable, a CC0 license is applied.&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;As before: If you are not comfortable with the work you have contributed being available through such a license, please get in touch with me ASAP. I will happily help you download/save your work elsewhere and remove it from the site.&lt;/p&gt;
&lt;h2 id=&#34;other-recent-work&#34;&gt;Other Recent Work&amp;hellip;&lt;/h2&gt;
&lt;p&gt;I have been working a lot in the past few weeks on a big re-modeling project within the database, which I hope to have fully implemented by next week. (But it has been a complex process so we&amp;rsquo;ll just see how it goes&amp;hellip;) You can read these &lt;a href=&#34;https://github.com/ohmg-dev/OldInsuranceMaps/pull/212&#34;&gt;pull request notes&lt;/a&gt; for more details on the changes. Some of the outward improvements that this will make possible are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Grouping mosaics from multiple volumes for better display in the viewer (currently this is kind of a mess for cities with many volumes, like the 10 new ones in &lt;a href=&#34;https://oldinsurancemaps.net/viewer/new-orleans-la/?sanborn03376_034=100&amp;amp;sanborn03376_032=100&amp;amp;sanborn03376_031=100&amp;amp;sanborn03376_030=100&amp;amp;sanborn03376_029=100&amp;amp;sanborn03376_028=100&amp;amp;sanborn03376_027=100&amp;amp;sanborn03376_026=100&amp;amp;sanborn03376_025=100&amp;amp;sanborn03376_024=100&amp;amp;sanborn03376_005=100&amp;amp;sanborn03376_004=100&amp;amp;sanborn03376_003=100&amp;amp;sanborn03376_002=100&amp;amp;sanborn03376_001=100#/center/-90.0618,29.9627&#34;&gt;New Orleans&lt;/a&gt; from the 1951 edition)&lt;/li&gt;
&lt;li&gt;A data model that more closely reflects the structure of the &lt;a href=&#34;https://preview.iiif.io/api/georef/extension/georef/&#34;&gt;IIIF Georeference Extension&lt;/a&gt;, laying groundwork for its eventual adaption within the platform&lt;/li&gt;
&lt;li&gt;Complete (well, almost complete) removal of the dependency on LOC&amp;rsquo;s map collection&amp;ndash;a big step toward making the system more generic overall.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This is the topic I&amp;rsquo;ll be &lt;a href=&#34;https://nacis2024.sched.com/event/1gtkD/making-connections-session-2-track-3&#34;&gt;presenting about at NACIS&lt;/a&gt; next month in Tacoma, so if you are attending the meeting please say hello! Even better, Riley Champine from the University of Richmond&amp;rsquo;s Digital Scholarship Lab will be in the same session, talking about their work at the DSL, and in part their use of &lt;em&gt;OldInsuranceMaps.net.&lt;/em&gt; I think these talks will be recorded, so I&amp;rsquo;ll be sure to pass links to them on eventually.&lt;/p&gt;
&lt;p&gt;All the best,&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;
</description>
      <source:markdown>## Upcoming Georeference-a-thons!

Here in New Orleans we have two public Georeference-a-thons **_right around the corner!_** On the next two Tuesdays we will be gathering at [Second Line Brewing](https://www.secondlinebrewing.com/) (as before) from 6:30 to 8:30pm to georeference more New Orleans Sanborn maps for [_HistoryForge._](https://sela.historyforge.net/forge) We did this last summer, and the resulting work has been integrated directly into the _HistoryForge_ platform (as you can see in the link, click the map icon). Having the Sanborn map layers is very helpful for tracking down old US Census records, and makes exploring the city&#39;s history even more engaging. Hope to see you there!

![Flyer](https://mradamcox.github.io/theme/img/flyer.jpg)

[RSVP Form](https://docs.google.com/forms/d/e/1FAIpQLScGrN_XTk9u0CrmXXTPjvA4Qgfxjuxhpq227oF1hBe9MP9xew/viewform)

A big thank you to Elizabeth from _HistoryForge_ for making the flyer!

## CC licensing update

Last winter, I [wrote](https://oldinsurancemaps.net/news/2023-year-in-review/) about my interest in applying a [CC BY](https://creativecommons.org/licenses/by/4.0/) license to the work that people have completed on _OldInsuranceMaps.net_. Since then, I have done much more research on the topic by reaching out to people with experience in other crowdsourcing applications, as well as copyright experts within university libraries. Overall, I&#39;ve found that [**CC0**](https://creativecommons.org/public-domain/cc0/) **will be a better fit for contributed content on the site,** which would place individual contributions &#34;as completely as possible in the public domain,&#34; to borrow Creative Commons language. _CC0_ is the most permissive Creative Commons license, and will allow the use of map content for research, personal, or commercial use. _CC BY_ would require that attribution be given whenever content is used elsewhere, which sounds good in theory but would bring a level of enforcement and legal burden that I am not able to meet in practice.

\\r\\n

More importantly, however, I&#39;ve learned that the data created through the georeferencing process is unlikely to be considered copyrightable in the first place, because the cut-lines, ground control points, and masks are effectively recordation of facts (&#34;this is the boundary of an inset&#34;, &#34;this pixel coordinate corresponds to that lat/long&#34;), and facts cannot be copyrighted. So the language I will be adopting soon will be along the lines of:

_&#34;To the extent that contributed content on OldInsuranceMaps.net can be considered copyrightable, a CC0 license is applied.&#34;_

As before: If you are not comfortable with the work you have contributed being available through such a license, please get in touch with me ASAP. I will happily help you download/save your work elsewhere and remove it from the site.

## Other Recent Work...

I have been working a lot in the past few weeks on a big re-modeling project within the database, which I hope to have fully implemented by next week. (But it has been a complex process so we&#39;ll just see how it goes...) You can read these [pull request notes](https://github.com/ohmg-dev/OldInsuranceMaps/pull/212) for more details on the changes. Some of the outward improvements that this will make possible are:

- Grouping mosaics from multiple volumes for better display in the viewer (currently this is kind of a mess for cities with many volumes, like the 10 new ones in [New Orleans](https://oldinsurancemaps.net/viewer/new-orleans-la/?sanborn03376_034=100&amp;sanborn03376_032=100&amp;sanborn03376_031=100&amp;sanborn03376_030=100&amp;sanborn03376_029=100&amp;sanborn03376_028=100&amp;sanborn03376_027=100&amp;sanborn03376_026=100&amp;sanborn03376_025=100&amp;sanborn03376_024=100&amp;sanborn03376_005=100&amp;sanborn03376_004=100&amp;sanborn03376_003=100&amp;sanborn03376_002=100&amp;sanborn03376_001=100#/center/-90.0618,29.9627) from the 1951 edition)
- A data model that more closely reflects the structure of the [IIIF Georeference Extension](https://preview.iiif.io/api/georef/extension/georef/), laying groundwork for its eventual adaption within the platform
- Complete (well, almost complete) removal of the dependency on LOC&#39;s map collection--a big step toward making the system more generic overall.

This is the topic I&#39;ll be [presenting about at NACIS](https://nacis2024.sched.com/event/1gtkD/making-connections-session-2-track-3) next month in Tacoma, so if you are attending the meeting please say hello! Even better, Riley Champine from the University of Richmond&#39;s Digital Scholarship Lab will be in the same session, talking about their work at the DSL, and in part their use of _OldInsuranceMaps.net._ I think these talks will be recorded, so I&#39;ll be sure to pass links to them on eventually.


All the best,

Adam
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: Spring and Mid-Summer Updates 2024</title>
      <link>https://blog.oldinsurancemaps.net/2024/06/24/newsletter-spring-and-midsummer-updates/</link>
      <pubDate>Mon, 24 Jun 2024 08:24:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2024/06/24/newsletter-spring-and-midsummer-updates/</guid>
      <description>&lt;p&gt;Hello! The last newsletter I sent out was &lt;em&gt;&lt;a href=&#34;https://oldinsurancemaps.net/news/2023-year-in-review/&#34;&gt;over half a year ago&lt;/a&gt;,&lt;/em&gt; so a lot has happened in the meantime (including: I got married!). I&amp;rsquo;ll get to most of the updates here, but hopefully will be able to follow-up sooner than later with more. Before going further, I&amp;rsquo;d like to welcome the 50+ new folks who have registered since the year started. Looking forward to hearing and seeing what you work on! Which is a good segue to the next point&amp;hellip;&lt;/p&gt;
&lt;h3 id=&#34;we-have-a-new-community-forum&#34;&gt;We have a new Community Forum!&lt;/h3&gt;
&lt;p&gt;Jeff Meyer at OpenHistoricalMap suggested that we make a dedicated &lt;a href=&#34;https://forum.openhistoricalmap.org/c/oldinsurancemaps/13&#34;&gt;category for OldInsuranceMaps.net&lt;/a&gt; within the existing OHM forum. This provides a permanent, external location to have discussions and post about what people are working on. So, please don&amp;rsquo;t be shy, let us know what cities you are georeferencing (or have worked on in the past :)). Moreover, do you have a city in mind but haven&amp;rsquo;t been able to georeference it yourself? Use the forum to let us know, maybe someone else would like to work on it with you. All questions and comments welcome!&lt;/p&gt;
&lt;h3 id=&#34;recent-publications-about-oldinsurancemapsnet&#34;&gt;Recent publications about OldInsuranceMaps.net&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://waml.org/waml-information-bulletin/volume-55-number-2/piloting-a-sanborn-map-georef-a-thon&#34;&gt;Piloting a Sanborn Map Georef-a-thon for GIS Day 2023&lt;/a&gt;, WAML Information Bulletin, Western Association of Map Libraries. 2024. Josh Sadvari and Michelle Hooper
&lt;ul&gt;
&lt;li&gt;Josh and Michelle hosted a Georef-a-thon last fall at OSU Libraries using OldInsuranceMaps.net, and wrote this great piece about how it went (spoiler: really well!).&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://southrichmondnews.com/2024/02/12/scroll-though-time-with-the-sanborn-fire-maps/&#34;&gt;Scroll through Time with the Sanborn Fire Insurance Maps&lt;/a&gt;, South Richmond News. February 12, 2024. John M. and Riley Champine
&lt;ul&gt;
&lt;li&gt;This article in the South Richmond News highlights historical maps on OldInsuranceMaps.net in Richmond, VA, georeferencing work completed by the URichmond DSL.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://doi.org/10.1080/15420353.2024.2326812&#34;&gt;Toward a Georeferencing Commons: A Crowdsourcing Case Study and the Creation of OldInsuranceMaps.Net&lt;/a&gt; (&lt;a href=&#34;https://hcommons.org/deposits/item/hc:64725/&#34;&gt;link for open access version&lt;/a&gt;), Journal of Map &amp;amp; Geography Libraries, March 2024. Adam Cox.
&lt;ul&gt;
&lt;li&gt;Finally, I&amp;rsquo;ve created an article-length abridgment of my MS thesis, which was the beginning of this whole project.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;stats&#34;&gt;Stats!&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;220 cities have at least &lt;em&gt;some&lt;/em&gt; maps georeferenced&lt;/li&gt;
&lt;li&gt;550 maps (or &amp;ldquo;volumes&amp;rdquo;), completed or in-progress across all cities&lt;/li&gt;
&lt;li&gt;17,500 individual layers within these maps&lt;/li&gt;
&lt;li&gt;230 registered users&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;So much of this content has been created by staff and students at the URichmond DSL lab. They are doing fantastic work! This must be the largest Sanborn map georeferencing effort that has been undertaken in a public platform, by far.&lt;/p&gt;
&lt;h3 id=&#34;other-new-things&#34;&gt;Other new things&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;New About website and documentation location &lt;a href=&#34;https://about.oldinsurancemaps.net&#34;&gt;https://about.oldinsurancemaps.net&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;New Github organization for better repository management/namespacing: &lt;a href=&#34;https://github.com/ohmg-dev&#34;&gt;https://github.com/ohmg-dev&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;New content about the underlying workflow structure: &lt;a href=&#34;https://www.ohmg.dev/concepts&#34;&gt;https://www.ohmg.dev/concepts&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;p&gt;Until next time,&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;
</description>
      <source:markdown>Hello! The last newsletter I sent out was _[over half a year ago](https://oldinsurancemaps.net/news/2023-year-in-review/),_ so a lot has happened in the meantime (including: I got married!). I&#39;ll get to most of the updates here, but hopefully will be able to follow-up sooner than later with more. Before going further, I&#39;d like to welcome the 50+ new folks who have registered since the year started. Looking forward to hearing and seeing what you work on! Which is a good segue to the next point...

### We have a new Community Forum!

Jeff Meyer at OpenHistoricalMap suggested that we make a dedicated [category for OldInsuranceMaps.net](https://forum.openhistoricalmap.org/c/oldinsurancemaps/13) within the existing OHM forum. This provides a permanent, external location to have discussions and post about what people are working on. So, please don&#39;t be shy, let us know what cities you are georeferencing (or have worked on in the past :)). Moreover, do you have a city in mind but haven&#39;t been able to georeference it yourself? Use the forum to let us know, maybe someone else would like to work on it with you. All questions and comments welcome!

### Recent publications about OldInsuranceMaps.net

- [Piloting a Sanborn Map Georef-a-thon for GIS Day 2023](https://waml.org/waml-information-bulletin/volume-55-number-2/piloting-a-sanborn-map-georef-a-thon), WAML Information Bulletin, Western Association of Map Libraries. 2024. Josh Sadvari and Michelle Hooper
  - Josh and Michelle hosted a Georef-a-thon last fall at OSU Libraries using OldInsuranceMaps.net, and wrote this great piece about how it went (spoiler: really well!).
- [Scroll through Time with the Sanborn Fire Insurance Maps](https://southrichmondnews.com/2024/02/12/scroll-though-time-with-the-sanborn-fire-maps/), South Richmond News. February 12, 2024. John M. and Riley Champine
  - This article in the South Richmond News highlights historical maps on OldInsuranceMaps.net in Richmond, VA, georeferencing work completed by the URichmond DSL.
- [Toward a Georeferencing Commons: A Crowdsourcing Case Study and the Creation of OldInsuranceMaps.Net](https://doi.org/10.1080/15420353.2024.2326812) ([link for open access version](https://hcommons.org/deposits/item/hc:64725/)), Journal of Map &amp; Geography Libraries, March 2024. Adam Cox.
  - Finally, I&#39;ve created an article-length abridgment of my MS thesis, which was the beginning of this whole project.

### Stats!

- 220 cities have at least _some_ maps georeferenced
- 550 maps (or &#34;volumes&#34;), completed or in-progress across all cities
- 17,500 individual layers within these maps
- 230 registered users

So much of this content has been created by staff and students at the URichmond DSL lab. They are doing fantastic work! This must be the largest Sanborn map georeferencing effort that has been undertaken in a public platform, by far.

### Other new things

- New About website and documentation location [https://about.oldinsurancemaps.net](https://about.oldinsurancemaps.net)
- New Github organization for better repository management/namespacing: [https://github.com/ohmg-dev](https://github.com/ohmg-dev)
- New content about the underlying workflow structure: [https://www.ohmg.dev/concepts](https://www.ohmg.dev/concepts)

---

Until next time,

Adam
</source:markdown>
    </item>
    
    <item>
      <title>&#34;Piloting a Sanborn Map Georef-a-thon for GIS Day 2023&#34;</title>
      <link>https://blog.oldinsurancemaps.net/2024/06/23/piloting-a-sanborn-map-georefathon/</link>
      <pubDate>Sun, 23 Jun 2024 18:00:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2024/06/23/piloting-a-sanborn-map-georefathon/</guid>
      <description>&lt;p&gt;Last November, Josh Sadvari and Michelle Hooper hosted a Georef-a-thon at The Ohio State University Libraries using &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt;, and wrote this detailed piece about how they prepared for the event, how the platform worked for them, and what kind of engagement their participants got from the experience.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://waml.org/waml-information-bulletin/volume-55-number-2/piloting-a-sanborn-map-georef-a-thon/&#34;&gt;Piloting a Sanborn Map Georef-a-thon for GIS Day 2023&lt;/a&gt;, WAML Information Bulletin, Western Association of Map Libraries. 2024. Josh Sadvari and Michelle Hooper&lt;/p&gt;
&lt;p&gt;Some nice quotes from the article, that illustrate how the event was able to expand knowledge and appreciation of historical maps:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Very few georef-a-thon participants indicated they had previously used or even heard of Sanborn maps when asked this question during the introduction, which reinforces how such an activity can help in creating awareness of the potential uses of this collection.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;The &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt; platform provides a low barrier entry point for teaching spatial and data literacy concepts through georeferencing and engaging students in the “process” of geospatial data, illustrating a standalone educational value that was perhaps not envisioned as a specific outcome during the platform’s conceptualization and development but could be one nonetheless&lt;/p&gt;
&lt;/blockquote&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/piloting-article-headline.webp&#34;&gt;
</description>
      <source:markdown>Last November, Josh Sadvari and Michelle Hooper hosted a Georef-a-thon at The Ohio State University Libraries using [OldInsuranceMaps.net](http://OldInsuranceMaps.net), and wrote this detailed piece about how they prepared for the event, how the platform worked for them, and what kind of engagement their participants got from the experience.

[Piloting a Sanborn Map Georef-a-thon for GIS Day 2023](https://waml.org/waml-information-bulletin/volume-55-number-2/piloting-a-sanborn-map-georef-a-thon/), WAML Information Bulletin, Western Association of Map Libraries. 2024. Josh Sadvari and Michelle Hooper

Some nice quotes from the article, that illustrate how the event was able to expand knowledge and appreciation of historical maps:

&gt; Very few georef-a-thon participants indicated they had previously used or even heard of Sanborn maps when asked this question during the introduction, which reinforces how such an activity can help in creating awareness of the potential uses of this collection.

&gt; The [OldInsuranceMaps.net](http://OldInsuranceMaps.net) platform provides a low barrier entry point for teaching spatial and data literacy concepts through georeferencing and engaging students in the “process” of geospatial data, illustrating a standalone educational value that was perhaps not envisioned as a specific outcome during the platform’s conceptualization and development but could be one nonetheless


&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/piloting-article-headline.webp&#34;&gt;
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: 2023 Year in Review</title>
      <link>https://blog.oldinsurancemaps.net/2023/12/31/year-in-review/</link>
      <pubDate>Sun, 31 Dec 2023 14:39:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2023/12/31/year-in-review/</guid>
      <description>&lt;p&gt;Hello everyone and welcome to the final newsletter of 2023! It was last January that I made an announcement letting you all know we were back in business here, and since then a lot of wonderful things have come from the project. First, a couple of recent things I haven&amp;rsquo;t yet told you about&amp;hellip;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;As always, you can reply with comments or questions directly to this email (it won&amp;rsquo;t be a &amp;ldquo;reply all&amp;rdquo;!), or &lt;a href=&#34;https://oldinsurancemaps.net/news/&#34;&gt;view past newsletters here&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;on-development-seeds-blog&#34;&gt;On Development Seed&amp;rsquo;s Blog&lt;/h2&gt;
&lt;p&gt;Over the course of the year I worked with Kiri Carini and Sanjay Bhangar at Development Seed to create a post about OldInsuranceMaps.net, and we finally released it on Dec. 1st: &lt;a href=&#34;http://devseed.com/blog/2023-12-01-spotlight-oldinsurancemaps&#34;&gt;Open Source Spotlight: Old Insurance Maps&lt;/a&gt;.  This year I completed a transition to using DevSeed&amp;rsquo;s open source software, TiTiler, to serve all raster layers and because it is typically used for tiling satellite imagery, they were excited to see my use of it for historical maps. The blog post is one of the more detailed things I&amp;rsquo;ve written about the tech side of the platform, I encourage you to check it out!&lt;/p&gt;
&lt;h2 id=&#34;on-maps-mania-blog&#34;&gt;On Maps Mania Blog&lt;/h2&gt;
&lt;p&gt;A few days after that, the &lt;a href=&#34;https://googlemapsmania.blogspot.com/&#34;&gt;Maps Mania&lt;/a&gt; blog (which I have followed for a while and I highly recommend to anyone who likes maps) also featured OldInsuranceMaps.net in a nice post, &lt;a href=&#34;https://googlemapsmania.blogspot.com/2021/02/historical-sanborn-maps-of-america.html&#34;&gt;Historical Sanborn Maps of America&lt;/a&gt;. Very happy for this exposure, though there&amp;rsquo;s nothing to make you feel like you need to improve a home page like all of a sudden having a hundred new people look at it :/.&lt;/p&gt;
&lt;h2 id=&#34;boring-but-very-important-upcoming-cc-by-license-implementation&#34;&gt;Boring But Very Important: Upcoming CC BY License Implementation&lt;/h2&gt;
&lt;p&gt;As more institutions have started using the platform to georeference content, it&amp;rsquo;s time to formalize licensing for content that is created on the site. At its heart, this is a collaborative crowdsourcing platform that facilitates the transformation of, access to, and public engagement with historical map content. With this in mind, &lt;strong&gt;I plan to implement the &lt;a href=&#34;https://creativecommons.org/licenses/by/4.0/&#34;&gt;CC BY 4.0&lt;/a&gt; license for all georeferenced content that is created on OldInsuranceMaps.net&lt;/strong&gt;. Creative Commons licenses offer a formal way to ensure that content is shareable, and the BY extension requires only that attribution be given when the content is used in other contexts. When I finalize this decision with a statement on the website, I&amp;rsquo;ll provide more info on how to give credit (probably something like &amp;ldquo;OldInsuranceMaps.net contributors&amp;rdquo;, a la OpenStreetMap).&lt;/p&gt;
&lt;p&gt;Once implemented, the CC BY 4.0 license would be applied to the following (existing and future) content on OldInsuranceMaps.net:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;User input data: cut-lines, ground control points, and trim mask coordinates.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Geospatial datasets derived from this data: georeferenced layers and full trimmed mosaics.&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Generally, this content is all free and downloadable already, so I see the CC BY 4.0 license as a way to formalize what has already been in place for almost 2 years now.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;That said:&lt;/em&gt; If you have georeferenced maps on OldInsuranceMaps.net and you do not want this license to be applied to your work, then I have absolutely no problem with helping you download everything you&amp;rsquo;ve created and then I will remove it from the site.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Finally:&lt;/em&gt; If you have experience with CC licenses and/or licensing for crowdsourced content, I would love to hear your thoughts on this! Just reply directly to this email.&lt;/p&gt;
&lt;h2 id=&#34;2023-stats-and-summary&#34;&gt;2023 Stats and Summary&lt;/h2&gt;
&lt;p&gt;Now that that is out of the way, back to the year-in-review with some stats and graphs. Over the last year, OldInsuranceMaps.net has received ~5,000 unique visitors. Most importantly, the trendline is clearly going up (spikes correspond to newsletters, georeferencing-events, etc.).&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://mradamcox.github.io/theme/img/plausible-2023.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;p&gt;Visitorship is one thing, but what about the georeferencing?? Overall, 4,500 new layers have been georeferenced this year.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://mradamcox.github.io/theme/img/2023-sessions.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;
&lt;p&gt;Of course, a huge proportion of that is the incredible effort by students and staff at the University of Richmond DSL starting in September (this work continues). We&amp;rsquo;ll have much more about this effort and what it is achieving in the future. For now, I&amp;rsquo;ll just shoutout Riley for managing this effort, and to the top-notch georeferencers involved:&lt;/p&gt;
&lt;p&gt;wendyle, samyoga, nayers, 10varun17, jattys, JacksonSB, Shelby_m_richards, mekletb, amara017, mirandam, AYAH, and NyKyaSM (sorry if I missed anyone!).&lt;/p&gt;
&lt;p&gt;But there have also been a lot of great independent efforts over the last year that I&amp;rsquo;d like to highlight. For example:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Nolan in &lt;a href=&#34;https://oldinsurancemaps.net/viewer/des-moines-ia?utm_source=newsletter12&#34;&gt;Des Moines, IA&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Kevin in &lt;a href=&#34;https://oldinsurancemaps.net/viewer/macon-bibb-county-ga?utm_source=newsletter12&#34;&gt;Macon, GA&lt;/a&gt; (and many other nearby towns)&lt;/li&gt;
&lt;li&gt;Tod in &lt;a href=&#34;https://oldinsurancemaps.net/viewer/salt-lake-city-ut?utm_source=newsletter12&#34;&gt;Salt Lake City, UT&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;tagifford in &lt;a href=&#34;https://oldinsurancemaps.net/viewer/schenectady-ny?utm_source=newsletter12&#34;&gt;Schenectady, NY&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Ian in &lt;a href=&#34;https://oldinsurancemaps.net/viewer/st-paul-mn?utm_source=newsletter12&#34;&gt;St. Paul, MN&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Jason in &lt;a href=&#34;https://oldinsurancemaps.net/viewer/essex-county-nj/?utm_source=newsletter12&#34;&gt;Essex County, NJ&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Pete in &lt;a href=&#34;https://oldinsurancemaps.net/viewer/menlo-park-ca?utm_source=newsletter12&#34;&gt;Menlo Park, CA&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I know there are a handful of other folks who have request maps be added but haven&amp;rsquo;t gotten a chance to work on them yet, so look out for much more in the coming year!&lt;/p&gt;
&lt;h3 id=&#34;georef-a-thons&#34;&gt;Georef-a-thons&lt;/h3&gt;
&lt;p&gt;We held two small events at Second Line Brewing in New Orleans this past summer, especially to support HistoryForge&amp;rsquo;s use of the site for their New Orleans project (more HistoryForge collaboration coming next year). We created a &lt;a href=&#34;https://oldinsurancemaps.net/viewer/new-orleans-la/?sanborn03376_005=100#/center/-90.0725,29.9686/zoom/15&#34;&gt;beautiful mosaic&lt;/a&gt; of a 1896 New Orleans volume (and had a few beers too).&lt;/p&gt;
&lt;p&gt;Then, in November, Josh and Michelle at Ohio State University held a GIS Day event where they had 30 people participate and georeferenced almost 200 sheets of Columbus maps in 4 hours! I&amp;rsquo;ll be able to share a nice write-up in the next few months, and they already have another event planned for &lt;a href=&#34;https://library.osu.edu/events/international-love-data-week-2024&#34;&gt;International Love Data Week&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;thanks-for-a-great-year&#34;&gt;Thanks for a great year!&lt;/h2&gt;
&lt;p&gt;Finally, a huge thank you to people this year that helped out, gave advice, or got involved some way or another, in addition to all of the contributors listed above&amp;hellip; Jeff Meyers at OpenHistoricalMap; Eve Snyder and Elizabeth Williams at HistoryForge; Rob Nelson and Riley Champine at University of Richmond DSL; and Josh Sadvari at OSU Libraries&amp;hellip; to name just a few. The project owes much to you all!&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s been a great year, and I have no doubt 2024 will see a huge expansion of the usership, engagement, and georeferencing capabilities on the platform.&lt;/p&gt;
&lt;p&gt;Happy New Year!&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;
&lt;p&gt;p.s. I&amp;rsquo;ve just run out of time and space to describe the tech updates that the past year has seen&amp;hellip; if that interests you, see the DevSeed blog post linked above.&lt;/p&gt;
</description>
      <source:markdown>Hello everyone and welcome to the final newsletter of 2023! It was last January that I made an announcement letting you all know we were back in business here, and since then a lot of wonderful things have come from the project. First, a couple of recent things I haven&#39;t yet told you about...

_As always, you can reply with comments or questions directly to this email (it won&#39;t be a &#34;reply all&#34;!), or [view past newsletters here](https://oldinsurancemaps.net/news/)._

## On Development Seed&#39;s Blog

Over the course of the year I worked with Kiri Carini and Sanjay Bhangar at Development Seed to create a post about OldInsuranceMaps.net, and we finally released it on Dec. 1st: [Open Source Spotlight: Old Insurance Maps](http://devseed.com/blog/2023-12-01-spotlight-oldinsurancemaps).  This year I completed a transition to using DevSeed&#39;s open source software, TiTiler, to serve all raster layers and because it is typically used for tiling satellite imagery, they were excited to see my use of it for historical maps. The blog post is one of the more detailed things I&#39;ve written about the tech side of the platform, I encourage you to check it out!

## On Maps Mania Blog

A few days after that, the [Maps Mania](https://googlemapsmania.blogspot.com/) blog (which I have followed for a while and I highly recommend to anyone who likes maps) also featured OldInsuranceMaps.net in a nice post, [Historical Sanborn Maps of America](https://googlemapsmania.blogspot.com/2021/02/historical-sanborn-maps-of-america.html). Very happy for this exposure, though there&#39;s nothing to make you feel like you need to improve a home page like all of a sudden having a hundred new people look at it :/.

## Boring But Very Important: Upcoming CC BY License Implementation

As more institutions have started using the platform to georeference content, it&#39;s time to formalize licensing for content that is created on the site. At its heart, this is a collaborative crowdsourcing platform that facilitates the transformation of, access to, and public engagement with historical map content. With this in mind, **I plan to implement the [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) license for all georeferenced content that is created on OldInsuranceMaps.net**. Creative Commons licenses offer a formal way to ensure that content is shareable, and the BY extension requires only that attribution be given when the content is used in other contexts. When I finalize this decision with a statement on the website, I&#39;ll provide more info on how to give credit (probably something like &#34;OldInsuranceMaps.net contributors&#34;, a la OpenStreetMap).

Once implemented, the CC BY 4.0 license would be applied to the following (existing and future) content on OldInsuranceMaps.net:

- **User input data: cut-lines, ground control points, and trim mask coordinates.**
- **Geospatial datasets derived from this data: georeferenced layers and full trimmed mosaics.**

Generally, this content is all free and downloadable already, so I see the CC BY 4.0 license as a way to formalize what has already been in place for almost 2 years now.

_That said:_ If you have georeferenced maps on OldInsuranceMaps.net and you do not want this license to be applied to your work, then I have absolutely no problem with helping you download everything you&#39;ve created and then I will remove it from the site.

_Finally:_ If you have experience with CC licenses and/or licensing for crowdsourced content, I would love to hear your thoughts on this! Just reply directly to this email.

## 2023 Stats and Summary

Now that that is out of the way, back to the year-in-review with some stats and graphs. Over the last year, OldInsuranceMaps.net has received ~5,000 unique visitors. Most importantly, the trendline is clearly going up (spikes correspond to newsletters, georeferencing-events, etc.).

![](https://mradamcox.github.io/theme/img/plausible-2023.png)

Visitorship is one thing, but what about the georeferencing?? Overall, 4,500 new layers have been georeferenced this year.

![](https://mradamcox.github.io/theme/img/2023-sessions.png)

Of course, a huge proportion of that is the incredible effort by students and staff at the University of Richmond DSL starting in September (this work continues). We&#39;ll have much more about this effort and what it is achieving in the future. For now, I&#39;ll just shoutout Riley for managing this effort, and to the top-notch georeferencers involved:

wendyle, samyoga, nayers, 10varun17, jattys, JacksonSB, Shelby_m_richards, mekletb, amara017, mirandam, AYAH, and NyKyaSM (sorry if I missed anyone!).

But there have also been a lot of great independent efforts over the last year that I&#39;d like to highlight. For example:

- Nolan in [Des Moines, IA](https://oldinsurancemaps.net/viewer/des-moines-ia?utm_source=newsletter12)
- Kevin in [Macon, GA](https://oldinsurancemaps.net/viewer/macon-bibb-county-ga?utm_source=newsletter12) (and many other nearby towns)
- Tod in [Salt Lake City, UT](https://oldinsurancemaps.net/viewer/salt-lake-city-ut?utm_source=newsletter12)
- tagifford in [Schenectady, NY](https://oldinsurancemaps.net/viewer/schenectady-ny?utm_source=newsletter12)
- Ian in [St. Paul, MN](https://oldinsurancemaps.net/viewer/st-paul-mn?utm_source=newsletter12)
- Jason in [Essex County, NJ](https://oldinsurancemaps.net/viewer/essex-county-nj/?utm_source=newsletter12)
- Pete in [Menlo Park, CA](https://oldinsurancemaps.net/viewer/menlo-park-ca?utm_source=newsletter12)

I know there are a handful of other folks who have request maps be added but haven&#39;t gotten a chance to work on them yet, so look out for much more in the coming year!

### Georef-a-thons

We held two small events at Second Line Brewing in New Orleans this past summer, especially to support HistoryForge&#39;s use of the site for their New Orleans project (more HistoryForge collaboration coming next year). We created a [beautiful mosaic](https://oldinsurancemaps.net/viewer/new-orleans-la/?sanborn03376_005=100#/center/-90.0725,29.9686/zoom/15) of a 1896 New Orleans volume (and had a few beers too).

Then, in November, Josh and Michelle at Ohio State University held a GIS Day event where they had 30 people participate and georeferenced almost 200 sheets of Columbus maps in 4 hours! I&#39;ll be able to share a nice write-up in the next few months, and they already have another event planned for [International Love Data Week](https://library.osu.edu/events/international-love-data-week-2024).

## Thanks for a great year!

Finally, a huge thank you to people this year that helped out, gave advice, or got involved some way or another, in addition to all of the contributors listed above... Jeff Meyers at OpenHistoricalMap; Eve Snyder and Elizabeth Williams at HistoryForge; Rob Nelson and Riley Champine at University of Richmond DSL; and Josh Sadvari at OSU Libraries... to name just a few. The project owes much to you all!

It&#39;s been a great year, and I have no doubt 2024 will see a huge expansion of the usership, engagement, and georeferencing capabilities on the platform.

Happy New Year!

Adam

p.s. I&#39;ve just run out of time and space to describe the tech updates that the past year has seen... if that interests you, see the DevSeed blog post linked above.
</source:markdown>
    </item>
    
    <item>
      <title>Dev Seed: Open Source Spotlight - Old Insurance Maps</title>
      <link>https://blog.oldinsurancemaps.net/2023/12/09/dev-seed-open-source-spotlight/</link>
      <pubDate>Sat, 09 Dec 2023 19:00:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2023/12/10/dev-seed-open-source-spotlight/</guid>
      <description>&lt;p&gt;Working with Kiri and Sanjay from Development Seed, we put together this post for Dev Seed&amp;rsquo;s blog: &lt;a href=&#34;https://developmentseed.org/blog/2023-12-01-spotlight-oldinsurancemaps/&#34;&gt;Open Source Spotlight - Old Insurance Maps.&lt;/a&gt; This came about because Kiri saw my presentation at FOSS4G Southeast in Nashville last year, where I described how I had reworked &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt; to use &lt;a href=&#34;https://developmentseed.org/titiler/&#34;&gt;TiTiler&lt;/a&gt; (open source software that Dev Seed created and maintains) for dynamic raster tiling, replacing GeoServer which had been incorporated into the platform from the beginning.&lt;/p&gt;
&lt;p&gt;It was very satisfying to put this piece together, and get to talk more about the tech stack that makes OldInsuranceMaps work.&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/devseed-post-snippet.webp&#34;&gt;
</description>
      <source:markdown>Working with Kiri and Sanjay from Development Seed, we put together this post for Dev Seed&#39;s blog: [Open Source Spotlight - Old Insurance Maps.](https://developmentseed.org/blog/2023-12-01-spotlight-oldinsurancemaps/) This came about because Kiri saw my presentation at FOSS4G Southeast in Nashville last year, where I described how I had reworked [OldInsuranceMaps.net](http://OldInsuranceMaps.net) to use [TiTiler](https://developmentseed.org/titiler/) (open source software that Dev Seed created and maintains) for dynamic raster tiling, replacing GeoServer which had been incorporated into the platform from the beginning.

It was very satisfying to put this piece together, and get to talk more about the tech stack that makes OldInsuranceMaps work.


&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/devseed-post-snippet.webp&#34;&gt;
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: Fall 2023 | Virtual Presentation Tomorrow</title>
      <link>https://blog.oldinsurancemaps.net/2023/10/25/newsletter-fall-virtual-presentation-tomorrow/</link>
      <pubDate>Wed, 25 Oct 2023 23:03:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2023/10/25/newsletter-fall-virtual-presentation-tomorrow/</guid>
      <description>&lt;h2 id=&#34;healthy-regions--policies-lab-speaker-series-tomorrow&#34;&gt;Healthy Regions &amp;amp; Policies Lab Speaker Series: Tomorrow!&lt;/h2&gt;
&lt;p&gt;I will be presenting (virtually) to the Geography &amp;amp; GIScience department at the University of Illinois tomorrow, as part of the Healthy Regions &amp;amp; Policies Lab monthly speaker series. I&amp;rsquo;m really looking forward to this&amp;ndash;it will largely be an introduction and summary of OldInsuranceMaps.net, but I also plan to highlight a bit of the work that the students at University of Richmond have been doing recently. And, anyone can join via Zoom! 12pm Central Time, 40-45 minutes.&lt;/p&gt;
&lt;p&gt;More info here: &lt;a href=&#34;https://healthyregions.org/2023/10/25/october-speaker-series-creating-oldinsurancemaps-net/&#34;&gt;https://healthyregions.org/2023/10/25/october-speaker-series-creating-oldinsurancemaps-net/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Register here: &lt;a href=&#34;https://go.illinois.edu/herop-series-adam&#34;&gt;https://go.illinois.edu/herop-series-adam&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;historyforge-a-wms-integration-success-story&#34;&gt;HistoryForge: A WMS Integration Success Story&lt;/h2&gt;
&lt;p&gt;Working with the HistoryForge team we have gotten the mosaicked New Orleans 1895, vol. 1 edition into their web map interface! You can find it in the map overlays at &lt;a href=&#34;https://sela.historyforge.net/forge&#34;&gt;https://sela.historyforge.net/forge&lt;/a&gt;. (Also admire the Robinson Atlas and other layers Elizabeth has added while you are there!) Some may recall this edition was the focus of our first georeference-a-thon this past summer. Happy to see it in use outside of OldInsuranceMaps.net! The best thing about this integration is that it spurred some development on the HF platform, so now &lt;em&gt;any&lt;/em&gt; maps/mosaics from OldInsuranceMaps.net can be pulled directly in. No need to move files, etc. I have a feeling there will be more HF collaboration in the future!&lt;/p&gt;
&lt;p&gt;On the tech side, I&amp;rsquo;d like to acknowledge Github user &lt;em&gt;mindless-bureaucrat&lt;/em&gt; (and of course endless appreciation for &lt;em&gt;Vincent Sarago)&lt;/em&gt; who &lt;a href=&#34;https://github.com/developmentseed/titiler/pull/572&#34;&gt;added a WMS endpoint to TiTiler&lt;/a&gt; early this year. When they did, I knew it would be useful to us sooner or later, and HistoryForge is a wonderful first use. Now any sheets or mosaics from OldInsuranceMaps.net are available through this standard (get in touch if using layers that way interests you!).&lt;/p&gt;
&lt;h2 id=&#34;other-news-constant-activity&#34;&gt;Other News&amp;hellip; Constant Activity&lt;/h2&gt;
&lt;p&gt;Not too many other &amp;ldquo;big news&amp;rdquo; items to report at the moment, but everyday 20-30 new layers are georeferenced&amp;hellip; Checkout the &lt;a href=&#34;https://oldinsurancemaps.net/activity&#34;&gt;activity&lt;/a&gt; page if you haven&amp;rsquo;t already, and head to the volume summaries to watch the mosaics grow.&lt;/p&gt;
&lt;h2 id=&#34;the-spooky-season&#34;&gt;The Spooky Season&lt;/h2&gt;
&lt;p&gt;Spent a little time last night finding undertakers for you. Enjoy!&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://oldinsurancemaps.net/viewer/new-orleans-la/?sanborn03376_002=76#/center/-90.05793,29.96302/zoom/20.3&#34;&gt;New Orleans, La. (1885)&lt;/a&gt;, &lt;a href=&#34;https://oldinsurancemaps.net/viewer/shreveport-la/?sanborn03401_007=68#/center/-93.75136,32.51202/zoom/21&#34;&gt;Shreveport, La. (1909)&lt;/a&gt;, &lt;a href=&#34;https://oldinsurancemaps.net/viewer/savannah-ga/?sanborn01500_008=95#/center/-81.08635,32.07425/zoom/20&#34;&gt;Savannah, Ga. (1955)&lt;/a&gt;, &lt;a href=&#34;https://oldinsurancemaps.net/viewer/sacramento-ca/?sanborn00799_006=90#/center/-121.50218,38.57608/zoom/19.6&#34;&gt;Sacramento, Ca. (1949)&lt;/a&gt;, and &lt;a href=&#34;https://oldinsurancemaps.net/viewer/birmingham-al/?sanborn00015_014=71#/center/-86.81549,33.51729/zoom/20.6&#34;&gt;Birmingham, Al. (1951)&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Bonus: &lt;a href=&#34;https://oldinsurancemaps.net/viewer/pittsburgh-pa/?sanborn07911_007=85#/center/-80.00028,40.44141/zoom/21.1&#34;&gt;Artificial Limb Factory&lt;/a&gt; in Pittsburgh (1905).&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;That&amp;rsquo;s all for now, thanks for reading, and maybe see some of you tomorrow!&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;
&lt;p&gt;p.s. As always, you can reply directly to this email with questions or thoughts.&lt;/p&gt;
</description>
      <source:markdown>## Healthy Regions &amp; Policies Lab Speaker Series: Tomorrow!

I will be presenting (virtually) to the Geography &amp; GIScience department at the University of Illinois tomorrow, as part of the Healthy Regions &amp; Policies Lab monthly speaker series. I&#39;m really looking forward to this--it will largely be an introduction and summary of OldInsuranceMaps.net, but I also plan to highlight a bit of the work that the students at University of Richmond have been doing recently. And, anyone can join via Zoom! 12pm Central Time, 40-45 minutes.

More info here: [https://healthyregions.org/2023/10/25/october-speaker-series-creating-oldinsurancemaps-net/](https://healthyregions.org/2023/10/25/october-speaker-series-creating-oldinsurancemaps-net/)

Register here: [https://go.illinois.edu/herop-series-adam](https://go.illinois.edu/herop-series-adam)

## HistoryForge: A WMS Integration Success Story

Working with the HistoryForge team we have gotten the mosaicked New Orleans 1895, vol. 1 edition into their web map interface! You can find it in the map overlays at [https://sela.historyforge.net/forge](https://sela.historyforge.net/forge). (Also admire the Robinson Atlas and other layers Elizabeth has added while you are there!) Some may recall this edition was the focus of our first georeference-a-thon this past summer. Happy to see it in use outside of OldInsuranceMaps.net! The best thing about this integration is that it spurred some development on the HF platform, so now _any_ maps/mosaics from OldInsuranceMaps.net can be pulled directly in. No need to move files, etc. I have a feeling there will be more HF collaboration in the future!

On the tech side, I&#39;d like to acknowledge Github user _mindless-bureaucrat_ (and of course endless appreciation for _Vincent Sarago)_ who [added a WMS endpoint to TiTiler](https://github.com/developmentseed/titiler/pull/572) early this year. When they did, I knew it would be useful to us sooner or later, and HistoryForge is a wonderful first use. Now any sheets or mosaics from OldInsuranceMaps.net are available through this standard (get in touch if using layers that way interests you!).

## Other News... Constant Activity

Not too many other &#34;big news&#34; items to report at the moment, but everyday 20-30 new layers are georeferenced... Checkout the [activity](https://oldinsurancemaps.net/activity) page if you haven&#39;t already, and head to the volume summaries to watch the mosaics grow.

## The Spooky Season

Spent a little time last night finding undertakers for you. Enjoy!

[New Orleans, La. (1885)](https://oldinsurancemaps.net/viewer/new-orleans-la/?sanborn03376_002=76#/center/-90.05793,29.96302/zoom/20.3), [Shreveport, La. (1909)](https://oldinsurancemaps.net/viewer/shreveport-la/?sanborn03401_007=68#/center/-93.75136,32.51202/zoom/21), [Savannah, Ga. (1955)](https://oldinsurancemaps.net/viewer/savannah-ga/?sanborn01500_008=95#/center/-81.08635,32.07425/zoom/20), [Sacramento, Ca. (1949)](https://oldinsurancemaps.net/viewer/sacramento-ca/?sanborn00799_006=90#/center/-121.50218,38.57608/zoom/19.6), and [Birmingham, Al. (1951)](https://oldinsurancemaps.net/viewer/birmingham-al/?sanborn00015_014=71#/center/-86.81549,33.51729/zoom/20.6).

Bonus: [Artificial Limb Factory](https://oldinsurancemaps.net/viewer/pittsburgh-pa/?sanborn07911_007=85#/center/-80.00028,40.44141/zoom/21.1) in Pittsburgh (1905).

---

That&#39;s all for now, thanks for reading, and maybe see some of you tomorrow!

Adam

p.s. As always, you can reply directly to this email with questions or thoughts.
</source:markdown>
    </item>
    
    <item>
      <title>HistoryForge: A WMS Integration Success Story</title>
      <link>https://blog.oldinsurancemaps.net/2023/10/25/historyforge-a-wms-integration-success/</link>
      <pubDate>Wed, 25 Oct 2023 18:00:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2023/10/25/historyforge-a-wms-integration-success/</guid>
      <description>&lt;p&gt;Working with the &lt;a href=&#34;https://historyforge.net&#34;&gt;HistoryForge&lt;/a&gt; team we have gotten the mosaicked New Orleans 1895, vol. 1 edition into their web map interface! You can find it in the map overlays at &lt;a href=&#34;https://sela.historyforge.net/forge&#34;&gt;https://sela.historyforge.net/forge&lt;/a&gt;. (Also admire the Robinson Atlas and other layers Elizabeth has added while you are there!) Some may recall this edition was the focus of our first georeference-a-thon this past summer. Happy to see it in use outside of &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt;! The best thing about this integration is that it spurred some development on the HF platform, so now &lt;em&gt;any&lt;/em&gt; maps/mosaics from &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt; can be pulled directly in. No need to move files, etc. I have a feeling there will be more HF collaboration in the future!&lt;/p&gt;
&lt;p&gt;On the tech side, I&amp;rsquo;d like to acknowledge Github user &lt;em&gt;mindless-bureaucrat&lt;/em&gt; who &lt;a href=&#34;https://github.com/developmentseed/titiler/pull/572&#34;&gt;added a WMS endpoint to TiTiler&lt;/a&gt; early this year (and of course endless appreciation for TiTiler&amp;rsquo;s core maintainer, &lt;a href=&#34;https://github.com/vincentsarago&#34;&gt;Vincent Sarago&lt;/a&gt;). When they did, I knew it would be useful to us sooner or later, and HistoryForge is a wonderful first use. Now any sheets or mosaics from &lt;a href=&#34;http://OldInsuranceMaps.net&#34;&gt;OldInsuranceMaps.net&lt;/a&gt; are available through this standard (get in touch if using layers that way interests you!).&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/history-forge-points.webp&#34;&gt;
</description>
      <source:markdown>Working with the [HistoryForge](https://historyforge.net) team we have gotten the mosaicked New Orleans 1895, vol. 1 edition into their web map interface! You can find it in the map overlays at [https://sela.historyforge.net/forge](https://sela.historyforge.net/forge). (Also admire the Robinson Atlas and other layers Elizabeth has added while you are there!) Some may recall this edition was the focus of our first georeference-a-thon this past summer. Happy to see it in use outside of [OldInsuranceMaps.net](http://OldInsuranceMaps.net)! The best thing about this integration is that it spurred some development on the HF platform, so now _any_ maps/mosaics from [OldInsuranceMaps.net](http://OldInsuranceMaps.net) can be pulled directly in. No need to move files, etc. I have a feeling there will be more HF collaboration in the future!

On the tech side, I&#39;d like to acknowledge Github user _mindless-bureaucrat_ who [added a WMS endpoint to TiTiler](https://github.com/developmentseed/titiler/pull/572) early this year (and of course endless appreciation for TiTiler&#39;s core maintainer, [Vincent Sarago](https://github.com/vincentsarago)). When they did, I knew it would be useful to us sooner or later, and HistoryForge is a wonderful first use. Now any sheets or mosaics from [OldInsuranceMaps.net](http://OldInsuranceMaps.net) are available through this standard (get in touch if using layers that way interests you!).


&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/history-forge-points.webp&#34;&gt;
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: July &#43; Aug &#43; 1/2 Sept = Big Updates</title>
      <link>https://blog.oldinsurancemaps.net/2023/09/18/newsletter-july-aug-sept-big/</link>
      <pubDate>Mon, 18 Sep 2023 14:48:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2023/09/18/newsletter-july-aug-sept-big/</guid>
      <description>&lt;p&gt;Hello everyone, and welcome to a characteristically long-overdue newsletter. &lt;em&gt;Much&lt;/em&gt; to report.&lt;/p&gt;
&lt;h2 id=&#34;collaboration-with-university-of-richmond-dsl-and-university-of-michigan&#34;&gt;Collaboration with University of Richmond DSL and University of Michigan&lt;/h2&gt;
&lt;p&gt;I’m &lt;em&gt;very&lt;/em&gt; excited to announce that beginning this month, a large team of University of Richmond students is now using OldInsuranceMaps.net for a massive georeferencing effort led by Rob Nelson and Riley Champine at the &lt;a href=&#34;http://dsl.richmond.edu/&#34;&gt;Digital Scholarship Lab&lt;/a&gt;. The work will be a foundational component of &lt;a href=&#34;https://reporter.nih.gov/search/bCrnkRo-rkWJJXyXqsj44g/project-details/10582012&#34;&gt;an NIH grant&lt;/a&gt; undertaken through a partnership between the University of Michigan &lt;a href=&#34;https://isr.umich.edu&#34;&gt;Institute for Social Research&lt;/a&gt;, the Richmond DSL, and the &lt;a href=&#34;https://ncrc.org&#34;&gt;National Community Reinvestment Coalition&lt;/a&gt;. Here&amp;rsquo;s the &lt;a href=&#34;https://isr.umich.edu/news-events/news-releases/grant-to-enable-creation-of-new-data-resources-for-studying-structural-racism/&#34;&gt;ISR press release&lt;/a&gt; for more info.&lt;/p&gt;
&lt;p&gt;What this means for OldInsuranceMaps.net is pretty incredible: the University of Michigan is now a funder of the project, and, perhaps more excitingly, the students are already making progress on cities like &lt;a href=&#34;https://oldinsurancemaps.net/loc/sanborn00015_014/?utm_source=newsletter10&#34;&gt;Birmingham&lt;/a&gt;, &lt;a href=&#34;https://oldinsurancemaps.net/loc/sanborn01309_014/?utm_source=newsletter10&#34;&gt;Miami&lt;/a&gt;, &lt;a href=&#34;https://oldinsurancemaps.net/loc/sanborn00799_006/?utm_source=newsletter10&#34;&gt;Sacramento&lt;/a&gt;, and many others.. Also, my new(ish) full-time position at the &lt;a href=&#34;https://healthyregions.org/&#34;&gt;Healthy Regions &amp;amp; Policies Lab&lt;/a&gt;, University of Illinois Urbana-Champaign, will allow a bit of time to be put toward the effort, so my heartflet thanks to everyone that is making this possible!&lt;/p&gt;
&lt;p&gt;A shoutout again to Jeff Meyer at OpenHistoricalMap for including me in his presentation at SOTMUS in Richmond&amp;ndash;it&amp;rsquo;s how this new collaboration came about. That presentation video is now on &lt;a href=&#34;https://www.youtube.com/watch?v=rKkAzJr25YU&amp;amp;pp=ygUac290bXVzIG9obSBvcGVuIHN0cmVldCBtYXA%3D&#34;&gt;YouTube&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;oldinsurancemaps-on-soar&#34;&gt;OldInsuranceMaps on Soar&lt;/h2&gt;
&lt;p&gt;The folks behind &lt;a href=&#34;https://soar.earth&#34;&gt;Soar&lt;/a&gt; got in touch earlier this summer with an interest in getting mosaics from OldInsuranceMaps into their digital atlas, and I&amp;rsquo;ve pursued this because it is a such a good opportunity to get these maps in front of more people, and perhaps even drive some georeferencing activity as well.&lt;/p&gt;
&lt;p&gt;There will be more to say about the Soar in coming weeks, but in the meantime checkout the new &lt;a href=&#34;https://soar.earth/profile/76430f2f7b664cf6928684ecc023d2ff&#34;&gt;OldInsuranceMaps (.net)&lt;/a&gt; account where I&amp;rsquo;ve been trying out some mosaic uploads. Soar offers nice features like the ability to bookmark, comment on, and even embed the maps in other web pages, and they&amp;rsquo;ve recently &lt;a href=&#34;https://about.soar.earth/blog-pages/installing-and-using-soars-qgis-plugin&#34;&gt;released a QGIS plugin&lt;/a&gt;, which you can use to search and use any maps in their platform. Many new ways to engage with these maps.&lt;/p&gt;
&lt;h2 id=&#34;action-in-central-georgia&#34;&gt;Action in Central Georgia!&lt;/h2&gt;
&lt;p&gt;A couple of months ago Kevin Haywood, a cartographer from Macon, Georgia got in touch, (donated!), and requested the addition of a few volumes. Well, now you can explore &lt;a href=&#34;https://oldinsurancemaps.net/viewer/macon-bibb-county-ga/?utm_source=newsletter10&#34;&gt;Macon in 1908&lt;/a&gt;, &lt;a href=&#34;https://oldinsurancemaps.net/viewer/milledgeville-ga/?sanborn01475_006=100&amp;amp;utm_source=newsletter10#/center/-83.2271,33.0816/zoom/16&#34;&gt;Milledgeville (6 years of coverage)&lt;/a&gt;, and &lt;a href=&#34;https://oldinsurancemaps.net/viewer/forsyth-ga/?sanborn01436_007=100&amp;amp;utm_source=newsletter10&#34;&gt;Forsyth in 1920!&lt;/a&gt; The work was a hit with a local history groups in the area, which is a category of people I&amp;rsquo;ve had in mind from the beginning&amp;ndash;so happy to see this kind of interest. Thanks Kevin, and to anyone reading from Georgia, check out his &lt;a href=&#34;http://www.maphiker.info/&#34;&gt;trail maps&lt;/a&gt; next time you go adventuring!&lt;/p&gt;
&lt;h2 id=&#34;georeference-a-thon-update&#34;&gt;Georeference-a-thon Update&lt;/h2&gt;
&lt;p&gt;An exceptionally belated thank you to Eliot, Rick, Hoon, and Nicole who came out to the last georeference-a-thon we had at Second Line Brewing, yes, all the way back in June :/. We continued to work on &lt;a href=&#34;https://oldinsurancemaps.net/loc/sanborn03376_005/?utm_source=newsletter10&#34;&gt;New Orleans 1896 vol. 1&lt;/a&gt;, and since then Elizabeth at HistoryForge has finished it up. It looks great. She and I are working now to integrate that mosaic into the Southeast Louisiana HistoryForge (more news on that to come).&lt;/p&gt;
&lt;p&gt;As for future georeference-a-thons, some folks have already approached me about supporting an event for &lt;a href=&#34;https://www.gisday.com/en-us/overview&#34;&gt;GIS day&lt;/a&gt; (November 15th, in case you weren&amp;rsquo;t aware of this holiday). If an event on that day interests people in the New Orleans area, please get in touch! Maybe we will have simultaneous events in multiple locations&amp;hellip;&lt;/p&gt;
&lt;h2 id=&#34;performance-improvement-and-site-updates&#34;&gt;Performance Improvement and Site Updates&lt;/h2&gt;
&lt;p&gt;As usual, there are a few developments to the platform itself that I&amp;rsquo;d like to highlight:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt; I&amp;rsquo;ve implemented much &lt;a href=&#34;https://github.com/mradamcox/ohmg/pull/145&#34;&gt;better image compression&lt;/a&gt; (literally reduced storage needs by 90%) and then rewarped all of the layers. You may notice some &amp;ldquo;edge artifacts&amp;rdquo; around the layers at lower zoom levels, before a layer has been trimmed (a very small price to pay).&lt;/li&gt;
&lt;li&gt;To support the Richmond work, we&amp;rsquo;ve upgraded our server instance, and this, combined with me learning about a GDAL setting I should have known about before (oops), speeds the actual background warping process up &lt;em&gt;significantly&lt;/em&gt;, just about 5-6 seconds per full page, instead of 20-30. Another great improvement.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Also&lt;/em&gt; to support the Richmond work, I&amp;rsquo;ve added an &lt;a href=&#34;https://oldinsurancemaps.net/activity/?utm_source=newsletter10&#34;&gt;Activity&lt;/a&gt; page so it&amp;rsquo;s easy to see the latest work sessions at any time.&lt;/li&gt;
&lt;li&gt;Finally, a bit of cleaning up the main nav bar and added &lt;a href=&#34;https://oldinsurancemaps.net/about/?utm_source=newsletter10&#34;&gt;About&lt;/a&gt; and &lt;a href=&#34;https://oldinsurancemaps.net/faq/?utm_source=newsletter10&#34;&gt;FAQ&lt;/a&gt; pages. I know there are probably some FAQs I still have to address there, so if you have suggestions, please get in touch.&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;p&gt;That&amp;rsquo;s all for now! Thanks for your interest, and as always, you can reply directly to this email with questions or feedback.&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;
&lt;p&gt;p.s. I would love help with putting together this newsletter on a more regular basis (maybe a recent work highlights section??) and generally improving it. Let me know if you have free time and would be interested in helping out.&lt;/p&gt;
</description>
      <source:markdown>Hello everyone, and welcome to a characteristically long-overdue newsletter. _Much_ to report.

## Collaboration with University of Richmond DSL and University of Michigan

I’m _very_ excited to announce that beginning this month, a large team of University of Richmond students is now using OldInsuranceMaps.net for a massive georeferencing effort led by Rob Nelson and Riley Champine at the [Digital Scholarship Lab](http://dsl.richmond.edu/). The work will be a foundational component of [an NIH grant](https://reporter.nih.gov/search/bCrnkRo-rkWJJXyXqsj44g/project-details/10582012) undertaken through a partnership between the University of Michigan [Institute for Social Research](https://isr.umich.edu), the Richmond DSL, and the [National Community Reinvestment Coalition](https://ncrc.org). Here&#39;s the [ISR press release](https://isr.umich.edu/news-events/news-releases/grant-to-enable-creation-of-new-data-resources-for-studying-structural-racism/) for more info.

What this means for OldInsuranceMaps.net is pretty incredible: the University of Michigan is now a funder of the project, and, perhaps more excitingly, the students are already making progress on cities like [Birmingham](https://oldinsurancemaps.net/loc/sanborn00015_014/?utm_source=newsletter10), [Miami](https://oldinsurancemaps.net/loc/sanborn01309_014/?utm_source=newsletter10), [Sacramento](https://oldinsurancemaps.net/loc/sanborn00799_006/?utm_source=newsletter10), and many others.. Also, my new(ish) full-time position at the [Healthy Regions &amp; Policies Lab](https://healthyregions.org/), University of Illinois Urbana-Champaign, will allow a bit of time to be put toward the effort, so my heartflet thanks to everyone that is making this possible!

A shoutout again to Jeff Meyer at OpenHistoricalMap for including me in his presentation at SOTMUS in Richmond--it&#39;s how this new collaboration came about. That presentation video is now on [YouTube](https://www.youtube.com/watch?v=rKkAzJr25YU&amp;pp=ygUac290bXVzIG9obSBvcGVuIHN0cmVldCBtYXA%3D).

## OldInsuranceMaps on Soar

The folks behind [Soar](https://soar.earth) got in touch earlier this summer with an interest in getting mosaics from OldInsuranceMaps into their digital atlas, and I&#39;ve pursued this because it is a such a good opportunity to get these maps in front of more people, and perhaps even drive some georeferencing activity as well.

There will be more to say about the Soar in coming weeks, but in the meantime checkout the new [OldInsuranceMaps (.net)](https://soar.earth/profile/76430f2f7b664cf6928684ecc023d2ff) account where I&#39;ve been trying out some mosaic uploads. Soar offers nice features like the ability to bookmark, comment on, and even embed the maps in other web pages, and they&#39;ve recently [released a QGIS plugin](https://about.soar.earth/blog-pages/installing-and-using-soars-qgis-plugin), which you can use to search and use any maps in their platform. Many new ways to engage with these maps.

## Action in Central Georgia!

A couple of months ago Kevin Haywood, a cartographer from Macon, Georgia got in touch, (donated!), and requested the addition of a few volumes. Well, now you can explore [Macon in 1908](https://oldinsurancemaps.net/viewer/macon-bibb-county-ga/?utm_source=newsletter10), [Milledgeville (6 years of coverage)](https://oldinsurancemaps.net/viewer/milledgeville-ga/?sanborn01475_006=100&amp;utm_source=newsletter10#/center/-83.2271,33.0816/zoom/16), and [Forsyth in 1920!](https://oldinsurancemaps.net/viewer/forsyth-ga/?sanborn01436_007=100&amp;utm_source=newsletter10) The work was a hit with a local history groups in the area, which is a category of people I&#39;ve had in mind from the beginning--so happy to see this kind of interest. Thanks Kevin, and to anyone reading from Georgia, check out his [trail maps](http://www.maphiker.info/) next time you go adventuring!

## Georeference-a-thon Update

An exceptionally belated thank you to Eliot, Rick, Hoon, and Nicole who came out to the last georeference-a-thon we had at Second Line Brewing, yes, all the way back in June :/. We continued to work on [New Orleans 1896 vol. 1](https://oldinsurancemaps.net/loc/sanborn03376_005/?utm_source=newsletter10), and since then Elizabeth at HistoryForge has finished it up. It looks great. She and I are working now to integrate that mosaic into the Southeast Louisiana HistoryForge (more news on that to come).

As for future georeference-a-thons, some folks have already approached me about supporting an event for [GIS day](https://www.gisday.com/en-us/overview) (November 15th, in case you weren&#39;t aware of this holiday). If an event on that day interests people in the New Orleans area, please get in touch! Maybe we will have simultaneous events in multiple locations...

## Performance Improvement and Site Updates

As usual, there are a few developments to the platform itself that I&#39;d like to highlight:

1.   I&#39;ve implemented much [better image compression](https://github.com/mradamcox/ohmg/pull/145) (literally reduced storage needs by 90%) and then rewarped all of the layers. You may notice some &#34;edge artifacts&#34; around the layers at lower zoom levels, before a layer has been trimmed (a very small price to pay).
2.  To support the Richmond work, we&#39;ve upgraded our server instance, and this, combined with me learning about a GDAL setting I should have known about before (oops), speeds the actual background warping process up _significantly_, just about 5-6 seconds per full page, instead of 20-30. Another great improvement.
3.  _Also_ to support the Richmond work, I&#39;ve added an [Activity](https://oldinsurancemaps.net/activity/?utm_source=newsletter10) page so it&#39;s easy to see the latest work sessions at any time.
4.  Finally, a bit of cleaning up the main nav bar and added [About](https://oldinsurancemaps.net/about/?utm_source=newsletter10) and [FAQ](https://oldinsurancemaps.net/faq/?utm_source=newsletter10) pages. I know there are probably some FAQs I still have to address there, so if you have suggestions, please get in touch.

---

That&#39;s all for now! Thanks for your interest, and as always, you can reply directly to this email with questions or feedback.

Adam


p.s. I would love help with putting together this newsletter on a more regular basis (maybe a recent work highlights section??) and generally improving it. Let me know if you have free time and would be interested in helping out.
</source:markdown>
    </item>
    
    <item>
      <title>&#34;Mapping the turn of the Century with OHM and OldInsuranceMaps.net&#34; w</title>
      <link>https://blog.oldinsurancemaps.net/2023/07/10/mapping-the-turn-of-the/</link>
      <pubDate>Mon, 10 Jul 2023 18:00:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2023/07/10/mapping-the-turn-of-the/</guid>
      <description>&lt;p&gt;In June I went to Richmond, Va. to present with Jeff Meyer from &lt;a href=&#34;https://openhistoricalmap.org&#34;&gt;OpenHistoricalMap&lt;/a&gt; at the State of the Map US, an annual meeting for the OpenStreetMap US organization. It was a fantastic conference, and our presentation &amp;ldquo;&lt;strong&gt;Mapping the turn of the Century with OHM and OldInsuranceMaps.net&amp;rdquo;&lt;/strong&gt; was really well-received. We demonstrated how people can georeference maps in OIM and then turn around and use them as basemap layers in OHM to digitize historical buildings and other features. The next day we did a workshop as well, where people used this workflow with Sanborn maps of Richmond.&lt;/p&gt;
&lt;p&gt;[Video of the presentation here on YouTube: &lt;a href=&#34;https://www.youtube.com/watch?v=rKkAzJr25YU%5D(https://www.youtube.com/watch?v=rKkAzJr25YU)&#34;&gt;www.youtube.com/watch&lt;/a&gt;&lt;/p&gt;
&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/sotmus-logo-2023.webp&#34;&gt;
</description>
      <source:markdown>In June I went to Richmond, Va. to present with Jeff Meyer from [OpenHistoricalMap](https://openhistoricalmap.org) at the State of the Map US, an annual meeting for the OpenStreetMap US organization. It was a fantastic conference, and our presentation &#34;**Mapping the turn of the Century with OHM and OldInsuranceMaps.net&#34;** was really well-received. We demonstrated how people can georeference maps in OIM and then turn around and use them as basemap layers in OHM to digitize historical buildings and other features. The next day we did a workshop as well, where people used this workflow with Sanborn maps of Richmond.

[Video of the presentation here on YouTube: [www.youtube.com/watch](https://www.youtube.com/watch?v=rKkAzJr25YU](https://www.youtube.com/watch?v=rKkAzJr25YU))


&lt;img src=&#34;https://cdn.uploads.micro.blog/280698/2025/sotmus-logo-2023.webp&#34;&gt;
</source:markdown>
    </item>
    
    <item>
      <title>Newsletter: Summer 2023</title>
      <link>https://blog.oldinsurancemaps.net/2023/06/14/newsletter-summer/</link>
      <pubDate>Wed, 14 Jun 2023 13:46:00 -0500</pubDate>
      
      <guid>http://oldinsurancemaps.micro.blog/2023/06/14/newsletter-summer/</guid>
      <description>&lt;p&gt;Hello all! Some announcements and recaps, plus a few updates on (subtle but important) improvements to the site.&lt;/p&gt;
&lt;p&gt;Before going further though, I&amp;rsquo;ve scheduled &lt;strong&gt;another&lt;/strong&gt; &lt;strong&gt;georeference-a-thon at Second Line Brewing&lt;/strong&gt; for &lt;strong&gt;Tuesday June 27th, 6:30pm-8:30pm&lt;/strong&gt;! You can RSVP here: &lt;a href=&#34;https://forms.gle/wTMtoeHR3NwzXN4q8&#34;&gt;https://forms.gle/wTMtoeHR3NwzXN4q8&lt;/a&gt;. Also, please fill that form out if 1) you can&amp;rsquo;t make it on that day but would like to in the future, or 2) you don&amp;rsquo;t live in New Orleans but would be interested in doing an event like this in your town. I&amp;rsquo;d love to discuss this idea with anyone interested.&lt;/p&gt;
&lt;h2 id=&#34;state-of-the-map-us-open-street-map-conference&#34;&gt;State of the Map US (Open Street Map conference)&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;m recently returned from Richmond, Va., after a great weekend at &lt;a href=&#34;https://2023.stateofthemap.us&#34;&gt;State of the Map US&lt;/a&gt;, an annual regional meeting of the &lt;a href=&#34;https://www.openstreetmap.org&#34;&gt;Open Street Map&lt;/a&gt; community. I presented with Jeff Meyer of &lt;a href=&#34;https://www.openhistoricalmap.org/about&#34;&gt;OpenHistoricalMap&lt;/a&gt; on Friday, highlighting how you can use georeferenced Sanborn maps from OldInsuranceMaps.net directly in the OHM editor&amp;ndash;an extremely easy way to trace old buildings and roads to add them into OHM. A perfect external use of the layers created through this project.&lt;/p&gt;
&lt;p&gt;Presentation slides: &lt;a href=&#34;https://tiny.cc/sotmus23-ac&#34;&gt;https://tiny.cc/sotmus23-ac&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;We also did an OHM map-a-thon on Saturday morning, where folks digitized buildings by using the &lt;a href=&#34;https://oldinsurancemaps.net/loc/sanborn09064_001/&#34;&gt;Richmond 1886&lt;/a&gt; mosaic in OldInsuranceMaps that some of you had already georeferenced (esp. &lt;a href=&#34;https://oldinsurancemaps.net/profile/sbuckley730/&#34;&gt;sbuckley730&lt;/a&gt;!), and some people started working on &lt;a href=&#34;https://oldinsurancemaps.net/loc/sanborn09064_002/&#34;&gt;Richmond 1895&lt;/a&gt; as well. Great to see some new people work with these old maps :).&lt;/p&gt;
&lt;h2 id=&#34;georeference-a-thon-recap--redux&#34;&gt;Georeference-a-thon Recap &amp;amp; Redux&lt;/h2&gt;
&lt;p&gt;It seems like a while ago already, but &lt;strong&gt;the georeference-a-thon we did in May at Second Line Brewing went really well&lt;/strong&gt;! About 10 people came, including some fortuitous overlap with a University of New Orleans urban planning department happy hour social. New faces are wonderful to see! We georeferenced about 1/3 of the New Orleans 1896 vol. 1 that we started, and, as you can see from &lt;a href=&#34;https://oldinsurancemaps.net/loc/sanborn03376_005/&#34;&gt;the current state of that volume&lt;/a&gt;, people have continued to work on that content so it&amp;rsquo;s over half done now. We still haven&amp;rsquo;t setup direct integration of this layer into SELA HistoryForge, but we will get that done eventually.&lt;/p&gt;
&lt;p&gt;So, as mentioned above, I&amp;rsquo;ve scheduled another event with Second Line at the end of this month (they told us multiple times how much they liked this old maps project). Hope to see you there, and maybe we&amp;rsquo;ll finish this entire volume!&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://mradamcox.github.io/theme/img/IMG_20230529_101241.jpg&#34; alt=&#34;folks&#34;&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Thanks Elizabeth for taking this photo!&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;site-improvements&#34;&gt;Site Improvements&lt;/h2&gt;
&lt;h3 id=&#34;more-reference-layers-during-georeferencing&#34;&gt;More reference layers during georeferencing&lt;/h3&gt;
&lt;p&gt;I&amp;rsquo;ve (re)introduced the Key Map as a reference layer during georeferencing, click the &amp;ldquo;layers&amp;rdquo; button in the bottom right corner to show this option or turn the layer off. Or &amp;ldquo;r&amp;rdquo; as a keyboard shortcut to toggle the reference layers.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://mradamcox.github.io/theme/img/georeference-key-map-ref-layers.jpg&#34; alt=&#34;georeference&#34;&gt;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve also added the option to show all already-georeferenced layers from the volume alongside the one that you are currently georeferencing. This allows you to make very small adjustments to make adjacent layers line up as closely as possible.&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;https://mradamcox.github.io/theme/img/georeference-main-ref-layers.jpg&#34; alt=&#34;georef&#34;&gt;&lt;/p&gt;
&lt;h3 id=&#34;use-titiler-for-live-georeferencing-preview-layer&#34;&gt;Use TiTiler for live georeferencing preview layer&lt;/h3&gt;
&lt;p&gt;I &lt;a href=&#34;https://github.com/mradamcox/ohmg/issues/135&#34;&gt;recently&lt;/a&gt; swapped out &lt;a href=&#34;https://mapserver.org&#34;&gt;MapServer&lt;/a&gt; for &lt;a href=&#34;https://developmentseed.org/titiler/&#34;&gt;TiTiler&lt;/a&gt; to generate the live preview during georeferencing. I&amp;rsquo;ve used MapServer for this one small functionality since the beginning of the project because it was easier to use with VRTs than GeoServer (and a fun excuse to learn a little about it), but now that TiTiler handles tile generation everywhere else (and natively serves VRTs), this was the natural next step. Happy to have it squared away.&lt;/p&gt;
&lt;h3 id=&#34;set-documents-as-non-maps&#34;&gt;Set documents as &amp;ldquo;non-maps&amp;rdquo;&lt;/h3&gt;
&lt;p&gt;I&amp;rsquo;ve finally addressed, at least in part, the very &lt;a href=&#34;https://github.com/mradamcox/ohmg/issues/1&#34;&gt;first ticket in the repo&lt;/a&gt;, a request for a way to mark particular documents as &amp;ldquo;not-georeferenceable.&amp;rdquo; Now, once a document is prepared, you can mark it as a non-map, moving it into a separate category in the volume summary page. This is necessary for images like the title page and text index, and allows for a more accurate georeferencing completeness percentage to be calculated across the volume.&lt;/p&gt;
&lt;h3 id=&#34;improving-management-of-other-layer-classifications&#34;&gt;Improving management of other layer classifications&lt;/h3&gt;
&lt;p&gt;Also on the topic of content management, I&amp;rsquo;ve added a few more categories for layer classification within a volume. To date, we&amp;rsquo;ve just had Main Content and Key Map, but as we found a long time ago in &lt;a href=&#34;https://oldinsurancemaps.net/resource/5169&#34;&gt;Shreveport&lt;/a&gt;, some volumes include a &amp;ldquo;Map of Congested District,&amp;rdquo; or, more recently in &lt;a href=&#34;https://oldinsurancemaps.net/resource/6621&#34;&gt;Columbus&lt;/a&gt;, a &amp;ldquo;General Index of Volumes.&amp;rdquo; This content will overlap other content from the same volume, so it must be set apart so it can (eventually) be placed into separate layers in the Mosaic Preview map or main viewer&amp;hellip; tiny steps in the ever-churning, slow move toward a more generic system.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;That&amp;rsquo;s all for now! If you recently signed up and are getting this newsletter for the first time, you can read my past sporadic missives in the &lt;a href=&#34;https://oldinsurancemaps.net/newsletter/lahmg-news/archive/&#34;&gt;archive&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;
</description>
      <source:markdown>Hello all! Some announcements and recaps, plus a few updates on (subtle but important) improvements to the site.

Before going further though, I&#39;ve scheduled **another** **georeference-a-thon at Second Line Brewing** for **Tuesday June 27th, 6:30pm-8:30pm**! You can RSVP here: [https://forms.gle/wTMtoeHR3NwzXN4q8](https://forms.gle/wTMtoeHR3NwzXN4q8). Also, please fill that form out if 1) you can&#39;t make it on that day but would like to in the future, or 2) you don&#39;t live in New Orleans but would be interested in doing an event like this in your town. I&#39;d love to discuss this idea with anyone interested.

## State of the Map US (Open Street Map conference)

I&#39;m recently returned from Richmond, Va., after a great weekend at [State of the Map US](https://2023.stateofthemap.us), an annual regional meeting of the [Open Street Map](https://www.openstreetmap.org) community. I presented with Jeff Meyer of [OpenHistoricalMap](https://www.openhistoricalmap.org/about) on Friday, highlighting how you can use georeferenced Sanborn maps from OldInsuranceMaps.net directly in the OHM editor--an extremely easy way to trace old buildings and roads to add them into OHM. A perfect external use of the layers created through this project.

Presentation slides: [https://tiny.cc/sotmus23-ac](https://tiny.cc/sotmus23-ac)

We also did an OHM map-a-thon on Saturday morning, where folks digitized buildings by using the [Richmond 1886](https://oldinsurancemaps.net/loc/sanborn09064_001/) mosaic in OldInsuranceMaps that some of you had already georeferenced (esp. [sbuckley730](https://oldinsurancemaps.net/profile/sbuckley730/)!), and some people started working on [Richmond 1895](https://oldinsurancemaps.net/loc/sanborn09064_002/) as well. Great to see some new people work with these old maps :).

## Georeference-a-thon Recap &amp; Redux

It seems like a while ago already, but **the georeference-a-thon we did in May at Second Line Brewing went really well**! About 10 people came, including some fortuitous overlap with a University of New Orleans urban planning department happy hour social. New faces are wonderful to see! We georeferenced about 1/3 of the New Orleans 1896 vol. 1 that we started, and, as you can see from [the current state of that volume](https://oldinsurancemaps.net/loc/sanborn03376_005/), people have continued to work on that content so it&#39;s over half done now. We still haven&#39;t setup direct integration of this layer into SELA HistoryForge, but we will get that done eventually.

So, as mentioned above, I&#39;ve scheduled another event with Second Line at the end of this month (they told us multiple times how much they liked this old maps project). Hope to see you there, and maybe we&#39;ll finish this entire volume!

![folks](https://mradamcox.github.io/theme/img/IMG_20230529_101241.jpg)

_Thanks Elizabeth for taking this photo!_

## Site Improvements

### More reference layers during georeferencing

I&#39;ve (re)introduced the Key Map as a reference layer during georeferencing, click the &#34;layers&#34; button in the bottom right corner to show this option or turn the layer off. Or &#34;r&#34; as a keyboard shortcut to toggle the reference layers.

![georeference](https://mradamcox.github.io/theme/img/georeference-key-map-ref-layers.jpg)

I&#39;ve also added the option to show all already-georeferenced layers from the volume alongside the one that you are currently georeferencing. This allows you to make very small adjustments to make adjacent layers line up as closely as possible.

![georef](https://mradamcox.github.io/theme/img/georeference-main-ref-layers.jpg)

### Use TiTiler for live georeferencing preview layer

I [recently](https://github.com/mradamcox/ohmg/issues/135) swapped out [MapServer](https://mapserver.org) for [TiTiler](https://developmentseed.org/titiler/) to generate the live preview during georeferencing. I&#39;ve used MapServer for this one small functionality since the beginning of the project because it was easier to use with VRTs than GeoServer (and a fun excuse to learn a little about it), but now that TiTiler handles tile generation everywhere else (and natively serves VRTs), this was the natural next step. Happy to have it squared away.

### Set documents as &#34;non-maps&#34;

I&#39;ve finally addressed, at least in part, the very [first ticket in the repo](https://github.com/mradamcox/ohmg/issues/1), a request for a way to mark particular documents as &#34;not-georeferenceable.&#34; Now, once a document is prepared, you can mark it as a non-map, moving it into a separate category in the volume summary page. This is necessary for images like the title page and text index, and allows for a more accurate georeferencing completeness percentage to be calculated across the volume.

### Improving management of other layer classifications

Also on the topic of content management, I&#39;ve added a few more categories for layer classification within a volume. To date, we&#39;ve just had Main Content and Key Map, but as we found a long time ago in [Shreveport](https://oldinsurancemaps.net/resource/5169), some volumes include a &#34;Map of Congested District,&#34; or, more recently in [Columbus](https://oldinsurancemaps.net/resource/6621), a &#34;General Index of Volumes.&#34; This content will overlap other content from the same volume, so it must be set apart so it can (eventually) be placed into separate layers in the Mosaic Preview map or main viewer... tiny steps in the ever-churning, slow move toward a more generic system.

---

That&#39;s all for now! If you recently signed up and are getting this newsletter for the first time, you can read my past sporadic missives in the [archive](https://oldinsurancemaps.net/newsletter/lahmg-news/archive/).

Adam
</source:markdown>
    </item>
    
  </channel>
</rss>
