Standardization of OSM tags

[KHobbs3]

Hi!

I'm wondering if someone could direct me to any scripts/documentation on the standardization protocol for OSM tags. I'm comparing data between OSM and Overture Maps and notice some OSM tags are absent in Overture (for e.g., in a sample extract of the same geographic region, OSM's maxspeed and hov tags are present but OM's restrictions:speedLimits:maxSpeed and lanes:restrictions:access:allowed:when:mode:hov are not) and would like to know if this was due to identified inaccuracies in OSM tagging, conservative standardizations, or a mistake I'm making!

I also visually observed some road segments in OSM, primarily ways in residential areas or traversing greenspaces, that are not present in OM.

Thanks in advance!

[larsskaug]

I'm not qualified to answer your question, but you should probably check if the latest version of Overture still has the discrepancies you are pointing to. The first beta version was published in April and your comment seems to be from February.

[brad-richardson]

Yes, we've made a number of improvements since February. There are cases where we'll drop this data if we don't consider it parseable but there may have been missed cases.

[brad-richardson]

I also visually observed some road segments in OSM, primarily ways in residential areas or traversing greenspaces, that are not present in OM.

Could you point me to a specific example of this? There is a small time gap between OSM and our Overture data which may explain this issue if the way was deleted, but it's also possible something is being misclassified.