Talk:Key:maxstay

Maxstay 10 minutes with Emergency Lights

In front of many farmacies in Brazil there are a special zone marked with "Maximum stay 10 minutes with emergency lights flashing, only for customers of the farmacy <name>. According to municipal law of xxxxxxx". How should this be tagged? --Skippern 14:42, 28 December 2009 (UTC)

IMHO Simply as maxstay=10 minutes maybe together with access=permissive. Nothing/nobody looking for a real parking place is going to be interested in something with that short a duration. Furthermore people (end users) are equiped with eyes and brains to figure out the rest. --Cartinus 13:13, 29 December 2009 (UTC)

Format of value

Wouldn't it be better with a more machine readable value of maxstay than f.ex '3 hours'. How about using 00:30 for 30 minutes and so on? (Similar to duration=*) --Gorm 17:19, 15 June 2012 (BST)

This is the ISO 8601 ;-) --Pyrog (talk) 06:37, 28 November 2014 (UTC)

Time value of "maxstay"

While I am checking Tagwatch (for Germany), I've found 52 different kinds of given time values, which are used to describe the Time of legal parking. I think this is a big problem if you want to use this Information for routings or things like this. Maybe it could be better to specify the time of maxstay by defining the time in hours.

For example

1. You're allowed to park for one hour: maxstay=1
2. It's allowed to park for 15 minutes: maxstay=0.25

I know that using hours to define the value, needs to recalculate minutes or day values in a hour value, but it makes it simpe to use maxstay and hopefully we haven't furthermore 52 different kinds of time values. Also you have to think about, that parking permissions for some days, are the exeption. Maybe at an Airport you have "Holliday parking" for 5 days and that are only 120 hours (maxstay=120).

While some standardization would be in order, I think that explicitly stating the unit (and allowing different units) is not a problem. It's not different from other values like speed (which can be given in km/h or mph), distances (km, m, foot/inches) and so on. As long as we agree on a set of acceptable units, it's not hard for software to do the conversion. --Tordanik 14:45, 3 May 2014 (UTC)

For what it's worth, there is an ISO standard for time durations which would remove all ambiguity and settle the issue that way (since after all, the entire world only does use one standard set of time intervals), at http://en.wikipedia.org/wiki/ISO_8601#Durations . The software would have to do conversion, but it would only have to convert exactly one standard string type. Skybunny (talk) 23:46, 8 July 2014 (UTC)

+1 --Pyrog (talk) 06:37, 28 November 2014 (UTC)

+1 for using ISO 8601.--Stemby (talk) 01:22, 27 February 2016 (UTC)

Tordanik proposed to use just one unit (hours) to avoid recalculations when the data is used. Changing the representation to ISO 8601 doesn't address his issue as also ISO 8601 allows different representations of the same duration (e.g. PT2H, PT120M, etc.). Instead, to address Tordanik's issue, unlike Tordanik I would not require users to use a specific unit when tagging a duration but rather recommend that OSM data users recalculate all 'maxstay' values once before usage, e.g. as part of the process when original data from the OSM database is filtered and compressed to the data base file that is later used by the router. --Biff (talk) 00:13, 3 June 2016 (UTC)

Disc parking

Hi, how to map disc parkings? For example, maxstay=1 hour but only from 08:00 to 18:00, and after free parking?--Stemby (talk) 10:22, 31 December 2015 (UTC)

I suggest to use 'Time and date' condition in Conditional_restrictions#Condition

maxstay=1 @ (08:00-18:00)

--Pyrog (talk) 15:21, 4 January 2016 (UTC)

Wouldn't that then be maxstay:conditional=1hr @ (08:00-18:00)? Aharvey --(talk) 23:52, 13 December 2019 (UTC)

Yep, the :conditional is needed. Probably should be "1 hour", though, looking at the examples on this page. So we end up with maxstay:conditional=1 hour @ (08:00-18:00). --Tordanik 22:14, 19 December 2019 (UTC)

Ok I've updated the main page. --Aharvey (talk) 22:49, 19 December 2019 (UTC)

Infinite Max Stay?

To default out of maxstay time limits (the standard restriction in Australia that needs defaulting)

parking:condition:left:maxstay:default = ???

I propose parking:condition:left:maxstay:default = none

Samuelrussell (talk) 23:44, 1 April 2016 (UTC)

Default unit

