{"id":56,"date":"2013-01-16T17:26:35","date_gmt":"2013-01-16T17:26:35","guid":{"rendered":"http:\/\/doozer\/wordpress\/?page_id=56"},"modified":"2013-02-20T16:20:05","modified_gmt":"2013-02-20T21:20:05","slug":"autocad-integration","status":"publish","type":"page","link":"https:\/\/jniemuth.hubns.net\/gis520\/autocad-integration\/","title":{"rendered":"AutoCAD Integration"},"content":{"rendered":"<p><strong>Problem:<\/strong> Develop a file geodatabase for the NC State University campus containing specified featured classes using data from a CAD file that is not georeferenced.<\/p>\n<p><strong>Analysis Procedures:<\/strong> <a title=\"Georeferencing CAD Datasets\" href=\"http:\/\/resources.arcgis.com\/en\/help\/main\/10.1\/index.html#\/About_georeferencing_CAD_datasets\/001000000010000000\/\" target=\"_blank\">Georeferencing a CAD file<\/a> to a reference file with known coordinates, such as an aerial orthophoto, gives CAD data a spatial reference, which makes it more useful for solving GIS problems. Layers of interest in the georeferenced CAD file can also be exported to feature classes in a file geodatabase for easy organization and distribution (Fig. 1). Specific feature classes to be included in the final file geodatabase were located in both the CAD polygon and polyline layers. These layers were campus buildings, streets, sidewalks, streams\/creeks, lakes\/ponds, and athletic fields. The projected coordinate system was set to match the reference file and then the CAD data was scaled and shifted to roughly match the aerial orthophoto and georeferenced by selecting 2 control points on opposite extents of the map. Some of the polygons for buildings in the CAD file were displayed as polylines because their polygons were not closed. By exporting the building features to a shapefile, the features could be converted to polygons, and the resulting feature class imported to the file geodatabase. Each remaining feature class of interest was selected and exported individually to the file geodatabase. A procedure log for this exercise is available <a title=\"Procedure Log\" href=\"http:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/Procedure-Log1.pdf\" target=\"_blank\">here<\/a>.<\/p>\n<div id=\"attachment_194\" class=\"wp-caption aligncenter\" style=\"width: 816px\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-194\" alt=\"Georeferencing workflow\" src=\"http:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/Diagram.png\" width=\"806\" height=\"479\" srcset=\"https:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/Diagram.png 806w, https:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/Diagram-300x178.png 300w, https:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/Diagram-500x297.png 500w\" sizes=\"auto, (max-width: 806px) 100vw, 806px\" \/><p class=\"wp-caption-text\">Figure 1. General workflow diagram for georeferencing and exporting CAD data to a file geodatabase in ArcMap.<\/p><\/div>\n<p><strong>Results:<\/strong><\/p>\n<div id=\"attachment_195\" class=\"wp-caption aligncenter\" style=\"width: 1430px\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-195\" alt=\"Georeferencing results\" src=\"http:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/georeferencing.jpg\" width=\"1420\" height=\"1288\" srcset=\"https:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/georeferencing.jpg 1420w, https:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/georeferencing-300x272.jpg 300w, https:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/georeferencing-1024x928.jpg 1024w, https:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/georeferencing-330x300.jpg 330w\" sizes=\"auto, (max-width: 1420px) 100vw, 1420px\" \/><p class=\"wp-caption-text\">Figure 2. CAD data of the NCSU campus after georeferencing to the reference aerial orthophoto (color scheme for visibility). Note that the CAD features are aligned with the features in the photo.<\/p><\/div>\n<p><strong>Application and Reflection: <\/strong>Frequently, many scientific disciplines must work together in order to solve a problem.\u00a0 Wildlife biologists and veterinarians often work with foresters, developers, law enforcement officials, government agencies, non-profit organizations, and others to manage wildlife.\u00a0 Given the prevalence and complementary nature of CAD and GIS, it would not be unexpected for these groups to utilize data from both systems.\u00a0 It is also important to understand the limitations and pitfalls of each; for example, so one knows to look for possibly polygons that have not been completely closed before moving on to analysis steps.\u00a0 Being proficient at moving between systems and creating organized data that is easy to distribute is fundamental.<\/p>\n<p><a name=\"WLCrossing\"><\/a>An example of how these systems can work together is found in <a title=\"A GIS-based identification of potentially significant wildlife habitats associated with roads in Vermont\" href=\"http:\/\/escholarship.org\/uc\/item\/91c3z0rg\" target=\"_blank\">Austin <i>et al.<\/i> 2005<\/a> where wildlife habitat associated with roads is examined in Vermont. Various GIS data was utilized (e.g. land cover, core habitat, etc.) along with CAD data from the state police on wildlife collisions to create a map comparing wildlife crossing ratings and habitat suitability (Fig. 3). The data needed to solve complex research problems is likely to come from diverse sources and in a variety of formats. Georeferencing CAD data and distributing features of interest to a file geodatabase is one example of how non-GIS data can be converted to be useful for GIS analyses.<\/p>\n<div id=\"attachment_196\" class=\"wp-caption aligncenter\" style=\"width: 907px\"><a href=\"http:\/\/escholarship.org\/uc\/item\/91c3z0rg\" target=\"_blank\"><img loading=\"lazy\" decoding=\"async\" class=\" wp-image-196 \" alt=\"Wildlife habitat along roads\" src=\"http:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/WLhabitatroads.jpg\" width=\"897\" height=\"736\" srcset=\"https:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/WLhabitatroads.jpg 897w, https:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/WLhabitatroads-300x246.jpg 300w, https:\/\/jniemuth.hubns.net\/gis520\/files\/2013\/01\/WLhabitatroads-365x300.jpg 365w\" sizes=\"auto, (max-width: 897px) 100vw, 897px\" \/><\/a><p class=\"wp-caption-text\">Figure 3. Final map from <a title=\"A GIS-based identification of potentially significant wildlife habitats associated with roads in Vermont\" href=\"http:\/\/escholarship.org\/uc\/item\/91c3z0rg\" target=\"_blank\">Austin <i>et al.<\/i> 2005<\/a> showing habitat suitability, wildlife-linkage habitat values, and road-mortality data in Vermont.<\/p><\/div>\n<div class=\"alignleft\"><a href=\"https:\/\/jniemuth.hubns.net\/gis520\/geocoding-tabular-data-2\/\" title=\"Geocoding Tabular Data\">< Previous<\/a><\/div><div class=\"alignright\"><a href=\"https:\/\/jniemuth.hubns.net\/gis520\/data-cardinality-issues-in-arcgis\/\" title=\"Database Cardinality Issues in ArcGIS\">Next ><\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Problem: Develop a file geodatabase for the NC State University campus containing specified featured classes using data from a CAD file that is not georeferenced. Analysis Procedures: Georeferencing a CAD file to a reference file with known coordinates, such as &hellip; <a href=\"https:\/\/jniemuth.hubns.net\/gis520\/autocad-integration\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":206,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"folder":[],"class_list":["post-56","page","type-page","status-publish","has-post-thumbnail","hentry"],"_links":{"self":[{"href":"https:\/\/jniemuth.hubns.net\/gis520\/wp-json\/wp\/v2\/pages\/56","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jniemuth.hubns.net\/gis520\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/jniemuth.hubns.net\/gis520\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/jniemuth.hubns.net\/gis520\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jniemuth.hubns.net\/gis520\/wp-json\/wp\/v2\/comments?post=56"}],"version-history":[{"count":15,"href":"https:\/\/jniemuth.hubns.net\/gis520\/wp-json\/wp\/v2\/pages\/56\/revisions"}],"predecessor-version":[{"id":289,"href":"https:\/\/jniemuth.hubns.net\/gis520\/wp-json\/wp\/v2\/pages\/56\/revisions\/289"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/jniemuth.hubns.net\/gis520\/wp-json\/wp\/v2\/media\/206"}],"wp:attachment":[{"href":"https:\/\/jniemuth.hubns.net\/gis520\/wp-json\/wp\/v2\/media?parent=56"}],"wp:term":[{"taxonomy":"folder","embeddable":true,"href":"https:\/\/jniemuth.hubns.net\/gis520\/wp-json\/wp\/v2\/folder?post=56"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}