Proposal:Shoefiti
| Shoefiti | |
|---|---|
| Proposal status: | Just for Laughs (inactive) |
| Proposed by: | TrickyFoxy |
| Tagging: | amenity=shoefiti
|
| Applies to: |  
|
| Definition: | Shoes hanging from overhead wires or trees |
| Statistics: |
|
| Draft started: | 2026-04-01 |
| RFC start: | 2026-04-01 |
| Vote start: | 2026-04-01 |
| Vote end: | 2026-04-01 |
Problem Statement
This proposal is a logical continuation of the previously approved proposal for mapping line arrangements on wires, including clotheslines (see Proposal:Lines arrangements#Misc), which established a precedent for mapping objects and configurations associated with overhead lines.
In many urban and suburban environments worldwide, contributors encounter pairs (and occasionally single instances) of shoes tied together and suspended from overhead utility wires. Despite their presence and cultural significance, there is currently no established or widely accepted tagging scheme in OpenStreetMap for such features.
Proposal
This proposal introduces a new tag to represent shoes hanging from overhead wires:
Additional subtags are proposed to further describe the feature:
The feature should typically be mapped as a node located beneath the hanging shoes. In rare cases, may be mapped as a relation if spanning multiple wires (advanced mapping only)
Rationale
The key amenity=* is chosen due to the semi-permanent and publicly observable nature of the feature, similar to other small but notable objects in the urban environment. While the feature does not provide a service in the traditional sense, it contributes to the lived experience of a place and is often used informally as a landmark. Similar to amenity=bench
In some cases, prominent or long-standing shoefiti can also become a minor local attraction for visitors.
Tagging
amenity=shoefiti
A pair or group of shoes tied together and suspended from an overhead wire.
shoefiti:type=*
Specifies the type of shoefiti; currently only two widely recognised type: shoefiti:type=shoes_on_wire and shoefiti:type=shoes_on_tree
shoefiti:count=*
Number of shoe pairs observed. Example: shoefiti:count=3
Single shoes may be mapped with shoefiti:count=0.5
The special value shoefiti:count=many is also assumed when an exact number cannot be counted.
shoefiti:brand=*
Brand of the shoes, if identifiable from ground survey
Example: shoefiti:brand=Nike
Multiple brands can be listed using semicolon-separated values (e.g. shoefiti:brand=Nike;Adidas)
shoefiti:brand:wikidata=*
Wikidata identifier (QID) of the shoe brand, if it can be reliably identified
Example: shoefiti:brand:wikidata=Q483915 (for Nike)
shoefiti:height=*
Approximate height above ground (in metres)
Example: shoefiti:height=6.66
shoefiti:lace:length=*
Approximate lace length between the two shoes (in metres), if visible from ground survey
Example: shoefiti:lace:length=1.2
Potentially, this length could be calculated using the distance measuring tool in StreetComplete
Additional notes
Do not climb poles or wires to verify tagging details
Do not create shoefiti for the purpose of mapping
Examples
| Photo | Tagging |
|---|---|
|
amenity=shoefitishoefiti:type=shoes_on_wireshoefiti:count=1shoefiti:height=6.66
|
|
|
amenity=shoefitishoefiti:type=shoes_on_treeshoefiti:count=many
|
Impact on Data Consumers
This proposal introduces a new tag and does not modify or deprecate any existing tagging schemes.
Potential positive impacts include:
+ Renderers: Ability to display playful or thematic icons (e.g. dangling shoes or emoji 👟)
+ Navigation software: Enhanced, personality-rich directions
+ Data analysis tools: New datasets for urban studies and cultural mapping
+ Games and applications: Opportunities for location-based gameplay (e.g. shoefiti hunting)
+ Energy companies can track when shoefiti:count=* becomes too high and can take appropriate action.
Data consumers that do not recognise the tag will safely ignore it.
Rendering support is optional and can be implemented incrementally. Animated rendering (e.g. gentle swinging) is left to renderer discretion.
🤫 According to insider information, Shortbread 1.1 is ready to add support for this proposal after community approval, so that the OSM website will be the first in the world to demonstrate an animated vector map style!
External discussions
According to the new community rules, a discussion on the wiki is enough
Comments
Please comment on the discussion page.
Voting
- Log in to the wiki if you are not already logged in.
- Scroll back down and click "Edit source" next to the title "Voting". Copy and paste the appropriate code from this table on its own line at the bottom of the text area:
| To get this output | you type | Description |
|---|---|---|
|
{{vote|yes}} --~~~~
|
Feel free to also explain why you support the proposal! |
|
{{vote|no}} reason --~~~~
|
Replace reason with your reason(s) for voting no. |
|
{{vote|abstain}} comments --~~~~
|
If you don't want to vote yes or no but do have something to say. Replace comments with your comments. |
~~~~ automatically inserts your name and the current date.For more types of votes you can cast, see Template:Vote. See also how vote outcome is processed.
⚠️ Only participants who can throw a pair of boots five meters high on their first try are allowed to vote! Be sure to attach a photo!
I approve this proposal. --TrickyFoxy (talk) 00:40, 1 April 2026 (UTC)
I have comments but abstain from voting on this proposal. I don't have proof so I can't vote. Hope it passes! --pkoby (talk) 13:12, 1 April 2026 (UTC)
Hell yes I want this proposal right now. Here's a video of me creating shoefiti, as requested --LordGarySugar (talk) 15:24, 1 April 2026 (UTC)- I approve this proposal. Are there considerations for counterfeit brands? --O0235 (talk)
- There are some uses of
replica=yes(82 at the moment) for artworks, it could be extended to counterfeit shoes as well. --Ivanbranco (talk) 17:51, 1 April 2026 (UTC)
- There are some uses of
- I have comments but abstain from voting on this proposal. In the case of
shoefiti:count=0.5, how can we specify if it's a left or a right shoe? --Ivanbranco (talk) 17:45, 1 April 2026 (UTC) - I approve this proposal. --Democat (talk) 22:54, 1 April 2026 (UTC)