Been using the highway=service + driveway=pipestem, in fact made a two click custom preset for JOSM (tick access=private when needed as many are signed at single entrance), since about the driveway2 storm (in a teacup).
Surely the main objection to service=driveway, driveway=… is that a way definitively leading to multiple properties does not qualify as being a way leading to a single property.
Whatever this is called, it’s clearly a subtag of service defining what type of service road this is. Currently blank in 10000s of cases.
Pipestem means nothing to me, except the stem of a pipe, or by extension something the shape of a stem of a pipe, whatever that is.
Clearly not settled. The discussion referred to links to here. What is the proposed rendering? As thin and quickly disappearing on zoom out as unqualified driveway? Or exceptionally for driveway, fatter and persisting to slightly higher zooms like all other service?
That is decision to be taken by map styles, I would do something in the middle of those stylings.
If map style designer has preference both schemes enable them to choose.
Admittedly, choosing one has influence which default current map styles get - but I would not let it influence me in choosing which mapping scheme is better (as both are digestible by data consumers).
If someone would start proposal process for a yet another tagging scheme, maybe with more intuitive tag, I would wait for it’s conclusion or abandonment.
Regardless of linguistics, or OSM and wiki history. it would be more specific and useful to use another service= for shared roads or sections, and have individual homes connected with =driveway
I’ve mapped thousands of shared driveways since my very first edit in 2008. I’ve also lived on a shared driveway – but not a pipestem. These days, I prefer service=shared_driveway, which is yet another contender for this concept.
For years, I routinely deleted driveways because they often came in from the TIGER import as misleading highway=residential, but shared driveways were different. I did go along with leaving them as simply highway=service without service=*, but the service=driveway2 situation convinced me that we need to further develop the service=* classification scheme.
I disagree with refining shared driveways as a type of service=driveway, because we use that tag for a specific purpose: to indicate the least important roads in the road network. A shared driveway has decision points along it, leading to actual driveways. Data consumers routinely ignore driveways under a variety of circumstances, but shared driveways are different, a halfway state between streets and driveways that should not be ignored to the same degree:
A renderer could hide driveways at even a high zoom level to avoid repetitive clutter, but shared driveways are critical to understanding the spatial structure of the neighborhood, as they often reach houses in recesses that the user might mistakenly associate with a different street.
A router would typically stop at the foot of a driveway to avoid insulting the user’s intelligence, but this isn’t good enough for a shared driveway, because the user needs to know which driveway to turn into after driving down the shared driveway.
A geocoder could ignore the name of a driveway when corroborating a building’s address. Most driveways and shared driveways are completely anonymous, but to the extent they have names, the name of a driveway is more likely to be a vanity name, just a sign the owner put up to be cute. This isn’t so much the case with a shared driveway, which would require all the abutters or the homeowners’ association to agree on a name. In that sense, it more closely resembles a standard residential street, even if it doesn’t look like one.
I’ve also soured on service=pipestem because the term is too specific. Technically, a pipestem is a kind of shared driveway that is surrounded by flag lots, whereas many shared driveways simply provide access to all the abutters. I’ve witnessed mappers “correct” service=pipestem to service=residential or service=driveway because it’s such an obscure, bizarre-sounding term. If this is a distinction anyone cares to make, I would support refining a shared driveway as a pipestem, something like service=shared_drivewayshared_driveway=pipestem. But service=shared_driveway captures the more important, more verifiable distinction.
This is how I tag shared driveways. I only tag the final portion leading to a single property as service=driveway. Or the whole thing when it’s an individual driveway. It feels natural to me that the shared portion be tagged a bit differently as it has a slightly higher importance in the transportation network than the final destination purpose that an individual driveway serves.
If a distinct tag is needed for shared driveways then service=pipestem seems fine although it’s not a term I’m familiar with even as a native English speaker. I’d probably just go with something like service=shared_driveway.
I thought they were the same thing, we’ve documented them as the same thing at Tag:service=driveway - OpenStreetMap Wiki . What’s a pipestem but not a shared driveway? ah I see you’ve provided a description. I’ve never heard of pipestream before and so I suspect it’s a specialised US specific term.
The way I saw it was service=driveway is for unspecified driveway, it could be a single residence driveway or a shared multiple-residence driveway, so driveway=pipestream for shared or driveway=single for single.
The alternative view is what you suggest that service=driveway already means single residence only, so in that case service=shared_driveway would be better.
Mapping these manually (without a preset) is tedious when we need to use 3 different tags, so I think service=shared_driveway is probably better. Easier to tag and avoids the issue that most of the world won’t understand what “pipestem” means but “Shared Driveway” is much more universally understood.
The issue is that driveway=pipesteam has 11k uses and service=shared_driveway only has 800, but if there’s consensus I’m happy to change all the ones I tagged to shared_driveway.
I am with Minh here, service=driveway is a specific driveway (one that leads to a single property, maybe in exceptions also 2, but not “multiple”, if it leads to multiple properties, it is not a service=driveway in osm, typical tagging is highway=service and no service tag)
Would you be okay with service=shared_driveway for driveways that lead to multiple properties? An issue with only using highway=service without a service=* tag is that highway=service is quite broad and used for many different kinds of roads, so without a service=* tag it’s unclear what kind of service road it is.
It’s a driveway (ie. a way that branches off the public road to provide access to a residence) that is shared or used by multiple residences, instead of just a single residence.
