<div dir="ltr"><div>One of the best data sources for mapping in the U.S. has been the <a href="http://fragis.fra.dot.gov/GISFRASafety/">Federal Railroad Administration's GIS Data</a>; and the most expansive data is the level crossing inventory. There's a few things in there that are documented that don't have tags yet, and I think they are useful. They are: </div><ul><li>key=crossing:cantilever</li><ul><li>Values: yes/no </li><li>Description: Metal cantilever that extends over the road, and usually has a crossbuck/saltire and/or flashing lights mounted to it.</li></ul><li>key=crossing:contact:emergency</li><ul><li>Values: <string></li><li>Description: A designated contact number for contacting emergency operators.</li></ul><li>key=crossing:contact:railroad</li><ul><li>Values: <string></li><li>Description: A designated contact number for contacting the railroad. </li></ul><li>key=crossing:contact:state </li><ul><li>Values: <string></li><li>Description: A designated contact number for contacting state government. </li></ul><li>key=crossing:quiet_zone</li><ul><li>Values: yes/no</li><li>Description: Locomotive engineers/operators are not to sound the horn at these crossings. There is often some sort of additional sound-producing device at these crossings. </li><li><a href="http://www.fra.dot.gov/Page/P0689">Federal Railroad Administration page</a></li></ul><li>key=crossing:traffic_signal</li><ul><li>Values: control/interconnected/no </li><li>Description: In Urban environments, highway intersections and level crossings are often adjacent to each other and therefore the level crossing is integrated into the traffic signal controller. "control" is to indicate a crossing where traffic signals replace the typical alternating crossing lights and other standard protections. "interconnected" is when the traffic controller program will alter from typical operation when a train is approaching. It could be a red light for traffic in that direction, a temporary no right/left turn restriction, or a number of other scenarios. </li></ul><li>key=crossing:wigwag</li><ul><li>Values: yes/no</li><li>Description: Old type of crossing protection consisting of a pendulum swinging back and forth. There's approximately 100 left in service in the U.S. </li><li><a href="https://en.wikipedia.org/wiki/Wigwag_%28railroad%29">Wikipedia page</a></li></ul></ul>The inventory reports also list the count of crossing lights, crossbucks/saltires, and other such warning devices. I am unsure if these would be useful enough to tag, however. In addition, the integration of traffic signals at highway intersections with level crossings leads to a problem of grouping together elements of the entire junction, or even just the level crossing with itself. This is a problem with highway junctions in general. I think it could be a good idea to co-opt the complex junction relation from <a href="https://wiki.openstreetmap.org/wiki/Proposed_features/Junction">Proposed_features/Junction</a>. This would also allow level crossings of multiple tracks to be grouped together. They way I would structure it is:<ul><li>Relation tagging: </li><ul><li>key=type=junction</li><li>key=junction=level_crossing</li><li>key=ref:fra_crossing</li><ul><li>Value: <string></li><li>Note: While not an approved value, this is the value I have been using for marking the ID used in the FRA's Crossing Inventory.</li></ul><li>Any of the tags used for the level_crossing node, as many of them are better applied to the relation than the node.</li></ul><li>Relation roles:</li><ul><li>(blank)</li><ul><li>Used on: Anything else</li><li>Description: Used to include anything else that isn't listed below. The only thing I can think of that could be is the segment of track that is embedded in the roadway. I have tagged this in the past as key=embedded=yes/pavement/metal/wood/plastic (plastic includes rubber). The highway section between stop lines/traffic signals could be added as well, as I suppose those are part of the junction as well. </li></ul><li>level_crossing </li><ul><li>Occurance: 1 or more. </li><li>Used on: key=railway=level_crossing or key=railway=crossing </li><li>Description: This is where the railway track intersects a highway or pedestrian path. </li></ul><li>traffic_signal </li><ul><li>Occurance: 0 or more </li><li>Used on: highway=traffic_signals </li><li>Description: Any traffic signals that are part of this junction. This assumes that the traffic_signal is not mapped at the intersection of roadways. </li></ul><li>stop_line</li><ul><li>Occurance: 0 or More, mutually exclusive with traffic_signal </li><li>Used on: Nodes tagged with key=highway=stop_line </li><li>Description: This is where vehicles are to come to a stop, in cases where a traffic signal would not otherwise be tagged at this position. </li></ul><li>location_hint</li><ul><li>Occurance: Optionally one. Mutually exclusive with.</li><li>Used on: Any node. </li><li>Description: A hint to a renderer as to where a good place to put the the junction number or name on the map. </li></ul></ul></ul>Anyways, just seeing what other thoughts you have. I cannot say that all of the terminology used in tags or roles are optimal. </div>