{"id":2120,"date":"2018-09-25T10:47:15","date_gmt":"2018-09-24T22:47:15","guid":{"rendered":"http:\/\/blogs.lincoln.ac.nz\/gis\/?p=2120"},"modified":"2023-05-07T03:28:39","modified_gmt":"2023-05-07T03:28:39","slug":"loaded-layers","status":"publish","type":"post","link":"https:\/\/blogs.lincoln.ac.nz\/gis\/loaded-layers\/","title":{"rendered":"Loaded Layers"},"content":{"rendered":"

We look at using the Load command to add new records to a layer in this post.\u00a0 Sometimes it’s a far better option than a spatial join or a merge.<\/em><\/p>\n

We recently had a summer scholarship student looking at some mapping work for the Department of Conservation (DOC).\u00a0 Amongst the myriad of things they look after (1\/3 of the NZ landmass, all those critters) DOC is also responsible for keeping track of the movements of exotic fish.\u00a0 So when someone wants to transfer some rainbow trout to a pond in Northland, they need to gain permission from DOC and MPI before doing so.\u00a0 This also means keeping track of all the paperwork that goes into granting those permissions.\u00a0 In the spirit of a picture telling a 1,000 words, they were interested in mapping all these permissions as an alternative way to mange the data.\u00a0 What a great idea!<\/p>\n

After several weeks of work, the end result was a webmap that DOC can use to access these data and focus on whatever areas they’re interested in:<\/p>\n

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

Each point represents one of the permissions and can be clicked on to get the details for each.<\/p>\n

Our student got started by having a look at the data DOC provided.\u00a0 Not surprisingly, the data were kept in a table-based database with links to PDFs and spreadsheets in some cases.\u00a0 For a few, there were only paper documents.\u00a0 Buried deeply in all the\u00a0data were several ways of locating the permissions.<\/p>\n

In the most fortuitous cases, x and y coordinates were listed.\u00a0 In other cases, just a place name could be found.\u00a0 In still other cases, the only spatial data was around the land section details.\u00a0 We’ll deal with them one by one and see how they ended up as points on a map above.\u00a0 At the end of this post we’ll see how three separate layers were merged into one using a handy tool.<\/p>\n

Permissions with Coordinates<\/strong><\/p>\n

This was the best case with these data, but they weren’t quite as straightforward as we had hoped.\u00a0 As an example, we found coordinates like this: NZMS 260 M36-671-293 (Ed. – not real coordinates<\/em>).\u00a0 These spreadsheets looked something like this (I’ve blanked out the Holders and some other vital details):<\/p>\n

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

Those of you familiar with eastings and northings in New Zealand Transverse Mercator or Map Grid would look a bit askance at these – they don’t look much like coordinates.\u00a0 They are, but they’re from a much older mapping system.\u00a0 NZMS 260 is an older version of 1:50,000 scale topo maps.\u00a0 The country was broken down into 329 tiles with a letter and two numbers to identify it.\u00a0 Around here, M36 was the map that covered Lincoln and parts of Banks Peninsula.<\/p>\n

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

Within each sheet, two triplets of numbers would allow you to locate a point to within a hundred metres or so. For instance, in the old NZMG system, the rough coordinates for the Forbes Building would be Easting 24671<\/strong>00 Northing 57293<\/strong>00 (these are in meters).\u00a0 Since this point is on map sheet M36, an alternative way to identify this point is as NZMS 260 M36-671-293.\u00a0 On the map sheet, the leading 24 and 57 won’t change so the 671 and 293 are shorthand for that point.\u00a0 With a little bit of practice this becomes easy to use (provided you’ve got the maps) but the bigger problem is that ArcMap isn’t going to like that map reference.\u00a0 (The current mapping system is set up in the same way<\/em><\/a>.) So how to convert the NZMS map references to something more useful (i.e. current), like NZTM?<\/p>\n

LINZ<\/a> to the rescue – they provide a coordinate conversion page<\/a> where you can input a series of coordinates and get their NZTM equivalents out the other end.\u00a0 These could be added to the spreadsheet and then easily mapped using the Display X Y Data<\/a> option.\u00a0 That was the easy part.<\/p>\n

Permissions with Place Names<\/strong><\/p>\n

I was hoping this would also be an easy one…but… (Ed. – a common refrain in GIS.)\u00a0<\/em> There’s a layer from LINZ called the gazetteer<\/a> which lists a plethora of place names.\u00a0 I was hoping it would be a quick table join<\/a> to bring the spreadsheet and the points together but there weren’t many useable matches so most of these had to mapped manually.\u00a0 Our poor student\u00a0is blind now…<\/p>\n

Permissions with Legal Descriptions<\/strong><\/p>\n

The remaining points’ only spatial information was tied to the legal descriptions of property sections.\u00a0 All sections across NZ have a title and a legal description which is sort of a unique identifier.\u00a0 Unfortunately, there’s not much rhyme or reason to how legal descriptions get assigned, so unlike the map grid references above, we’re pretty much starting from scratch.\u00a0 There are legal description layers<\/a> on the LINZ Data Service but try as we might, there were enough discrepancies between legal description texts that we got no useful matches.\u00a0 With just over 30 records having only this limitation, what to do now?\u00a0 Here’s an image of the spreadsheet to give you an idea of what we were dealing with (with holder names blocked out).\u00a0 The “Location” column has the legal descriptions:<\/p>\n

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

There is one mapping software application that allows you to search on legal descriptions – QuickMap<\/a>, which is available on the computers in C4.\u00a0 With both ArcMap and QuickMap open on the desktop, I was able to read off the legal descriptions from the spreadsheet and then search from them in QuickMap, as shown below:<\/p>\n

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

Then, in ArcMap, I could place the point in the correct place.\u00a0 There was no way to get around having to do this record by record, but happily there weren’t too many.<\/p>\n

Pulling the Data Together<\/strong><\/p>\n

So now we’ve got three separate layers of points mapped in three different ways.\u00a0 The final challenge is to bring them all together into one layer so we can produce a map for DOC.\u00a0 Normally, one could do a spatial join, like Union<\/a>, or perhaps use a command like Merge<\/a>.\u00a0 The problem was that each of my layers had a different set of attributes (a different schema<\/a> in database terms).\u00a0 If using something like Merge I would end up with possibly two or three different versions of similar attributes.\u00a0 This was a good place to use the Load <\/a>tool. With this tool, one of your layers is the target and has the attribute names that you want to maintain.\u00a0 The other layers are “loaded” into that one and differently named attributes can be mapped to the target ones.\u00a0 This allows you to retain the important ones, overlook those that aren’t needed and keep everything consistent.<\/p>\n

Load only works with feature classes in a geodatabase and shapefiles.\u00a0 To load addition data into an existing layer, start by right-clicking the layer name (in Catalog) and choose Load > Load Data…\u00a0 A wizard then steps up through the process (what would we do without wizards?)<\/p>\n

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

This first window just summaries what the tool does<\/p>\n

Here you set the target layer:\"\"<\/a><\/p>\n

Next, set the layer to be loaded:\"\"<\/a><\/p>\n

(We’ll have to talk about subtypes other time.)<\/p>\n

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

This window allows us to map the attribute values from the source layer to the target layer:<\/p>\n

\"\"<\/a>Next, confirm that you want to load all the data or only that that are selected:<\/p>\n

\"\"<\/a>A final summary and off we go:<\/p>\n

Once completed, the new records are added directly into the target layer with the attributes matching up nicely. The benefit here is that the attribute names don’t have to be the same yet we can still match them up.\u00a0 This would cause us some problems when using a spatial join or a merge.<\/p>\n

So two (hopefully) useful things in this post – mapping points in a spreadsheet that have various different types of spatial data and use of the Load tool to standardise attributes.\u00a0 All those points on the final map look good but don’t really indicate the work that went into getting them in the right place.\u00a0 Perhaps this is a good example of not paying attention to that man behind the curtain<\/a>.<\/p>\n

(Ed. – we do aim to be apolitical here at the GIS Blog, but occasionally we just can’t help ourselves.)<\/em><\/p>\n

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

We look at using the Load command to add new records to a layer in this post.\u00a0 Sometimes it’s a far better option than a spatial join or a merge. We recently had a summer scholarship student looking at some mapping work for the Department of Conservation (DOC).\u00a0 Amongst the myriad of things they look […]<\/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-2120","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/posts\/2120","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=2120"}],"version-history":[{"count":1,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/posts\/2120\/revisions"}],"predecessor-version":[{"id":4115,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/posts\/2120\/revisions\/4115"}],"wp:attachment":[{"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/media?parent=2120"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/categories?post=2120"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/tags?post=2120"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}