{"id":2791,"date":"2021-02-24T16:30:46","date_gmt":"2021-02-24T03:30:46","guid":{"rendered":"http:\/\/blogs.lincoln.ac.nz\/gis\/?p=2791"},"modified":"2023-05-07T03:10:51","modified_gmt":"2023-05-07T03:10:51","slug":"those-unformatted-dragonflies-again","status":"publish","type":"post","link":"https:\/\/blogs.lincoln.ac.nz\/gis\/those-unformatted-dragonflies-again\/","title":{"rendered":"Those Unformatted Dragonflies Again&#8230;"},"content":{"rendered":"<p><em>Analysis and mapping is almost always preceded\u00a0by time spent getting data ready to be mapped.\u00a0 In this post we cover an instance of reformatting some raw spatial data so that they can be used for mapping.<\/em><\/p>\n<p>Over the years, there have been a few posts about dragonflies of the Pacific, from using a <a href=\"http:\/\/blogs.lincoln.ac.nz\/gis\/dont-let-that-dragonfly-get-away-offline-mapping-in-vanuatu\/\" target=\"_blank\" rel=\"noopener noreferrer\">smartphone app<\/a> to collect data in the field, to <a href=\"http:\/\/blogs.lincoln.ac.nz\/gis\/where-this-is-no-elevation\/\" target=\"_blank\" rel=\"noopener noreferrer\">acquiring elevation data<\/a>,\u00a0and\u00a0<a href=\"http:\/\/blogs.lincoln.ac.nz\/gis\/taveuni-an-island-torn-in-two\/\" target=\"_blank\" rel=\"noopener noreferrer\">effective Pacific coordinate systems<\/a>.\u00a0 Those dragonflies aren&#8217;t going anywhere (we hope!) and still need to be catalogued, so my colleague, Milen, is still travelling the Pacific (though not in the past year), most recently in the island group of <a href=\"https:\/\/en.wikipedia.org\/wiki\/Wallis_and_Futuna\" target=\"_blank\" rel=\"noopener noreferrer\">Wallis and Futuna<\/a>.\u00a0 Where are these islands?<\/p>\n<figure id=\"attachment_2805\" aria-describedby=\"caption-attachment-2805\" style=\"width: 800px\" class=\"wp-caption alignnone\"><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/800px-Wallis_and_Futuna_on_the_globe_Polynesia_centered.svg_.png\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-2805 size-full\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/800px-Wallis_and_Futuna_on_the_globe_Polynesia_centered.svg_.png\" alt=\"\" width=\"800\" height=\"800\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/800px-Wallis_and_Futuna_on_the_globe_Polynesia_centered.svg_.png 800w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/800px-Wallis_and_Futuna_on_the_globe_Polynesia_centered.svg_-300x300.png 300w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/800px-Wallis_and_Futuna_on_the_globe_Polynesia_centered.svg_-150x150.png 150w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/800px-Wallis_and_Futuna_on_the_globe_Polynesia_centered.svg_-768x768.png 768w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><\/a><figcaption id=\"caption-attachment-2805\" class=\"wp-caption-text\"><span style=\"font-size: 8pt\"><em>By TUBS &#8211; Own work\u00a0This W3C-unspecified vector image was created with Adobe Illustrator.\u00a0This file was uploaded with Commonist.\u00a0This vector image includes elements that have been taken or adapted from this file:\u00a0Polynesian triangle.svg (by\u00a0Gringer)., CC BY-SA 3.0, https:\/\/commons.wikimedia.org\/w\/index.php?curid=15127571<\/em><\/span><\/figcaption><\/figure>\n<p>Note how Wallis and Futuna are south of the equator and just on the other side of the international dateline from us &#8211; that will become more important later.<\/p>\n<p>Now Milen is well versed with using the app to collect his observations, but we needed some locations collected by someone else to be mapped.\u00a0 He was sent a Word document with the points that looked something like this (around 45 points in all):<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/WordDoc.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2793\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/WordDoc.jpg\" alt=\"\" width=\"626\" height=\"214\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/WordDoc.jpg 626w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/WordDoc-300x103.jpg 300w\" sizes=\"auto, (max-width: 626px) 100vw, 626px\" \/><\/a><\/p>\n<p>Here was my reaction:<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/1024px-Van_Gogh_-_Trauernder_alter_Mann.jpeg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2792\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/1024px-Van_Gogh_-_Trauernder_alter_Mann.jpeg\" alt=\"\" width=\"1024\" height=\"1348\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/1024px-Van_Gogh_-_Trauernder_alter_Mann.jpeg 1024w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/1024px-Van_Gogh_-_Trauernder_alter_Mann-228x300.jpeg 228w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/1024px-Van_Gogh_-_Trauernder_alter_Mann-778x1024.jpeg 778w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/1024px-Van_Gogh_-_Trauernder_alter_Mann-768x1011.jpeg 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/p>\n<p>Why?\u00a0 Clearly, there is spatial information in each entry given by the latitude and longitude BUT it is in a form that is not easily imported into ArcGIS.\u00a0 This is a very frequent occurrence, I&#8217;m afraid, and one must be prepared to massage the data into a more useful form.<\/p>\n<p>A few things to note before we dive into this.\u00a0 The coordinates are essential for getting the points on the map, but they aren&#8217;t quite in the right form.\u00a0 For instance,\u00a0<a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Coords.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2794\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Coords.jpg\" alt=\"\" width=\"132\" height=\"17\" \/><\/a>\u00a0give me latitude and longitude, but the &#8220;S&#8221; (for South of the equator) and the &#8220;W&#8221; (for West of the <a href=\"https:\/\/en.wikipedia.org\/wiki\/Prime_meridian\" target=\"_blank\" rel=\"noopener noreferrer\">Prime Meridian<\/a>) won&#8217;t make sense to Pro.\u00a0 What is preferred is either a positive or a negative value to indicate N\/S of the equator or E\/W of the prime meridian, as shown below:<\/p>\n<p><a href=\"http:\/\/www.fekete.com\/san\/webhelp\/feketeharmony\/harmony_webhelp\/content\/html_files\/reference_material\/General_Concepts\/GIS_Theory.htm\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-2795 size-full\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/LatLong.png\" alt=\"\" width=\"512\" height=\"298\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/LatLong.png 512w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/LatLong-300x175.png 300w\" sizes=\"auto, (max-width: 512px) 100vw, 512px\" \/><\/a><\/p>\n<p><em><span style=\"font-size: 8pt\"><a href=\"http:\/\/www.fekete.com\/san\/webhelp\/feketeharmony\/harmony_webhelp\/content\/html_files\/reference_material\/General_Concepts\/GIS_Theory.htm\" target=\"_blank\" rel=\"noopener noreferrer\">http:\/\/www.fekete.com\/san\/webhelp\/feketeharmony\/harmony_webhelp\/content\/html_files\/reference_material\/General_Concepts\/GIS_Theory.htm<\/a><\/span><\/em><\/p>\n<p>For mapping in our part of the world, latitudes need to be negative, so I&#8217;ll have to take this into account at some point.\u00a0 And being just the other side of the dateline, the longitudes will be negative as well.<\/p>\n<p>But the biggest problem by far is getting these data organised into something more closely resembling something mappable &#8211; GIS does not like Word docs.\u00a0 There are a number of different ways to do this, and more often than not I fall back on Excel (How would you do it?)\u00a0 I can&#8217;t open a Word file in Excel so as a first step, I saved the Word file as a straight text file and then opened it in Excel.<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import1.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2796\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import1.jpg\" alt=\"\" width=\"578\" height=\"439\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import1.jpg 578w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import1-300x228.jpg 300w\" sizes=\"auto, (max-width: 578px) 100vw, 578px\" \/><\/a><\/p>\n<p>This dialogue will allow me start parsing the text into more useful columns.\u00a0 The file is not well aligned with columns so I chose to use Delimited &gt; Next:<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import2.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2797\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import2.jpg\" alt=\"\" width=\"576\" height=\"439\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import2.jpg 576w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import2-300x229.jpg 300w\" sizes=\"auto, (max-width: 576px) 100vw, 576px\" \/><\/a><\/p>\n<p>With some judicious use of delimeters (semicolons, commas and open parentheses) I&#8217;ve got a good first cut.\u00a0 I accepted the defaults on the next screen, hit Finish and here&#8217;s what I got:<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import3.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2798\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import3.jpg\" alt=\"\" width=\"1142\" height=\"779\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import3.jpg 1142w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import3-300x205.jpg 300w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import3-1024x699.jpg 1024w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Import3-768x524.jpg 768w\" sizes=\"auto, (max-width: 1142px) 100vw, 1142px\" \/><\/a><\/p>\n<p>Not a bad start but I&#8217;ve still got some mucking around to do.\u00a0 I&#8217;m aiming to get all the latitudes and longitudes into their own column &#8211; there are 45 rows in this file so I&#8217;ll bite the bullet and do some manual rearranging, being careful not to lose any data:<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Fix1-1.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2801\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Fix1-1.jpg\" alt=\"\" width=\"721\" height=\"520\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Fix1-1.jpg 721w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Fix1-1-300x216.jpg 300w\" sizes=\"auto, (max-width: 721px) 100vw, 721px\" \/><\/a><\/p>\n<p>Notice that I&#8217;ve added column names &#8211; we&#8217;ll need those as field names when we add the file to Pro.\u00a0 I know I&#8217;m going to be creating some new lat\/long columns along the way so I add a &#8220;1&#8221; to these column names.\u00a0 Next I&#8217;ll remove the &#8220;S&#8221; from the latitudes and make the number negative using a formula with the <a href=\"https:\/\/exceljet.net\/excel-functions\/excel-left-function\" target=\"_blank\" rel=\"noopener noreferrer\">LEFT <\/a>function.\u00a0 This function lets me extract a set number of characters starting from the left of the first one:<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2802\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left.jpg\" alt=\"\" width=\"1131\" height=\"128\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left.jpg 1131w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left-300x34.jpg 300w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left-1024x116.jpg 1024w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left-768x87.jpg 768w\" sizes=\"auto, (max-width: 1131px) 100vw, 1131px\" \/><\/a>\u00a0C2 is the cell that has my South enabled latitude.\u00a0 Most of my coordinates have seven characters (including the &#8220;.&#8221;) multiplying this by -1 gives me the right result:<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Fix2.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2803\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Fix2.jpg\" alt=\"\" width=\"1133\" height=\"513\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Fix2.jpg 1133w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Fix2-300x136.jpg 300w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Fix2-1024x464.jpg 1024w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Fix2-768x348.jpg 768w\" sizes=\"auto, (max-width: 1133px) 100vw, 1133px\" \/><\/a><\/p>\n<p>That&#8217;s half the battle &#8211; now to my longitudes.\u00a0 The LEFT function works well here too:<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left2.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2806\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left2.jpg\" alt=\"\" width=\"1134\" height=\"110\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left2.jpg 1134w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left2-300x29.jpg 300w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left2-1024x99.jpg 1024w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Left2-768x74.jpg 768w\" sizes=\"auto, (max-width: 1134px) 100vw, 1134px\" \/><\/a><\/p>\n<p>I&#8217;m mostly done though there was a bit of jiggery pokery to be done with a few coordinates that marked the beginnings and ends of transects and tidying up the comments, so I copied the relevant columns to a new sheet and saved the Excel file:<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/reformatted2.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2808\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/reformatted2.jpg\" alt=\"\" width=\"1077\" height=\"873\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/reformatted2.jpg 1077w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/reformatted2-300x243.jpg 300w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/reformatted2-1024x830.jpg 1024w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/reformatted2-768x623.jpg 768w\" sizes=\"auto, (max-width: 1077px) 100vw, 1077px\" \/><\/a><\/p>\n<p>(The ones highlighted in green are the transect points.)\u00a0 In Pro, I can now add that sheet to a map and use <a href=\"https:\/\/pro.arcgis.com\/en\/pro-app\/latest\/help\/mapping\/layer-properties\/add-x-y-coordinate-data-as-a-layer.htm\" target=\"_blank\" rel=\"noopener noreferrer\">Display X Y Data<\/a> to get the points plotted:<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/OnTheMap.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2809\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/OnTheMap.jpg\" alt=\"\" width=\"1912\" height=\"1005\" srcset=\"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/OnTheMap.jpg 1912w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/OnTheMap-300x158.jpg 300w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/OnTheMap-1024x538.jpg 1024w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/OnTheMap-768x404.jpg 768w, https:\/\/blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/OnTheMap-1536x807.jpg 1536w\" sizes=\"auto, (max-width: 1912px) 100vw, 1912px\" \/><\/a><\/p>\n<p>Job done!\u00a0 To wrap this up, here&#8217;s the figure that&#8217;s most likely to go in the paper for this study, coming to a reputable journal near you:<\/p>\n<p><a href=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Figure1A.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2810\" src=\"https:\/\/d-blogs.lincoln.ac.nz\/gis\/wp-content\/uploads\/sites\/3\/2021\/02\/Figure1A.jpg\" alt=\"\" width=\"3347\" height=\"2400\" \/><\/a><\/p>\n<p>As many of you GIS users out there will know, much of &#8220;doing GIS&#8221; means prepping your data before the glory work of analysis and mapping &#8211; and this was a good example of the work that often needs to go into the raw data that someone sends you and getting them on the map.\u00a0 I don&#8217;t feel as downtrodden as Van Gogh portrayed above after this&#8230;but I&#8217;ll certainly encourage the next expedition to use the bloomin&#8217; app!<\/p>\n<p>Oh wait, what&#8217;s this I see in my inbox?\u00a0 It&#8217;s a note from Milen with a Word doc of additional dragonfly observations&#8230;<\/p>\n<p>C<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Analysis and mapping is almost always preceded\u00a0by time spent getting data ready to be mapped.\u00a0 In this post we cover an instance of reformatting some raw spatial data so that they can be used for mapping. Over the years, there have been a few posts about dragonflies of the Pacific, from using a smartphone app [&hellip;]<\/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-2791","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/posts\/2791","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=2791"}],"version-history":[{"count":1,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/posts\/2791\/revisions"}],"predecessor-version":[{"id":4091,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/posts\/2791\/revisions\/4091"}],"wp:attachment":[{"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/media?parent=2791"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/categories?post=2791"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.lincoln.ac.nz\/gis\/wp-json\/wp\/v2\/tags?post=2791"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}