Analyze Tag Usage Frequency

[droogmic]

It would be good to have an ordered list of tags (key + val) used in ways, such that we can prioritize support.
We can then make milestones tracking our coverage of all tags used in >1% of ways, then 0.1% of ways, etc.

e.g. https://taginfo.openstreetmap.org/tags/oneway=yes is used in 1.77% of ways.

[droogmic]

https://taginfo.openstreetmap.org/keys/highway#combinations

> 1%

• name
• surface
• oneway
• maxspeed
• lanes
• access
• ref
• tracktype
• lit
• bicycle
• foot
• bridge
• footway
• sidewalk
• smoothness

> 0.1%

• public_transport
• width
• bus
• motor_vehicle

[dabreegster]

Should we exclude name and ref from this list? I can't see a very direct reason they'd influence current osm2lanes output, or a reason why to plumb them along in the output.

[droogmic]

I was thinking that client using this library may just want to say "tell me about way 12345". It's very little effort on our side and may remove the need to parse tags on their side. We also know that name and ref apply to all lanes.

…

On Sun, 8 May 2022, 13:49 Dustin Carlino, ***@***.***> wrote: Should we exclude name and ref from this list? I can't see a very direct reason they'd influence current osm2lanes output, or a reason why to plumb them along in the output. — Reply to this email directly, view it on GitHub <#175 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACEL2Z73RFK6DPR4DYIKOBDVI6S53ANCNFSM5U2BTHQQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dabreegster]

Similarly, lit and bridge and other attributes are common to the entire road. Maybe we should plumb through things like this, or maybe we should hand people the Tags too? Otherwise it could be scope creep to have fields in the struct to represent everything

[droogmic]

We could process the relevant tags like we do now, passthrough known tags like name and ref, and then the remaining ones are in a "remainder" Tags object. This solves another problem we have: how to have the website's roundtrip system output tags you can actually paste back into osm without losing information. We could also use an input config decide if the output `Tags` should have all tags or just the unprocessed remainders.

…

On Sun, 8 May 2022, 14:24 Dustin Carlino, ***@***.***> wrote: Similarly, lit and bridge and other attributes are common to the entire road. Maybe we should plumb through things like this, or maybe we should hand people the Tags too? Otherwise it could be scope creep to have fields in the struct to represent everything — Reply to this email directly, view it on GitHub <#175 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACEL2Z72LBAUN7QDEDBKURDVI6XABANCNFSM5U2BTHQQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[BudgieInWA]

What a great idea! I have been thinking to myself "is tag X actually combined with tag Y in the wild, or can we skip support for the combo". The taginfo combinations tab is a great resource, and I've been learning how to use OverpassQL properly, to answer questions like that too.