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
Aaron Goodman at PDD asked us: "When using the buffer feature, such as 300ft buffer - is there a way to filter those addresses within the original boundary from those in the buffer zone?"
Currently, users would need to download the table of addresses within the boundary then download the addresses within the boundary + the buffer area and use another tool to join the two tables on the ‘addr_id’ field to determine which addresses are ONLY in the buffer area.
I see two options here:
New output column: Add this information to a new column in the output table with values of 'boundary' or 'buffer' and users can filter the output on their on.
New selection option: If a user applies a buffer from a boundary, add an option/button to cut the boundary out of the buffer and reselect the addresses within it.
On July 8, 2022 @jmcbroom commented "Let's think about how hard it would be to implement option 1: computing the distance."
The text was updated successfully, but these errors were encountered:
@alicehargreaves created this issue Jan 28, 2022
Aaron Goodman at PDD asked us: "When using the buffer feature, such as 300ft buffer - is there a way to filter those addresses within the original boundary from those in the buffer zone?"
Currently, users would need to download the table of addresses within the boundary then download the addresses within the boundary + the buffer area and use another tool to join the two tables on the ‘addr_id’ field to determine which addresses are ONLY in the buffer area.
I see two options here:
On July 8, 2022 @jmcbroom commented "Let's think about how hard it would be to implement option 1: computing the distance."
The text was updated successfully, but these errors were encountered: