eSearch Widget (3.1.9) and buffer distance errors

[JasonStanton__GISP]

I have seem similar posts to this but nothing has worked for me and I can't make any sense of it.

When I buffer a graphic or a selected feature using the eSearch Widget (3.1.9) the buffer distances are roughly 70% of what they should be.  The wkid in the config and eSearch XML's, as well as my data, are 102100.

Originally I thought the issue might be that the data source itself is wkid 26986 and the MXD, and resulting service, is 102100.  However I both (1) converted the data the correct wkid and separtely (2) set the correct projection transformation in the MXD and republished the services.  Neither attempt worked.

Using the eDraw widget my calculations appear to be correct so I'm very confused on what is wrong.  Any suggestions would be GREATLY appreciated!!

Jason

[RobertScheitlin__GISP]

Jason,

  Use 102003 as the WKID and see if that helps.

[JasonStanton__GISP]

I tried that, depending on exactly what you are referring to.  Should I use wkid 102003 in just the eSearch XML or also the config XML and service?

[RobertScheitlin__GISP]

Jason,

  Just the eSearch widget xml. Short of that I don't know. I don't remember if I fixed something with buffering in between 3.1 and 3.6.5 (always better to stay current you can get all the bug fixes).

[JasonStanton__GISP]

No dice.  The buffer doesn't generate using that wkid.

[JasonStanton__GISP]

I created a quick 3.6 project, changed the wkid to 102003 and the buffers appear correct.  However, when I do a graphic buffer the symbol flashes and disappears, but I guess I can work on that issue later.

[RobertScheitlin__GISP]

Jason,

   In version 3.6.5 there is a configuration option to leave the buffer on the map or not (keepbufferaftersearch), by default it is false.

[JasonStanton__GISP]

I figured it was something like that.  Thanks for your help, it is greatly appreciated!