# \- intervention in the functions that detect collisions of drawn data (names, icons, points, etc.)

**URL:** <https://community.thinkgeo.com/t/intervention-in-the-functions-that-detect-collisions-of-drawn-data-names-icons-points-etc/500>\
**Category:** WinForms\
**Created:** [June 24, 2009, 5:19am UTC](https://community.thinkgeo.com/t/intervention-in-the-functions-that-detect-collisions-of-drawn-data-names-icons-points-etc/500 "2009-06-24T05:19:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wesolowski](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/w/90db22/32.png) [@wesolowski](https://community.thinkgeo.com/u/wesolowski)\
**Post date:** [June 24, 2009, 5:19am UTC](https://community.thinkgeo.com/t/intervention-in-the-functions-that-detect-collisions-of-drawn-data-names-icons-points-etc/500/1 "2009-06-24T05:19:22Z")

</div>

Control  
  
&nbsp;WinformsMap&nbsp;does&nbsp;not&nbsp;like&nbsp;too&nbsp;much&nbsp;data&nbsp;to&nbsp;draw.&nbsp;Also&nbsp;does&nbsp;not&nbsp;like&nbsp;draw&nbsp;to&nbsp;much&nbsp;labels,&nbsp;names,&nbsp;points,&nbsp;icons,&nbsp;etc.&nbsp;as&nbsp;they&nbsp;really&nbsp;exist,&nbsp;names&nbsp;in&nbsp;particular.&nbsp;How&nbsp;and&nbsp;which&nbsp;methods&nbsp;should&nbsp;I&nbsp;use&nbsp;to&nbsp;obtain&nbsp;possibility&nbsp;to&nbsp;intervention&nbsp;in&nbsp;the&nbsp;functions&nbsp;that&nbsp;detect&nbsp;collisions&nbsp;of&nbsp;drawn&nbsp;data&nbsp;(names,&nbsp;points,&nbsp;etc.)?

&nbsp;

---

<div class="post-metadata">

**Author:** ![ThinkGeo](https://community.thinkgeo.com/user_avatar/community.thinkgeo.com/thinkgeo/32/25029_2.png) [@ThinkGeo](https://community.thinkgeo.com/u/ThinkGeo)\
**Post date:** [June 24, 2009, 7:56pm UTC](https://community.thinkgeo.com/t/intervention-in-the-functions-that-detect-collisions-of-drawn-data-names-icons-points-etc/500/2 "2009-06-24T19:56:33Z")

</div>

Pawel,&nbsp;

Thanks&nbsp;for&nbsp;your&nbsp;post&nbsp;and&nbsp;welcome&nbsp;you&nbsp;ThinkGeo&nbsp;Desktop&nbsp;Forum!  
&nbsp;  
For&nbsp;symbol&nbsp;display,&nbsp;we&nbsp;have&nbsp;no&nbsp;way&nbsp;to&nbsp;detect&nbsp;collisions&nbsp;and&nbsp;avoid&nbsp;it&nbsp;automatically,&nbsp;you&nbsp;have&nbsp;to&nbsp;control&nbsp;it&nbsp;manually&nbsp;by&nbsp;ZoomLevel,&nbsp;we&nbsp;have&nbsp;developed&nbsp;App&nbsp;with&nbsp;around&nbsp;20GB&nbsp;which&nbsp;seems&nbsp;not&nbsp;so&nbsp;clustered&nbsp;with&nbsp;very&nbsp;decent&nbsp;control&nbsp;of&nbsp;data&nbsp;based&nbsp;on&nbsp;ZoomLevel&nbsp;controlling.  
&nbsp;  
For&nbsp;Label&nbsp;display,&nbsp;we&nbsp;provided&nbsp;some&nbsp;properties&nbsp;you&nbsp;can&nbsp;use&nbsp;to&nbsp;detect&nbsp;the&nbsp;collection&nbsp;and&nbsp;avoid&nbsp;them&nbsp;in&nbsp;some&nbsp;particular&nbsp;ZoomLevel&nbsp;and&nbsp;Windows&nbsp;extent;&nbsp;Following&nbsp;just&nbsp;gives&nbsp;you&nbsp;2&nbsp;simple&nbsp;and&nbsp;obvious&nbsp;control&nbsp;settings&nbsp;from&nbsp;a&nbsp;whole&nbsp;bunch&nbsp;of&nbsp;them.  
`lineShapeFile.ZoomLevelSet.ZoomLevel01.DefaultTextStyle.DuplicateRule = LabelDuplicateRule.OneDuplicateLabelPerQuadrant;lineShapeFile.ZoomLevelSet.ZoomLevel01.DefaultTextStyle.OverlappingRule = LabelOverlappingRule.NoOverlapping;`

Any&nbsp;more&nbsp;questions&nbsp;just&nbsp;let&nbsp;me&nbsp;know.

&nbsp;Thanks.  
&nbsp;  
Yale