# GetFeaturesWithinDistanceOf Unexpected Results

**URL:** <https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147>\
**Category:** WinForms\
**Created:** [December 27, 2012, 4:55pm UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147 "2012-12-27T16:55:55Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [December 27, 2012, 4:55pm UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/1 "2012-12-27T16:55:55Z")

</div>

Hi,

I've&nbsp;got&nbsp;a&nbsp;procedure&nbsp;that&nbsp;tests&nbsp;if&nbsp;any&nbsp;point&nbsp;features&nbsp;in&nbsp;an&nbsp;in&nbsp;memory&nbsp;feature&nbsp;layer&nbsp;collection&nbsp;are&nbsp;near&nbsp;to&nbsp;a&nbsp;line&nbsp;shape&nbsp;that&nbsp;I&nbsp;specify.&nbsp;&nbsp;The&nbsp;procedure&nbsp;seems&nbsp;to&nbsp;work&nbsp;great&nbsp;most&nbsp;of&nbsp;the&nbsp;time,&nbsp;but&nbsp;when&nbsp;the&nbsp;line&nbsp;is&nbsp;oriented&nbsp;exactly&nbsp;0&nbsp;or&nbsp;180,&nbsp;the&nbsp;query&nbsp;results&nbsp;sometimes&nbsp;misses&nbsp;1&nbsp;of&nbsp;the&nbsp;points&nbsp;that&nbsp;should&nbsp;be&nbsp;included.

Can&nbsp;you&nbsp;please&nbsp;investigate?

Thanks,

Damian

&nbsp;

---

<div class="post-metadata">

**Author:** ![John4](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/j/e0b2c6/32.png) [@John4](https://community.thinkgeo.com/u/John4)\
**Post date:** [December 27, 2012, 6:05pm UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/2 "2012-12-27T18:05:39Z")

</div>

Hi&nbsp;Damian,

You&nbsp;are&nbsp;not&nbsp;alone,&nbsp;struggling&nbsp;with&nbsp;the&nbsp;same&nbsp;problem,&nbsp;it&nbsp;also&nbsp;occurs&nbsp;if&nbsp;it&nbsp;is&nbsp;090&nbsp;or&nbsp;270!

John

&nbsp;

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [December 28, 2012, 9:03am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/3 "2012-12-28T09:03:18Z")

</div>

Thanks&nbsp;John,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Glad&nbsp;to&nbsp;see&nbsp;someone&nbsp;else&nbsp;out&nbsp;there&nbsp;can&nbsp;confirm&nbsp;the&nbsp;issue.&nbsp;&nbsp;Let’s&nbsp;hope&nbsp;for&nbsp;a&nbsp;speedy&nbsp;resolve.

---

<div class="post-metadata">

**Author:** ![Gary2](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/g/49beb7/32.png) [@Gary2](https://community.thinkgeo.com/u/Gary2)\
**Post date:** [December 31, 2012, 12:58am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/4 "2012-12-31T00:58:24Z")

</div>

Hello&nbsp;Damian,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks&nbsp;fo&nbsp;your&nbsp;post,&nbsp;could&nbsp;you&nbsp;please&nbsp;provide&nbsp;your&nbsp;test&nbsp;feature&nbsp;wkt&nbsp;or&nbsp;wkb(including&nbsp;the&nbsp;lineshape&nbsp;and&nbsp;pointshape)&nbsp;to&nbsp;me&nbsp;that&nbsp;I&nbsp;can&nbsp;recreate&nbsp;it?&nbsp;  
&nbsp;&nbsp;  
&nbsp;I&nbsp;appreciate&nbsp;your&nbsp;help.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Gary

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [December 31, 2012, 11:42am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/5 "2012-12-31T11:42:56Z")

</div>

Hi&nbsp;Gary,

Attached&nbsp;is&nbsp;a&nbsp;test&nbsp;project&nbsp;to&nbsp;simulate&nbsp;the&nbsp;results.

When&nbsp;the&nbsp;program&nbsp;runs,&nbsp;it&nbsp;loads&nbsp;the&nbsp;line&nbsp;and&nbsp;points&nbsp;from&nbsp;2&nbsp;shape&nbsp;files&nbsp;in&nbsp;the&nbsp;data&nbsp;subdirectory.&nbsp;&nbsp;The&nbsp;line&nbsp;is&nbsp;oriented&nbsp;0&nbsp;degrees&nbsp;and&nbsp;the&nbsp;points&nbsp;fall&nbsp;along&nbsp;the&nbsp;line&nbsp;as&nbsp;can&nbsp;be&nbsp;seen&nbsp;in&nbsp;the&nbsp;map.

In&nbsp;the&nbsp;tool&nbsp;strip&nbsp;area,&nbsp;there&nbsp;is&nbsp;a&nbsp;text&nbsp;box&nbsp;that&nbsp;allows&nbsp;you&nbsp;to&nbsp;change&nbsp;the&nbsp;search&nbsp;distance&nbsp;of&nbsp;the&nbsp;GetFeaturesWithinDistanceOf&nbsp;function.&nbsp;&nbsp;After&nbsp;you&nbsp;set&nbsp;the&nbsp;value,&nbsp;click&nbsp;the&nbsp;button&nbsp;saying&nbsp;"Get&nbsp;All&nbsp;Points&nbsp;On&nbsp;the&nbsp;Line".

With&nbsp;1000m&nbsp;default&nbsp;search,&nbsp;you&nbsp;will&nbsp;see&nbsp;1&nbsp;of&nbsp;the&nbsp;points&nbsp;is&nbsp;not&nbsp;found.&nbsp;&nbsp;If&nbsp;you&nbsp;set&nbsp;it&nbsp;to&nbsp;500m,&nbsp;you&nbsp;will&nbsp;find&nbsp;2&nbsp;points&nbsp;not&nbsp;found.&nbsp;&nbsp;If&nbsp;you&nbsp;set&nbsp;it&nbsp;to&nbsp;250m,&nbsp;you&nbsp;will&nbsp;find&nbsp;6&nbsp;points&nbsp;not&nbsp;found.&nbsp;&nbsp;When&nbsp;the&nbsp;search&nbsp;is&nbsp;big&nbsp;enough&nbsp;(~1250m),&nbsp;you&nbsp;get&nbsp;all&nbsp;features&nbsp;returned.

It&nbsp;is&nbsp;definitely&nbsp;an&nbsp;error&nbsp;with&nbsp;the&nbsp;method&nbsp;as&nbsp;you&nbsp;can&nbsp;quickly&nbsp;scan&nbsp;the&nbsp;debug&nbsp;output&nbsp;of&nbsp;the&nbsp;converted&nbsp;features&nbsp;of&nbsp;each&nbsp;InMemoryFeatureLayer&nbsp;and&nbsp;see&nbsp;that&nbsp;they&nbsp;have&nbsp;identical&nbsp;X&nbsp;coordinates&nbsp;and&nbsp;that&nbsp;all&nbsp;Y&nbsp;coordinates&nbsp;for&nbsp;the&nbsp;points&nbsp;are&nbsp;inside&nbsp;the&nbsp;line&nbsp;Y&nbsp;coordinates.&nbsp;&nbsp;Sorry&nbsp;the&nbsp;test&nbsp;code&nbsp;is&nbsp;full&nbsp;of&nbsp;reprojections,&nbsp;but&nbsp;in&nbsp;my&nbsp;project&nbsp;I&nbsp;do&nbsp;a&nbsp;lot&nbsp;of&nbsp;converting&nbsp;to&nbsp;UTM&nbsp;from&nbsp;spherical&nbsp;mercator&nbsp;and&nbsp;I&nbsp;wanted&nbsp;it&nbsp;to&nbsp;be&nbsp;as&nbsp;close&nbsp;to&nbsp;my&nbsp;project&nbsp;as&nbsp;possible.

This&nbsp;only&nbsp;happens&nbsp;when&nbsp;you&nbsp;are&nbsp;at&nbsp;exact&nbsp;line&nbsp;headings&nbsp;of&nbsp;0,&nbsp;90,&nbsp;180&nbsp;and&nbsp;270.

I&nbsp;am&nbsp;using&nbsp;6.0.0.149.

Regards,

Damian

[ThinkGeo\_ZeroHeadingError.zip](https://community.thinkgeo.com/uploads/default/original/2X/c/ca590af0a7c3a68e5046d0a6c3d2b9098aab100f.zip) (48.7 KB)

---

<div class="post-metadata">

**Author:** ![Gary2](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/g/49beb7/32.png) [@Gary2](https://community.thinkgeo.com/u/Gary2)\
**Post date:** [January 4, 2013, 4:07am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/6 "2013-01-04T04:07:33Z")

</div>

Hello&nbsp;Damian,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks&nbsp;for&nbsp;your&nbsp;sample,&nbsp;this&nbsp;is&nbsp;a&nbsp;bug&nbsp;about&nbsp;precision,&nbsp;the&nbsp;lineshape&nbsp;you&nbsp;are&nbsp;using,&nbsp;they&nbsp;are&nbsp;almost&nbsp;heading&nbsp;90&nbsp;but&nbsp;not&nbsp;exactly&nbsp;90&nbsp;degree,&nbsp;like:&nbsp;  
&nbsp;&nbsp;  
&nbsp;Start&nbsp;Point:&nbsp;529212.589195103&nbsp;9692095.21456987&nbsp;  
&nbsp;End&nbsp;&nbsp;Point:&nbsp;529212.589195107&nbsp;9733095.21456987&nbsp;  
&nbsp;&nbsp;  
&nbsp;You&nbsp;can&nbsp;see&nbsp;their&nbsp;X&nbsp;coordinate&nbsp;just&nbsp;has&nbsp;a&nbsp;little&nbsp;difference.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Now&nbsp;we&nbsp;have&nbsp;fixed&nbsp;this&nbsp;bug&nbsp;and&nbsp;you&nbsp;can&nbsp;get&nbsp;newest&nbsp;dll&nbsp;6.0.236.0&nbsp;and&nbsp;have&nbsp;another&nbsp;try,&nbsp;we&nbsp;don’t&nbsp;synchronize&nbsp;to&nbsp;release&nbsp;branch&nbsp;immediately&nbsp;so&nbsp;please&nbsp;use&nbsp;development&nbsp;branch&nbsp;temporary.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Let&nbsp;us&nbsp;know&nbsp;if&nbsp;you&nbsp;still&nbsp;have&nbsp;the&nbsp;problem.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Gary

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [January 4, 2013, 3:26pm UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/7 "2013-01-04T15:26:13Z")

</div>

Hi&nbsp;Gary,&nbsp;  
&nbsp;&nbsp;  
&nbsp;I&nbsp;think&nbsp;there&nbsp;is&nbsp;an&nbsp;issue&nbsp;with&nbsp;the&nbsp;distribution&nbsp;site.&nbsp;&nbsp;The&nbsp;daily&nbsp;production&nbsp;builds&nbsp;have&nbsp;6.0.0.236,&nbsp;but&nbsp;on&nbsp;the&nbsp;development&nbsp;builds&nbsp;there&nbsp;is&nbsp;only&nbsp;6.0.235.0.&nbsp;  
&nbsp;&nbsp;  
&nbsp;At&nbsp;any&nbsp;rate,&nbsp;the&nbsp;6.0.0.236&nbsp;production&nbsp;build&nbsp;did&nbsp;not&nbsp;fix&nbsp;the&nbsp;issue.&nbsp;&nbsp;Maybe&nbsp;your&nbsp;changes&nbsp;did&nbsp;not&nbsp;make&nbsp;it&nbsp;in&nbsp;this&nbsp;version?&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;Damian

---

<div class="post-metadata">

**Author:** ![Gary2](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/g/49beb7/32.png) [@Gary2](https://community.thinkgeo.com/u/Gary2)\
**Post date:** [January 4, 2013, 7:20pm UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/8 "2013-01-04T19:20:13Z")

</div>

Hello&nbsp;Damian,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Sorry&nbsp;for&nbsp;the&nbsp;inconvenience,&nbsp;our&nbsp;auto&nbsp;build&nbsp;package&nbsp;about&nbsp;development&nbsp;branch&nbsp;failed&nbsp;yesterday(6.0.236.0),&nbsp;the&nbsp;one&nbsp;you&nbsp;are&nbsp;using&nbsp;is&nbsp;release&nbsp;branch(6.0.0.236),&nbsp;so&nbsp;as&nbsp;I&nbsp;said&nbsp;above&nbsp;"Now&nbsp;we&nbsp;have&nbsp;fixed&nbsp;this&nbsp;bug&nbsp;and&nbsp;you&nbsp;can&nbsp;get&nbsp;newest&nbsp;dll&nbsp;6.0.236.0&nbsp;and&nbsp;have&nbsp;another&nbsp;try,&nbsp;we&nbsp;don’t&nbsp;synchronize&nbsp;to&nbsp;release&nbsp;branch&nbsp;immediately&nbsp;so&nbsp;please&nbsp;use&nbsp;development&nbsp;branch&nbsp;temporary.&nbsp;"&nbsp;the&nbsp;release&nbsp;branch&nbsp;didn’t&nbsp;change,&nbsp;you&nbsp;can&nbsp;try&nbsp;today&nbsp;to&nbsp;get&nbsp;6.0.237.0&nbsp;or&nbsp;later(if&nbsp;failed&nbsp;again,&nbsp;you&nbsp;can&nbsp;wait&nbsp;6.0.238.0).&nbsp;  
&nbsp;&nbsp;  
&nbsp;We&nbsp;will&nbsp;try&nbsp;to&nbsp;make&nbsp;the&nbsp;build&nbsp;successful&nbsp;today.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Gary

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [January 7, 2013, 11:22am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/9 "2013-01-07T11:22:30Z")

</div>

Hi&nbsp;Gary,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Now&nbsp;I’m&nbsp;really&nbsp;confused.&nbsp;&nbsp;Why&nbsp;is&nbsp;the&nbsp;Production&nbsp;build&nbsp;number&nbsp;higher&nbsp;than&nbsp;the&nbsp;development&nbsp;build&nbsp;number.&nbsp;&nbsp;Doesn’t&nbsp;that&nbsp;suggest&nbsp;that&nbsp;the&nbsp;production&nbsp;code&nbsp;is&nbsp;more&nbsp;up&nbsp;to&nbsp;date&nbsp;than&nbsp;the&nbsp;development???&nbsp;&nbsp;Right&nbsp;now,&nbsp;the&nbsp;site&nbsp;has&nbsp;239&nbsp;for&nbsp;production&nbsp;and&nbsp;238&nbsp;for&nbsp;development.&nbsp;  
&nbsp;&nbsp;  
&nbsp;If&nbsp;that’s&nbsp;not&nbsp;the&nbsp;case,&nbsp;then&nbsp;how&nbsp;am&nbsp;I&nbsp;supposed&nbsp;to&nbsp;know&nbsp;when&nbsp;my&nbsp;bug&nbsp;fix&nbsp;is&nbsp;included&nbsp;in&nbsp;the&nbsp;production&nbsp;build&nbsp;so&nbsp;I&nbsp;can&nbsp;deploy&nbsp;my&nbsp;solution???&nbsp;&nbsp;The&nbsp;FAQ&nbsp;does&nbsp;not&nbsp;address&nbsp;this.&nbsp;  
&nbsp;&nbsp;  
&nbsp;I&nbsp;confirm&nbsp;that&nbsp;238&nbsp;development&nbsp;does&nbsp;fix&nbsp;the&nbsp;issue,&nbsp;but&nbsp;the&nbsp;239&nbsp;deployment&nbsp;does&nbsp;not.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;Damian

---

<div class="post-metadata">

**Author:** ![Gary2](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/g/49beb7/32.png) [@Gary2](https://community.thinkgeo.com/u/Gary2)\
**Post date:** [January 7, 2013, 8:32pm UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/10 "2013-01-07T20:32:52Z")

</div>

Hello&nbsp;Damian,&nbsp;  
  
  
  
Sorry&nbsp;for&nbsp;the&nbsp;inconvenience,&nbsp;so&nbsp;we&nbsp;have&nbsp;development&nbsp;branch(6.0.xx.0)&nbsp;and&nbsp;release&nbsp;branch(which&nbsp;you&nbsp;call&nbsp;it&nbsp;production&nbsp;and&nbsp;the&nbsp;version&nbsp;number&nbsp;is&nbsp;6.0.0.xx),&nbsp;in&nbsp;the&nbsp;normal&nbsp;situation&nbsp;they&nbsp;should&nbsp;be&nbsp;the&nbsp;same&nbsp;number&nbsp;and&nbsp;build&nbsp;the&nbsp;new&nbsp;version&nbsp;everyday,&nbsp;but&nbsp;sometimes&nbsp;because&nbsp;network&nbsp;problem,&nbsp;build&nbsp;problem&nbsp;or&nbsp;some&nbsp;fix&nbsp;cause&nbsp;the&nbsp;problem&nbsp;that&nbsp;one&nbsp;branch&nbsp;will&nbsp;failed,&nbsp;this&nbsp;is&nbsp;why&nbsp;you&nbsp;have&nbsp;seen&nbsp;the&nbsp;release&nbsp;branch&nbsp;version&nbsp;6.0.0.239&nbsp;but&nbsp;development&nbsp;branch&nbsp;only&nbsp;6.0.238.0(this&nbsp;time&nbsp;the&nbsp;reason&nbsp;is&nbsp;the&nbsp;network&nbsp;delay,&nbsp;so&nbsp;release&nbsp;branch&nbsp;upload&nbsp;finish&nbsp;first,&nbsp;if&nbsp;you&nbsp;can&nbsp;check&nbsp;your&nbsp;helpdesk&nbsp;now&nbsp;you&nbsp;will&nbsp;find&nbsp;out&nbsp;that&nbsp;6.0.239.0&nbsp;is&nbsp;ready&nbsp;for&nbsp;download)&nbsp;  
  
  
  
And&nbsp;for&nbsp;our&nbsp;bug&nbsp;fix&nbsp;mechanism,&nbsp;once&nbsp;we&nbsp;have&nbsp;fixed&nbsp;a&nbsp;bug,&nbsp;if&nbsp;we&nbsp;can&nbsp;confirm&nbsp;it&nbsp;without&nbsp;any&nbsp;doubt,&nbsp;we&nbsp;will&nbsp;synchronize&nbsp;to&nbsp;the&nbsp;release&nbsp;branch&nbsp;immediately,&nbsp;otherwise&nbsp;we&nbsp;will&nbsp;wait&nbsp;user's&nbsp;response&nbsp;or&nbsp;double&nbsp;check&nbsp;after&nbsp;several&nbsp;days.&nbsp;So&nbsp;for&nbsp;this&nbsp;situation,&nbsp;you&nbsp;have&nbsp;to&nbsp;use&nbsp;development&nbsp;branch&nbsp;temporary.&nbsp;  
  
  
  
Another&nbsp;situation&nbsp;is&nbsp;we&nbsp;have&nbsp;added&nbsp;some&nbsp;new&nbsp;feature,&nbsp;avoid&nbsp;to&nbsp;have&nbsp;the&nbsp;breaking&nbsp;changes,&nbsp;we&nbsp;only&nbsp;apply&nbsp;it&nbsp;in&nbsp;the&nbsp;development&nbsp;branch&nbsp;and&nbsp;never&nbsp;synchronize&nbsp;to&nbsp;release&nbsp;branch&nbsp;until&nbsp;next&nbsp;public&nbsp;release(7.0&nbsp;next&nbsp;time)&nbsp;  
  
  
  
For&nbsp;your&nbsp;problem&nbsp;now,&nbsp;we&nbsp;have&nbsp;synchronize&nbsp;to&nbsp;the&nbsp;release&nbsp;branch&nbsp;today,&nbsp;so&nbsp;you&nbsp;can&nbsp;choose&nbsp;either&nbsp;development&nbsp;branch&nbsp;or&nbsp;release&nbsp;branch&nbsp;after&nbsp;6.0.240.0(6.0.0.240)&nbsp;  
  
  
  
Let&nbsp;us&nbsp;know&nbsp;if&nbsp;you&nbsp;have&nbsp;any&nbsp;queries.&nbsp;  
  
  
  
Regards,&nbsp;  
  
  
  
Gary

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [January 9, 2013, 3:47pm UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/11 "2013-01-09T15:47:53Z")

</div>

Hi&nbsp;Gary,&nbsp;  
&nbsp;&nbsp;  
&nbsp;I’m&nbsp;still&nbsp;waiting&nbsp;for&nbsp;release&nbsp;to&nbsp;update&nbsp;in&nbsp;the&nbsp;customer&nbsp;portal.&nbsp;&nbsp;It&nbsp;says&nbsp;6.0.0.228&nbsp;right&nbsp;now&nbsp;which&nbsp;is&nbsp;really&nbsp;off.&nbsp;&nbsp;I’m&nbsp;not&nbsp;in&nbsp;too&nbsp;big&nbsp;a&nbsp;rush&nbsp;to&nbsp;get&nbsp;this&nbsp;fix,&nbsp;but&nbsp;I&nbsp;wanted&nbsp;to&nbsp;make&nbsp;sure&nbsp;someone&nbsp;knew&nbsp;it’s&nbsp;been&nbsp;messed&nbsp;up&nbsp;for&nbsp;quite&nbsp;some&nbsp;time&nbsp;now.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;Damian

---

<div class="post-metadata">

**Author:** ![Ryan](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/r/a8b319/32.png) [@Ryan](https://community.thinkgeo.com/u/Ryan)\
**Post date:** [January 10, 2013, 9:29am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/12 "2013-01-10T09:29:52Z")

</div>

Hi&nbsp;Damian,&nbsp;&nbsp;  
&nbsp;&nbsp;  
&nbsp;I&nbsp;just&nbsp;checked&nbsp;the&nbsp;daily&nbsp;builds&nbsp;for&nbsp;your&nbsp;account&nbsp;and&nbsp;a&nbsp;6.0.0.242&nbsp;version&nbsp;is&nbsp;available.&nbsp;Please&nbsp;let&nbsp;us&nbsp;know&nbsp;if&nbsp;you&nbsp;have&nbsp;any&nbsp;issues&nbsp;accessing&nbsp;it.

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [October 1, 2013, 2:46pm UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/13 "2013-10-01T14:46:33Z")

</div>

Hi,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Somewhere&nbsp;along&nbsp;the&nbsp;line,&nbsp;this&nbsp;error&nbsp;has&nbsp;gotten&nbsp;back&nbsp;into&nbsp;version&nbsp;7.0.&nbsp;&nbsp;Can&nbsp;you&nbsp;please&nbsp;take&nbsp;another&nbsp;look&nbsp;at&nbsp;this?&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;Damian

---

<div class="post-metadata">

**Author:** ![Summer1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/s/c89c15/32.png) [@Summer1](https://community.thinkgeo.com/u/Summer1)\
**Post date:** [October 3, 2013, 8:54am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/14 "2013-10-03T08:54:57Z")

</div>

Hi&nbsp;Damian,&nbsp;  
&nbsp;&nbsp;  
&nbsp;May&nbsp;I&nbsp;make&nbsp;a&nbsp;confirmation&nbsp;with&nbsp;you?&nbsp;Is&nbsp;the&nbsp;problem&nbsp;"DailyBuildProblem"&nbsp;or&nbsp;the&nbsp;"FunctionalityBugProblem"?&nbsp;  
&nbsp;&nbsp;  
&nbsp;Waiting&nbsp;for&nbsp;your&nbsp;further&nbsp;information.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Best&nbsp;Regards&nbsp;  
&nbsp;&nbsp;  
&nbsp;Summer

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [October 3, 2013, 10:16am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/15 "2013-10-03T10:16:38Z")

</div>

Hi&nbsp;Summer,&nbsp;  
&nbsp;&nbsp;  
&nbsp;It’s&nbsp;the&nbsp;functionality&nbsp;issue&nbsp;regarding&nbsp;precision.&nbsp;&nbsp;The&nbsp;GetFeaturesWithinDistanceOf&nbsp;returns&nbsp;inaccurate&nbsp;results&nbsp;when&nbsp;at&nbsp;0/90/180/270&nbsp;degrees.&nbsp;You&nbsp;can&nbsp;use&nbsp;previous&nbsp;attached&nbsp;project&nbsp;with&nbsp;current&nbsp;production&nbsp;libraries&nbsp;to&nbsp;confirm.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;Damian

---

<div class="post-metadata">

**Author:** ![Summer1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/s/c89c15/32.png) [@Summer1](https://community.thinkgeo.com/u/Summer1)\
**Post date:** [October 4, 2013, 10:08am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/16 "2013-10-04T10:08:51Z")

</div>

Hi&nbsp;Damian,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks&nbsp;for&nbsp;your&nbsp;further&nbsp;information,&nbsp;now&nbsp;we&nbsp;are&nbsp;looking&nbsp;into&nbsp;it,&nbsp;it&nbsp;might&nbsp;need&nbsp;a&nbsp;little&nbsp;time&nbsp;before&nbsp;we&nbsp;figure&nbsp;it&nbsp;out.Would&nbsp;you&nbsp;pelase&nbsp;wait&nbsp;a&nbsp;little&nbsp;while.&nbsp;Anything&nbsp;new&nbsp;will&nbsp;be&nbsp;updated&nbsp;here&nbsp;immediately.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Best&nbsp;Regards&nbsp;  
&nbsp;&nbsp;  
&nbsp;Summer

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [October 4, 2013, 10:11am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/17 "2013-10-04T10:11:13Z")

</div>

Okay,&nbsp;thanks&nbsp;Summer.

---

<div class="post-metadata">

**Author:** ![Summer1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/s/c89c15/32.png) [@Summer1](https://community.thinkgeo.com/u/Summer1)\
**Post date:** [October 6, 2013, 2:02am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/18 "2013-10-06T02:02:52Z")

</div>

Hi&nbsp;Damian,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks&nbsp;for&nbsp;your&nbsp;waiting,&nbsp;we&nbsp;have&nbsp;fixed&nbsp;this&nbsp;problem&nbsp;would&nbsp;you&nbsp;please&nbsp;get&nbsp;the&nbsp;latest&nbsp;dll&nbsp;package&nbsp;7.0.117.0&nbsp;or&nbsp;7.0.0.117&nbsp;and&nbsp;try&nbsp;it&nbsp;again?&nbsp;  
&nbsp;&nbsp;  
&nbsp;if&nbsp;you&nbsp;have&nbsp;any&nbsp;more&nbsp;question&nbsp;,&nbsp;please&nbsp;feel&nbsp;free&nbsp;to&nbsp;let&nbsp;us&nbsp;know.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Best&nbsp;Regards&nbsp;  
&nbsp;&nbsp;  
&nbsp;Summer&nbsp;

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [October 16, 2013, 11:50am UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/19 "2013-10-16T11:50:23Z")

</div>

Thank&nbsp;you&nbsp;Summer.&nbsp;&nbsp;I&nbsp;can&nbsp;confirm&nbsp;that&nbsp;the&nbsp;fix&nbsp;works.&nbsp;  
&nbsp;&nbsp;  
&nbsp;BR,&nbsp;  
&nbsp;Damian

---

<div class="post-metadata">

**Author:** ![Summer1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/s/c89c15/32.png) [@Summer1](https://community.thinkgeo.com/u/Summer1)\
**Post date:** [October 16, 2013, 8:28pm UTC](https://community.thinkgeo.com/t/getfeatureswithindistanceof-unexpected-results/2147/20 "2013-10-16T20:28:30Z")

</div>

Hi&nbsp;Damian,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Great&nbsp;to&nbsp;hear&nbsp;it&nbsp;is&nbsp;sorted&nbsp;out,&nbsp;if&nbsp;you&nbsp;have&nbsp;any&nbsp;more&nbsp;question,&nbsp;please&nbsp;feel&nbsp;free&nbsp;to&nbsp;let&nbsp;us&nbsp;know.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Best&nbsp;Regards&nbsp;  
&nbsp;&nbsp;  
&nbsp;Summer