The purpose of this issue is to:
I would personally find it nice if the surface quest also included service roads, since it already does include even smaller highway types like track.
The reason why the service road is excluded is because as a road of lowest priority (generally, but for routers anyway), it will usually only appear in a navigation route at the very start or very end. This is why the surface of a service road is almost irrelevant. In any case, the information value is really low and since in some places, every single private driveway is mapped (but sometimes missing access=private), it generates a lot of spam and possibly brings the surveyor into awkward or dangerous situations when the app incites them to linger on private property.
The only case where surface for service roads is likely to be useful is for service roads with cycling or walking or hiking route. In all this cases you are likely to be interested what kind of surface is there and it indicated that this service road is not just dead-end property access.
But adding this clause to query would increase query run time, for an insignificant benefit.
Actually thinking about my neighbourhood i think westnordost is correct here, it would be too spammy if someone else would get there and would try to tag something. If i really want to tag this, i can still do it cia JOSM or on the smartphone with vespucci.
Most helpful comment
The reason why the service road is excluded is because as a road of lowest priority (generally, but for routers anyway), it will usually only appear in a navigation route at the very start or very end. This is why the surface of a service road is almost irrelevant. In any case, the information value is really low and since in some places, every single private driveway is mapped (but sometimes missing
access=private), it generates a lot of spam and possibly brings the surveyor into awkward or dangerous situations when the app incites them to linger on private property.