Proposal:Car
see Tag:shop=car for approved implementation
With the help of ULFL, the former proposals Proposed_features/car_dealership and Proposed_features/auto_repair_shop have been merged into one new proposal with a lot of additional stuff.
Rationale
Most satellite navigation systems already include information on car dealers and repair shops in their data. This is especially useful if you experience problems with your car while on the road.
Description
This proposal adds a new shop tag value called "car" (and related vehicles - even bicycles) to the world of OSM. Optional, but recommended tags include name=*, brand=* and others.
While working out the current proposal, it was becoming more and more obvious that the required "subtags" would not be limited to cars, but also be suitable for motorcycles, bicycles and other kind of vehicles.
Tags
Tags apply to nodes and areas.
| Tag | Description |
|---|---|
| shop=car shop=car_repair |
selling (and/or repairing) cars, motorcycles, tyres, parts etc. |
| name=<text> | name of the shop |
| brand=<text> | comma separated list of brands which are sold or repaired |
| type=<text> | comma separated list of vehicles "affected", e.g. car, motorcycle, lorry, bus, utility_vehicle, construction_vehicle, farm_machine, ... |
| sale=yes/used_only/no | sells new and/or used vehicles? "yes" implies new and used |
| parts=all/brand/<text>/no | range of spare parts on customer sale - might be limited to brand, e.g. tyres, brakes, exhaust, ... |
| repair=all/brand/<text/no | range of repair services - might be limited to brand, e.g. tyres, brakes, exhaust, ... |
Interestingly, the set of properties (from name to repair) also seem to apply to all vehicles like motorcycles, bicycles, ... :-)
There are car dealers also doing repairs and car repairers also selling some cars "left over from repairs" - you may choose their "main business" for shop=xy.
Rendering
- shop=car: car
- shop=car_repair: car + wrench
- shop=car_parts: car + "plus"
- shop=motorcycle: motorcycle
- shop=motorcycle_repair: motorcycle + wrench
- shop=tyres: stack of tyres
- ...
Example
|
common car "brand dealer" |
shop=car |
|
small used car dealer |
|
|
small "all purpose" car repair |
|
|
specialised car repair (only standard repairs) with parts shop |
shop=car_repair |
|
tyre shop |
|
|
motorcycle "brand dealer" |
shop=motorcycle |
|
shop only selling spare parts |
Opinion
- Thumbs up from me! MikeCollinson 08:29, 4 December 2007 (UTC)
- I would comment that comma-separation is not a general convention within OSM. In cases where multiple values are required, semicolons have been used previously. Gravitystorm 10:06, 4 December 2007 (UTC)
- Actually, there is a problem with semicolons in tags, see [1], [2], [3], [4] --Wabba 10:38, 4 December 2007 (UTC)
- Actually, no there isn't anymore. This was an issue before API 0.5. We are now at API 0.6. Semicolon is kosher to separate multiple values in a tag. --Gorm 09:51, 17 April 2010 (UTC)
- While that issue with database storage doesn't exist anymore, none of the current tools still don't support parsing a semicolon separated list; only those where a full text search makes sense can find all the combinations. It's still good to enter the data in any comprehensible format, though. Alv 12:23, 17 April 2010 (UTC)
- Actually, no there isn't anymore. This was an issue before API 0.5. We are now at API 0.6. Semicolon is kosher to separate multiple values in a tag. --Gorm 09:51, 17 April 2010 (UTC)
- Actually, there is a problem with semicolons in tags, see [1], [2], [3], [4] --Wabba 10:38, 4 December 2007 (UTC)
These tags should definitely be namespaced. (i.e. shop:car_repair:type=car/motorcycle/farm, shop:car_repair:brand=Mercedez, etc.) a tag of "type" is far far far too generic, and a tag of "repair" is meaningless without a namespace. --Hawke 09:32, 15 December 2007 (UTC)
...regardless of the namespace debate, these tag names are really a mess, and only make sense if they're all applied to the item in question. --Hawke 04:06, 21 December 2007 (UTC)
The car 'symbol' noted is way too complex for use on a map. There are several decent icon sets available that would work much better. --Cohort
- Wouldn't it be nicer to use the actual company logos for those companies that allow it? --N3S 17:13, 5 February 2009 (UTC)
What about the type of small shop that does paint, brake pads, oil, body panels, but has nothing to do with actual vehicles? These are common in UK at least, and don't fit this - I agree with Hawke that this is a mess as it stands; shop=car_dealer, shop=motorspares, shop=motorcycle are all catered for in map-features already, so what's needed is a tag to clarify services available. I don't agree with Hawke that generic tags eg type are bad; obviously, the context is derived from the other tags associated, so a vague tag can be used in many different ways, but won't be used unless the renderer (or whatever) has picked up something else first. --DrMark 08:30, 21 December 2007 (UTC)
- Mark.66: The problem as I see it is that there could be multiple keys which might want to have some additional information inferred from, say, "type"; if they're both applied to the same place the type tag will conflict. Further, any application of that data would need to know about each specific usage of "type" anyway, so there's no benefit in using a generic key. --Hawke 13:17, 21 December 2007 (UTC)
- Vehicle inspection services could be added here too. --Onion 16:55, 18 May 2008 (UTC)
- -1 for the comma separated list. Better use brand=foo brand=bar brand=spam (see Proposed_features/Value_separator). Makes it easier to search for a specific brand (navigation systems are not super computers :)). --Bkr 20:30, 3 June 2008 (UTC)
- I like the feature 'tyres', because some countries have very bad road conditions --MatMac 01:54, 15 July 2008 (UTC)
Some used car shops also buys vehicles, this can also be brand limited, or it can be general, so I suggest a tag buy=yes/brand/exchange/no where no is assumed default value, brand can indicate only brands listed in the list of brands, and exchange indicate that it only will buy your old car if you buy a car from them. --Skippern 17:46, 5 February 2009 (UTC)
Merge with other trade services
See Proposed_features/Service_business --Phobie 16:44, 6 September 2008 (UTC)
How to parse that?
You should always think about on how route-planners and renderer can parse these values! This proposal is like writing amenity=china_restaurant. This would result into to many values, think about shop=car_window_repair and shop=car_painting. "shop" should only contain a generic description like "vehicle", "food" or "alcohol" and further descriptions should go into other tags! I think vending- and repair-services should be separated! --Phobie 16:44, 6 September 2008 (UTC)
Alternate Proposal
I changed the example shown above after a short brainstorming --Phobie 16:44, 6 September 2008 (UTC)