Proposal:Adopter
| The Feature Page for this approved proposal is located at Key:community_adopted |
| Adopter | |
|---|---|
| Proposal status: | Approved (active) |
| Proposed by: | Partytax |
| Tagging: | community_adopted=*, community_adopter=*, community_adopter:litter=*, community_adopter:landscaping=*, community_adopter:graffiti=* |
| Applies to: |  ,  ,  , 
|
| Definition: | Tagging for volunteer adoption of streets, highways, facilities, drains, etc. |
| Rendered as: | hidden |
| Draft started: | 2023-07-10 |
| RFC start: | 2023-08-08 |
| Vote start: | 2024-02-05 |
| Vote end: | 2024-03-04 |
Proposal
Adoption of streets, paths or places is a common practice in which an individual or organization takes volunteer responsibility for cleaning or minor maintenance of the facility. "Adopt-a-Street", "Adopt-a-Highway", and "Adopt-a-Spot" programs are common across the United States and Canada, and typically provide for signs to be erected with the name of the individual or organization in exchange for their service. "community_" is prepended to add clarity and preclude the tag from being interpreted as specifying ownership.
Rationale
While operator=* and maintainer=* express an official responsibility for maintenance of a road, path, or facility (repaving, construction, major landscaping, etc.), there is no way to express that the same is "adopted" by a volunteer for regular litter pickup or other specified maintenance activities. With the community_adopter=* tag and/or community_adopted=yes, mappers will be able to document where volunteers have taken responsibility for regular litter pickup or other specified maintenance activities, allowing data users to identify areas with poor volunteer coverage. It could also provide cities with a better inventory of their "Adopt-a-Street" signs, indicating where signs may exist, but volunteer work has ceased. To further specify the volunteer entity responsible for particular maintenance activities, community_adopter:litter=*, community_adopter:landscaping=*, and community_adopter:graffiti=* may be used.
Tagging
community_adopter=adopting entity name and/or community_adopted=yes should be tagged on the OSM object that has been adopted. If you wish to further specify what activities the adopting entity participates in, or if different entities participate in different adoption activities, use community_adopter:litter=adopting entity name, community_adopter:landscaping=adopting entity name, and/or community_adopter:graffiti=adopting entity name. In the case of ways, there are often signs at the beginning and end of the adopted section, but if it is not clear where an adopted segment ends, the way should only be tagged as adopted until the next intersection with another route.
Examples
| Tag | Description |
|---|---|
| community_adopted=yes | Street, path, or facility that has a sign indicated that it has been adopted, but the adopting organization or individual is not displayed on the sign. |
| community_adopter=Sigma Sigma Phi Fraternity;Springfield Kiwanis Club | Street with a sign indicating that the Sigma Sigma Phi Fraternity and the Springfield Kiwanis Club have adopted a section of street in some way |
| community_adopter:litter=Sigma Sigma Phi Fraternity | Street with a sign indicating that the Sigma Sigma Phi Fraternity has adopted the street for litter cleanup purposes |
| community_adopter:landscaping=Springfield Kiwanis Club | Street with a sign indicating that the Springfield Kiwanis Club has adopted the street for landscaping purposes |
Rendering
Not applicable, as it is a minor attribute and not a top-level tag.
Features/Pages affected
- MUTCD/I#I20: Acknowledgment Signs
- MUTCD/California/S#S32: Adopt-A-Highway
- MUTCD/Ohio/D#D14: Acknowledgement Signs
External discussions
https://osmus.slack.com/archives/C2VJAJCS0/p1688746418478219
https://community.openstreetmap.org/t/rfc-feature-proposal-adopter/102257
Comments
Please comment on the discussion page.
Voting
Voting on this proposal has been closed.
The result is approved
I approve this proposal. --Minh Nguyễn 💬 23:43, 5 February 2024 (UTC)- I approve this proposal. --Fortera (talk) 00:00, 6 February 2024 (UTC)
- I approve this proposal. --Pi11 (talk) 03:47, 6 February 2024 (UTC)
- I approve this proposal. --Watmildon (talk) 19:57, 6 February 2024 (UTC)
- I approve this proposal. --EneaSuper (talk) 17:49, 11 February 2024 (UTC)
- I approve this proposal. --Team mazungu (talk) 12:23, 17 February 2024 (UTC)
- I approve this proposal. --Partytax (talk) 16:23, 26 February 2024 (UTC)
- I approve this proposal. --Fortera (talk) 08:33, 4 March 2024 (UTC)
- I approve this proposal. --Timonade (talk) 14:34, 4 March 2024 (UTC)
- I approve this proposal. -- Something B (talk) 21:20, 4 March 2024 (UTC) with 9 votes for, 0 votes against and 0 abstentions.
The content of this proposal has been archived to avoid confusion with the current version of the documentation.