Exclude residential roads from residential area?

I would not think so? Not only “residential” roads are a landuse on their own, all public roads are a landuse on their own. “houses”, “apartment blocks”, “driveways”, “gardens” are all on plots used for residential purposes, aren’t they? How should they not fit under the “residential” use?

1 Like

(Hi from The Netherlands) In Brisbane the last method tends to be used. Main disadvantage I see is that it results in a checkerboard pattern of individual parcel groups being either ‘done’ or not. The term ‘landuse’ also suggests a more broad concept than a single individual block and a residential road is by the name part of a residential area.

I say they cannot. Consumers could at most estimate a road width and sidewalk widths and assume that adjacent properties start right beyond the sidewalk, but there will be lots of situations where you would not get it right with these heuristics. I believe part of the dispute is about the term “residential area”, or “residential landuse”, the former can be seen as a part of a settlement, a quarter or neighbourhood with predominating residential use, and it could also be seen as an area with predominant residential use (but on a different scale, block related). The terms used in the wiki to describe what “landuse” means are approximate and allow for both kind of interpretations. Landuse refinement in many areas somehow stopped at the detail level of 2007, where many motorways in my country still had a oneway=no tag because a single way represented both directions. People do not use “landuse” for routing, and there are buildings for detailed city mapping, so even if the landuse if completely off, it doesn’t matter to many usecases, that’s why we still are where we are.

