From OpenStreetMap Wiki
Jump to: navigation, search

New values

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 12:16, 4 May 2011 (BST)

time limits

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

The actual fee (amount of money) should be given in an extra field, e.g. fee:amount=$1/h instead of misusing the key. Kay D 15:31, 19 September 2011 (BST)

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
  • free
  • customers

I tend to say "everything except fee=no is paid", but that's probably too coarse.

I have not found instances of a time interval (as given in the proposal) within the first 50 lines of taginfo Kay D 15:31, 19 September 2011 (BST)

Variable fees

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)
  • How to tag $2 per hour with $5 max? Fbax (talk) 15:20, 13 July 2016 (UTC)

Free or lower fee for disabled persons and their helpers

I would like to use:

Any comments? --Lulu-Ann (talk) 09:52, 20 September 2013 (UTC)

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.


  1. Is this the proper usage of toll=* and fee=* tags?
  2. Should all the roadways inside the toll area be tagged with toll=yes?

-- T99 (talk) 08:36, 21 April 2014 (UTC)


I've used fee=voluntary where they ask for a donation for entry, but it isn't required. --Aharvey (talk) 08:45, 27 January 2015 (UTC)

Currency symbols

Pls don't use any symbols, it's absolutely unparsable. Use ISO codes (as usd, eur, czk ... etc. ) And, maybe better, if you declare currency with one tag - say fee:cur = usd, and use nums only in prices

--Jezevec (talk) 21:13, 2 May 2017 (UTC)