Talk:Draft:Foundation/Local Chapters/United States/Pedestrian Working Group/Schema

Please contribute any comments, suggestions, concerns, etc. on this page.

Example: Tagging Crossings (multi-tier overview)

Tag	Bronze	Silver	Gold	Diamond
highway=*	footway	--	--	--
footway=*	crossing	--	--	--
crossing:markings=*	Are markings present?: yes, or no	In the silver tier, this tag becomes more specific, ex: zebra, or lines, or any other valid value	--	--
crossing:signals=*	Are signals present?: yes, or no	--	--	In the diamond tier, this tag becomes more specific, ex: shared, or dedicated
tactile_paving=*	n/a	Is tactile paving present?: yes no partial (may be used to describe a crossing node where tactile paving is present on one side of the crossing but not the other.)	--	--
surface=*	n/a	Required in the silver tier, example values include: concrete asphalt	--	--
crossing:island=*	n/a	Required in the silver tier.	--	--
button_operated=*	n/a	n/a	Required in the gold tier.	--
traffic_signals:arrow=*	n/a	n/a	Required in the gold tier.	--
traffic_signals:vibration=*	n/a	n/a	Required in the gold tier.	--
traffic_signals:minimap=*	n/a	n/a	Required in the gold tier.	--
traffic_signals:sound=*	n/a	n/a	In the gold tier, this tag becomes more specific: yes no	If acoustic signals are present for finding the button only:traffic_signals:sound=locate If acoustic signals are present for walk permission only: traffic_signals:sound=walk
width=*	n/a	n/a	Required in the gold tier.	--

Does the existing formatting not communicate this effectively? For example:

• Crossing Node and Way Tagging:

crossing:markings=* - Specify presence and type of markings

crossing:markings=no - No markings

crossing:markings=yes - Markings present, type unspecified

crossing:markings=zebra - Zebra markings

crossing:markings=lines - Lines markings

crossing:markings=* - Any other applicable value

-- UW Amy Bordenave (talk) 21:20, 18 February 2025 (UTC)

@UW Amy Bordenave: The table is a work in progress as I clumsily try to port my notes from markdown format. The color coding of the list does support scanning and it is comprehensive. The nesting also communicates the different levels of specificity. The problem I'm trying to solve with the table is visual overwhelm when scanning with a specific tier in mind. When I scan the list, I get visual interference and struggle to mentally filter for the relevant tags. By separating the information on two axes I can scan down for the tag and across for the tier. I can also scan across for the tier and then down for the tags. -- Thompsondt (talk) 21:49, 18 February 2025 (UTC)

@Thompsondt: Makes sense - thanks for the explanation. Some formatting advice - {{Value|yes}} results in yes (to use in place of the markdown "`example`" formatting. :) -- UW Amy Bordenave (talk) 21:54, 18 February 2025 (UTC)

@UW Amy Bordenave: Sounds good. I'm fine with continuing to experiment with it... On formatting, I've got to shift my head back into Wiki mode. I had thought I'd post my notes to my GitHub, but figured I'd pitch it here first. --Thompsondt (talk) 22:55, 18 February 2025 (UTC)