From OpenStreetMap Wiki
Jump to navigation Jump to search

I think we should recommend to use the three letter ISO 4217 standard currency codes ( instead of the one unicode characters. So $ should be USD, € should be EUR, etc. Many currencies don't have character symbols at all.

Also we should expect to have a space between the amount and the currency code.

Amount should be used in US format, so using . (full stop) as the decimal mark to separate the integer and fractional parts.
Apostrophe ' would be optional to separate thousands.

So the examples would look like:
charge=May - October Mo - Sa 8:00 - 16:00 1.5 EUR/2h
charge=16 USD/hgv; 8 USD/motorhome; 6 USD/motorcar
charge=4 USD/person/day; 12 USD/person/week; 0 USD/child < 14years
charge=1'000 USD/day
charge=10.25 EUR/adult


Agree. Please add your signature in future. --MeastroGlanz (talk) 11:34, 1 August 2017 (UTC)
Am I allowed to change the wiki page according to this or should I wait for confirmations from others? --AndrasFuchs (talk) 06:28, 2 August 2017 (UTC)
I agree with three letter currency codes.
I think the currency code should be before the amount, as that is the custom in BrE (which is OSM convention) and apparently widely used
If we're following conventions, might as well follow SI convention: dot for decimal separator (because BrE) and space for thousands.
Finally, I think subkeys would be more appropriate for certain types of fees, something like a specific format for toll booths (in response to charge=16 USD/hgv; 8 USD/motorhome; 6 USD/motorcar)
--Tqdv (talk) 09:52, 7 January 2018 (UTC)
I agree with three letters (just because $ is used not only for USD), agree with "." (it used anywhere), and totally disagree with apostrophe (looks as feet) - don't do unnecessary formatting. And I have no idea what for is the space between the amount and letters (and some other spaces). Format of period is described in opening_hours=*: May-Oct Mo-Sa 08:00-16:00 VlIvYur (talk) 21:58, 20 March 2019 (UTC)

Conditional restrictions

Now that Conditional restrictions exist and are widely used for other keys already, time-based price differences should probably be expressed using that syntax rather the one suggested in "Proposed advanced usage". That is, the older example would use like this instead:

 charge:conditional = 1.5€/2h @ (May-Oct: Mo-Sa 08:00-16:00)

--Tordanik 20:34, 29 August 2019 (UTC)