Proposal:Service:vehicle namespace
| service:vehicle namespace | |
|---|---|
| Proposal status: | Draft (under way) |
| Proposed by: | Tyr |
| Tagging: | service:vehicle:*=yes/no |
| Applies to: | node, area |
| Definition: | Detailed description of the services offered at car repair shops and similar businesses. |
| Statistics: |
|
| Draft started: | 2022-09-13 |
Proposal
Currently, two different ways to map the details of shop=car, shop=car_repair and similar businesses: The "traditional" way (supported in JOSM for example) is using a semicolon based approach and the service key. In 2018, iD introduced a secondary way to map the same information using a subkey based approach using the service:vehicle:* namespace.
This proposal intends to deprecate the traditional "service key" approach in favor of the "service:vehicle namespace" method, because this approach has several benefits which are listed below.
Rationale
For context: The introduction of the service:vehicle namespace in iD did not go through the regular tagging proposal process (thus rightfully causing a controversy). It was originally discussed in github issues, for example #3535.
The benefits of the new way to tag the services in this way are manifold:
- It avoids the overloading of the service=* key, which is already used as a subkey for highway=service, railway=* or type=route features. This overloading has the downside that tools like Taginfo cannot offer precise statistics about the individual usage of the tag in each context as well as not provide value suggestions or be used in autocomplete in form fields.
- The semicolon based approach has no way to indicate that a service is not provided by a specific business. For example, the value service=repair does leave it undecided whether the car shop does also provide further services such as tyre change, etc.
- Using the subkey method, it is possible to indicate that specific services are not offered, by using "no" as a value. For example: service:vehicle:repair=no
- The existing approved tagging schema for services of bicycle shops (service:bicycle) is successfully using the subkey based approach. This would harmonize the way services of the relatively similar features of bike can car shops are mapped.
Tagging
The following table shows possible subkeys to be used in the service:vehicle namespace: Should a new key be needed, it should be added to the table with a clear and concise description. All keys should only use yes/no values.
| key | possible values | description |
|---|---|---|
| service:vehicle:new_car_sales=* | yes/no | New cars are sold |
| service:vehicle:used_car_sales=* | yes/no | Used cars are sold |
| service:vehicle:car_repair=* | yes/no | Cars are repaired |
| service:vehicle:tyres=* | yes/no | Tyre services are offered |
| service:vehicle:car_parts=* | yes/no | Spare parts are sold |
| service:vehicle:oil_change=* | yes/no | Combustion engine oil changes are performed |
See also the list of currently used subkeys on taginfo.
If a car (repair) shop is not tagged with a key from the above list, it means that its status is unknown: for instance, if a shop does not have a service:vehicle:car_repair tag, nothing can be assumed about its repair service.
Examples
- A car dealer which only sells new cars but doesn't repair them:
shop=car service:vehicle:new_car_sales=yes service:vehicle:used_car_sales=no service:vehicle:repair=no
- A car repair shop which also sells used cars:
shop=car_repair service:vehicle:new_car_sales=no service:vehicle:used_car_sales=yes service:vehicle:repair=yes
- A shop specialized in selling and servicing tyres
shop=tyres service:vehicle:new_car_sales=no service:vehicle:used_car_sales=no service:vehicle:repair=no service:vehicle:tyres=yes
Rendering
N/A
Features/Pages affected
These tags can be used for any businesses which deal with vehicles and their repair, except for bicycle shops where a dedicated tag to map their services exists (service:bicycle). The applicable features for the service:vehicle tag include:
Motorcycle features might also be affected:
The section on the page for the service key would need to be reworded.
External discussions
- https://github.com/openstreetmap/id-tagging-schema/issues/556
- Talk:ID/Controversial Decisions#4th format for vehicle services "introduced"
- https://github.com/openstreetmap/iD/issues/3535
Comments
Please comment on the discussion page.