You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pre-LocoKit Arc App used 1 SD for all visit radius tasks, both display and processing. LocoKit has instead always used 2 SD.
2 SD is more "correct", but it means that visits look fatter on the map, and makes the edge cleansing versus paths much more hungry.
The fatter presentation on the map is probably fine. It does show a more true radius for the visit. But the greedy edge cleansing can be too much, especially when dealing with visits to places that are only a short distance apart.
So yeah, I want to try going back to 1 SD for edge cleansing.
The text was updated successfully, but these errors were encountered:
Note that this change is live in Arc App v2.1.3, which will be going live presumably later today. (It's been in the review queue for 12+ hours, so it shouldn't be too far off).
Closing this, as it at the very least hasn't caused any troubles. I'd still like to do more tweaking to visit radiuses, but I think this SD change on edge cleansing is still a step in the right direction, so it's good to stay.
Pre-LocoKit Arc App used 1 SD for all visit radius tasks, both display and processing. LocoKit has instead always used 2 SD.
2 SD is more "correct", but it means that visits look fatter on the map, and makes the edge cleansing versus paths much more hungry.
The fatter presentation on the map is probably fine. It does show a more true radius for the visit. But the greedy edge cleansing can be too much, especially when dealing with visits to places that are only a short distance apart.
So yeah, I want to try going back to 1 SD for edge cleansing.
The text was updated successfully, but these errors were encountered: