{"id":207,"date":"2011-08-18T18:00:00","date_gmt":"2011-08-18T18:00:00","guid":{"rendered":"https:\/\/blogs.lib.uconn.edu\/outsidetheneatline\/2011\/08\/18\/creating-kmzs-in-arcmap\/"},"modified":"2011-08-18T18:00:00","modified_gmt":"2011-08-18T18:00:00","slug":"creating-kmzs-in-arcmap","status":"publish","type":"post","link":"https:\/\/blogs.lib.uconn.edu\/outsidetheneatline\/2011\/08\/18\/creating-kmzs-in-arcmap\/","title":{"rendered":"Creating KMZ’s in ArcMap"},"content":{"rendered":"

Our recent blog series featuring the collaboration between MAGIC<\/a>\u00a0and the On The Line<\/a> project has detailed the development of digital maps. Although we have given some technical detail in each post, I thought it would be fun to post a tutorial on how to create KMZ’s<\/a>\u00a0(for use in Google Maps and Google Earth) in ESRI’s ArcMap. For this exercise, I will create a map of Connecticut towns symbolized by total population.<\/p>\n

1.Acquire Data<\/i><\/b>: The first step in creating any cartographic project is to acquire the necessary data. For this project, I have downloaded Census data by town (county subdivision) from MAGIC’s GIS Data Page<\/a>.<\/p>\n

<\/a><\/div>\n
<\/div>\n
The shapefiles download will include shapefiles in both WGS84 and NAD83 coordinate systems. Once I download the shapefiles, I can add the P001 (which contains total population) WGS84 shapefile into ArcMap. If you are going to be working with MAGIC’s Census data, it is also important to download the spreadsheet data in addition to the shapefiles. The spreadsheet data contains a codebook that will allow you to interpret the field names of the shapefile attribute table.\u00a0<\/div>\n
<\/div>\n
2. Remove Counties Not Defined:<\/i><\/b> There are 4 features in the Connecticut County Subdivisions data set that are not really towns, but are features that occupy the Long Island Sound area. In the Name10 <\/i>field of the attribute table, I can see which these are.\u00a0<\/div>\n
<\/div>\n
<\/a><\/div>\n
<\/div>\n
To remove these, I need to write a simple Definition Query, which is done in the Properties menu of the layer. Click Apply or OK to save the changes.<\/div>\n
<\/div>\n
<\/a><\/div>\n
<\/div>\n
<\/a><\/div>\n
<\/div>\n
<\/div>\n
3. Symbolize Layer(s)<\/i><\/b>: Now that I have only the 169 Connecticut towns displayed, I’m ready to symbolize the layer. This, like the Definition Query, is done in the Layer Properties.\u00a0Click Apply or OK to save the changes.<\/div>\n
<\/div>\n
<\/a><\/div>\n
<\/div>\n
4. Hide\u00a0Unnecessary\u00a0Labels<\/i><\/b>: Next, I am going to hide all of the fields I do not want displayed in my final product (I only want the name of the town and total population). Under the Fields tab of the Layer’s Properties, I can uncheck \u00a0the fields I don’t need or want to display.\u00a0Click Apply or OK to save the changes.<\/div>\n
<\/div>\n
<\/a><\/div>\n
<\/div>\n
<\/div>\n
5. Configure Pop-Up Labels<\/b><\/i>: ArcMap allows you to export labels as pop up windows. This is done under the HTML Labels tab in the Layer’s Properties. By default, the field name will be included, but you can check the hide field name column<\/i> if you don’t want it to display (as I have done).\u00a0Click Apply or OK to save the changes.<\/div>\n
<\/div>\n
<\/a><\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
6. Export Layer\/Map using Conversion To KML<\/b><\/i>: There are two options to export your data; you can either export an individual layer or the whole map. If you choose Layer to KML you will need to browse to your layer, if you choose Map To KML you must browse to your .MXD file.<\/div>\n
<\/div>\n
<\/div>\n
<\/a><\/div>\n
<\/div>\n\n\n\n\n
<\/a><\/td>\n<\/tr>\n
You can adjust the output scale as well as the resolution of your output in the Layer (or Map) to KML<\/i> tool.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/div>\n
7. Display in Google Earth<\/b><\/i>: If you have Google Earth already installed on your computer, you should be able to double-click your new KML to open it.\u00a0<\/div>\n
<\/div>\n
<\/a><\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
8. Clean up Labels<\/i><\/b>: To give my labels a cleaner look, I’m going to reduce their redundancy. To do this, I must go back into ArcMap and ensure my primary label is set under the display tab of the Layer Properties menu. I chose the town name field.<\/div>\n
<\/div>\n\n\n\n\n
<\/a><\/td>\n<\/tr>\n
Note<\/b>: You can also adjust transparency under the Display tab.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/div>\n
Then, I can turn the name field off.\u00a0Click Apply or OK to save the changes.<\/div>\n
<\/div>\n
<\/a><\/div>\n
<\/div>\n
<\/div>\n
Now, at least one of the repeated labels has been removed.<\/div>\n
<\/div>\n
<\/a><\/div>\n
<\/div>\n
If you want to edit the labels in more detail, many times it will be more efficient to edit them in ArcMap using tools like the Field Calculator before exporting the layer or map.\u00a0<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"

Our recent blog series featuring the collaboration between MAGIC\u00a0and the On The Line project has detailed the development of digital maps. Although we have given some technical detail in each post, I thought it would be fun to post a … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"footnotes":""},"categories":[1],"tags":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p9NL4O-3l","_links":{"self":[{"href":"https:\/\/blogs.lib.uconn.edu\/outsidetheneatline\/wp-json\/wp\/v2\/posts\/207"}],"collection":[{"href":"https:\/\/blogs.lib.uconn.edu\/outsidetheneatline\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.lib.uconn.edu\/outsidetheneatline\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.lib.uconn.edu\/outsidetheneatline\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.lib.uconn.edu\/outsidetheneatline\/wp-json\/wp\/v2\/comments?post=207"}],"version-history":[{"count":0,"href":"https:\/\/blogs.lib.uconn.edu\/outsidetheneatline\/wp-json\/wp\/v2\/posts\/207\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.lib.uconn.edu\/outsidetheneatline\/wp-json\/wp\/v2\/media?parent=207"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.lib.uconn.edu\/outsidetheneatline\/wp-json\/wp\/v2\/categories?post=207"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.lib.uconn.edu\/outsidetheneatline\/wp-json\/wp\/v2\/tags?post=207"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}