Question: What is the potential use of this data? Obviously you could render it but without streets being mapped as areas, the rendering is likely to look rather odd. It seems like it would be more useful to put the effort of mapping these things into mapping their meaning in the form of lanes tags and turn restriction relations. These are tags that are already being used by OSM based tools to improve routing. --ToeBee (talk)
- This is not reserved for highway markings. I think about bus stops for instance. Such tag can be used by road maintenance services for instance. --Pieren (talk) 15:39, 22 August 2014 (UTC)
- I don't think it would look odd. Given road type, width and number of lanes you already can make street markings quite convincing. The only difficulty is that the road width would be rendered only at higher zoom levels --Vanuan (talk) 10:22, 24 September 2014 (UTC)
- I second the need for this information and would add that as autonomous vehicles (AV) become more common, the need for this data will only grow. Pedestrian crossings are particularly dangerous and sometimes road markings fade, rendering vision obsolete. A digitization of this information would help prevent lane incursion and late stops. --pflier (talk)
Integration with the road network
I’ve started using this tag to indicate the positions of stop lines along a road. Contrary to the guidance given on this page, I’ve tagged nodes along the road way with road_marking=solid_stop_line (or road_marking:forward=solid_stop_line or road_marking:lanes=* in the case of a staggered stop line). For stop line data to be most useful, it needs to be connected to the road way. As the road way itself is already an abstraction of the road surface, it would be better to tag stop lines on the road way itself. I think I’d only start mapping stop lines as separate ways once we start generally mapping roads as areas.
As for the other road markings, I haven't felt a strong need to use other tags like road_marking=solid_lane_divider, because so far that's already adequately expressed by tags such as change:lanes=* and overtaking=*. Such tags are more readily consumed by data consumers such as routers.