<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hey guys,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have been working with ModelBuilder recently and have found a few oddball issues. First, when unioning two datasets together it is natural to create some pretty gnarly data. With all of the slivers come geometry issues that need to be cleaned up before further geoprocessing can be done. Now what you may not be prepared for is when running the Repair Geometry tool doesn’t iron out the kinks. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Typically, when you try to run any sort of spatial analysis/selection/etc and the tool fails bad geometry is to blame. Repair Geometry has always done the job for me in the past however my tools kept failing. I created all sorts of insane steps and reordering of processes to cut down on the error, but on a whim decided to do something a bit odd. I ran repair geometry two times in a row within my model, and that allowed me to process larger chunks of my dataset, but not everything. So I tacked on an extra repair geometry, because at this point, why not, and it worked.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So Repair… Repair… and Repair some more if needed.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The fallout from my frustration and attempts to circumvent the need for multiple repairs I created a “simplified” model that runs record by record and appends the processed row into the new dataset (I only have 7,500 rows to run). I run it, and it gets through a few hundred records, with excellent looking results, and then ArcMap crashes. I pray I haven’t corrupted my database and open up ArcMap while wincing, but it is okay this time. I decide to be smart and create a backup of the dataset in ArcCatalog by doing the right-click + “Copy,” and my computer freezes. I restart my computer and check the folder, my geodatabase is over 4 gigabytes for two datasets. Now something is not quite right with this. I run compact, and the database shrinks to a respectable 60mb.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Moral of the story, keep an eye on your database size. If you are iterating multi-step analysis and are dissolving/appending data like your license is about to expire throw a compact at the end of the analysis for good measure. For a file geodatabase it only takes a second or so to run (After your first compact). No clue as to what exactly the bloat is coming from but compact fixes it.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I hope everyone is doing well,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Getting aggregated Zoning data to coincide parcels where it should, and maintain the shape of Zoning where it matters…<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There is a specific case where errors will be produced but it will reduce the number of manual edits necessary significantly. …and those errors are consistent which I will take on any day.<o:p></o:p></p><p class=MsoNormal><img width=2112 height=231 id="Picture_x0020_0" src="cid:image003.jpg@01CCBA7B.F76B2640" alt="the_model.jpg"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>After I run this model I also need to run the Eliminate Polygon Part tool to clean-up any tiny sliver/holes within polygons (Under 25 square feet).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Tahoma","sans-serif"'>Jason A. Griffin</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>, Ext. 33613</span> <span style='color:gray'>| BTS Senior Technology Specialist, GIS Dev. | Pinellas County Government, Business Technology Services [BTS] | 400 S Ft. Harrison Ave | Clearwater, FL 33756 | </span>Tel: 727-453-3613 <span style='color:gray'>| Cell: 727-600-6634 | <a href="mailto:JGriffin@co.pinellas.fl.us">JGriffin@co.pinellas.fl.us</a>|<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>