Latest Contributions by MatthewDobson

From my experience, selecting the appropriate ESRI AMI when building the server is painless & easy .... ... View more

Mayur, your suggestion fixed this issue for me. Thanks!!! ... View more

Megan, have you tried a repair geometry on the featureclass (see this)?? In my experience, polygons with geometry issues can display okay but fail to label. Good luck! ... View more

I put my two cents in to a similar issue over on this post: https://community.esri.com/thread/62725?sr=inbox&ru=153770. My issues were solved by doing a repair geometry on each layer in the FGDB source for the cache mxd. There weren't many errors, but the auto-fix (including deleting null-geometry features) has made a difference. Matthew ... View more

Hey guy's. I have started generating a grid over the features to be cached then executing the cache process on the grid featureclass. It adds an additional step, but the results are better. The help for the Grid Index Features tool is here: http://resources.arcgis.com/en/help/main/10.1/index.html#//00700000000q000000 I restart the CachingTools service regularly also. Hope this helps .... MD ... View more

Try  http://resources.arcgis.com/en/help/main/10.1/index.html#/CreateMapSDDraft/00s30000006q000000/ ... View more

I am not sure, but will the 'Export Feature Attribute to ASCII' tool do the trick? I found it under Spatial Statistics -> Utilities .... Matthew ... View more

Maybe the domain to table tool? ... View more

Deleting the ....\AppData\Local\ESRI\DefaultDomain_Path folders resolved this for me as well. ... View more

Or using 'not' .... def FindLabel ( [PARCEL] , [LOTNUMBER] , [DEEDACRES] ):   if not [LOTNUMBER]:     return "<CLR yellow='255'>" + [PARCEL] + "</CLR>\n" + str([DEEDACRES])   else:     return "<CLR yellow='255'>" + [PARCEL] + "</CLR>\n" + [LOTNUMBER] ... View more

Won't "not" work? I haven't corrected for your specific example, but what about something like: def FindLabel ( [contractorName] ):   if not [contractorName]:     a = "Apples"   else:     a = [contractorName]   return a ... View more

Can you treat the features as lines - instead of points? Could the start x & y location be the same as the end x & y and use the 'height' and 'from height' options to represent the pole? The help says 'When using two height fields, each line will start at the first height and end at the second '. Just a thought. Good luck! Matthew ... View more

Craig, have you looked at the 'Feature To 3D By Attribute' within the 3D Analyst extension? (10.1 help is here) It should do steps 2 & 3 of your process .... Matthew ... View more