I see a tendency to equip more and more local secondary and tertiary highways with either an adjacent bike path or an (advisory) bike lane = fietssuggestiestrook, cycleway=shared_lane in OSM speak. This isn’t always reflected in OSM, yet. I’ve fixed some that I’ve come across, but I suspect there’s many more.
Because I find that they matter for bicycle routing, I’ll try and survey those that I can access easily, in province Groningen. Mapillary will help reduce my mileage. The idea is to tag all secondary and tertiary highways outside of town (buiten de bebouwde kom) with a cycleway tag (cycleway=no if none is present), except if they’re tagged bicycle=no or bicycle=use_sidepath. While I’m at it, I’ll also set mofa and moped tags, surface, and where surveyed locally: smoothness. Things like weight limits, updated speed limits and so on will be by-catch.
Why secondary and tertiary? Primary highways and up don’t come with bike lanes in this country. They typically come with adjacent bike tracks, which are typically mapped already. “Unclassified” highways, on the other hand, are typically too small for bike lanes. This leaves us with secondary and tertiary.
Why out of town? Mostly because I prefer cycling in the nature :) But also because I have the impression that highways in town get a good amount of attention from my fellow mappers, already (which is great!). That’s less true ‘op het platteland.’ That’s where I come in.
Here’s an Overpass query to identify targets:
area[admin_level=4]["name"="Groningen"][boundary=administrative]->.searchArea; // specify: within province (admin_level=4)
way[highway ~ '^terti'][!cycleway][!bicycle][maxspeed~'0'](area.searchArea);
way[highway ~ '^terti'][!cycleway][bicycle=yes][maxspeed~'0'](area.searchArea);
(change terti –> seconda or similar for secondary highways, of course).
Note that I’m relying on the maxspeed tag here to exclude highways within town. This isn’t fool-proof and notably excludes highways for which maxspeed isn’t set. You would want to craft your query much more carefully for, say, an automated edit. Since that’s not what I’m planning, I can live with a certain error margin. I’ll sort out the rest later. Low-hanging fruit comes first.