nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Has anyone had to draw a public notification buffer that excludes right of way?

deleted-user-kASrD7OWVCDl

Our City code says that the buffer should be 500' not including rights of way. I can't think of a way to standardize this.

Najděte více příspěvků označených jako

Federal State Local

Urban and Regional Planning

Land Administration

Accepted answers

All comments

ChrisDonohue__GISP

A few questions to help clarify the issue:

Does your organization have Right-of-Way (ROW) polygons stored either in a parcel layer or a regular feature class?
Which software are you using to accomplish this? ArcGIS? ArcGIS Online? Another?
What version of the software?
Is it a specific tool/process that already exists that you are encontering this issue with (like something from the Local Government Information Model (LGIM)) or is this a brand new set of functionality you want to create?
Based on your CIty Code, what is the basis of where the buffer starts? Is it a parcel boundary and then 500 feet out, the center of a parcel and then 500 feet out, or another basis?

Our city uses a parcel layer for public notifications that has all the ROW stripped out prior to running the buffers. However, that said, I've noticed other municipalities have a different combination of data and process. So I guess solving this comes down to "what have you got to work with" and then "how do you want to get there given what is available."

Chris Donohue, GISP

deleted-user-kASrD7OWVCDl

Thanks Chris.

We do not have ROW polygons. We have a legal property line layer and a matching parcel layer for assessor's parcels.
I am using ArcGIS Desktop but I could use Online or Pro.
version 10.4.1
In the past I have used the buffer tool to draw a polygon 500 feet out from the boundary of the parcel. I just found out that I am supposed to exclude ROW.

I'm not really sure how that could be done aside from just estimation. Is it possible to configure the buffer tool to account for ROW?

ChrisDonohue__GISP

My very first thought would be to do it the way you said you did it in the past. I.e,. buffer the selected polygon 500 feet and then find all the parcels that intersect that. With this process the intersected ones would become the ones you need to notify.

But after re-reading your question I think what is going on is that you are saying the selected parcel needs to be buffered 500' and that distance needs to exclude from the measurement any ROW traversed as part of the 500 foot distance part. In other words, going away from the selected parcel we start to measure across parcels but whenever we traverse a ROW we stop increasing the measurement and only continue it once we are traversing parcels again. So a parcel 590 feet away from your selected parcel would be notified it in the traverse to it a 100 foot ROW was crossed (which does not count towards the 500 ft notification distance). In short, it is not a simple 500 foot buffer to solve this. So the goal will be to find a process that measures 500 feet out from a polygon to find all other non-ROW polygons by intentionally excluding from the 500ft distance any ROW polygons crossed.

Can you confirm if I theorized this correctly? If this is the case I don't immediately know the answer to this, but am sure with the talent on GeoNet we can find a solution. Let me know if I got the issue correct and/or if there is another aspect to it.

Chris Donohue, GISP

ChrisDonohue__GISP

Some ideas:

ESRI Local Government Information Model Public Notification Tool. I have not used this, but it may be worth looking into.

http://solutions.arcgis.com/local-government/help/public-notification/

If the goal is indeed to traverse 500 feet out only accumulating distance across parcels (ie the distance across ROW does not count), I'll throw out some preliminary workflow ideas (untested) on how it may be possible to solve that. Note that these will need to be fleshed out a bit and they would be an interesting challenge for someone to implement (i.e. not a simple solution quickly done):

If one has access to the Spatial Analyst Extension, create a Cost Allocation or Euclidean Distance. Make ROW zero and parcels a value of 1. Once the distance surface equivalent to 500feet is found, convert from raster back to vector and do the parcel selections. http://desktop.arcgis.com/en/arcmap/10.3/tools/spatial-analyst-toolbox/understanding-euclidean-distance-analysis.htm
Use Near or Generate Near Table, then construct a line based on the angle and distance, then Erase from the line the ROW polygons, then sum the line segments total distance and see if it is 500 feet or less. A Python process to do all this automatically for all the polygons in an area around a selected polygon would be optimal.

http://pro.arcgis.com/en/pro-app/tool-reference/analysis/near.htm

http://pro.arcgis.com/en/pro-app/tool-reference/analysis/generate-near-table.htm

http://pro.arcgis.com/en/pro-app/tool-reference/analysis/erase.htm

Chris Donohue, GISP

deleted-user-kASrD7OWVCDl

Yes Chris, you got it correct. It's not so hard when the ROW is parallel to the property. You could just add the width of the ROW to the buffer. But most of the time roads intersect the buffer at different angles and may not be a uniform width.

Thank you for your suggestions below! I'm starting to think of the problem in new ways.

Cindy

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.