I agree with your definition for marker: marker=<marker nature> The node corresponds to a marker seen on ground
but then the actual values that you propose do not (or only implicitly) refer to the marker but to the "thing" the marker refers to: "pipeline" - Indicate that a pipeline is buried next to the marker, possibly underground and not mandatorly righly below "power_cable" - A power cable is installed next to the marker, possibly underground and not mandatorly righly below "telecom_cable" - A telecommunication cable is installed next to the marker, possibly underground and not mandatorly righly below "fire_hydrant" - A fire hydrant is available next to the marker, possibily underground and not mandatorly rightly below I would rather have expected a generic description of the marker, like marker= post cone sign ... aerial_marker (maybe this should be a property, not a type? This seems to be a quite interesting property for our context) properties which might be useful for markers: dome_marker=yes/no (or: marker_top=flat/dome/...) placement(?)=soil / street If this is for a _utility_ marker only, you should consider using a more specific key name like "utility_marker". I could imagine defining a generic "marker" tag for utility markers but including also other markers, which may be similar by their physical appearance, although for many of them, e.g. survey points, milestones and boundary markers, we already have established different tagging and will likely not change this. Cheers, Martin
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
