{"id":2885,"date":"2021-03-25T21:50:56","date_gmt":"2021-03-25T08:50:56","guid":{"rendered":"http:\/\/blogs.lincoln.ac.nz\/gis\/?p=2885"},"modified":"2023-05-07T03:08:35","modified_gmt":"2023-05-07T03:08:35","slug":"atlas-would-be-jealous","status":"publish","type":"post","link":"https:\/\/blogs.lincoln.ac.nz\/gis\/atlas-would-be-jealous\/","title":{"rendered":"Atlas Would Be Jealous"},"content":{"rendered":"

In this post we look at creating a map series of similarly formatted maps.<\/em><\/p>\n

Here a GIS Central we recently started some work looking at the carrying capacity of cruise ships in Fiordland.\u00a0 There was some field work involved so to carry out some of the work,\u00a0the good people at Pacific Eco-Logic<\/a> needed some maps, specifically, “a grid at 1: 100,000 scale on the aerial\/satellite imagery of the fiords of Fiordland based on printing out A3 sheets of paper for fieldwork. I would need the fiords\u00a0and their catchments included”.\u00a0 Certainly sounds like something GIS should be able to help out with.<\/p>\n

My first thought was that this would end up looking like some kind of an atlas <\/a>of maps, with all at the same scale and accompanying information but each focused on a different area.\u00a0 While this may sound like a daunting task at the outset, it’s something that ArcGIS is set up to do relatively easily through the idea of map series<\/a>.\u00a0 It couldn’t be much simpler.<\/p>\n

To get started, I need a layer of polygons that cover the area of interest without overlapping that defines the extent of each map page.\u00a0 I could create one myself, using something like Create Fishnet<\/a>, but immediately I thought of an alternative that might make more sense: the 1:50,000 scale\u00a0Topo50<\/a> map series.\u00a0 These maps<\/a> cover the NZ landmass with 448 sheets, each\u00a024 km east-west and\u00a035 km north-south.\u00a0 Here’s what the South Island coverage looks like:<\/p>\n

\"\"<\/a><\/p>\n

Each sheet is assigned a code that places it in the large scheme, with two letters per row and two numbers per column, a bit like the grid used in Battleship (Ed. the game<\/strong>, not the movie, sheesh<\/em>)<\/p>\n

\"\"<\/a><\/p>\n

I grabbed the sheets covering Fiordland and then got some feedback on which ones would need and ended up with this as my index layer:<\/p>\n

\"\"<\/a><\/p>\n

Here’s the layer’s table so you can see what it’s got:<\/p>\n

\"\"<\/p>\n

“DESC_” holds the text name of each sheet while “PRIME” is the Battleship-like identifier.\u00a0 “row” and “col” just split those up for selection purposes (e.g. to select all the sheets in the same column).<\/p>\n

Great – this gives me my map extents.\u00a0 For the satellite imagery, I simply changed the basemap to World Imagery (Firefly):<\/p>\n

\"\"<\/a><\/p>\n

Next up is to set up the map series parameters<\/a>.\u00a0 I first need to create a layout\u00a0and build the basic labelling and symbology that will appear on every page:<\/p>\n

\"\"<\/a><\/p>\n

Some of the key decisions on this one were around sheet border colours and label placement.\u00a0 Given the overall darker tones to the satellite image, a dark outline colour could easily get lost, so I chose a softer, light-gray and matched this on the labels.<\/p>\n

Most atlases\u00a0put labels on the sides where another sheet abuts the current one to make it easier to move between them – I can do this by choosing the boundary placement in the Label Class window.\u00a0 To get here, right-click on a layer you want to label and go to Labeling Properties…\u00a0 Here’s where you can make all those choices around font size, type and colour and hiding under Position are the placement options.\u00a0 Boundary placement works well in this context by placing the sheet name for the current and surrounding sheets:<\/p>\n

\"\"<\/a><\/p>\n

Font size controls how much emphasis they get.\u00a0 I’ve also placed my scale bar and have a placeholder for a legend (more on that later on).\u00a0 On the Layout tab one of my many options is Map Series:<\/p>\n

\"\"<\/a><\/p>\n

Spatial is the option we want here.\u00a0 It’s a pretty simple setup:<\/p>\n

\"\"<\/a><\/p>\n

A key choice here is the “Layer” – this is set to my layer of Fiordland Topo50 map sheets.\u00a0 In that layer, the “PRIME” attribute holds the code of each sheet so I’m using that for the Name Field.\u00a0 Sort Fields are used to set out the order that each map in the series is put into.\u00a0 Options include things like rotating the map frames, setting extents, and controlling output page numbers.\u00a0 When done, it’s all put together with no muss and little fuss:<\/p>\n

\"\"<\/a><\/p>\n

From here I can move between each sheet by selecting one in the Contents.\u00a0 Once set up I can always go back and tweak this by right-clicking the Layout name, going to Properties and choosing Map Series.<\/p>\n

Before I can say I’m done, I exported a few of these as A3 PDFs and ran them by the field workers.\u00a0 For the first round, they seemed pretty happy overall but had this comment: “What would be really useful would be to have the bathymetry <\/a>for the marine environment shown”.\u00a0 No problem!<\/p>\n

I just happen to have a layer of offshore 50 m bathymetry from NIWA (you can find it at J:\\Data\\Bathymetry).\u00a0 After a bit of back and forth on symbology, we settled on this:<\/p>\n

\"\"<\/a><\/p>\n

(Oh dear…really should have included units in my legend…maps are never really done.)\u00a0 \u00a0This does show one of the trickier aspects of map series – placing an element in the same place on every page can cause conflicts with covering features on certain map.\u00a0 Short of making each one custom, one must learn to live with that I’m afraid.<\/p>\n

In any event, we’re just about done here – next job is to export the sheets as PDFs and send them off.\u00a0 With the map series Layout active, look for the Layout Export button, \"\"<\/a>, on the Share tab.\u00a0 \u00a0 With the Type set to PDF, the Map Series tab becomes visible:<\/p>\n

\"\"<\/a><\/p>\n

You’ve got choices on what to export (including only selected features in the index layer).\u00a0 I suspect these are less useful as a single PDF file in case they just want to print out specific ones.\u00a0 Clicking on the Files down arrow, I do have some other options:<\/p>\n

\"\"<\/a><\/p>\n

With the second option, I can print each one out separately with the page name or number (as set in the Options earlier) as the suffix.\u00a0 This seems pretty handy to me so option two it is.\u00a0 Once exported, they all went to a folder on OneDrive which I could then share.<\/p>\n

\"\"<\/a><\/p>\n

Note that I threw in a sheet index that hopefully made it a bit easier to make sense of where everything is:<\/p>\n

\"\"<\/a><\/p>\n

With that they were\u00a0off to do their field work.\u00a0 I checked in a few weeks later – to which they replied, “We\u00a0completed the field trip with mostly very good weather and your images were very useful”, to which I swooned<\/a>.<\/p>\n

So, where have we gotten to in this post?\u00a0 Vicariously, Fiordland, but more importantly we’ve seen just how easy it is to make your own atlas.\u00a0 All up, this probably took me a wee bit less than an hour to spin up, which is pretty good value for money.\u00a0 Atlas<\/a> was said to have carried the weight of the celestial world on his shoulders (and by the by, it was Gerardus Mercator, he of the Mercator projection<\/a>, who coined the name Atlas for a book of maps), but Pro has certainly taken the weight of my shoulders by making this so easy.<\/p>\n

C<\/p>\n","protected":false},"excerpt":{"rendered":"

In this post we look at creating a map series of similarly formatted maps. Here a GIS Central we recently started some work looking at the carrying capacity of cruise ships in Fiordland.\u00a0 There was some field work involved so to carry out some of the work,\u00a0the good people at Pacific Eco-Logic needed some maps, […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2885","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/posts\/2885","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/comments?post=2885"}],"version-history":[{"count":1,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/posts\/2885\/revisions"}],"predecessor-version":[{"id":4089,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/posts\/2885\/revisions\/4089"}],"wp:attachment":[{"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/media?parent=2885"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/categories?post=2885"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/tags?post=2885"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}