Talk:Tag:service=driveway

Rendering

This should really be rendered the same (or smaller) as service=parking_aisle. Perhaps it shouldn't even be rendered at all, or perhaps not rendered only if it's also access=private.

In the long run, when every house and building will have a driveway mapped, it would make the map too cluttered to read except at the most zoomed in. And when using the map for navigation, seeing every driveway would be distracting. I think a good routing program would only show driveways you're going to use on your route, and hide the rest. BigPeteB 04:31, 22 June 2010 (UTC)

i'm totally with you on that, because i'm someone who maps all those driveways :-) the problem is, that there is no differentiation between short driveways, only a couple meters long (to a garage or into a courtyard) and long driveways, a couple of hundred meters long, leading to rich peoples houses or farms. for now i add an additional tag "driveway=garage" or "driveway=courtyard" to those ways. that would give renderers and routing programs the chance to ignore those ways while still being able to render general service=driveway ways. maybe we should add this additional tags to the wiki page even though it's not heavily used right now. i also started a discussion about that in the german forum: http://forum.openstreetmap.org/viewtopic.php?id=11563 -- Flaimo 16:08, 16 March 2011 (UTC)

I agree with you; when the topic at the German forum has settled down, would you mind posting a summary here for us non-German readers? I've just mapped a few driveways in my community, which you can see here, and I think it might be acceptable to render them at this high of a zoom, but I'm not sure where the cutoff is. -- Joshdoe 00:45, 17 March 2011 (UTC)

Pipestems

How do we differentiate between driveways and pipestems? Pipestems are common in planned residential developments, where a number of houses are located off a pipestem, each with their own driveways. Maintenance of the pipestem is the responsibility of all the homeowners off that particular pipestem. Pipestems aren't named roads, so highway=residential doesn't make sense, but I'm not sure if I should use service=driveway both for the pipestems and for the individual driveways. Fairfax County, Virginia, USA has a short page and photo of a sign here. - Joshdoe 15:01, 19 January 2011 (UTC)

I've started using highway=service, service=driveway, and driveway=pipestem to tag pipestems in my area. This is compatible with existing tagging, can be easily changed to something else if it is warranted. - Joshdoe 17:42, 7 March 2011 (UTC)

Perhaps "shared driveway" might be the better term? A quick search reveals that it's used for places in the US, and it's a common enough term here in the UK. I'd not heard the term "pipestem" for this before today, and Wikipedia thinks it's a kind of tree. Liking the drill-down typology going on here, whatever term we choose. --achadwick 14:31, 9 December 2011 (UTC)

Myself I use service=driveway for both shared and non-shared since with a few exceptions neither go anywhere other then to properties. In practice I only really map ones going to shared garage-blocks, or extensions of tens of metres to residential culs-de-sac that go on to more than one typical detached house but which aren't really public road or turning circle. Out in the countryside, farms have them and so do big posh country houses: those can loop or link two public roads, so it's a good idea to mark them as being driveways, but beyond that I don't think routing algorithms would care very much. --achadwick 14:31, 9 December 2011 (UTC)

I see some usage of service=pipestem as an alternative to service=driveway driveway=pipestem. I think it's better to use service=pipestem and have started using that tag in areas where shared driveways are common. Renderers should give a shared driveway more prominence than most driveways, because in many cases it's essentially an extension of the street rather than a driveway that happens to lead to other driveways. Routers should include shared driveways in guidance instructions, just as they would include alleys, because there remain decision points along the shared driveway. – Minh Nguyễn (talk, contribs) 01:15, 16 September 2018 (UTC)

From this description it seems that pipestems are closer to highway=residential+noname=yes than to highway=service Mateusz Konieczny (talk) 06:41, 17 September 2018 (UTC)

In many newer subdivisions, shared driveways are indistinguishable from the residential roads they branch off of, except for (usually) being narrower and (usually) lacking a curb or sidewalk. The only physical characteristic that seems to reliably apply to shared driveways is that all the mailboxes are colocated where the shared driveway meets the main street. Thus any house along the shared driveway has the main street’s street address. It’s this lack of dedicated addresses, I think, that suggests the shared driveway should be tagged highway=service but not service=driveway. –Minh Nguyễn ^💬 00:55, 6 January 2019 (UTC)

