Skip to content

Commit

Permalink
Updated to the correct image
Browse files Browse the repository at this point in the history
  • Loading branch information
hepplerj authored Mar 18, 2024
1 parent ac1411b commit b001312
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion bom-website/content/blog/2024-03-12-gis.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ To re-transcribe this data, I would hide all columns other than burials and the
- Check Attribute Table: Go to the Layers panel on the side > Right-click on “WithinTheBills1622” > Open Attribute Table.
- Choose joinable column. You'll likely want to differentiate between parishes if you’re mapping, so I would choose one of the parish name columns. There are 3 different parish name columns on these shapefiles. I chose the DNB_PAR column, since I knew that DBN (Database Name) values were unique.

{{< figure src="/images/ward-image9.png" caption="" alt="A screenshot of the attribute table for the 1622 shapefiles. The X-axis shows name and category labels, while the Y-axis shows each parish's delineations based on the X-axis" >}}
{{< figure src="/images/ward-image13.png" caption="" alt="A screenshot of the attribute table for the 1622 shapefiles. The X-axis shows name and category labels, while the Y-axis shows each parish's delineations based on the X-axis" >}}

- Open an empty spreadsheet. I’d recommend naming it something like “1622 Mapping Template,” but that’s up to you and how organized you are. Then I made two columns: “DBN_PAR” (just like it’s written in the attribute table. It needs to be identical) and “BURIALS”. Then I copied every DBN_PAR item in the column to the matching spreadsheet column, making sure I had the right amount of rows compared to the attribute table. (I used ctrl-c and ctrl-v to make sure the names were identical to their original names. It doesn’t matter if they’re in the right order, but it is important that the names are the exact same.) You should have something like this:

Expand Down

0 comments on commit b001312

Please sign in to comment.