Just to wrap this up: the issue has been addressed for v4 here https://github.com/archesproject/arches/issues/3248, and I have made a pull request to fix it in the stable/3.x branch of the repo. When and if that branch can be pushed out as a general v3 update is TDB.
Adam On Monday, April 16, 2018 at 6:58:26 PM UTC-5, Cyrus Hiatt wrote: > > My apologies - I misinformed Dennis about our use of turf in v3. However, > he is correct that older versions of turf poorly calculated buffers. In V3 > we actually calculate the buffer using GEOS. Looking at the code it > appears the buffer calculation is done with SRID 3857. It may help to > change that projection, but what is used to replace 3857 would depend on > the project's size and location. > > - Cyrus > > On Mon, Apr 16, 2018 at 4:37 PM, Adam Cox <[email protected]> wrote: > >> Hi Dennis, I know a lot of people are still using v3 of Arches. What >> would be the best way to update their installations so the buffer tool is >> accurate? Do you know what version of turf.js fixed the issue? >> >> Adam >> >> On Mon, Apr 16, 2018 at 5:59 PM, Dennis Wuthrich <[email protected]> >> wrote: >> >>> 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. >>> >> >> -- >> -- 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. >> > > -- -- 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.
