Hi Carrie, Arches uses Turf.js (http://turfjs.org/) to calculate buffers on geometries. It turns out that the version of Turf used in v3 incorrectly calculated buffers. We've updated the Turf library in Arches v4, which has resolved the problem.
Cheers, Dennis On Saturday, April 14, 2018 at 6:56:27 AM UTC-7, [email protected] wrote: > > We use an application of Version 3 and recently discovered that the buffer > measurements in the location filter are not accurate. For example, if I > define a buffer of 2,640 ft, the buffer it creates is actually 2,400 ft. We > have checked this on other Arches applications, and it seems to be a > problem across the board and not just with our application. > Has anyone else noticed this issue, and if so, has it been resolved? > Thanks, > Carrie > > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