This page provides no explicit default unit for the value of this tag. The discussion appears to indicate that the default unit should be 'hours'. However, the German page defines that the default unit is 'minutes'. Taginfo shows that both units have apparently been assumed to be the default (values such as 1 and 240 appear there and I suppose this means 1 'hours' and 240 'minutes' but that's just an assumption). To resolve this issue , I would recommend to explicitly state (both here and on the German page) that no default unit exists and that the unit always needs to be provided. --Biff (talk) 00:36, 3 June 2016 (UTC)

 Support. Sounds reasonable! --Marsupium (talk) 01:02, 18 June 2018 (UTC)

kiss & ride

example, more at Commons

There are some short terms parkings, often called "kiss & ride". Sometimes time limit is explicitly specified, but often it is not. How tagging that would work well? Guess reasonable value (maxstay=4 minutes)? maxstay=kiss&ride? Mateusz Konieczny (talk) 10:35, 19 July 2019 (UTC)

maxstay in restaurants

I would like to suggest the use of this tag in restaurants which have a visible maxstay value and add that possibility to the wiki. --AntMadeira (talk) 14:24, 13 July 2024 (UTC)

No return

Lots of roadside or surface parking in the UK has stipulations like "No return within 3 hours". Is there any way people have chosen to map this?

There are some *no_return=* . But I suggest considering something more general and not in negative form, eg maxvisit=* that can be used for other purposes. It will fit nicely along maxstay=* . This can handle a limit on total number of uses on top of the no-return restriction.
So yours could be eg maxvisit=1 stay/(end+3 hours) (the unit can be discussed), following charge=* format. Or it can even be folded into maxstay=* to be maxstay=15 minutes/(end+3 hours) .
Specifying maxvisit=1 stay/(start+* hours) and maxvisit=1 stay/(end+* hours) would be clearer. This reserves maxvisit=1 stay/1 day for the calendar day.
—— Kovposch (talk) 07:48, 13 September 2024 (UTC)

Maxstay for EV chargers

Some EV chargers define their maximum stay in time (and thus perfectly fits this tag), however some will define their maximum time in state of charge percentage. The common value for this is 80% because due to significant charge curves, anything over 80% takes significantly longer than in the "sweet spot" of 10-80%. To cut down on people taking up a charger when there is a high demand (or a line), some stations will stop your charge at a percent and start charging hefty idle fees to get throughput higher.

Would it be fair to tag this example as maxstay=80 percent? `percent` isn't a time value, especially since all EVs charge at different rates and have different charge curves, but it seems like this belongs more in maxstay=* than ATYL something like maxcharge=*. Thoughts? --GA Kevin (talk) 00:05, 15 June 2025 (UTC)

Notice maxcharge=* is already for max charge=*
As you said, charger further simply incurs higher prices, not that you are prohibited to stay longer, or have the parking fees reset to short-term parking again. Then it should be charge=* , not maxstay=* . charge=* already allows different units. Eg charge=1 USD/80% charging;2 USD /100% charging . In theory, charge=* would be what's used at amenity=fuel or vending=fuel if the fuel price doesn't fluctuate.
—— Kovposch (talk) 08:56, 15 June 2025 (UTC)

That’s a fair point, but there is no way to charge to 100% at these stations, they cut you off and start charging idle fees to get you to move your vehicle because it’s no longer accepted to be there (these are restriction charging only spaces) and charging you high idle fees is better than paying a tow truck so the spirit and idea is “the maximum you can charge here is 80%, then you’re expected to leave.” which to me fits more with max stay vs charge. - GA Kevin (talk) 12:15, 15 June 2025 (UTC)

Oh sorry, I didn't read closely. But maxstay=* alone would yet not express idle fees higher than initial charging fees, unlike its meaning in parking. Eg charge=1 USD; 2 USD/80% charged / charge=1 USD/80% charging; 2 USD/idle etc could still be considered.
—— Kovposch (talk) 08:35, 16 June 2025 (UTC)

I think GA Kevin we shouldn't use maxstay=* for EV charging. maxstay seems to be based in time units. It doesn't seem a great fit for this so I wouldn't mess with this tag. Keep it for time based stays. Even maxcharge=* and charge=* doesn't look good either as that is price based.

I think this is so unique we should have a new tag completely for this specific EV charging tag. Let's move the chat to some of the charging_station talk pages about this. The whole tag could get complex with some of the Tesla ones (and more than the EA stations) that are 80% only but only 50% of stalls are busy which makes it even more complex to tag. Rovastar

I suppose the question is from maxstay=load-unload , but it might be possible to have both a time and charging limit, making you start charging then leave after disconnecting faster. *charging=* has been used in capacity:charging=* and service:bicycle:charging=* , for a maxcharging=* here.
—— Kovposch (talk) 08:40, 16 June 2025 (UTC)