In the following map, I have:

  • A line / road layer
  • A parcel / lot layer

The Task:

  • Find and count the list of lots adjacent to the road with their types (parcel_type is a field in the parcel layer)
  • The data is both stored as shp files and as a postgis tables

The Issues:

  • The line layer and the lot layer do not intersect i.e. the lot layer has the right of way specified in it of the actual width of the road; whereas, the road layer is just a line layer.
  • a parcel might be adjacent to a road on more than one location. think of it as a large lot, with a lot within it. or lots with double frontages. (there is an example of such a lot in the picture below
  • This has to be automated on all roads of the study area (roughly 20,000 segments)

Image Sample alt text

  • Sorry, can you clarify what you mean by "the lot layer has the right of way specified in it of the actual width of the road"? You have information about the width of a road inside the lot layer? What if multiple roads run past one lot? – underdark Aug 11 '10 at 23:16
  • @undermark, if you see in the picture, the white space where the road line goes through is not defined in the parcel layer. it is a representation of "as built" – dassouki Aug 11 '10 at 23:22
  • Is an arcobjects based command written for arcmap an acceptable solution? If it is, it might provide some performance advantages. – Kirk Kuykendall Aug 12 '10 at 15:28
  • @Kirk Kuykendall - I would think so. In all reality, this is a command that I'll probably do once a year (when our plot maps get updated) – dassouki Aug 12 '10 at 15:41
  • I am working on a similar project but it is the other way around. I need to select the roads adjacent to the property. My problem is all the roads are located a different distance apart to buffering doesn't work. Any suggestions? – user51740 May 7 '15 at 16:04

This is a PostGIS query that I just tried on our data set so it may work for what you need, and I'm not much of a PostGIS expert yet so I'm 100% sure it could be done better but here goes anyway:

select DISTINCT ON (p."land_no") a."Road_asset_ID", p."land_no", p."SP_GEOMETRY"
from "roads_old_centre_lines" a
INNER JOIN "Property" p on st_intersects(st_buffer(a."SP_GEOMETRY",50), p."SP_GEOMETRY") 
where a."Road_asset_ID" = 1500
   OR a."Road_asset_ID" = 1502

It should create a buffer around the road and select the property geometry that intersects the buffer, the property land no, and the road id that was used for the buffer. It should also only select one property using DISTINCT ON (p."land_no") even if the property touches two road buffers.

This query uses a buffer of 50m but you will just need to adjust that so that cover the road reserve area.

This is what the result in QGIS looks like:

alt text

EDIT: This seems to do the count right, it's a bit slow due to having to do two runs but I'm sure someone might be able to optimize it.

SELECT road, Count(land_no) FROM 
    (select DISTINCT ON (p."land_no") a."Road_asset_ID" as road, p.land_no ,p."SP_GEOMETRY"
    from "roads_old_centre_lines" a
    INNER JOIN "Property" p on st_intersects(st_buffer(a."SP_GEOMETRY",50), p."SP_GEOMETRY") 
    where a."Road_asset_ID" = 1500 OR a."Road_asset_ID" = 1502) as Test
  • I really need to freshen up on my SQL, thanks a lot Nathan – dassouki Aug 12 '10 at 13:49
  • A nice plus of the PostGIS query is that you can get an answer without having to serialize out two data sets to disk and then do a query. – DavidF Aug 12 '10 at 15:03
  • The only problem I see in using a buffer is that at the end of the roads, parcels located at the opposite side of the crossing might also intersect the buffer area. – underdark Aug 12 '10 at 15:37
  • @underdark true, I guess the OP would have to test it and see if that is a problem. – Nathan W Aug 13 '10 at 0:30

Create a buffer for each street centerline segment, wider than the standard ROW. Make sure that the buffer has the name of the street as an attribute. Then intersect your buffer layer with your parcel layer. You will then have a list of all of the street names, along with any parcel ids that intersected that particular buffer. That should also cover the double frontages. Once you have the workflow down, it should be easy to set it up in ModelBuilder.


With an ArcInfo level license, you can use the Buffer command with a "FLAT" end type, which allow you to get around the problem mentioned by @underdark. As @Zachary mentioned, this is a pretty easy model to create. Using the "make feature layer" will allow you to define a query (ie- Main St), and buffer the selected layer to a temp in memory layer (in_memory\road_buffer) using a distance (set as a parameter to make interactive), and use the in memory buffer to select taxlots within the chosen distance (select features by location). See below:

alt text

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.