My observation in my local area is that Amazon's army of mappers tag all pipestems as just highway=service. Just because they tag a lot of things "wrong" (imo) doesn't mean the wiki should promote that scheme based on usage. We shouldn't tag it this way because we like the current rendering. If it's a pipestem it should be tagged as a pipestem. service=pipestem would be nice, but I think service=driveway + driveway=pipestem has been used since it would still be understood or rendered better even if an app didn't recognize pipestems.--Rassilon (talk) 16:39, 29 November 2019 (UTC)

I agree that it is better to use service=pipestem or even highway=residential for a shared road which leads to several residential properties. The idea of a driveway in British English is a private service road which leads to a single residence. While the word "driveway" has a much broader meaning in North American English, we should stick to the original definition. --Jeisenbe (talk) 19:30, 17 May 2020 (UTC)

Why access=private?

Isn't a driveway typically a private road? I think we should only tag what we see. If a house owner adds a sign "do not enter/private road" a access tag is needed. But if we add access tags if no signs are exists, we can not say if there is a sign or not by only looking into OSM-data. It's the same like motorways where we don't add bicycle=no.
The access will make editin or routing to complicated. If the first user adds the driveway, the second who draw the foot- or cycleway must split EVERY driveway to delete the access tags form the small part between road and cycleway. Routing Example --HalverHahn (talk) 14:48, 17 August 2015 (UTC)

• My feeling is that driveways should be tagged with access=destination as service workers and unannounced visitors are generally allowed access without obtaining prior permission. They could be subsequently chased from the properly as unwanted, but unless posted as 'private property, keep out, no permission to be assumed' or something of the same gist (such as a locked gate), at least in the United States it is generally assumed that if your intention is to reach the private residence as a destination, using the driveway is permitted. --Ceyockey (talk) 02:37, 30 August 2016 (UTC)
• Please dont tag/map stuff thats not there. Its in in Good Practices that we only map stuff that is there and verifyable. Any access=* on a driveway which does not correspond to a explicit signage of the owner is broken and just "felt access restriction" not "factual access restriction" Flohoff (talk) 18:08, 23 May 2018 (UTC)
  • It may depend on a location. At least in Poland closed gate or something similar making clear that it is a private property requires no explicit signage Mateusz Konieczny (talk) 06:39, 17 September 2018 (UTC)

Removal on restrictions on service=driveway tagging

There has been a discussion on not tagging service ways as driveway within a parking lot. However, this contradicts OSM policies on the following points.--JaLooNz (talk) 13:22, 17 July 2020 (UTC)

• There is no mandate on how a user chooses to tag in any manner, as long as it is verifiable on-the-ground.
• It contradicts the general rule that secondary tags adds additional details, and forces user to tag without secondary tags. It has never been OSM practice to tell users not to do things in a particular manner.
• This "rule" is applied in various regions, but not globally. The change un-intentionally forces regional preferences into a global "standard", which also is not OSM practice.
• In fact, users should be encouraged to categorise the service way type where possible, and not use the generic classification.

But service=driveway is for driveways: small service ways which access a single house, not for parking aisles or access aisles. If you would like a new value of service=* to tag the main services ways entering parking lots, it's certainly possible to do so (perhaps service=parking?), but you should not mis-use an existing tag. --Jeisenbe (talk) 05:21, 20 July 2020 (UTC)

parking alone seems easy to confuse with parking aisles... I have no good ideas, service=main_parking_road is ugly. Mateusz Konieczny (talk) 07:32, 20 July 2020 (UTC)

I am ok with new definitions, but the restrictions have to go as it contradicts various general rules and is not a standard globally.--JaLooNz (talk) 14:57, 20 July 2020 (UTC)

"This "rule" is applied in various regions, but not globally." - where it is not used and people use service=driveway for main roads on parkings? Mateusz Konieczny (talk) 07:32, 20 July 2020 (UTC)

Various legal definitions differ from the definition "small service ways which access a single house, not for parking aisles or access aisles", examples include US-CA statures, and others define driveway as "point access linking to lots from public way". Just from these examples along, it tells us definitely that the tagging convention even for access routes to parking bays do meet the definition of driveway. However, as an exception, you may want to choose to tag your region in whatever way you like as long as your rules are not imposed on others.--JaLooNz (talk) 14:57, 20 July 2020 (UTC)