On some parking lots, you do not have to pay e.g. for motorcycles (only for cars and buses). There should be a value to define that, e.g. fee=motorcar. --Plasmon 12:22, 27 September 2009 (UTC)
There should also be something to say how much different vehicles pay.I suggest: fee:car=x fee:bike=y fee:lorry=z
This is very important for toll roads and such, and would also work for the first comment in 2009.--www.usergenerateddesign.com 12:16, 4 May 2011 (BST)
How do I indicate the timelimits for paying a parking fee? E.g.: One has to pay only on working days from 7:00 to 19:00 hrs. --ALE! 15:23, 3 January 2010 (UTC)
- Some use fee:times=Mo-Fr 07:00-19:00. There could be other keys that others use to record the times, but the value format is still described at Key:opening_hours. No software uses the data, yet, so they can be later converted to a common key, if necessary. Alv 15:35, 3 January 2010 (UTC)
Amount of the fee
- It's bad database design to use 2 redundant database fields for 1 chunk of information. fee=no means the same as fee:amount=0, and fee=yes corresponds to a non-zero amount. Wherever there are redundant data fields, inconsistencies arise sooner or later. E.g. fee=no + fee:amount=10$, or fee=yes + fee:amount=0. Therefore, I think that fee=<number>[optional whitespace]<currency> should be permitted as a value. But everything more complicated should go into description=*, because applications cannot parse data with an undefined syntax, and due to its yes/no values, fee=* can not even be treated as a free text tag whose contents could be displayed to end users as is. Of course, it may make sense to introduce specialized tags such as hourly_fee=* or charge:child=*, or some tag with an eleborated and exactly defined syntax similar to Conditional restrictions. --Fkv (talk) 10:47, 25 May 2017 (UTC)
Please do not use other values than yes/no
For the parking map, I evaluate whether a parking lot is paid or free using the fee=*. However, I am unable to decide if there are other values than yes/no in the database. Here are some values I found:
- 1,50 €/h
- How to tag that fee is charged after first 15 minutes? fee:except=15min? -- Joosep-Georg 20:52, 3 January 2013 (UTC)
- Or fee:except:first=15min, adding possibility to use it in combination with fee:except=Sa-Su and fee:times=* proposed above? -- Joosep-Georg 20:58, 3 January 2013 (UTC)
- I'd proposed using fee=yes (generally a fee is changed, except) + fee:conditional=[[Tag:fee:conditional=no @ (maxstay<3 hours)|no @ (maxstay<3 hours)]]. This is more in line with how Conditional restrictions work generally. However I admit it becomes problematic when you combine this with a time conditional fee, since you'd need two `fee:conditional` keys. Aharvey (talk) 02:30, 11 February 2020 (UTC)
Free or lower fee for disabled persons and their helpers
I would like to use:
- fee:disabled=* for different fees for disabled persons
- fee:disabled_assistant=* for different fees for disabled persons' companions
Toll/fee tagging details
The details of tagging tolls and fees don't seem to be completely documented. I tagged the 4 toll entrances to Monterey Peninsula (Pebble Beach / 17 Mile Drive area) today as follows:
- The toll booth has one of barrier:forward=toll_booth, barrier:backward=toll_booth or barrier=toll_booth depending on the direction of the way and whether the in/out roadways are separated or not. Example: 89985692.
- The toll booth also has fee:automobile=$10 because it costs USD 10 per car for the general public to drive into the area. (I failed to ask about truck/bus/motorcycle/bicycle/pedestrian/horse tolls.)
- The roadway just inside the toll booth has toll=yes. When the roadways are separated, the entire one-way section through the toll booth has toll=yes. Example: 10474842.
- Is this the proper usage of toll=* and fee=* tags?
- Should all the roadways inside the toll area be tagged with toll=yes?
- automobile is not OSM (it is American English vs British English). Use fee:motorcar=10, fee:cur=usd Warin61 (talk) 09:01, 23 December 2018 (UTC)
- i will also use this, but the current tag description is very limiting, it uses the same key for yes/no/hours. what if a place has a fee for some hours, and is voluntary for the rest of the time ? --Richlv (talk) 11:13, 28 October 2017 (UTC)
Pls don't use any symbols, it's absolutely unparsable. Use ISO codes (as usd, eur, czk ... etc. https://cs.wikipedia.org/wiki/Seznam_m%C4%9Bn ) And, maybe better, if you declare currency with one tag - say fee:cur = usd, and use nums only in prices
- Actually you shouldn't be using either. fee=* just says if there is a fee or not, not how much the fee is. The latter is what charge=* is for. Aharvey (talk) 02:33, 11 February 2020 (UTC)
Normally, in museums, admission is paid 'except for a few days'. For example : Free on Wednesdays; Free from 18:30, Free on the first Sunday of each month. This use is very complicated to 'see' the free days or timetables. My question : how should I use this tag?
See this case:
- opening_hours: Tu-Fr 11:00-20:00; Sa-Su 10:00-20:00
- fee: We-Fr 11:00-18:45; Sa-Su 10:00-18:45
Thank you for your comments !
- Also, Fees may vary depending on whether the visitor is a member or non-member. For that matter, museums and non-museums might offer discounts for children, seniors, or others. Jogger2 (talk) 20:30, 21 July 2019 (UTC)
I have arrived at the conclusion that the details of the fee tag are NOT applicable to museums. Many possibilities make its use liable to confusion. I would ONLY recommend the use Yes/No. Just that. A similar problem for the tag [opening_hours] --Martingggg (talk) 13:09, 22 July 2019 (UTC)
- " details of the fee tag are NOT applicable to museums" - why? I used fee:conditional in some cases to tag free days - see form example https://www.openstreetmap.org/node/472125058 fee=yes + fee:conditional=no @ Monday Mateusz Konieczny (talk) 20:26, 28 July 2019 (UTC)
- In my opinion, the use of tag fee exceeds OSM as an application for spatial data. On the other hand, the complexity of its application only makes sense to use yes/no/conditional(?).
For example, some museums offer free admission one hour before closing, others one Sunday a month, many have differentiated rates by nationality, age and many museums change schedules throughout the year.
This shows that OSM is not the right platform for this kind of maneuvers in a sustainable way.
Also, the complexity of the syntax means that museum staff do not have access to these types of editions.
If we are to use a tag fee, it must be readable by everyone, not by a few connoisseurs.
I repeat: I discourage spending calories on this item. In my case, that I publish 1000 museums in Argentina, I will stop doing it.
In exchange for this, I believe if entry in Wikidata and Wikipedia if it exists. Look at this Leaflet map that we have made and you will understand what I mean: https://mapas.museosabiertos.org/museos/caba/ --Martingggg (talk) 21:30, 28 July 2019 (UTC)
- PS: Certainly, the use of the conditional tag is right, but it would only go so far [yes/no/conditional].