I believe it is more complicated to do reasonable generalization (and generalization always has to reflect the scale for which it is intended, so in the context of OSM it seems inherently impossible to do it well) than it is to simply map what is there (i.e. landuse polygons for those areas where the landuse actually is. Nobody lives in a church, a kindergarten, in a lake, in a public park, in a school, on a public square or similar (or maybe someone exceptionally does, but it is not the dominant use). For the mapper, it is more complicated to continue the currently still predominant style than it is to give more information by being more detailed. It also helps to prevent errors by connecting roads to landuse polygons, when the landuse polygons don’t cross the highways.

I agree that driveways should not cut out of residential areas, and I have not seen such suggestion, nor would it be logical with even more detailed landuse mapping, because these driveways are seen as part of the residential property, unlike the public road.

Anyway, we are moving, very slowly but I can notice it is happening, towards a more detailed landuse mapping of built up areas, so inevitably we will sooner or later arrive at (potentially, where necessary) plot-sized detail level.

There is no strict rule. Drawing larger areas and include the area of reads inbetween is perfectly okay.

I do aswell typically exclude roads, sidewalks, cycleways etc as i guess in a couple of years we will also map areas for “mobility” as seperate landuses. There have been a lot of experiments with making highway areas (additionally to the line needed for routing).

So one could envision a world where we have landuses for highways, and then a tagging scheme for the broken down individual spaces for pedestrians, kerbs, cycleway, carriageways etc.

So excluding them now may be the way forward. But i wouldnt remap everything to do so, neither would i grow the existing landuses.

Be relaxed.


I use all three, but I usually leave the residentials mapped by others alone.
I never see other data use of residential areas than the “residential” colouring on maps. I can think of other uses, but are there actual implementations?

Recently discussed in Croatian community:

The original poster, @Vedran_V, complained about someone’s “patchy” mapping style which complicated his analysis, although he did not specify the exact use case. Perhaps he could clarify.

Mapping exact landuses, encourages more fine-grained specification. Especially when the type of landuse is generally small like religious and education landuses.

On the landuse and landcover map you can get more precise numbers on the specific landuse percentages.



I don’t see that including residential roads in residential landuse prevents this, area:highway or whatever tags are settled on can still be used. Just as we can have detailed mapping of buildings within a landuse polygon, can’t we also have detailed mapping of road areas?


I politely disagree with this and see streets in residential areas as part of landuse=residential. There’s no benefit to turning OSM into a pseudo-parcel map. Mapping landuse as zoning is more practical.

Also, roads are not landuse areas IMO. Roads are roads, and there’s no benefit to mapping them a second time with landuse tags.


The whole point of landuse residential is to provide a generalised indication of the most prominent usage. If you don’t use it for that it doesn’t make any sense at all as all the other bits are aera:highway, leisure=garden, building outlines and so on.



  • | - |

I politely disagree with this and see streets in residential areas as part of landuse=residential. There’s no benefit to turning OSM into a pseudo-parcel map. Mapping landuse as zoning is more practical.

I don’t know how zoning maps are drawn and at which scale, and whether there are different scales involved, but I know from Germany that landuse is done on parcels (the authorities prescribe landuse at least at parcel granularity but ocassionally also finer grained) hence when we go out surveying, we find the reflection of these prescriptions.

Also, roads are not landuse areas IMO. Roads are roads, and there’s no benefit to mapping them a second time with landuse tags.

then you should not include them (if they are not considered “landuse” in your book). I agree that drawing them is not what seems most appealing to do with my time either, so I consider them implicit (what also can be done with roads drawn as lines, but is more approximate as having the border explicitly drawn, but the legal road areas omitted)

A variant of one of these methods draws the landuse area to correspond to a coherent planned development, with the name of this development in name. This isn’t quite the same as mapping a place or boundary; rather, it’s an alternative way to indicate a built-up area’s structure based on planned developments.

For better or worse, this style departs somewhat from the classical concept of land use in urban planning. But at this point, if we must map an apartment complex as a coherent landuse=residential residential=apartments and a mobile home park as a coherent landuse=residential residential=trailer_park, then for consistency’s sake, we must also map a housing estate (aka subdivision or master-planned community) as a landuse=residential as well.

The caveat, of course, is that not every region of the world is developed in such a rigid manner.

All this to say that the housing estate obviously includes the public streets that serve (and mostly dead end within) the housing estate. You might have already passed an entrance sign by the time you reach one of these streets. If you want to micromap to the point that each of these streets has a landuse=highway around it and the lush front lawns are blanketed in landuse=grass, by all means please do so. But it doesn’t have to result in cutting up the named residential landuse area, because our data model allows areas to overlap.


this is one part, and the other is preservation and transformation. In Europe at least, it isn’t en vogue any more to just tear down what was there in order to make space for a new development from scratch, the cities, particularly the central areas, are the result of hundreds and sometimes thousands of years of development. Also not rarely, (urban (re)development) plans are not executed completely because halfway the leading ideology changes. When the sixties generally subordinated everything to the requirements of automobilized citizens, these plans have been criticized at least since 1970, initially by some scientists and with some delay the criticism has sometimes been echoed by society and politics. Of course this is not the same everywhere, urban development is generally subject to local culture and traditions, but what is common is that as a result of urban transformations for longer periods of time the landuse is often less homogeneous. What we are mapping with landuse is the current landuse and not the currently prescribed landuse, so even if there is a zoning plan and current zoning seems homogeneous there may sometimes be outliers due to former use (or due to not respecting what is legally prescribed)

To be clear, I wasn’t referring to zoning, but indeed the housing estates I’m referring to are very often a product of car culture. That said, some are infill developments, such as Hawthorn Woods, which packs nine single-family houses on what was once a single plot. Or Orchard Trail, which consists of 29 houses on a single street where there was once a private swim center. Despite its small size, there’s a prominent entrance sign. This subdivision isn’t considered one of the city’s neighborhoods in the classic sense of that term, but people do use the name for various purposes.

It all goes back to a point I made earlier when we similarly debated the degree of precision to use with landuse=industrial:

When landuse=* is used in this manner, cutting out the street(s) would be not only pedantic but also inaccurate. But this doesn’t prevent someone from also mapping an overlapping landuse=highway, landuse=grass, or even natural=wood for the few surviving trees that they named the subdivision after.

1 Like

I usually draw landuse=residential areas with a shared node with other landuse or area based tags. The lines are precisely overlayed (not overlapped). that way it looks good for the render result.

I’ve always mapped with method three, because I once read this was the optimum, but after having read this thread, I think I’ll map with method 2 from now on, i.e. the blocks between main roads only, unless local consensus seems to be different.

In general, I think manageable sizes should be used, so a few blocks in places where the landuse is homogenous or a small neighbourhood with a shared identity. In general, if the landuse crosses the road in the real world, e.g. shops on both sides of a road, so should the polygon. Covering entire towns or city quarters with a single polyogn seems problematic, as there is likely to be other landuses.

Important Do NOT attach the edges of landuses to highways, railways, etc.as those often have relations and later editing can become problematic. Important

In Ireland, named housing estates are exceptionally common. This can take the form of X Road, X Avenue, X Way, etc. as here: Way: ‪Suncroft‬ (‪123211970‬) | OpenStreetMap

Alternatively, there are larger estates that might be X Estate, but the roads are Y Road, Z Avenue, etc. Way: ‪Courtlands Estate‬ (‪132713513‬) | OpenStreetMap

Dublin is a ‘city of villages’ so neighbourhood retail / services areas also carry the names of the original village: Way: ‪Terenure Village‬ (‪61789435‬) | OpenStreetMap

In places, landuse=* has been tied to place=* and wikidata=*, e.g. Way: ‪East Wall‬ (‪33492190‬) | OpenStreetMap

Please don’t map landuse, then. Including other land uses in your landuse polygons makes maintainability a gigantic pain in the butt. No data is better than wrong data.

I think I’m doing it right and you’re doing it wrong, so no.

I agree on @Friendly_Ghost here. A street is not per se its own landuse. There is a reason why there is no landuse=highways or the like. Street areas mapping has always been experimental and in area:highway like tags.


I agree that using streets to simplify/split landuses is a good thing to do because large/huge landuses tend to break a lot more often, so a street is a natural possibility to split.

landuse is not something for micromapping and stuff like “flowerbed” has been a huge mistake. Landuse is for larger area, zoning type mapping.


1 Like