Creating a proposal
From OpenStreetMap
If you have any suggestions, problems or otherwise with this page, please discuss them on the talk page
This page is designed to assist anyone considering putting forward a tag proposal, with the aim of speeding the tag proposing process. It is not meant as a set of absolute rules, but as a guide. OSM was created out of a desire to change things, to break the status quo; this principal should be kept in mind when creating tags as well.
Contents |
Before creating a proposal
Existing tags/proposals
- Does your proposed tag already exist? check the Map features page
- Is it already a proposal in progress? check the Proposed features page
- Has it been proposed before and rejected? check the Rejected features page
- being a rejected feature does not necessarily mean it should not be proposed again: some proposals fail due to a poor definition, being ambiguous or lacking information to justify their significance, some items become more significant over time and thus more map-worthy
- Is there any other work not referenced on these pages? perform a general search on the wiki, including related words
e.g.
- you want a tag for a 'racecourse' - consider searching for 'racing', 'horse', etc.
- you want a tag for a 'peninsula' - consider searching for 'headland', 'point', etc.
- you want a tag for a 'brewery' - consider searching for 'beer', 'manufacturing', 'alcohol', 'industrial', 'plant', 'works'
Significance
Is the tag you are considering for proposal, worthy of a new tag? Consider possible uses for the map, and specifically the data you want to add
This is a difficult judgement to make: if you want to tag it, then that is generally reason enough to create a tag
- Is it a destination in itself?
- people may search for some locations, for example: a national park, a bus station, a street address or a rubbish dump, because they want to visit that location.
- How many of the item do you think there will be in the world?
- for instance, you want to map an aero-engine factory - there are very few aero-engine factories in the world, so rather than creating a specific tag, this may be better served by using an existing man_made tag and specifying type=aero_engines
- How large is the item?
- large items can assist with navigation
- is it useful for research/study?
- a geography student may want to determine the total area of national parks in a given region
- a sociology student may want to map correlation between number/location of Porsche dealerships and houses greater than 600m^2 in area
- a history student may want to show the locations of all battles in a given war
- does it assist in route-planning?
- it is useful to know which junctions are traffic lights and which are roundabouts as this can affect journey times
- truck drivers need to know the maximum height allowed under bridges, or the maximum weight allowed through population centres
- traffic calming structures can affect journey times, routing software will generally not use roads with these on
- walkers would want to know surfaces/conditions of walking tracks
Creating a proposal page
Proposal Page Template
{{Proposal_Page|user=*|name=*|
key=*|value=*|type=*|definition=*|appearance=*|
status=*|proposalDate=*|rfcStartDate=*|voteStartDate=*|voteEndDate=*}}
Page details
In general: be verbose. The more information you can include, the better. Photos, descriptions, situations, examples. Anything to create a well-defined image in people's mind.
More specifically: this list is a starting point for items you may want to consider putting in your proposal:
- Proposal - a short description of what you want to map, including links to relevant material with photos if possible
- Rationale - why the tag is needed, considering significance and potential uses of the data
- Examples - names, locations, rough idea of numbers (e.g. one on every street corner, several in each suburb in Germany, half a dozen in each South American country)
- Tagging
- the category the tag falls under (man_made, waterway, tourism, etc,), with a justification of why other similar categories are not suitable (for instance, there may be too many to map individually - such as residential properties in which case a landuse tag would be of more use if they are grouped closely enough?)
- the name of the tag itself - keep it as short as possible (15 characters is generally as long as they get), whilst still being logical, descriptive enough to need little explanation and not overlapping with another tag in a different category
- other significant tags to describe specific instances of the item (e.g. author for a work of art, contents for a pipeline, etc.)
- generic tags that are re-used extensively (e.g. name, operator, access, etc.)
- Applies to: nodes, ways or areas; when considering nodes vs. areas: generally, if an item is smaller than 5m by 5m, it would not be mapped as an area, but as a node.
- Rendering - not a part of the proposals process as such, but hints for the renderer maintainer will help them out. maybe a description of an icon, or an example mock-up
- Comments - there must be a time set aside for other people to comment on the proposal, do not go straight to a vote
Don't forget to add a link to your new proposal on the Proposed features page. Let people know of your new proposal by sending a mail to the talk mailing list.
